Author Topic: Canon 80D  (Read 209990 times)

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 11833
  • 5D Mark Free
Re: Canon 80D
« Reply #450 on: September 19, 2018, 08:30:56 PM »
I guess, I will start with the most generic thing: Have a blank screen drawn and change the background color. Next up is your example [...]

I suggest starting with something that is known to work. Drawing on the screen from code running alongside main firmware (i.e. after the bootloader stage) is not working yet. For debugging, you've only got LED blinking and file I/O.

Be sure to check the blind edition, in particular its source code.

RavingRover

  • New to the forum
  • *
  • Posts: 23
Canon 80D vs 5D IV
« Reply #451 on: October 04, 2018, 08:05:12 PM »
80D has a DIGIC 6, the 5D IV has a DIGIC 6+, i do not know if either has been shown to be multi-core, but then why should that matter.

I believe i saw that typically the '+' DIGICs were just faster clock speeds, maybe something diff about them, don't know.

The 5DIV has only a sinlge DIGIC, & the 80D.

It appears that the 5DIV is progressing well in its port.

So why does not some/most/all of the 80D port (besides addresses) not benefit from the 5DIV effort and success ?

Just wondering since I have used ML on my old orig M model and do see lovely benefits, ML is nice and would love to see some of its benefits on my 80D as we all would.

Happy porting and much success !!

k!r+

  • New to the forum
  • *
  • Posts: 3
Re: Canon 80D
« Reply #452 on: October 08, 2018, 07:38:04 AM »
Keeping in mind I'm new to both RE and open source projects.

As far as I can tell, most of the camera's with NFC are at a similar stage in emulation. I wonder if it is possible that at least one reason for this is to do with NFC.

Looking at the second Debug log from Dj4n90 (near the end), three lines before the line:

Code: [Select]
ASSERT : ./System/MariusAPI/OmarSysInfo.c, Task = RTCMgr, Line 73
there is the line:

Code: [Select]
   456:  1599.232 ERROR [I2C] I2C_Read[CH1] : 0xa8,0x00,0x01,0x00 (Task : NFCMgr)
which made me think that the ASSERT could be related to this error.

I took the camera apart again to take photo's of the NFC board (sorry not as good as the last ones - ISO was too high). From the code on the chip and the chip pin-out I believe the NFC chip is a Panasonic MN63Y1214. The 0xa8 portion of the error code from Dj4n90's debug log is the standard i2c location for reading from this chip, but I don't know what the rest of the codes are asking for in that error.

