• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 746 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.

OMAP L137 | WinCE | Boot issue after "Booting with TI UBL Device OPP (300MHz, 1.2V)01"

Roderich
Prodigy 20 points

Other Parts Discussed in Thread: CODECOMPOSER, OMAP-L137

 

Hello,

currently I am trying to run Windows Embedded CE 6.0 on my OMAP L137 Floating Point Starter Kit. I just followed the steps in the Quick Start Guide of the BSP and flashed EBOOT to the EVM with CCS. There was no error.

When I start my board it stops after

Booting with TI UBL

Device OPP (300MHz, 1.2V)01

Any ideas why the EBOOT start-up menu does not appear?

Thanks in advance!

  • 0
    TI__Intellectual 1640 points

    Did you compile the eboot you flashed?  If not can you try the pre-built eboot included in the demo release?  Also, instead of CCS, try the serial flash tool and see if it helps.

    Regards

    WM

  • 0 in reply to WMK
    Prodigy 20 points

     

    Hi WM,

    Thanks.

    Yes, I compiled eboot. The serial flash tool indeed helped. I thought it would just do exactly the same as CCS...

    Regards

    Roderich

  • 0 in reply to Roderich
    Prodigy 185 points

    Hi WMK,

    after having flashed the armubl and eboot images using CodeComposer V3.3 followed by resetting the OMAP L137 eval board I've been running into the same problem as Roderich  described in this post:

    --------------------------------------------------

    Booting with TI UBL
    Device OPP (300MHz, 1.2V)01

    ---------------------------------------------------

    So, Eboot is not started.

    You told Roderich to solve this problem by using the 'serial flash tool' but I cannot do the same because I've not the possibility to use a COM port set to 230000 baud.

    Do you perhaps already know why flashing with CCS does not do the job ?

    What other alternatives do I have ?

    Best regards,

    Franz

     

  • 0 in reply to Franz Frisch
    Prodigy 185 points

    Hi,

    I've solved my problem of flashing the 3 bootloaders using the sfh_omap-l137.exe flash utility but without the "-baud" switch as shown on the 'TI WinCE BSP quick start guide'.

    With following command line you can use the flash utility with 115200 baud:

    sfh_omap-l137 -flash_dsp -p COM1 -v -appStartAddr 0xC3F60000 -app LoadAddr 0xC3F60000 dsp-spi-ais.bin ubl-spi.bin ebootspiflash.nb0

    I assume , that only users of version 1 of OMAP_L137 are forced to 230400 baud, but users of  version 2 are not. Am I correct ?

    For granting success when starting to work with OMAP-L137-EVM for new users I would suggest to modifiy the repeated hints in the quick start guide that one must use always an 'usb to serial converter cable supporting the 230400 baudrate' .

    By the way :

    In the quick start guide the 'load and start addr' for the above command line are given as 0xC3F60000.

    The default load and start addrof sfh_omap-l137.exe tool are 0xC1080000.

    Which one do you recommend for usage ?

    Best regards,

    Franz