Gerhard Fiedler wrote:
>
> At 14:14 02/05/97 +0200, Tjaart van der Walt wrote:
> >We left a few small pads to do the programming on a bed of nails. Works
> >well.
> >You can also test the other functionality on the board.
>
> I'm thinking about a thing like this and putting some calibration data
> (ADC) into OTPROM, like measure it first and then program the chip with a
> patched file. Or better, burn the program, do a calibration run (part of
> the program), get some reference values (from the PIC), send these back to
> the programmer, and then put these reference values in the program memory
> at some unused location. Does anybody have experience with a setup like
> this? I.e. is it possible to program just some locations after the "main"
> program has already been burned?

I haven't done it, but I think it would be possible. Program the memory
earmarked for the calibration data with retl FF 's (unused). You could
also
pop the data into external EEPROM if you could do something with the
extra
memory.

>
> >Don't do production runs with a PICstart - it's not made for the job.
>
> Would you mind to explain briefly why? (More as to give me some clues what
> to look for what I don't have in a PICstart when I have to buy a production
> type programmer...)

The PICstart does not verify the PIC at the specified voltage levels.
Most manufacturers will have the correct programmers to do production
runs with, so
you wouldn't have to fork out the really big bucks. The PICstart is
perfect for
fooling around in the Lab.

Friendly Regards

Tjaart van der Walt
mailto:tjaart@wasp.co.za
 _____________________________________________________________
| Another sun-deprived R&D Engineer slaving away in a dungeon |
|             WASP International  http://wasp.co.za           |
|             GSM and GPS value-added applications            |
|  Voice : +27-(0)11-622-8686   |   Fax : +27-(0)11-622-8973  |
|_____________________________________________________________|