• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 83 subscribers
  • Views 274 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.

Original question:

TMS320F28388D: CM Configurable Watchdog timer

TMS320F28388D: Unable to reboot CM after WWD/WD trigger

pranay r
Intellectual 390 points

Part Number: TMS320F28388D

Hi / ,/,

This is continuation to the thread "https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1211213/tms320f28388d-cm-configurable-watchdog-timer/4596452#4596452".

As I said in the past, I want to reboot CM without rebooting or effecting other cores. I'm able to trigger WWD and make it expire so that CM go to reset state. I'm also able to generate NMI ISR in CPU1 when WWD on CM expires as well.

Now after WWD expiry it is generating a NMI to the CMNMIWD module and in CM FW  I'm intentionally not handling/clearing/servicing the NMI interrupt making CM to reset.

I want to make CM boot from CPU1 which I'm unable to resolve. As CPU1 will also get NMI interrupt when CM WWD expires, I'm calling " Device_bootCM(BOOTMODE_BOOT_TO_FLASH_SECTOR0);" but I'm unable to boot CM.

We're at a critical stage where we want to boot CM alone without disturbing other controller. Can someone please help us. If required to we can share sourcecode and can have a teams call to have the resolution faster.

Been trying this since some weeks and unable to find a working solution.

Have gone through this flowchart and what stage it is in now after wwd expired. Need help.

Thanks and regards,

Pranay