Modern SSDs would have some refresh logic of their own but I don't expect that in the cameras.
So, I wondered what could we do about this? Wouldn't it make sense to have a functionality that iterates over the entire ROM area in a read a byte, write a byte, re-read the byte and if it's the same go on while otherwise write again kind of fashion? Just address by address so that even a power outage should ruin little?
Unlike old film cameras, these things shouldn't be expected to be heirlooms that will work 50 or 100 years down the road.
EDIT: The S80 is in that for a reason other than being a cute camera. While I saw one S80 with FW 1.01B the handful of others I looked at were 1.00G or below and there is an "unofficial FW upgrade to 1.00G" which will even work on an existing 1.00G and thus effectively do the refreshing. Whether it works on the 1.01B I didn't dare instruct to try at the time which is where the S80 1.01B port originated... Anyway, this gives the S80 a headstart over most others.
Given that S80 *.fir file and the known 1.00G S80 dump, how complex is the FIR file architecture in this use case? Can a .fir file be created for a given camera with the intent of overwriting the existing FW with a copy of itself? That would do what is needed.
Not to be confused with producing FW updates for cameras that did not originally have the given FW.
Is there any functionality to read/write block wise?
Speaking of the romstarter (essentially, bootloader), there's a good chance that normal firmware updates only do the main firmware, so would not refresh the romstarter. It's quite possible there are other areas a regular firmware update doesn't touch.
I can well imagine that the memory for the firmware is a ping pong memory. Only when the firmware has been completely saved and checked, is it switched over.
Quote from: c_joerg on 22 / December / 2019, 11:15:47My question is actually whether it is possible to carry out a Canon firmware update without a Canon menu?For example, if parts of the firmware in the camera are destroyed.If the main firmware is able to start a diskboot.bin, one could create a special one that is able to reflash the damaged areas. If the damage is extensive enough, many parts of the rom would need to be copied to make diskboot functional.In some cases (erased or damaged main fw start), the bootloader can also resort to starting diskboot.bin - if it finds one on card.AFAIK the bootloader cannot deal with firmware update files.
My question is actually whether it is possible to carry out a Canon firmware update without a Canon menu?For example, if parts of the firmware in the camera are destroyed.
Started by mattkime
Started by acid2000
Started by reyalp
General Discussion and Assistance
Started by koshy
Started by pigeonhill
« 1 2 »
General Help and Assistance on using CHDK stable releases