EOS M3 porting [M3] [EOS_M3]

Ant

Is it really necesserily to use 110 firmware?
https://chdk.setepontos.com/d/12542/85

New firmware does not fix the problem with IS control on my Sigma lens:
camera freezes during power-off process for a few minutes with muted display and active IS. It looks like problem is caused by EFLensCom.Disconnect function.

So my question to other developers: how to save something(manual focus value) and how to do something during power-off process?

Hardware_Hacker

ness0013
"...STICK is reading my firmware at 110a...
...Am I out of luck?..."

See:- Magic Lantern ; Topic: Canon EOS M3 (Read 46786 times); Reply #75 on: May 23, 2016;
"...FWIW, Canon posted firmware updates for the M3 and M10:.."
https://www.magiclantern.fm/forum/index.php?PHPSESSID=jppegjjm0828653hlsfkee6vb0&topic=14990.75

Edit #3:- EOS M3 and M10 Firmware Update, 01st June 2016 , 12:00am

"...Changes in Canon Firmware Version 1.1.0 is incorporated with the following functional improvement:- "

"...Improves the autofocus speed for movie when the EF-M 28mm F3.5 IS STM is attached to the EOS M3..."

End of Edit #3

I have two "Good EOS M3-100d", and a "Faulty EOS M3-101a" which I don't intend to Up-Date.

Just guessing from the ML post above there may be Newer Canon Firmware Up-dates available. ??
If so, to download 101a and "Newer" versions, of the encrypted Canon Firmware Up-dates you will
need to enter a valid EOS-M3 or M10 serial Number.

Currently the 101a version is the only version that has a CHDK port that is working.
My "Faulty EOS M3-101a" will only power up via the play key and can only be turned off by removing the
battery or by crashing the camera. ( ??? )
The other strange thing that happens is that the Aspect Ratio is reset to 1:1 when using CHDK ( ??? )
There are also some CHDK stuff that needs to be ported @ CHDK-101a R29.

The 100d version will require a separate CHDK porting attempt.
Using IDA-6v95 (Demo) I have found most of the changes need, but have not yet tested the 100d version.
Note that the IDA-6v95 disassembly will have some differences that will need further investigations.
So, I just create temporary IDA-6v95 disassembly file's, and then a the CHDK file's.

If there is a "NEW" M3 version then a "NEW" M3 version Firmware dump will be needed, and a
link posted.
A "NEW" M3 CHDK version porting attempt will also probably be the required.

Edit #1 Using Acid (Automatic Camera Identifier) to Identify the M3 version.

Acid Ref:- http://www.zenoshrdlu.com/acid/acid.html

Note #1 Acid Down loader won't work for the M3.

Edit #2 See attached Acid Files for EOS M3-100d & M3-101a

H-H

2x "Working" Canon 22mm STM lenses.
3x "Faulty" Canon "Original" lenses.
Lot's of Canon FD "Original" lenses.
1x Sigma 4.5mm Fisheye lens.

Hardware_Hacker

Ant
New firmware does not fix the problem with IS control on my Sigma lens:
camera freezes during power-off process for a few minutes with muted display and active IS. It looks like problem is caused by EFLensCom.Disconnect function.

So my question to other developers:
how to save something(manual focus value)
and how to do something during power-off process?

a/ What "Original Canon" lenses do you have. ??
b/ What "Non Canon" lenses do you have. ??

What happens when you "M" mode. ??

Ref: EOS M3 Canon users Manual:-
(From Memory) "...Shooting with out "Original Canon" lenses is supported in (Four??) modes. ???

H-H

srsa_4c

Ant
and how to do something during power-off process?

