From: "Dave VanHorn"
References: <3D8A6BE9.6455BB7@webaccess.net> <3D8A8F7D.865B97EB@webaccess.net> <2Jxi9.email@example.com> <3D8ABEF0.6386FF38@webaccess.net>
Subject: Re: Which Microcontroller to use?
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
NNTP-Posting-Date: Fri, 20 Sep 2002 01:35:21 CDT
Organization: Giganews.Com - Premium News Outsourcing
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
Date: Fri, 20 Sep 2002 06:35:21 GMT
>Another problem is that
> breakpoints are dangerous. For dynamic reasons, my power drivers can fry
> my actuators. A breakpoint can literally cause smoke.
Tell me about it. This one is a thermal line printer. More than 300-500uS
and the pixels fall off. Of course they aren't very spectacular, but I have
burned lines across the paper!
> Debug has to be
> done with the real physical environment. I design the code as far as
> possible with a GIGO philosophy (Garbage In, Gospel Out), I can't
> predict transient conditions at the inputs so "gospel" is my best guess.
I usually have one pin that I can use for "ping", a routine I call that just
takes that pin high, then back low. In ISRs I just code it in. Great, when
combined with a scope, to say when something has happened.
This is my first multi-avr project, I have two M-128s and a Tiny 26, plus a
dedicated IRDA processor, but I don't have to worry about that one. (much)