> -----Original Message-----
   > From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu]On Behalf
   > Of Mark Scoville
   > Sent: Tuesday, May 17, 2005 8:16 AM
   > To: Microcontroller discussion list - Public.
   > Subject: RE: [PIC] MPLAB Checksum display?
   >
   >
   > I really think you should be able to do what I think you want
   > to do. I have
   > been doing what I *think* you want for several years. Once my
   > code is stable
   > it is released to our production department as a Hex file.
   > Production is
   > also given a "Programming sheet" with all the checksums listed for the
   > current firmware versions of all our products. If the production person
   > loads a .hex file and the checksum doesn't match what's on the
   > programming
   > sheet they come and find me. We have had a few instances where
   > they have
   > accidently loaded the wrong .hex file - and the checksum, of course was
   > wrong. By verifying the checksum they have avoided burning
   > chips with the
   > "wrong" firmware. Sure if the hex file itself is corrupt MPLab will
   > complain. But, that's no help for someone loading the wrong
   > hex file that is
   > NOT corrupt. We code-protect our chips, so a readback & compare to a
   > "master" chip is not an option. The checksum is just a way to
   > help ensure
   > that we are really putting the right stuff in the chip. I
   > think this is the
   > same thing you are wanting to do.
   >
   > Can you maybe try MPLab on a different computer?
   >
   > -- Mark
   >
I think the problem in my case is that the vendor is not using MPLAB.
If they were, we would not have a problem.  We just haven't been able
to correlate how their equipment/software calcs checksum vs MPLAB.
Carey

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist