• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1406 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.

DRA626: different between RESETz and PORZ

Tony Tang
Mastermind 30827 points

Part Number: DRA626

Doing Watchdog reset on my customer system to identify a system hang issue, found DRA624 hang after several hours test.

Issue: After hang, DRA624 can't reboot either by watchdog or assert RESETz. Can reboot with PORz. 

Check TRM, no founding much different between PORz and RESETz can impact reboot. Would you please help analysis.

About below  reset table, what is N3, Y1, Y2, Y6?

Can software trigger a reset as PORz?

  • 0
    TI__Mastermind 25170 points

    Hi Tony,

    As being indicated, warm reset and watchdog reset can be blocked during emulation session. Do you have the issue with and also without debugger connected?

    Other scenario could be the device actually resets but doesn't boot for some reason.

    Regards,

    Stan

  • 0 in reply to Stanislav Stilyanov
    TI__Mastermind 30827 points

    Where is my reply. Anyway, I reply again.

    Stanislav Stilyanov said:
    As being indicated, warm reset and watchdog reset can be blocked during emulation session. Do you have the issue with and also without debugger connected?

    No emulator connection. JTAG is not routed out.

    Stanislav Stilyanov said:
    Other scenario could be the device actually resets but doesn't boot for some reason.

    Any suggestion to root cause it? 

    Why RESETz can't recover the board, but PORz can. 

  • 0 in reply to Tony Tang
    TI__Guru 57777 points

    Tony,

    As summarized in the table you've highlighted, resetz does not reset all SoC logic whereas porz does.  If the logic that is not reset gets into a bad state then it is possible for resetz assertion to not recover the device and allow a successful reboot.  In general, PORz should be used to reset the device fully.

    Regards,

    Kyle