• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 838 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.

Getting Remote Desktop to connect without Platform Builder

Nelson Hall
Intellectual 405 points

Other Parts Discussed in Thread: AM1808, OMAPL138

TI,

AM1808 EVM
WinCE 6.0

I followed the directions in the Quick Start Guide to make Remote Display work.  Since my final configuration will be headless, I unchecked the display driver and set BSP_DISPLAY_CER=1 in the OMAPL138_AM18X\OMAPL138_AM18X.bat file.  Remote Display works well when booting from PB through EMAC.

When booting from SD card or NAND flash, Remote Display won’t connect.  If after booting from either of these and then performing Target->Attach from PB, Remote Display will then connect.

How can I get Remote Display to connect without involving PB?  What am I missing?  Thanks.

Regards,
Nelson

  • 0
    TI__Intellectual 1640 points

    Hello Nelson,

    Could you try the following:

    1. telnet to board

    2. once inside the telnet session, type "start cerdisp -c", then RETURN

    3. connect to board from cerhost.exe

  • 0 in reply to WMK
    Intellectual 405 points

    Couldn't telnet.  Don't see any sign of DHCP or IP assignment in the boot message terminal output.  Telnet works fine when booted from EMAC - terminal output shows DHCP assignment.  Looks like there is no DHCP activity when booting from SD card or NAND.  How should this be fixed?

    Nelson

  • 0 in reply to Nelson Hall
    TI__Intellectual 1640 points

    I don't see any problem with telnet when I boot from SD with the image built from the OMAPL138_AM18X_TI_DEFAULT OSDesign included in the release, no PB is involved.

    There won't be any IP assignment message shown on terminal.  

    You might want to use Wireshark to make sure whether IP assignment is there or not.

    Also if you are using your own OSDesign, you might want to make sure "telnet server" is enabled in the Catalog.  

    WM

  • 0 in reply to WMK
    Intellectual 405 points

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    WM,

    I found out what was going on.  I compared the BOOTME packet content when:

    1)  EBOOT is booting the OS from PB

    2)  After the OS boots from PB         (Remote Display connects OK)

    3)  After the OS boots from NAND   (Remote Display did not connect)

    It turned out that the EBOOT BOOTME of (1) was similar to the one seen after the OS booted from NAND (3).  I’m thinking that this is the KITL BOOTME.  Number (2)’s BOOTME was much different – that’s the one that Remote Display connects to.

    So, I unchecked KITL under build options which is under project configuration properties and rebuilt.  I flashed the result to NAND and booted – no PB.  Remote Display now works.  Maybe a note about disabling KTIL in the Quick Start Guide is in order.  Can you please verify that this is the proper way to get Remote Display working?  Is there a way to have both KITL and Remote Display working?  Thanks.

    Nelson