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

TMS320F28069 - Problems with SYS/BIOS after ESD event

Torben Frenzel
Prodigy 180 points

Other Parts Discussed in Thread: TMS320F28069

Hi,

I am using a SYS/BIOS application on a TMS320F28069 MCU. During our testing, we observed some very strange behavior after an ESD induced reset:

The MCU would perform a reset due to an electric discharge near the PCB. Everything up to BIOS_start(); would be executed correctly, but after this the MCU hangs.

A hardware reset at this point doesn't help, it will just hang after (or during, I don't know which) BIOS_start(); A watchdog reset doesn't help. Only disconnecting the power supply and reconnecting it will correctly restart the system.

A hardware or watchdog reset without the ESD event will always correctly restart the system.

Is there any way that a misconfigured register or RAM content might produce such a behavior? Is there any way to guarantee that everything is initialized correctly at startup?

Additional information:

CCS 5.2.0.00069 

SYS/BIOS 6.33.04.39

XDCTOOLS 3.23.03.53

Compiler TI v6.1.0

Thanks

Torben Frenzel

  • 0
    TI__Mastermind 26780 points

    Torben,

    Is this application booting from Flash successfully?  Or just running within CCS?  If it is booting fine from Flash, then it seems all RAM, register, etc. initialization during startup is being handled properly.  

    Is this consistently repeatable?  With the same system, as well as on multiple systems?  Do you have any idea what the ESD event does to the device that results in a reset?  

    I think the C2000 device forum might be a better place for this question: http://e2e.ti.com/support/microcontrollers/c2000/default.aspx

    Scott

  • 0 in reply to ScottG
    Prodigy 180 points

    Scott,

    thanks for your reply. Further testing has revealed that the problem is actually not SYS/BIOS related at all. It just seemed that way because interrupts are enabled during BIOS_start() and the problem is interrupt related. I will continue this in the C2000 forums.

    Thanks for your support

    Torben Frenzel