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.

MSPM0G1518: MSPM0G1518: Unexpected reset cause behavior

Part Number: MSPM0G1518

Hello,
I am observing a strange behavior after a reset on the MSPM0G1518 chip:
When a POR is performed via VDD < POR- violation and the reset cause register is read a reset cause is 0xC not 0x1, as it would have been expected. To reproduce the issue a 3V is manipulated externally to create a VDD < POR- violation and therefore a POR and a reset cause is read afer the start of execution.

On additional note, as per the recomendation from datasheet a 47 kOhm resistor is connected to the NRST pin. To furthermore test the behavior an additional 4 kOhm pull up resistor was temporarily  connected to NRST and that shortens the period of powering up on the NRST line as well as fixes the issue - reset cause becomes 0x1 as expected, however not sure whether it actually is how this should be fixed. Is it possible that there is some unwanted reset happening after POR or is it an issue similar to the PMCU_ERR_09? Please take a look on this. 

  • Hi Viktoriian,

    It sounds like a similar issue of PMCU_ERR_09 that reset cause does not shows correct POR (0x01) in some cases. Let me check internally about this issue and whether it is a case that is not fully covered by PMCU_ERR_09. 

  • Hello again! 
    I have noticed that there has been an update of Errata for MSPM0Gx51x and the PMCU_ERR_09 has been extended. Could you please confirm that the issue raised in this thread is now a part of PMCU_ERR_09 as well? And also could you please provide Errata MSPM0Gx51x Rev. D so that it could be compared side by side with the new Revision E for double clarity on this issue as well as some others?

  • Hi Viktoriian,

    Sorry for late reply. You are correct the errata PMCU_ERR_09 has been extended for this issue.

    As for the Errata upgrade items, I think you could check the revision history in latest version. Also I upload Rev.D here. SLAZ758=5=TI PDF=en-us (1).pdf