ian wrote:I'll add address evaluation to the bootloader.
Definitely a good idea.
btw, belated thanks for the posting in "OLS files and utilities
"! Can you edit it have the 2.01 release? I'd like to avoid burning anyone who tries updating to 2.6 firmware... :-(
Unfortunately i got burnt yesterday before i saw this (oh well that will teach me for jumping in to quickly) and i did see the warning in the winloader dialog box but went ahead anyway as i do have a pickit2 and thought it wouldn't be much of a problem to reflash the bootloader if i had to .
I had upgraded to meta4 core and then went to upgrade pic to v2.6 and it crashed and appeared to break the bootloader so i got out my pickit2 soldered a header on the board and flashed this bootloader OLSv1-DUMP-FW21BL2-16MHz and that appeared to work as now OLS is working again.
There is still a problem however, i now can no longer update the pic with any version of fw_update or either version of ols_winloader.With fw_update it tells me device not found and ols_winloader v2.01 states that the file i am trying to burn is 8 bytes too small and if i proceed anyway i get error reading file failed file to large for fpga flash rom.V2.0 just says error writing pic firmware. Windows is seeing it as a comm port with vid 04d8 & pid fc92 .It is also possible to flash any version of the firmware using pickit2 and they work.
"Careful, those last 8 bytes are the config words, we need to protect that page because the firmware ships without them, and there are both 20mhz and 16mhz crystal OLSes."
Could this be the problem , i really am not sure because i thought that the config bytes are set in the code i.e in the hex file i burnt.
My board is marked v1.01 with 16mhz crystal.
Any ideas how to solve this