Some good news for those affected by the 64-bit GDB bug:
- Found out why 5D3 GUI wasn't coming up without patching the date/time: it was waiting for... PROP_MPU_GPS (06 04 03 54 00 00 from MPU). After this change, 5D3 GUI booted without GDB (and the date/time dialog could be bypassed by clicking OK)!
- Even better - g3gg0 figured out how to
emulate the real-time clock! This change
superseded a bunch of GDB scripts - no more need to patch the date/time dialog!
-
Exception: 5D2 and 50D appear to use a different RTC chip edit: g3gg0 just solved it!
- EOS M boots Canon GUI (
with the same limitations as EOS M2)
- EOS M and M2 have the date/time dialog left enabled on purpose (to prevent the camera from entering LiveView, which is not emulated)
That means:
- The good news:
to boot the GUI, you no longer need GDB for most models (exceptions: M and M2)
-
The date/time dialog at startup is gone! (exceptions:
5D2, 50D, M and M2)
- More Canon menus navigable without locking up on DIGIC 5 models (because of that GPS property...)
- The bad news: if you want to do actual debugging in GDB, you
will need a 32-bit arm-none-eabi-gdb.
Current status:
- Models able to run the GUI and navigate Canon menu: 16 (most DIGIC 4 and 5, some DIGIC 3).
- Models with major GUI issues: 70D, 5D3 1.2.3.
- Models unable to run the GUI: 6D (
help needed), 7D (hard), all DIGIC 6 models, most VxWorks models.
Final note: if you have QEMU already set up, I recommend installing the new one from scratch - the install script will not delete old patches.gdb files. Or just delete these files manually.