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.
Hi, Do you have faced with this problem ? The USB debug adapter runs but the IDE debugger not. I can put breakpoint on the first line of the main but no break, no timer it generated too, when i stop running no stop on the code line executing. It seems there is a problem just before the main call.
thx
I think you have a very serious problem and it requires careful analysis. yes, he does: I have to disable the watchdog in the IDE or in the code ? but no "careful analysis" needed
What on earth does the ide have to do with the watchdogs operation???
the watchdog must be disabled AT THE START OF startup.a51
Erik
Post the code.
Erik will then spend some time looking at it and he will advise you as to what must be modified.
I don't really understand all requests for code in this and other threads. Is it in the hope that the posted code - after correction - will be possible to turn in as a school assignment?
already done
Hi, Thx for your quick responses, indeed it seems to be the watchdog, before main call, which reset. But do you know how what to write in the WATCHDOG macro in INIT.A51 file ?
here is my current watchdog reset macro. but seem to not work. however LST file show the macro at right place.
User-defined Watch-Dog Refresh. ; ; If the C application contains many initialized variables uses a watchdog ; it might be possible that the user has to include a watchdog refresh into ; the initialization process. The watchdog refresh routine can be included ; in the following MACRO and can alter all CPU registers except ; DPTR. ; WATCHDOG MACRO MOV 0CFH,#78H ENDM
mister orange,
have you disabelled the macro's in the ide?
thanx
hi, i'm using the silabs IDE with Keil compiler. so there is no macro options.
here part of LST file.. 003B 156 ?C_START: 003B 900000 F 157 MOV DPTR,#?C_INITSEG 003E 158 Loop: 159 WATCHDOG 003E 75CF78 160+1 MOV 0CFH,#78H 0041 E4 161 CLR A
i mean it's the watchdog reset method that not working..
it is 100 times easier to see what it is if you do not show code using macros BTW why are you even using a macro for something you only do once?
Hi, See Cx51.chm, "searching" with keyword: "watchdog" and you will see why ?
Thx
CX51 has no idea in the world how a SILabs watchdog works.
WHY do you REFUSE to do what i suggest?
THE END
It is fortunate that in a free society people have choices!
Some choices are better than others...
WHY do you REFUSE to read what he writes?
What a relief!
Erik,
in this project, we must use standard startup files from compiler. (mandatory for our customer) If Keil define one Macro to refresh WDT... why modify directly the code ? this method of work is better for futur upgrade of startup files. we don't have to modify the code.
i can try your idea but i don't see what is different than by macro.. macro principle is to replace keyword by some instructions. Macro is generaly defined in top of file to easily identify changeable portion of code.
but i'll try your suggestion now.
It would be if it were true. But just wait ... He'll be back with his usual 'style'!
?C_START: MOV DPTR,#?C_INITSEG Loop: MOV 0CFH,#0H ; WATCHDOG CLR A