- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
Hello experts,
I would like to utilize the feature of WDG (Watchdog) reset not clearing RAM variables to share variables between the user APP program and the user Boot program. This function works correctly in the 0025 model, but I encountered an issue when applying it to the 0039 model. The detailed problem description is as follows:
In the 0025 project, a uint16-type variable was placed at RAMM0 location 0x128. Before reset, the variable was set to 1, and after the watchdog reset, this RAM variable remained as 1.
When performing the same operation in the 0039/0039C model, the variable at this location was unexpectedly cleared to 0 after the watchdog reset.
We then relocated this variable to the end of RAMM0, at the beginning of RAMM1, RAMLS0, RAMGS0, etc. After the watchdog reset, the value remained as 1 and was not cleared.
Could this phenomenon be related to the size of the Reserved RAM for Boot? In the 0039 model, does the ROM Boot use a RAM region that exceeds the range of 0x2-0x127? What is the specific RAM range used by the ROM Boot in the 0039 model?
