Bootable SD Card Method with real Firmware - General Help and Assistance on using CHDK stable releases - CHDK Forum  

Bootable SD Card Method with real Firmware

  • 3 Replies
  • 357 Views
Bootable SD Card Method with real Firmware
« on: 22 / December / 2019, 06:15:10 »
Advertisements
What happens, if a SD card is prepared for the Bootable SD Card Method and there is only a real Firmware on the card?
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline srsa_4c

  • ******
  • 4285
Re: Bootable SD Card Method with real Firmware
« Reply #1 on: 22 / December / 2019, 10:39:10 »
What happens, if a SD card is prepared for the Bootable SD Card Method and there is only a real Firmware on the card?
Nothing, unless you enter the Canon menu, find the "firm update" entry and click on it.

Re: Bootable SD Card Method with real Firmware
« Reply #2 on: 22 / December / 2019, 11:15:47 »
Nothing, unless you enter the Canon menu, find the "firm update" entry and click on it.
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.
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline srsa_4c

  • ******
  • 4285
Re: Bootable SD Card Method with real Firmware
« Reply #3 on: 22 / December / 2019, 12:33:42 »
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.
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.


 

Related Topics