• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 353 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.

Does the OMAP3530/25 perform any BIST (Built in Self Test) prior to ROM boot?

zap56358
Prodigy 20 points
Other Parts Discussed in Thread: OMAP3530

Does the OMAP3530/25 perform any hardware self-test prior to ROM boot and if so can the results of those tests be read from software?

I've been through the technical reference manual and as far as I can tell the only status readable from software is how the unit came out of reset.

  • 0
    TI__Intellectual 2820 points

    Hi Zap, 

    The OMAP3530/25 does not peform a HW self-test upon boot-up. 

    What kind of features are you looking for?  Are you doing a safety critical application? 

    Regards,

    Lawrence

     

  • 0 in reply to Lawrence Ronk
    Prodigy 20 points

    Lawrence,

    Thanks for the confirmation.

    Actually the goal is early failure detection and field debug. Looking at the entire boot sequence (from the ref manual) I've got some general thoughts on failure notification:

    • Preinitialization - can't do much here

    • Power/clock/reset ramp sequence - ditto, maybe an LED on successful power up.

    • Boot ROM - detect bad boot media, flash LED...

    • Boot loader - detect bad peripherals, bad OS image, phone home (ethernet)

    • OS/application - crash log, etc

     

    Does TI have any code to log state at the early boot stages?

    -Zach

  • 0 in reply to zap56358
    TI__Expert 6175 points

    Zach,

     

    The TRACE vectors populated by the ROM code do exactly that. As the ROM code cross each milestone during the chip initialization, it logs its progress by setting a bit in the trace vector location. If a boot fails, CCS can be used to look at the trace vector location and post-mortem analysis can be done as to what went wrong.

    Information regarding the Tracing vector is in the TRM chapter regarding Initialization in the sub-section Device Initialization by ROM Code..

     

    Regards,

    Madan