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.
Hello people, I am using LPC2138 for very long now. I faced an issue with it.
WDTR: This bit is set when the Watchdog Timer times out and the WDTRESET bit in the Watchdog Mode Register is 1. It is cleared by any of the other sources of Reset.
This is what is mentioned in the user manual UM10120, Page: 44 of 297.
However this bit is set due to rise in temperature as well. I am not very sure but I face this problem only in summers.
Anyone got any idea ?
Do you mean that something in your system causes watchdog resets at high(er) temperatures?
"I face this problem only in summers"
Presumably, it is hot(ter) in the summer...?
Yes this happens only in summers. I am monitoring WDT very keenly. If the WDT is reset, I get a message on the LCD "WDT reset". This should happen only when it really gets reset. But whenever there is no change in the timer value but still it gets reset in summers is something which is not understandable.
Standard procedure in the certification of any microcontroller based product I encountered is testing in a climate chamber!
Sounds like you should be speaking to NXP about this...
Yes I guess this is an new problem which should be included in the errata sheet.
www.catb.org/.../smart-questions.html
(applies equally to hardware bugs)
Precisely because you still guess, it shouldn't. Your claim of a hardware bug is not supported by anything like conclusive evidence.
due to rise in temperature
You clearly do not actually know that for sure.
Something, somewhere in your system reacts to a rise in temperature, and in the end this bit somehow gets set. That's several steps removed from proving that this bit itself reacts to temperature.
For all you know, you could have a wild pointer somewhere in your program that just so happens to overwrite this register. Or it could just be an actual watchdog reset caused by some part of your software, or some other part of the hardware, malfunctioning in the heat.
Would surely check it out once again, now waiting for this summer to come. Now my product works perfectly fine in rainy and winter seasons. !!
Thanks for your replies !
Don't you have access to a climate chamber?
In that case, you can create your own, even if not as capable of keeping exact temperature.
go to debug windows in uv. u can change simulator temp 0c to 120c. good code works above 100c. u use malloc? leaks r bigger with high temp n bits dribble. check humidity and null pointers too.