revive it by placing the eerom in the second slot of an oopic-s and
erasing the eeprom via the compiler gui and then placing it back in the
oopic-R.
Thanks for the feedback. I'll start putting the oopic.delay in my
stuff from now on as well.
--- In oopic@yahoogroups.com, "rtstofer" <rstofer@...> wrote:
>
> If you don't have that OOPic.Delay = 500 as the first executable
> statement, an errant program can start up and prevent the OOPic from
> communicating. And, when you download it again, well, it does exactly
> the same thing it did the last time.
>
> You should always have some kind of blinking LED example that is KNOWN
> to work that you can download whenever you question the viability of
> the OOPic.
>
> Richard
>
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