S6 - PIC12F629 Original hex different than written hex?

[mektrix5000]

Hello,

I'm attempting to write a hex file using the S6 program PIC12F629(DIP8). The written CRC hex file doesn't match the original hex file. I noticed the original hex file contains FFFF in the unwritten/empty fields but the written hex contains 3FFF instead. Attached screenshots of the hex views from Dataman and the log file.

The programmed PIC isn't running correctly so I want to eliminate this as being a potential issue. I've used the same programmer and PIC12F529 Device / Project on other hex files so I'm not sure if there is something i need to edit on this particular hex file. I would've attached the hex file to this post but the forum doesn't allow the *.hex file extension.

Thank you in advance, cheers.

[Dataman (Neil Parker)]

Hello mektrix5000,

The values seen in the buffer are the default blank states of the two devices based on their organisation:

PIC12F629
Organisation: 400h (x14 bit)
Default blank state: 3FFF

PIC12F529
Organisation: 600h (x12 bit)
Default blank state: 0FFF

In general, when working with PIC devices it is a good idea to read a blank device into the buffer before loading your hex file. This way any gaps in your file will have the correct blank state in the buffer.

[mektrix5000]

Hello Neil,

Thank you very much for the reply with that helpful information. I'll try that method and report back with my findings.