EOS M3 porting - page 17 - DryOS Development - CHDK Forum

EOS M3 porting

  • 746 Replies
  • 385144 Views
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #160 on: 11 / November / 2016, 17:02:13 »
Advertisements
Is it really necesserily to use  110 firmware?
https://chdk.setepontos.com/index.php?topic=12542.msg129314#msg129314

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?
« Last Edit: 11 / November / 2016, 17:35:27 by Ant »

Re: EOS M3 porting
« Reply #161 on: 11 / November / 2016, 19:04:43 »
"...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.
« Last Edit: 16 / November / 2016, 00:38:51 by Hardware_Hacker »

Re: EOS M3 porting
« Reply #162 on: 11 / November / 2016, 19:36:35 »
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

*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #163 on: 11 / November / 2016, 20:29:58 »
and how to do something during power-off process?
Try hooking - directly or indirectly - task_Bye (0xfc131084 on 101a unless I'm wrong). I don't remember anyone doing this, so you'll need to do some research.
Quote
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.


Re: EOS M3 porting
« Reply #164 on: 12 / November / 2016, 00:01:09 »
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:

Quote
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

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #165 on: 12 / November / 2016, 02:14:54 »
This 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.

*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #166 on: 12 / November / 2016, 06:07:34 »
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:
Code: [Select]
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.
« Last Edit: 12 / November / 2016, 06:28:02 by srsa_4c »

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #167 on: 12 / November / 2016, 07:29:11 »
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...


*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #168 on: 12 / November / 2016, 07:46:56 »
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?

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #169 on: 12 / November / 2016, 08:51:54 »
Why do we need external hardware for our purposes?

 

Related Topics