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

EOS M3 porting

  • 696 Replies
  • 294305 Views
*

Offline c_joerg

  • *****
  • 1151
Re: EOS M3 porting
« Reply #80 on: 13 / July / 2016, 10:40:09 »
Advertisements
Hello,

I ask a guy from German DSLR forum to run my favorite Script on the M3.
https://chdk.setepontos.com/index.php?topic=12697.msg125962
The Result might be interesting for you. Log File is attached.

First interesting think for me:
There is actually an optical temperature! Whether they will but actually measured in the lens, I cannot say . It rises at least in the 14 recordings from 33 to 34 degrees. The sensor temperature increases over the same period from 37 to 39 degrees.
The battery voltage seems to be correct as well.

@reyalp
The Interval was 0.5s. The sleep goes up to 6s. I don’t think that the camera is so slow. Any idea why it happen?
(Update: The picture was made in RAW (32MB) and the SD card was an slow old one....)
This might be an inconsistent of Setting TV and ISO Value or?
tv 361 != cam 576 / sv 380 != cam 632
I don’t think that the Script really controls the cam…

@Ant
Great what you are doing  … One question about you:
There is an official Canon Firmware for the M3 available. Why you don’t make the port with this Version. The might be helpful for other users to use the port right now…



« Last Edit: 13 / July / 2016, 11:36:43 by c_joerg »
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline reyalp

  • ******
  • 13391
Re: EOS M3 porting
« Reply #81 on: 13 / July / 2016, 16:47:34 »
This might be an inconsistent of Setting TV and ISO Value or?
tv 361 != cam 576 / sv 380 != cam 632
I don’t think that the Script really controls the cam…
I'm not clear what source was being run, but I would say it's premature to try. In the last propset.h ant posted, SV, DELTA_SV and SV_MARKET propcases are all marked as not found. If they are wrong, ISO control is impossible, and some other random propcases will be set when the script tries to manipulate ISO.

The SV propcases should be pretty easy to identify and verify. When you set the ISO to a specific setting in the UI, they will change, and SV_MARKET should be the APEX96 value of the set ISO. The SV value will be similar, either identical or offset by some mostly fixed APEX96 value. The difference between SV and SV_MARKET needs to be found and set in platform_camera.h if it isn't the default.

DELTA_SV can be found in camera auto ISO mode, where SV_MARKET + DELTA_SV should equal APEX96 of the camera chosen ISO value. The SV_MARKET in this case will be the CAM_MARKET_ISO_BASE value, which might also need to be overridden.

If they don't exist or can't be found, it would be a big problem for CHDK.

This chdkptp module may be helpful for identifying propcases https://chdk.setepontos.com/index.php?topic=12759.0
Don't forget what the H stands for.

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #82 on: 13 / July / 2016, 17:55:59 »
There is an official Canon Firmware for the M3 available. Why you don’t make the port with this Version. The might be helpful for other users to use the port right now…
Firmware version 1.0.1.a is an official too. At this moment I don't see reasons to waste my time adding support for version 1.1.0 .
Downgrade from 1.1.0 still possible...

you may find that >60 second exposures or extremely short exposures work regardless.
I can not set exposure shorter than 1/4000.
« Last Edit: 13 / July / 2016, 18:01:45 by Ant »

Re: EOS M3 porting
« Reply #83 on: 14 / July / 2016, 12:25:55 »
Hello Ant,
Would you be so kind as to describe me how can I downgrade the firmware from 110 to 101a ?
I have an EOS M3 and would like to test the CHDK.
Thank you in advance.
BR, Wianki


*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #84 on: 14 / July / 2016, 14:14:44 »
Hello Ant,
Would you be so kind as to describe me how can I downgrade the firmware from 110 to 101a ?

Just find somewhere file "eosm3-v101-win.zip" and follow the instructions inside it.

Re: EOS M3 porting
« Reply #85 on: 15 / July / 2016, 16:36:17 »
Hello Ant,
I have already found this file but the standard method doesn’t work.
You only can upgrade but not downgrade the firmware :-(
Do you know any trick?
Thank you in advance.
BR, Wianki

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #86 on: 17 / July / 2016, 04:58:36 »
You only can upgrade but not downgrade the firmware :-(
Do you know any trick?
Just copy EOS_M3.FI2 to SD card and start update from camera's menu.

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #87 on: 17 / July / 2016, 05:35:13 »
It's funny, but I got my camera bricked after experimenting with language menu.
Now camera is in cyclic reboot:
Code: [Select]
<0>#<0>

NotInit
StartDiskboot
<0>

Start Program on RAM

<0>
DRYOS version 2.3, release #0055+p6
Copyright (C) 1997-2013 by CANON Inc.


NotInit
Assert: File CdsTable.c Line 144


 !!!WatchDog expired!!!

 [_imageSensorTask] -> [WdtPrint (LR:0xbfe13575 , PC:0xfc2699a4)]
 [WdtPrint] -> [_imageSensorTask (LR:0xbfe11453 , PC:0x010e1014)]
 [_imageSensorTask] -> [WdtPrint (LR:0xbfe118ad , PC:0xfc2699a4)]
<0>#<0>

NotInit
StartDiskboot
<0>

Start Program on RAM

<0>
DRYOS version 2.3, release #0055+p6
Copyright (C) 1997-2013 by CANON Inc.


NotInit
Assert: File CdsTable.c Line 144


 !!!WatchDog expired!!!

 [_imageSensorTask] -> [WdtPrint (LR:0xbfe13575 , PC:0xfc2699a4)]
 [WdtPrint] -> [_imageSensorTask (LR:0xbfe11453 , PC:0x010e1014)]
 [_imageSensorTask] -> [WdtPrint (LR:0xbfe118ad , PC:0xfc2699a4)]
<0>#<0>

NotInit
StartDiskboot
<0>

Start Program on RAM

<0>
DRYOS version 2.3, release #0055+p6
Copyright (C) 1997-2013 by CANON Inc.


NotInit
Assert: File CdsTable.c Line 144


With help of a1ex I turned on TIO debug UART. Its pinout is the same as on another cameras, and levels are 1.8 volt.
But it's need to be very lucky to get into debug shell. There I found that adjustment data(including model number and serial number) are erased.
Now I am looking the way to restore it from ROM dump...
Does anybody had experience with flash programming on camera?
Which functions I should use for file reading from SD?

P.S. I was surprised finding second flash chip on board(MX29GL640ETXEI). Maybe it used by Zico?


*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: EOS M3 porting
« Reply #88 on: 17 / July / 2016, 06:11:51 »
Does anybody had experience with flash programming on camera?

I did reflash my 60D and 550D with roms from other users, then back with my ROM. Looking into it.

How did you get access to the debug shell? Did you solder two wires to the RX/TX pins you mentioned from your image and applied my QEMU TIO patch from diskboot.bin?

Are you able to get a ROM dump in the bricked state? Can you send me a copy?

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #89 on: 17 / July / 2016, 06:23:26 »
Did you solder two wires to the RX/TX pins you mentioned from your image and applied my QEMU TIO patch from diskboot.bin?
Exactly.

Quote
Are you able to get a ROM dump in the bricked state?
It's very difficult to enter debug shell. I did it only two times from many attempts.
And dumping 32 megabytes on 115200 bit/s speed will take to much time.

I'm not sure that it possible to use file io functions because assert happens before calling CreateTask_spytask

 

Related Topics