Messages

1

Camera-specific Development / Re: Canon 80D

« on: January 31, 2019, 04:03:11 AM »

I have compiled and run the changeset with the config requested on the camera I have.
 
-      DEBUGMSG.LOG
 
The camera did not lock up at the beginning with just the standard configuration and allowed me to open the menu, liveView, movie, playback, etc. But at the end of the script (led stopped flashing) it did appear to "lock up" - the screen went blank and no input appeared to make any difference until the power switch was flicked, at which point the led came on for roughly one second. I don’t think it was a full lockup, as I did not have to remove the battery. The file of the log output did appear to complete fully and provide a summary of memory usage. @a1ex if you want more logs to check against just let me know and the best way to get them to you.
 
Current focus has been on understanding trying to understand way CHDK print to screen in an effort to get “helloworld” happening.

2

Camera-specific Development / Re: Canon 80D

« 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.

3

Camera-specific Development / Re: Canon 80D

« on: July 05, 2018, 03:29:57 AM »

Hi all.

Been watching and playing for a while with some others who are studying software development at uni and we would like to get ML on the 80D as a fun but challenging project. We've taken the 80D apart and posted some photos of the main board. If we missed something let me know as there are a few more we took, or we could take it apart again if we really need to (may have to if we need to find anything out about the NFC chip).

Hopefully these photo's will help with something.

4

User Introduction / Hi everyone!

« on: June 29, 2018, 09:23:30 AM »

Hi everyone,

I have an old 450D that I use mostly for scenic shots if I remember to take it out with me when I get out and about. I have access to an 80D and would like to get ML working on that - which is the reason I'm here. Maybe if I get bored I might play with the 450D emulation at a later date but it's probably not worth it.

See you round - probably on the 80D thread