• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 303 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 L138 who prints "OMAP-L138 initialization passed"

tom campbell
Prodigy 60 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

We have a custom OMAP L-138 board with a revision 2.0 silicon chip.

The board doesn't boot reliably from power on.  It prints some or all of

   "OMAP-L138 initialization passed"

and dies.  It works reliably from the reset button.  We are working on the theory that it is caused by the Silicon Errata issue of requiring a double reset.  If I understand the errata correctly, the ARM processor is never running.  Hence my question:

Which processor (arm/dsp/?) prints the OMAP-L138 initialization passed" ?

If it's the ARM, I would think that counter indicates the lack of the double reset is a problem.

thanks in advance

tom campbell

  • 0
    TI__Intellectual 2020 points

    If you are seeing this message then your ARM device has already been booted since I am pretty sure the ROM boot loader does not print out that message. I’ve booted up a new and old version of the silicon and I have not seen that message. This confirms to me that the code that is printing this message is not being done within the ROM.

    The culprit will probably be UBL/MLO which is the device’s secondary boot loader. If you can provide the SDK version that you are using then I can verify that message.

  • 0 in reply to Franklin Cooper
    TI__Guru** 116170 points

    Tom,

    The code for secondary bootloader (UBL) has the debug printf statement that prints "OMAPL138 initialization passed". This runs on the ARM. You can find this file in the Serial and flash boot utilities under OMAPL138_Flashand BootUtils_x_x/Common/ubl/src. The fact that you see this statement indicates that the issue in the errata may not be the cause of your boot failure because at the point ROM code has finished executing and all system initializations are complete. 

    Regards,

    Rahul