Thanks for your answer I will read your link and try run-code-gen. I checked the difference between the stubs_entry.S and funcs_by_adddress.csv and there are a lot of difference.
Yes. Looking at funcs_by_address.csv, we see the code part of the ROM differs after 0xff16bf58 task_ImageSyncController, before ConnectPtpIPService_FW (this makes sense given the update appears related to network functionality
https://www.usa.canon.com/support/canon-product-advisories/Firmware-Notice-PowerShot-SX-420-IS-Firmware-Version-1-1-0-0)
100a
0xff16bf58,task_ImageSyncController
0xff171adc,ConnectPtpIPService_FW
110a
0xff16bf58,task_ImageSyncController
0xff171b58,ConnectPtpIPService_FW
Additionally, looking at stubs_entry.S, we can see that RAM variable addresses change, somewhere after
canon_menu_active ,0x00003f58
and before focus_busy (0x7a**).
So in addition to rebuilding stubs_entry and running code-gen, we need to make sure anything in stubs_entry_2.s, stubs_min.S and any of the lib.c files in the changed address ranges are updated.
Notice also that MEMISOSTART has changed, so that needs to be updated in makefile.inc
Given how much has changed, you
should not attempt to run a build that has not had all the affected files checked.
I tried run-gen-code without problem and remake fir.
I tried the DISKBOOT.BIN but it didn't work.
Again, it would be helpful if you explain what you mean by "didn't work". Your problem could either be that the card is not prepared properly, or that your build doesn't work. If the camera boots normally without any sign of CHDK, then it's the former. If it appears not to power on at all, it's probably the latter.
I am not sure how to run DISKBOOT.BIN, I just make the card bootable with EOSCard and copy the DISKBOOT.INI on the card. Do I need other file to boot from the card?
You need prepare the card as you would for any CHDK build, described on
https://chdk.fandom.com/wiki/Prepare_your_SD_cardYour camera supports booting from FAT32, but not exFAT. If the card is larger than 32 GB, it will be formatted exFAT by default.
When using EOSCard, you need to be sure you choose the CHDK option not the EOS option. The UI is somewhat confusing.
If you have a card which was already working with the 100a build, and you have not re-formatted it or changed the boot setting with EOSCard etc, you can just copy your files to the card. Strictly you should only need the DISKBOOT.BIN and the .FLT files in CHDK/MODULES, but you can use make firzipsubcomplete to get a full build in a zip, and then unzip that onto your SD.