Try hooking - directly or indirectly - [tt]task_Bye[/tt] (0xfc131084 on 101a unless I'm wrong). I don't remember anyone doing this, so you'll need to do some research.

how to save something(manual focus value)

This is probably done differently on an ILC camera, so I don't know. The possibility of changing lenses makes this even more complicated.

ness0013

Okay so I got 101a on my camera with little effort thanks to everyone's guidance, however, when I attempt to install the CHDK build onto my card with STICK I am encountered with this error:

Preparing Device disk3 31.9 GB - please wait ...
Making card bootable as FAT32
Command 'diskutil unmountDisk disk3' = 'Unmount of all volumes on disk3 was successful'
return code was 0
Command 'printf "BOOTDISK" | dd bs=1 count=8 seek=0x1e0 conv=notrunc of=/dev/disk3s1' = '!Error

dd: /dev/disk3s1: Permission denied'
return code was 1
Command 'diskutil mountDisk disk3' = 'Volume(s) mounted successfully'
return code was 0
Copying files from /Users/Sherman/Downloads/stick/TEST/ to disk3
Command 'cd "/Users/Sherman/Downloads/stick/TEST/"' = ''
return code was 0
Command 'cp *.* '/Volumes/EOS_DIGITAL/.'' = '!Error
cp: /Volumes/EOS_DIGITAL/.: No such file or directory'
return code was 1
Installation failed - see log for details

Ant

srsa_4cThis is probably done differently on an ILC camera, so I don't know. The possibility of changing lenses makes this even more complicated.

I'm not talking about getting focus value. I whant to be sure that file io system is still active when I save my data to SD card during power-off process.

srsa_4c

Ant
I whant to be sure that file io system is still active when I save my data to SD card during power-off process.

To my knowledge, task_Bye (real name is "Bye") does the things necessary for shutting down the camera. If you replace it with a modified copy, you could try this:

task_Bye:
    push    {r4, lr}
    ldr     r4, =0x8390
    movs    r1, #0        ; wait indefinitely
    ldr     r0, [r4, #8]
    blx     loc_fc302318  ; j_TakeSemaphore
    ...

Put your code right after the TakeSemaphore call. Make sure you block the task until you're done with your operation.

edit:
One more thing. task_Bye has only 512 bytes of stack by default which is not a lot. Take that into account.

Ant

What about using debug unit in Monitor debug-mode for intercepting canon's code?
Potentially we can get 8 breakpoints + 8 watchpoints, but I did not found access to all debug registers...

srsa_4c

Ant
What about using debug unit in Monitor debug-mode for intercepting canon's code?
Potentially we can get 8 breakpoints + 8 watchpoints, but I did not found access to all debug registers...

I won't be able to help with that due to zero experience... Can you even use that facility without attaching external hardware to the DIGIC?

Ant

Why do we need external hardware for our purposes?

srsa_4c

Ant
Why do we need external hardware for our purposes?

The point is, you can't debug the CPU from within the CPU. This "typical" setup also seems to suggest that debugging requires a special hw+sw setup.

Ant

We don't need to debug. We need to call debug exception using breakpoints to intercept ROM functions.

ness0013

ness0013

Preparing Device disk3 31.9 GB - please wait ...
Making card bootable as FAT32
Command 'diskutil unmountDisk disk3' = 'Unmount of all volumes on disk3 was successful'
return code was 0
Command 'printf "BOOTDISK" | dd bs=1 count=8 seek=0x1e0 conv=notrunc of=/dev/disk3s1' = '!Error

dd: /dev/disk3s1: Permission denied'
return code was 1
Command 'diskutil mountDisk disk3' = 'Volume(s) mounted successfully'
return code was 0
Copying files from /Users/Sherman/Downloads/stick/TEST/ to disk3
Command 'cd "/Users/Sherman/Downloads/stick/TEST/"' = ''
return code was 0
Command 'cp *.* '/Volumes/EOS_DIGITAL/.'' = '!Error
cp: /Volumes/EOS_DIGITAL/.: No such file or directory'
return code was 1
Installation failed - see log for details

Hit a brick wall here. If anyone has any suggestions I'm all ears.

srsa_4c

ness0013
Hit a brick wall here. If anyone has any suggestions I'm all ears.

You could try contacting STICK's author (email at the bottom of this page: http://www.zenoshrdlu.com/stick/stick.html ).
Or, find another method for making the card bootable: http://chdk.wikia.com/wiki/Bootable_SD_card (the camera is a post-2010 one, obviously).

ness0013

srsa_4c

ness0013
Hit a brick wall here. If anyone has any suggestions I'm all ears.

You could try contacting STICK's author (email at the bottom of this page: http://www.zenoshrdlu.com/stick/stick.html ).
Or, find another method for making the card bootable: http://chdk.wikia.com/wiki/Bootable_SD_card (the camera is a post-2010 one, obviously).

The option to update the firmware does not exist when I boot the camera using the Play button. Is this unheard of?

I'm willing to do it in the standard menu, but I'm concerned with bricking the camera.

waterwingz

ness0013
Hit a brick wall here. If anyone has any suggestions I'm all ears.

Looks like you are on a Windows box? And maybe trying to run STICK using the stick.bat file? If so, run the stickx.cmd file instead. You screen dump file shows permission errors.

ness0013

waterwingz

ness0013
Hit a brick wall here. If anyone has any suggestions I'm all ears.

Looks like you are on a Windows box? And maybe trying to run STICK using the stick.bat file? If so, run the stickx.cmd file instead. You screen dump file shows permission errors.

Mac running STICK from stick.command. I have also tried running it from stick.jar

waterwingz

ness0013
Mac running STICK from stick.command. I have also tried running it from stick.jar

see https://chdk.setepontos.com/d/12306/5

ness0013

waterwingz

ness0013
Mac running STICK from stick.command. I have also tried running it from stick.jar

see https://chdk.setepontos.com/d/12306/5

It worked! Thanks for your help--I never would have found this on my own.

Unfortunately though the grid feature does not to be working at the moment. It also seems to have some interfacing issues with the EVF-DC1 by showing some scanlines. Both of these are unfortunate dealbreakers.

waterwingz

ness0013
Unfortunately though the grid feature does not to be working at the moment. It also seems to have some interfacing issues with the EVF-DC1 by showing some scanlines. Both of these are unfortunate dealbreakers.

I don't think anyone initially expected CHDK to work with the EOS M3. So any functionality at all is a bonus. Sorry it doesn't fit your needs but it is still very much a "work in progress".

« Previous Page Next Page »