EOS M3 porting - page 7 - DryOS Development - CHDK Forum supplierdeeply

EOS M3 porting

  • 746 Replies
  • 401113 Views
Re: EOS M3 porting
« Reply #60 on: 06 / April / 2016, 06:19:16 »
Advertisements
Yes I'll be happy to test the latest firmware (1.0.1).
If you have been using existing port, it would be helpful to know what is working and not. If any other users can chime in, that would be appreciated too.

Since an update to 1.0.1 is available from Canon, I probably won't spend any effort on supporting the older firmware.

I would also like to take part in testing on my EOS M3 with currently firmware 1.0.0 but I can update to 1.0.1 of course. I only dealt with ML on my bigger EOS gear so far. It seems CHDK installation works similar, however, I will need some link and advice on exactly what files to download ... 

*

Offline reyalp

  • ******
  • 14089
Re: EOS M3 porting
« Reply #61 on: 09 / April / 2016, 21:54:11 »
I looked at the existing source a some more and it's less complete than I initially thought. capt_seq was not implemented at all, and it uses propset6 with no modifications. This means that essentially no shooting functions will work.

A developer with the camera is probably required to get it to a useful state.

I did run it through the sigfinder without trouble. Of the stubs that are found, most either agree with the existing stubs_entry_2 or differ only by a veneer.
Don't forget what the H stands for.

Re: EOS M3 Porting Attempt
« Reply #62 on: 10 / April / 2016, 02:24:28 »
I looked at the existing source a some more and it's less complete than I initially thought. capt_seq was not implemented at all, and it uses propset6 with no modifications. This means that essentially no shooting functions will work.

Below is a Quote from a email, about M3 Porting, sent a day ago:-

"...The existing EOS M3 source code is very much a WIP and based on the Sx280 camera..."
"...Some parts are just a direct copy of the Sx280 source code..."
"...And there seems to be some basic (M3) stuff that is not configured correctly..."
"...G7x might be a good alternative choice camera..."

H-H
« Last Edit: 10 / April / 2016, 02:30:53 by Hardware_Hacker »

Re: EOS M3 porting
« Reply #63 on: 23 / May / 2016, 04:49:50 »
Yes I'll be happy to test the latest firmware (1.0.1).
If you have been using existing port, it would be helpful to know what is working and not.
If any other users can chime in, that would be appreciated too.
Eos M3-100d and  Eos M3-101a Port - Progress Report.

The Sig-Finder is working, see the Demo's in the attached Files.
The IDA_6v8-Demo only partially worked, for me.

Note that the attached files are just a comparison between Sig-Finder generated files,
so as to try to understand whats going on between the M10-100a, Eos M3-100d and  Eos M3-101a.

Eos M10 Port - Progress Report is here
https://chdk.setepontos.com/index.php?topic=12758.msg128698#msg128698

H-H


*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: EOS M3 porting
« Reply #64 on: 12 / June / 2016, 15:20:00 »
FYI, the latest QEMU branch from Magic Lantern is able to emulate a large part of the EOS M3 firmware.

Emulation log: EOSM3-qemu.log

More details on ML forum.

Hope it helps.
« Last Edit: 30 / June / 2016, 17:13:26 by a1ex »

*

Offline reyalp

  • ******
  • 14089
Re: EOS M3 porting
« Reply #65 on: 12 / June / 2016, 15:44:29 »
FYI, the latest QEMU branch from Magic Lantern is able to emulate a large part of the EOS M3 firmware.

Emulation log: EOSM3-qemu.log

More details on ML forum.

Hope it helps.
Nice work :D

FWIW, I think an EOS M3 port just needs a motivated developer. Ants codet already boots and display the UI, it just needs someone to implement the other task hooks (capt_seq etc), sort out the propset (probably the same as either G7X or SX60) and work around any differences due to interchangeable lens (things like fl_tbl may be tricky, but it should be possible to fake them in a way that leaves most things functional)

Edit:
Also FWIW, the display may cause trouble for emulation, since the GPU seems to be driven by a separate Xtensa core https://chdk.setepontos.com/index.php?topic=11316.60
« Last Edit: 12 / June / 2016, 15:52:24 by reyalp »
Don't forget what the H stands for.

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #66 on: 25 / June / 2016, 09:54:43 »
capt_seq.c has been implemented based on SX60HS port
now shooting scripts should work...
only for firmware version 1.0.1.a
source code: https://subversion.assembla.com/svn/chdk-m3/trunk/
« Last Edit: 13 / July / 2016, 18:07:55 by Ant »

*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #67 on: 25 / June / 2016, 14:43:44 »
@Ant

Some notes. You seem to be overriding exp_drv_task(), but I don't see a call to apex2us() in capt_seq.c.
Also, as far as I know, Canon has published a newer official firmware a few months ago - you may want to advise the potential users on the firmware version this build requires.


*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #68 on: 25 / June / 2016, 15:20:12 »
I don't see a call to apex2us() in capt_seq.c.
This function is called by address.
It is not easy for me to add support of newer firmware - now only 1.01A
« Last Edit: 25 / June / 2016, 15:28:03 by Ant »

*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #69 on: 25 / June / 2016, 15:42:40 »
I don't see a call to apex2us() in capt_seq.c.
This function is called by address.
We're replacing the original fw function with the CHDK replacement there. Just look at the sx280 or sx60 ports.
You can also try exposure time overrides without overriding exp_drv_task(), you may find that >60 second exposures or extremely short exposures work regardless.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal