> - change the serial port baud rate to anything other than 9600 bps
>
> - use the oEEPROM object and write to the wrong location - bye bye
> program
>
> - recurse and overflow the stack - just call main() from main()...
>
>
> It's real easy, which is why programs should always start with a
> delay instruction.
I was thinking that one could recover just by resetting the chip but
if the program immediately takes the systems out, yeah, that could be
a problem. :-) You'd have to wipe the eeprom first. I see your point
re the delay. Make it long enough that you have time to start to
download a new program. What do you use, 10s?
This is one of the things that I like about the propeller. For testing
I can load the program into RAM. If it takes out the system a reset
loads the program in eeprom. I just make sure that whatever is in
eeprom is safe, usually nothing more than a do-nothing program which
is also safe in case someone has stupidly wired an I/O pin to Vss or
Vdd.
--
73 de Brian, WB6RQN
Brian Lloyd - brian HYPHEN wb6rqn AT lloyd DOT com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment