• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 114 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

OMAPL138B-EP: OMAP L-138 2-nd stage bootloader doesn't start after update from my firmware

Pavel Mychko
Intellectual 360 points
Part Number: OMAPL138B-EP
Other Parts Discussed in Thread: OMAP-L138

I try to read the 2-nd bootloader block from NAND memory to RAM and then flash it back to the same position, but after that operation bootloader doesn't start again. After flashing by your utilities from PC it's ok. I compared this block after PC flashing and my flashing and they are the same. So I decided problem in some attributes of NAND memory. Maybe 1-st stage bootloader use ECC for the 2-nd bootloader block (I don't use)? Any other ideas?

  • 0
    TI__Guru** 114410 points

    If the user data in the NAND block pages matches with the PC flashing and your flashing then the boot is likely failing since the ECC data is not being written in the spare area in the correct format in your re-flashing process.

    You can refer to the NAND flash writer code that we provide in serial flash and boot tools for this device to confirm that the ECC data written to spare are is correct:

    Serial flash and boot utils for OMAPL138

    Location of files: OMAP-L138_FlashAndBootUtils_2_40\OMAP-L138\CCS\NANDWriter

    With bootloader if you are referring to the ROM bootloader then you should be able to read the ROM error status when the boot fails using the following GEL file with your JTAG based CCS setup. Please connect to the A9 core and load the GEL attached using Tools-> Gel Files (Right click and browse to GEL attached). When the file is added to GEL setup, you can go to Scripts tab of CCS Debug View and run the ROM status or the entire system state status.

    5672.C674x_debug.gel

    Check Chapter 4 here for ROM debugging with this file:

    http://www.ti.com/lit/an/spracm8/spracm8.pdf

    Please let us know if this helps root cause the issue.

    Regards,

    Rahul