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

AWR1642: Question about reset cause

Chris Meng
Mastermind 37656 points
Part Number: AWR1642

Hi,

Based on below post, I knew that we can check register @ "0xFFFFE2FC" to check the reset cause for ES2.0 chip. Customer and I did some test, but the result is not total matched with the register explanation in the post.

With watchdog reset in app code, we got value of 0x028A028A @ "0xFFFFE2FC" . Bit 3:0/19:6 (SYS_RESET_CAUSE) are matched with watchdog reset. But for bit 11:4/27:20 which is for MSS_RESET_CAUSE, I can't find info of 00101000.

With writing 0xAD to SOFTSYSRST register in app code, I got value of 0x028C028C. Similar as above, we don't know what 00101000 means.

Are above value of 0xFFFFE2FC we got as expected? Would you pls kindly advise what 00101000 means for MSS_RESET_CAUSE? 

What's the difference between current cause and at Reset cause for register @ "0xFFFFE2FC" ?

  • 0
    TI__Guru 69960 points
    Chris,
    "0xFFFFE2FC" is the register where bootloader saves the reset cause from TOPRCM->SYSRSTCAUSE and RCM->RSTCAUSE to [3:0] and [11:4] of that register (0xFFFFE2FC) respectively and same will be copied to other half of 0xFFFFE2FC for current boot or subsequent boot of the device.

    0xFFFFE2FC[11:4] may have the value ORed of multiple reset cause, like 0x28 means ORing of
    0000_1000 : System out of Warm Reset
    0010_0000 : CR4 reset because of Software trigger.

    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    TI__Mastermind 37656 points
    Jitendra,

    Thanks for your reply.

    For customer's watchdog reset, he got 0x028A028A @"0xFFFFE2FC". Does R4F treat watchdog reset as a software trigger?
  • 0 in reply to Chris Meng
    TI__Guru 69960 points

    Hello Chris,
    If SBL is present in the system which does the soft-reset to application to run or 0x2:Sft-reset-cause is generated by ROM eclipsing & core reset and it doesn't clear the soft-reset cause on RCM->RSTCAUSE. So in that case bootloader sees rcm->RSTCAUSE: soft-resest-cause (due to last SBL), RCM->RSTCAUSE: warm-reset-cause (due to watchdog reset) and TOPRCM->SYSRSTCAUSE: watchdog reset. Bootloader copies content from TOPRCM and RCM resetcasue register to SPARE9, so this explains this value.


    Regards,
    Jitendra