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

MSPM0G1519: Hard fault after target reset during update of SYSPLLPARAM0/1 tuning registers.

Manjunath Bhavimani
Prodigy 100 points
Part Number: MSPM0G1519
Other Parts Discussed in Thread: MSPM0G3519

Tool/software:

Hi Team,

As mentioned in the subject, our board bring-up and clock configuration code works fine without any issues when I flash the ELF directly. However, I encounter a Hard Fault during board bring-up when performing a target reset through the debugger.

On further debugging, I observed that the Hard Fault is triggered during the update of SYSPLLPARAM0/1 in the clock configuration function. After a target reset, the values at addresses 0x41C40030–0x41C4003C are reset to zero. As a result, accessing these memory locations causes the Hard Fault. I have attached the snippet for your reference.

 

Regards,
Manjunath B

  • 0
    TI__Genius 9095 points

    Hi Manjunath,

    For the 0x41C4xxxx access problem, the region is factory region, and a access to factory region in 80MHz on MSPM0G3519 device will cause a hard fault, you could check FLASH_ERR_01 of our Errata MSPM0Gx51x Mixed-Signal Microcontrollers Errata (Rev. B) for details.

    In our SDK driverlib, the Factory region data will be backup to SRAM before SYSPLL is enabled, so it should run well normally.

    Which IDE are you using? When you "performing a target reset through the debugger", is there "system reset" option in your IDE, if yes, you could try with system reset or a higher level reset.

    Best Regards,

    Pengfei