pjkim wrote:Tried the new firmware. Didn't go particularly smoothly but eventually got things working.
I didn't use diolan earlier, I put hex that I used myself, now, it behaves kinda weird, sometimes bootloader loads, sometimes don't ... but in anyhow hex for the SID don't really have anything to do with bootloader, so you can compile whatever diolan bootloader you like and .... I also could not get diolan's fw_update to run from linux .. something weird ... anyhow I'm not really a big fun of bootloaders on the projects like this one, you get way more control using pickit
pjkim wrote:I say sort of because the EEPROM values were again corrupted.
When you attach pickit and read values (after you update firmware with bootloader) does the eeprom show values that I posted on that picture?
pjkim wrote:Any idea why I am having the same problem programming the EEPROM using a serial PIC programmer and a bootloader?
no clue ... what I did notice is that by default fw_update does not update eeprom at all, there's
- Code: Select all
-m -memory <MEMMORY TYPE>
Memory type for read, write and verify operations.
Possible values: flash, eeprom, id, all.
so if you do not specify -m all diolan will only update flash (eeprom should stay untouched but .. who knows)
also it's weird that using direct programming you have this issues too .. maybe it's something wrt your programmer? I use pickit2 for this 18F chips, never had a problem.
pjkim wrote:And thank you Arhi and Arakis. And Ian too.
thank you for debugging it :)