Yes.


Steve Willoughby wrote:

>hmm.
>
>I've noticed that one sure-fire way to figure out something on your
>own is to walk over and ask someone else, only to have the answer
>finally dawn on you (maybe just by going through the exercise of
>framing the question differently to ask someone else)... I think
>I just did that to myself in my previous question posted here,
>although I wish I had that epiphany BEFORE I hit "send".
>
>Okay, so I think I was mentally confusing the PIC with another
>chip (an EPROM) I'm also working with which had different timing
>requirements for program mode.
>
>So feel free to just ignore my previous question, unless the
>following still doesn't sound right...
>
>I ought to be able to hold the chip at 0V (all pins), then raise
>Vpp and Vdd (in the order specified by the chip's datasheet)
>from 0V to their program voltages, then clock the data in.
>
>In general, random I/O pins may be floating, at Vdd, Vpp, or Vss
>during programming and verification.  (Since on multi-chip
>programmers they need to appear on several different pins.)
>
>Fiddling with Vdd at different levels is only for verification,
>and I'm guessing isn't always strictly necessary for prototypes
>and hobby work.
>
>Sound right?
>--steve
>--
>Steve Willoughby     | "It is our choices... that show what we truly
><steve@alchemy.com>  | are, far more than our abilities."
>                     |     --Albus Dumbledore, in Harry Potter and the
>                     |            Chamber of Secrets, by J. K. Rowling
>
>--
>http://www.piclist.com#nomail Going offline? Don't AutoReply us!
>email listserv@mitvma.mit.edu with SET PICList DIGEST in the body
>
>

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body