Customer found the XRSn pin of new devices would be driven low for 50us at every 15ms. After flashing with the emulator, XRSn will keep high normally. Could you please help explain the reason? Thank you.
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.
Customer found the XRSn pin of new devices would be driven low for 50us at every 15ms. After flashing with the emulator, XRSn will keep high normally. Could you please help explain the reason? Thank you.
Aki,
It is the watchdog timing out. You will see this on any part that has a blank (erased) flash. The WD counter keeps overflowing and resetting the part. The code you put in flash either disables the WD or services it periodically and that is why you don't see the periodic resets anymore.
Hareesh,
Thank you. One more question, how can the debugger stop the reset when flashing the device. We saw XRSn was pulled high during the flashing. Could you please share more details for the internal control logic?
how can the debugger stop the reset when flashing the device. We saw XRSn was pulled high during the flashing. Could you please share more details for the internal control logic?
Once the debugger takes control of the device, the device is "stopped in its tracks". i.e. the device operation comes under the control debugger, for the most part (unless you choose the "Run Free" option of the debugger).
And is it a common feature for all C2000 devices?
Yes.