Author Topic: DIGIC 7 development (200D/SL2, 800D/T7i, 77D, 6D2)  (Read 274234 times)

shankar101

  • New to the forum
  • *
  • Posts: 25
Re: DIGIC 7 development (200D/SL2, 800D/T7i, 77D, 6D2)
« Reply #400 on: April 30, 2022, 09:55:17 AM »
Hi where did the development reach?? I believe 200d is going to be way better than  eos m for raw.

kitor

  • Developer
  • Senior
  • *****
  • Posts: 350
Re: DIGIC 7 development (200D/SL2, 800D/T7i, 77D, 6D2)
« Reply #401 on: April 30, 2022, 10:03:19 AM »
Unfortunately your beliefs have no backup in any measurable data. We are not even close to any raw capabilities on Digic6+ models, do not expect anything in literally years from now unless a miracle happens.
Too many Canon cameras.

names_are_hard

  • Developer
  • Senior
  • *****
  • Posts: 478
  • 200D idiot
Re: DIGIC 7 development (200D/SL2, 800D/T7i, 77D, 6D2)
« Reply #402 on: June 26, 2022, 06:18:47 AM »
Using MMU patches, I hooked mpu_send() and mpu_recv().  This allowed me to obtain a nice clean log of early MPU messages from 200D.  The same technique will be easy to adapt to all other D7, D8, DX cams.

This should greatly help in improving emulation.  So far I've only logged the very early messages, but in theory this can also log MPU traffic while the camera is exercised, to see how different camera functions work.  Note that the messages as seen by these functions are missing a container layer, so e.g. these two lines (one from my code, one from Qemu logging) are the equivalent message:
Code: [Select]
mpu_send: 06 01 27 00 64 00
[MPU] Received: 08 06 01 24 00 01 00 00  (PROP_CARD2_STATUS - spell #7)
Adding this extra layer for Qemu use looks easy.

The build is from this commit: https://github.com/reticulatedpines/magiclantern_simplified/commit/4d037140ad1c3ea72c16d508de65ddcc13f98a8d

Log (after slight manual cleanup, UART log lines get interlaced sometimes): https://pastebin.com/VmRdvQ9E