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
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
Erik
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
in this project, we must use standard startup files from compiler. (mandatory for our customer) then tell you customer "we can't" and show him the silabs knowledge base articles
the issue: www.silabs.com/.../McuKB.aspx
howto: www.silabs.com/.../McuKB.aspx
so, is THAT enough to get you to do what you need to do instead of trying to do something else that you 'prefer' but does does not work
in the preview I see both links are the same you need to type watchdog into the search window that comes up and find the two articles.
PS to the sardine: if you would takr the time to verify that I was wrong (which I am not) before you spewed your bile, there woould be a whole lot less of it
if you would takr the time to verify that I was wrong (which I am not) before you spewed your bile, there woould be a whole lot less of it
Where did I say you were wrong?
The poor chap is merely trying to explain why he's doing what he's doing (following the instructions in the documentation) yet you just keep yelling at him before finally flying into a sulk and saying you're not playing any more. Sadly your sulks don't seem to last very long.
Hi, Simply, is someone able to answer why with instructions above the watchdog never reset ? A piece of code which work with c8051F500 would be cool... or INIT.A51 file which work
A piece of code which work with c8051F500 would be cool...
howto: www.silabs.com/.../McuKB.aspx you need to type watchdog into the search window that comes up and find the article
INIT.A51 file which work what is an INIT.A51 file?
what is an INIT.A51 file?
You are joking, aren't you?
Perhaps not - it would explain some of your misplaced arrogance in this thread.
Time to read the C51 manual I think...
Hi, Thx Erik for your answer but we are searching the way to reset (refresh) the watchdog during startup and init sequence (before main call). During this sequence, writing to PCA0CPH5 doesn't work and so doesn't refresh the Watchdog ! It's a little bit strange, isn't it ?
what is an INIT.A51 file? You are joking, aren't you?
Yes, there is an init file build by the tools (the one between statup and main), but if that is 'user modifiable' I do not know of it. Since it is built by the tools how can it be .a51