• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 282 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSPM0G1507: Not sure which file to reference for reset cause values

Bryan McDonald
Prodigy 165 points
Part Number: MSPM0G1507

Hi, It's not clear to me as to why the reset cause values are different between the MSPM0 G-Series Technical Reference Manual (section 2.6.1.32 RSTCAUSE Register) and the 

DL_SYSCTL_RESET_CAUSE enum structure defined in ti\mspm0_sdk_1_10_00_05\source\ti\driverlib\m0p\sysctl\dl_sysctl_mspm0g1x0x_g3x0x.h.  Is this just a mistake, and if so, which file is correct? 
  • 0
    TI__Mastermind 23540 points

    Hi Bryan,

    I opened the files and compared the enum values to the TRM. I found them to match

    This is on SDK 1.10 and the TRM that is currently online on TI.com

    Regards,

    Luke

  • 0 in reply to Luke Ledbetter
    Prodigy 165 points

    Hi Luke,

    Which source file are you showing in your reply?  It's something other than dl_sysctl_mspm0g1x0x_g3x0x.h.  Maybe the issue is just with the hover over feature, which shows values different than expected for this.

  • 0 in reply to Bryan McDonald
    TI__Mastermind 23540 points

    Hi Bryan,

    I'm getting different results when I hover over

    From my original screenshot, I did CTRL+Left Click on the right side of the "=" to get to the actual value. I was using CCS 12.4 when checking this. I switched over to CCS Theia and can confirm what you are seeing with the value of 6. When I go to the file it should pull the right side of the "=" from, it is properly set. See mspm0_sdk_1_10_00_05/source/ti/devices/msp.peripherals/m0p/sysctl/hw_sysctl_mspm0g1x0x_g3x0x.h

    I will check that this is a visual bug and get to investigating why the value is appearing incorrect.

    Regards,

    Luke