none
CE7/CE2013: "; @XIPREGION" block variables definition RRS feed

  • Question

  • Hi folks,

      there is a common part for CE7/CE2013 for touch screen components -

    ; @XIPREGION IF TOUCH_COMPONENTS
        tchproxy.dll    $(_FLATRELEASEDIR)\tchproxy.dll            NK SHK
        tchcaldll.dll   $(_FLATRELEASEDIR)\tchcaldll.dll           NK SHK
    ; @XIPREGION ENDIF TOUCH_COMPONENTS

    I'm familiar with "; @CESYSGEN" block variables, but can't recognize where is makefile for "; @XIPREGION" blocks ?

    BTW, what/when does define TOUCH_COMPONENTS variable at all?

    Thanks in advance, Igor

    Tuesday, July 5, 2016 10:48 AM

Answers

  • No, it is not the same.

    ;@CESYSGEN IF only includes components inside that block if the corresponding SYSGEN variable has been set.

    ;@XIPREGION only tells romimage builder that if TOUCH_COMPONENTS are included, they can be placed in an XIP region.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, July 21, 2016 8:59 AM
    Moderator

All replies

  • Hi Igor,

    XIP is Execute in Place memory. Ti has a wiki for setting it up on their boards at http://processors.wiki.ti.com/index.php/Supporting_Multiple_XIP_Regions_in_WinCE_BSP but you may want to reach out to your OEM/Silicon Vendor as to why it is configured this way on your board support package.

    Sincerely,

    IoTGirl

    Tuesday, July 12, 2016 5:13 AM
    Moderator
  • Hi IoTGirl,

     I'm talking about COMMON.REG file from WINCExxx\PUBLIC\Common\Oak\Files folder. Thus, "OEM/Silicon Vendor" is Microsoft  ;)

    Best regards, Igor

    Friday, July 15, 2016 6:11 AM
  • Hi iShust,

    I believe this means that :

    TOUCH_COMPONENTS are tchproxy.dll & tchcaldll.dll and if they are included they should be placed in XIP memory. 

    Sincerely,

    IoTGirl



    Friday, July 15, 2016 4:25 PM
    Moderator
  • Hi IoTGirl,

    it's obviously there isn't XIP on x86 platforms.
    I just want to make sure if block "; @XIPREGION IF TOUCH_COMPONENTS" is the same as "; @CESYSGEN IF CE_MODULES_TOUCH" and Microsoft use it within common.bib file?

    Best regards, Igor


    Thursday, July 21, 2016 7:48 AM
  • No, it is not the same.

    ;@CESYSGEN IF only includes components inside that block if the corresponding SYSGEN variable has been set.

    ;@XIPREGION only tells romimage builder that if TOUCH_COMPONENTS are included, they can be placed in an XIP region.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, July 21, 2016 8:59 AM
    Moderator
  • Hi Michel,

    the root question - where TOUCH_COMPONENTS is defined?

    "WINCE700\public\COMMON\cesysgen\makefile" generates CE_MODULES_TOUCH variable for @CESYSGEN section. But who does make variables for @XIPREGION ???



    for reference, original common.bib - 

    ; @CESYSGEN IF CE_MODULES_TOUCH
    ...
    ...

    ; @XIPREGION IF TOUCH_COMPONENTS
        tchproxy.dll    $(_FLATRELEASEDIR)\tchproxy.dll            NK SHK
        tchcaldll.dll   $(_FLATRELEASEDIR)\tchcaldll.dll           NK SHK
    ; @XIPREGION ENDIF TOUCH_COMPONENTS

    ; @CESYSGEN ENDIF CE_MODULES_TOUCH
    Friday, July 22, 2016 7:41 AM
  • Good question. The only thing I could find is the following comment in common.bib and common.reg:

    ; The TOUCH_COMPONENTS tag should not be used in platform.reg.
    ; If OEMs use this tag in platform.reg their component will end
    ; up in the TOUCHPROXY package

    No further links to TOUCHPROXY whatsoever... I would assume TOUCHPROXY is an XIP region, resulting in the touch components being in their own XIP block.

    It could very well be a remnant from Windows Mobile or PPC that is simply not used in CE...


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Friday, July 22, 2016 8:06 AM
    Moderator