Correct me if I’m wrong. The MCBootloader.hex is raw data. There’s no decompression or any further manipulation to be done. So how is the configs past to the programer from the compiler? I set the configs in our PBP and that tells the compiler what you want, the compiler passes this information to the programmer in the HEX file. I open the programer after compiling PBP and I open only a HEX file. So the information must be in the HEX file. Why do you need anything else to set configs? We just locate the config word within our HEX file and replace that word with the information we need and save the file. The config word %0011 1111 0111 0110 or $3F76 would just replace the current $3F72 (in the word pad form of 723F) in the hex file and save!!! Job complete! IF and only IF what appears to be the config word on the next to the last line of the loader is in fact IT. We think the Hex file has instructions for the programmer to write to 2007 (16F87x) so all we have to do is find the word it writes to 2007 and replace it. I know this sounds too easy. A test of Occam’s razor’s edge. OOPs, the checksum got me! Can't change the word in the file so easy. More brainstorming...
Bookmarks