Post by thread:[PIC]: Compiled HEX versus dumped HEX

Hello, I have what will probably seem like a stupid question but here it goes: I built a programmer (http://www.jdm.homepage.dk/newpics.htm) and programmed a 16F84 with the PP.EXE program. The programmer programmed the chip and then verified it successfully. (Or so the software says). I did a read on the chip and had it dump to a file. Below are a few lines of the original and the dumped hex file starting at line 1 of each. Original Hex :020000000528D1 :08000800052885008B01093079 :100010006600C23062000611031EE22864005830F8 :10002000B6209F20120803110310493A031D05282A Saved Hex :100000000528FF3FFF3FFF3F052885008B01093092 :100010006600C23062000611031EE22864005830F8 :10002000B6209F20120803110310493A031D05282A The original hex lines 3 and 4 are the same as the saved hex lines 2 and 3 but the header? is different. Is this normal? If this is normal can I burn the saved hex to a chip and it operate like the original hex? The reason I ask is that I will be building this project this weekend but I want to know if it is the chip or the circuit if I have problems. I hate to bother you with such a simple question but I am new to pics and am learning slowly. Thanks to everyone for your tips and all the great information that comes through the list. Albert

Albert Noah wrote: {Quote hidden}> > Hello, > > I have what will probably seem like a stupid question but here it goes: > > I built a programmer (http://www.jdm.homepage.dk/newpics.htm) and programmed > a 16F84 with the PP.EXE program. The programmer programmed the chip and then > verified it successfully. (Or so the software says). > > I did a read on the chip and had it dump to a file. Below are a few lines of > the original and the dumped hex file starting at line 1 of each. > > Original Hex > :020000000528D1 > :08000800052885008B01093079 > :100010006600C23062000611031EE22864005830F8 > :10002000B6209F20120803110310493A031D05282A > > Saved Hex > :100000000528FF3FFF3FFF3F052885008B01093092 > :100010006600C23062000611031EE22864005830F8 > :10002000B6209F20120803110310493A031D05282A > > The original hex lines 3 and 4 are the same as the saved hex lines 2 and 3 > but the header? is different. Is this normal? If this is normal can I burn > the saved hex to a chip and it operate like the original hex? > > The reason I ask is that I will be building this project this weekend but I > want to know if it is the chip or the circuit if I have problems. > > I hate to bother you with such a simple question but I am new to pics and am > learning slowly. > > Thanks to everyone for your tips and all the great information that comes > through the list. > > Albert not sure on the exactness but the hex file format uses some type of doubling like everything is 2x or something like that.. I forget.. there are alot of converters out their so you might want to check around... probably http://www.piclist.com in the techref stuff is a good place.. Good luck hopefully someone else will speak up with more knowledge than i have.. Damon Hopkins

<x-flowed>These are equivalent. The first example skipped some blank locations. The second example included the original FIRST line, the blank locations and the original SECOND line all in one line. Both versions are legal HEX. At 01:39 PM 5/25/00, you wrote: {Quote hidden}>Hello, > >I have what will probably seem like a stupid question but here it goes: > >I built a programmer (http://www.jdm.homepage.dk/newpics.htm) and programmed >a 16F84 with the PP.EXE program. The programmer programmed the chip and then >verified it successfully. (Or so the software says). > >I did a read on the chip and had it dump to a file. Below are a few lines of >the original and the dumped hex file starting at line 1 of each. > >Original Hex >:020000000528D1 >:08000800052885008B01093079 >:100010006600C23062000611031EE22864005830F8 >:10002000B6209F20120803110310493A031D05282A > >Saved Hex >:100000000528FF3FFF3FFF3F052885008B01093092 >:100010006600C23062000611031EE22864005830F8 >:10002000B6209F20120803110310493A031D05282A > >The original hex lines 3 and 4 are the same as the saved hex lines 2 and 3 >but the header? is different. Is this normal? If this is normal can I burn >the saved hex to a chip and it operate like the original hex? > >The reason I ask is that I will be building this project this weekend but I >want to know if it is the chip or the circuit if I have problems. > >I hate to bother you with such a simple question but I am new to pics and am >learning slowly. > >Thanks to everyone for your tips and all the great information that comes >through the list. > >Albert Jerry Merrill spam_OUTjerrymTakeThisOuTtech-tools.com http://www.tech-tools.com FAX: (972) 494-5814 VOICE:(972) 272-9392 TechTools PO Box 462101 Garland, TX 75046-2101 Join our PIC discussion list at http://www.tech-tools.com/piclist.htm </x-flowed>

Each line specifies an address and some data to stick there. Typically an assembler or linker will generate the file in the order of the definition of various ROMable chunks, but what is dumped by a debugger or etc. will be in linear address order. Search for "Intel hex file format", or see http://www.8052.com/tutintel.htm {Quote hidden}> Original Hex > :020000000528D1 > :08000800052885008B01093079 > :100010006600C23062000611031EE22864005830F8 > :10002000B6209F20120803110310493A031D05282A > > Saved Hex > :100000000528FF3FFF3FFF3F052885008B01093092 > :100010006600C23062000611031EE22864005830F8 > :10002000B6209F20120803110310493A031D05282A