Detecting Different Software Reset Events, Additional Bits Beyond SRS

Keith4DSmith — Wed, 24 Oct 2018 12:45:28 GMT

I understand the POR and SW bits of the RCM-SRS0 register.

I see the POR (and LVD) bits on a power on of my K22F eval board.

I also see an SW bit set when calling the core_cm4.h function __NVIC_SystemReset()

What I would like to have is one or more additional bits to distinguish additional reasons for calling __NVIC_SystemReset().

What are recommended procedures to have data persist across a restart session?

Re: Detecting Different Software Reset Events, Additional Bits Beyond SRS

mjbcswitzerland — Wed, 24 Oct 2018 14:15:46 GMT

Hi Keith

See the first few paragraphs of Appendix B of http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.pdf
for a simple method of leaving a reason for a commanded software reset.

Regards

Mark

For less questions and restrictions, and faster, cheaper developments: try uTasker for Kinetis