We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Guys - I am new to this micro and this tool set, and I need some help. I need to set a flag and then perform a CPU software reset (due to another problem). But I need to have a byte that survives the software reset and does not get cleared. If I define an XDATA byte, the STARTUP code will (I think) zap it before I can see it.
How can I write an XDATA byte (or any other byte for that matter) that will survive a software reset (not a power down, just a reset)?
Can anyone help?
Thanks in advance!
Chris
I am fighting a USB problem where the 'F320 gets stuck and stops communicating. I figured out how to detect that condition and reset the device. However, after the reset the device goes away and never enumerates again. (I think it is the old USB problem of devices that go away while in use.) Anyway, I found that if I reset the device again then it magically enumerates again, so I was trying to make the code reset it and then reset it again. you will, probab;y, be better off posting at the SILabs forum www.cygnal.org/.../Ultimate.cgi
Erik
Understood, but my question was about using 'C' and variables that would get past resets. Thanks to all who helped!
just a helpful hint