How could I know whether the reset is caused by the watchdog???

Hi liyang,

You can check if a platform reset issues by replacing the platform_reset_func in the jump_table.c file with a custom empty function and try to catch the call of the function with a break point in debbuging.

Thanks MT_dialog

Hi liyang,

Sorry i can't. I just misunderstood your question.

如果the reset is caused by the watchdog timer it goes to the NMI_Handler. Can you debug your program and try to catch it there ?

Thanks MT_dialog

Hi liyang,

There is no specific way for knowing that the reset was issued by the watchdog timer. A way i can think of is maybe storing a value, in an external memory(if your system has one)or in a retained space, from the NMI handler and to read this particular memory to see if there was a reset.

Thanks MT_dialog

Hi liyang,

You can find examples of how to store variables in the retained memory space in most of examples of the SDK and in the reference designs, the keyboard ref design for example.

In order to store a variable in the retained space you can use this for example int extended_timer_cnt __attribute__((section("retention_mem_area0"), zero_init));

The thing is that the retention rams when the system reboots are initialized to zero by the SystemInit() in the system_ARMCM0.c so i 'm not certain if this can help you even if you remove the part that where the initialization to zero happens. The external memory scenario is more certain.

Thanks MT_dialog

Hi, all,

I set variable not like this int extended_timer_cnt __attribute__((section("retention_mem_area0"), zero_init));
I set variable is like this :int extended_timer_cnt;
is the extended_timer_cnt save in retention_mem_area0 or retention_mem_area1?

thanks

Hi YuanhangWu,

如果you decalre a variable without the __attribute__ then your variable isn't located in a retention space.

Thanks MT