Which brings me to my questions:
  • Is this assumption likely correct? Or did I wast my time?
  • If this assumption is correct and the emulation is ceasing because of this NFC error, what are the next steps? NFC emulation?
  • Can NFC emulation be skipped by NOPing NFC related tasks in the ROM1.BIN (for the purpose of camera emulation only)?
  • If the NFC needs to be emulated, how would that be done and where should the code go? (remember I'm new to this...)
  • Can anyone see anything to indicate that I have identified the wrong chip?

Thanks for your help, and hopefully this info will assist somehow.

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 11833
  • 5D Mark Free
Re: Canon 80D
« Reply #453 on: October 08, 2018, 08:16:54 AM »
Omar is a secondary CPU; from what I could tell, it does not use I2C at all. The two lines happen to be adjacent because of multitasking.

In particular, the Omar initialization is started in startupPrepareCapture; the patches from 80D/patches.gdb are trying to bypass it, without much success.

I don't think missing NFC emulation does any harm (there are I2C warnings on other cameras that boot the GUI, and you can patch either the I2C routine or the entire NFC task). There are a bunch of debug functions registered for NFC, which makes it a fairly low-hanging fruit for investigating how it works. Some info from real hardware in this log:
With b35a216 as last changeset:
- log
Code: [Select]
2BE98>     NFCMgr:fe71aee7:4d:03:  nfcmgrstate_Initialize:NewsDet_R Hi
2BEF5>     NFCMgr:fe168615:00:01: [I2C] I2CD_Initialize
2BF12>     NFCMgr:fe168683:00:01: [I2C] I2CD_Com mode[3], devAddr[0xA8]
2BF31>     NFCMgr:fe167ec7:00:01: [I2C] CH1 bus ready
2BF46>     NFCMgr:fe167ec7:00:01: [I2C] CH1 bus ready
2BF60>     NFCMgr:fe168465:00:01: [I2C] read start condition
2C03B>   PowerMgr:001ccab0:00:0f: INT-0DDh FE167F29(0)
2C069>     NFCMgr:fe168187:00:01: [I2C] read stop condition
2C091>   PowerMgr:001ccab0:00:0f: INT-0FDh FE167FC7(0)
2C0AB>   PowerMgr:fe2807ed:00:01: [I2C] SIRQ
2C0BC>     NFCMgr:fe168709:00:01: [I2C] CH1 Init

On the other side, I'm pretty sure the incomplete Omar initialization is holding back the startup process (unlike DIGIC 5 models, where Eeko initialization is pretty much skipped without major side effects); this is because other initialization routines are waiting for this step to complete. Unfortunately, Omar communication is not exactly easy to figure out, at least for me. RE notes in the Eeko thread.

To log the info required to emulate this stuff, one has to port the MMIO tracing backend:
- https://bitbucket.org/hudson/magic-lantern/pull-requests/900/mmio-tracing-backend-insanely-powerful
- https://bitbucket.org/hudson/magic-lantern/commits/0a2e116 (same technique in a different context, allowing C callbacks)

If that works, we'll get a huge log with every MMIO access performed by the main CPU, i.e. several megabytes of numbers that have to be interpreted to figure out their meaning, or replayed somehow in the emulator. If there's any more energy left after dealing with trolls, that is.

Thanks for identifying the BLE chip. The pinout makes sense to me (direct link, as it took me a while to find the picture). FYI, @ids1024 managed to reverse the protocol:
https://iandouglasscott.com/2018/07/04/canon-dslr-bluetooth-remote-protocol/

Hubuki

  • New to the forum
  • *
  • Posts: 1
Re: Canon 80D
« Reply #454 on: October 25, 2018, 07:18:42 PM »
Is there a a download for the 80d yet?
Please Please Please say yes!! T^T

nagamayasi

  • New to the forum
  • *
  • Posts: 4
Re: Canon 80D
« Reply #455 on: November 04, 2018, 05:53:10 PM »
please download link for canon 80d

ricflair4life

  • New to the forum
  • *
  • Posts: 5
  • Canon 80d for the win
Re: Canon 80D
« Reply #456 on: November 23, 2018, 09:06:11 AM »
Happy late thanksgiving, everyone! I’m PayPal’ing the person who can provide a working magic lantern for the 80d. Seriously, I check this thread several times a day everyday.. what’s going on???

nagamayasi

  • New to the forum
  • *
  • Posts: 4
Re: Canon 80D
« Reply #457 on: November 25, 2018, 09:21:28 AM »
Happy late thanksgiving, everyone! I’m PayPal’ing the person who can provide a working magic lantern for the 80d. Seriously, I check this thread several times a day everyday.. what’s going on???
yes same with me,
everyday i chehk this thread, and still waiting for magiclantern working on canon 80d.
from 2016....  :-[

theBilalFakhouri

  • Member
  • ***
  • Posts: 234
Re: Canon 80D
« Reply #458 on: November 25, 2018, 10:11:43 AM »
I don't think the right person has arrived to work on this camera seriously.

If you are ready to pay I will suggest to start an offer in freelancer.com for "Making Magic Lantern working in 80D" maybe we will catch him there  :D
700D 1.1.5 | no more ISOless LV err 8

polkah

  • New to the forum
  • *
  • Posts: 1
Re: Canon 80D
« Reply #459 on: November 26, 2018, 03:52:06 PM »
Happy late thanksgiving, everyone! I’m PayPal’ing the person who can provide a working magic lantern for the 80d. Seriously, I check this thread several times a day everyday.. what’s going on???
Yeah, we should make a kickstarter to fund anyone that would make a working port for 80d