![]() make sure you are running firmware 1.0. JMPG80D.FIR - relocate Canons startup code, reserve RAM, run our init task, dump ROM1.BIN on the card after 5 seconds (1.0. the digic6-dumper branch (you will have to modify the code and experiment - it won't boot in its current state)įor troubleshooting the above experiment (trying to run code alongside Canon firmware): JMPE80D.FIR - relocate Canons startup code, reserve RAM, jump to Canon firmware (1.0.1 only) JMPF80D.FIR - LED blinking alongside Canon firmware (1.0.1 only). anything compiled from the recovery branch (it runs from bootloader context) check for options the portable ROM dumper (you may have to format the card to a very small size, or dd this 256MB image - howto) the portable display test (copy autoexec.bin and make your card bootable) If anyone wants to fiddle with the code, here's the FIR to enable the boot flag (on any firmware version):Īfter enabling the boot flag in the camera, you may run: However, if JMPC didn't work, the remaining ones won't work either. JMPG_80D.FIR - relocate Canon's startup code, reserve RAM, run our init task, dump ROM1.BIN on the card after 5 seconds (1.0.1 only) JMPF_80D.FIR - LED blinking alongside Canon firmware (1.0.1 only). JMPE_80D.FIR - relocate Canon's startup code, reserve RAM, jump to Canon firmware (1.0.1 only) JMPD_80D.FIR - relocate Canon's startup code without patching it (1.0.1 only) JMPC_80D.FIR - vanilla reboot.c, jump to Canon firmware from copy_and_restart (any firmware version) JMPB_80D.FIR - copy ML, DSB/ISB, then jump to Canon firmware (any firmware version) JMPA_80D.FIR - jump to Canon firmware at 0xFE0A0000 (any firmware version) The outcome might not be always the same, so it's best to try each FIR a couple of times.Īll of them will write the self-modifying code to uncacheable memory (something we didn't try before). They will also execute various stages of loading ML - some may fail (camera will lock up). Let's try it.Īll these FIRs should jump to Canon firmware (in other words, after the Loading screen, the camera should return to normal firmware). In particular, the second link has a concise explanation in the self-modifying code section. ![]() However, the results from previous experiments gave me some ideas for solving the issue of running code alongside Canon firmware. Alright - so the caching issue is still not solved.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |