• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 401 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

why the Wince system Unable to start while I enabled KITL

Siyou
Intellectual 560 points
Other Parts Discussed in Thread: AM3517

Hi all,

       when I debug Wince 6.0(BSP version BSP_WINCE_ARM_A8_01_02_00) on LogicPD AM3517 EVM, I found that when I enable the KITL the Wince boot will stop at the touch panel calibration. what's the problem of it? how to solve it? Thanks!

  • 0
    TI__Intellectual 1195 points

    Peter,

    That's the expected behavior,  the touch screen calibration program runs when you boot the board for the first time.

    You need to touch, using a pencil or stilus or even your finger, on the different marks (looks like a small x) to complete the touchscreen calibration. After that the TS calibration values are saved and the TS calibration program won't run on the next boot sequences.

    Hope that helps,

    Carlos.

     

  • 0 in reply to Carlos Hernandez
    Intellectual 560 points

    Hi Carlos,

          Thank you for your attention, but the problem seems not like it. when I disable KITL by the eboot menu, the different marks (looks like a small x)  will move while I touch the  touch screen on the calibration program, however, there is no response while I touch the touch screen when I enable the KITL, it couldn't run to the next boot sequences.

    Thanks!

    best regards

    peter

  • 0 in reply to Siyou
    TI__Intellectual 2525 points

    Hi Peter,

    Are the platform builder->target connectivity settings set up correctly? Could it be that in the eboot menu, you are using one of the ethernet interfaces for download which is "Boot Device" (say, emac) and the other interface for kitl  which is "Debug Device"(say, lan). In such a case, platform builder-> target connectivity might have information about the download interface and hence, image download goes through fine (I am assuming that is the case for you) but when it is trying to complete the kitl connection, it is unable to see the emac as the kitl interface. If that is the case, try using the same interface for both Boot and Debug in your eboot menu options.

    regards,

    Aparna