Hex isn't problem. You can have configs in hex, but application that parse hex file should ignore configs and send only program and eeprom to bootloader. I post simple bootloader code somewhere on forum.
Hex isn't problem. You can have configs in hex, but application that parse hex file should ignore configs and send only program and eeprom to bootloader. I post simple bootloader code somewhere on forum.
The 16F series isn't even capable of reprogramming their own CONFIG word(s). For example, on the 16F819, the CONFIG word is at address 2007h and the datasheet saysIt also saysIt is important to note that address 2007h is beyond the
user program memory space which can be accessed
only during programming.So if you TRIED to write to the CONFIG word you'd actually write to another location possibly corrupting the program.Accessing a location above the
physically implemented address will cause a
wraparound.
So yeah, you need to be carefull of what you're doing. I'm curious, the 16F819 doesn't have an UART, are you planning to use bitbanged serial for the download or are you going to inject the new firmware image in some other way (SPI, I2C)?
/Henrik.
Hi Team,
Pedja089 I will search for your post, thank you.
Henrik, I will have a friend of mine, who knows more assembly than I do, helping with this project.
We are trying to make small changes, to fit our needs, to this project I found in my research:
http://pygmy.utoh.org/pikme/
Right now we are collecting as much information as we can to make sure we are taking the right path.
Thank you for your advices and interest.
Nick
Bookmarks