Question about the .HEX file living update
I'm trying to develop a code to do the flash living update. Here I found a wield thing. The device is PIC32MZ2048EFH144.
1, If I do not do the boot flash erasing(protected), and only erase the program flash --- itself's .HEX file can be written down, and system can reboot normally.
2, If I do the boot flash erasing(unlocked), and also erase the program flash --- itself's .HEX file also can be written down, but the system can not reboot. In this case, even I reset the power, no difference.
However, I didn't find any error about the .HEX writing.
I had read the flash by ICD3 just after the chip had been programmed by the IDE v5, saved it to an new .HEX file; and compared it with the unable-reboot-flash-read-back.HEX file, they are exactly same.
I also use the IPE write the unable-reboot-flash-read-back.HEX file back to he device, the device works normally.
Is there any hidden operation steps need to do except the boot/program flash writing?
post edited by KevinHuang - 2020/08/08 18:44:25