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

EOS M3 porting

  • 746 Replies
  • 428090 Views
*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #370 on: 01 / July / 2017, 03:21:42 »
Advertisements
I've attached a copy of rawopint.lua with set_sv96(sv) replaced (at line 1055) by the code I've been using for years without problems. Will you see if it fixes the ISO problem on the G1X if you have time? Run the script in continuous mode.
Code: [Select]
-- *****lapser sv test
--   set_sv96(self.sv96)
  set_prop(props.DELTA_SV,self.sv96-get_prop(props.SV)+get_prop(props.DELTA_SV))
  set_prop(props.SV,self.sv96)
-- *****lapser sv test
Results of testing https://chdk.setepontos.com/index.php?topic=12697.msg133698#msg133698
M100 100a, M3 121a, 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

Re: EOS M3 porting
« Reply #371 on: 01 / July / 2017, 06:38:39 »
How do you "Load the CHDK Software" for the M3? I've tried searching, but can't find any info.

*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #372 on: 01 / July / 2017, 06:55:59 »
How do you "Load the CHDK Software" for the M3? I've tried searching, but can't find any info.
Why you don't read the first message in this topic?
Did you read
Quote
Only “Bootable SD Card Method” can be used on M3 to run CHDK.
Then copy the content of ZIP File to your card


Switch to playback mode and press "Set" button.
 
M100 100a, M3 121a, 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

Re: EOS M3 porting
« Reply #373 on: 01 / July / 2017, 19:49:29 »
Yes I've read all that. Those instruction worked to allow me to create a dump of the firmware.
I'm now trying to get CHDK running.

I've followed the instructions here: http://chdk.wikia.com/wiki/Prepare_your_SD_card
Using: "Method 3 - Using EOSCard to make the SD card bootable"
I've copied the CHDK files to my sd card, and made it bootable.
I have write protected the SD card and turned the camera on.
Step 5 says: "Now each time that you turn your camera on, the CHDK logo should briefly display automatically, indicating that CHDK has successfully loaded."

There is no logo displayed.
Pressing the Playback button followed by set does nothing.

*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #374 on: 02 / July / 2017, 07:34:56 »
There is no logo displayed.
 
No logo than CHDK is not loaded. Is your Card FAT32? Files in the root directory?

Pressing the Playback button followed by set does nothing.
OK, wrong info. On M3 you have to press ‚M-Fn‘ button
M100 100a, M3 121a, 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

Re: EOS M3 porting
« Reply #375 on: 02 / July / 2017, 20:40:23 »
....I'm now trying to get CHDK running....
....There is no logo displayed....
Just Guessing, that your M3-100d has not yet been up graded to a M3-101a.
see this post:- Re: EOS M3 porting « Reply #161 on: 11/November/2016
also see here https://chdk.setepontos.com/index.php?action=dlattach;topic=12542.0;attach=13536

Is there any valid reason to add the M3-100d when up-dates are available from Canon.
The reason for asking is that I am now planning to up date my two M3-100d,
and I have been working on a  M3-100d version, based on IDA_6v95, which is about 90% complete
but is not yet working.

H-H
« Last Edit: 02 / July / 2017, 20:54:42 by Hardware_Hacker »

*

Offline reyalp

  • ******
  • 14126
Re: EOS M3 porting
« Reply #376 on: 02 / July / 2017, 20:51:58 »
Just Guessing, that your M3 has not yet been up graded to a M3-101a.
If erspark2002 had successfully made the card bootable, they would have seen a black screen or blinking LED when loading the wrong firmware, not a normal boot without the CHDK logo.

The logo not being shown means one or more of
* Files weren't correctly installed
* Card wasn't made bootable
* SD lock was not set, or was not detected by the cam

@erspark2002
Does your camera display "card locked" when you boot?
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 14126
Re: EOS M3 porting
« Reply #377 on: 03 / July / 2017, 15:43:59 »
Lapser reported in a different thread:
I made a run with EOS M3.  There are no differences between original version and lapsers changes.

But, from both runs, the EXIF ISO is always ISO100. The run was made with (RAW+JPG). All files have EXIF ISO100 (RAW+JPG).
I discovered a new propcase on the EOS M3 that sets the exif ISO

  set_prop(pDELTA_SV,sv-get_prop(pSV)+get_prop(pDELTA_SV)) -- sets actual exposure
  set_prop(pSV,sv) -- sets EXIF data
  if eosm3 then set_prop(354,sv) end -- EXIF data on EOSM3

I tried in a test script last night and it worked!
It sounds like either the current the current PROPCASE_SV value is incorrect, or there should be a SV2 propcase, like we have TV2 for some cameras.

edit:
FWIW, G7X uses propcase 354 only for PROPCASE_SV and both override and exif appear correct.

256 does appear to also contain the PROPCASE_SV value
« Last Edit: 03 / July / 2017, 16:16:58 by reyalp »
Don't forget what the H stands for.

*

Offline lapser

  • *****
  • 1093
Re: EOS M3 porting
« Reply #378 on: 03 / July / 2017, 17:13:15 »
It sounds like either the current the current PROPCASE_SV value is incorrect, or there should be a SV2 propcase, like we have TV2 for some cameras.

edit:
FWIW, G7X uses propcase 354 only for PROPCASE_SV and both override and exif appear correct.

256 does appear to also contain the PROPCASE_SV value
I tried only saving propcase 354 on the EOSM3 and it crashed the camera. So I guess there's a new SV2 propcase. It might be prudent to add it to the G7X too?

ROMLOG attached
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline reyalp

  • ******
  • 14126
Re: EOS M3 porting
« Reply #379 on: 03 / July / 2017, 17:52:41 »
I tried only saving propcase 354 on the EOSM3 and it crashed the camera. So I guess there's a new SV2 propcase. It might be prudent to add it to the G7X too?


Just to be clear, you tried changing PROPCASE_SV to 354, and when you used CHDK ISO override after that, it crashed? Or was this only using your script setting the propcases directly? Knowing the details will help me figure out if g7x is affected.

Also, did you check that all of these propcases contain a value that looks like SV96 when you are NOT using any CHDK overrides? E.g. set ISO 100 in the Canon UI (with no CHDK overrides enabled), half press, look at the propcase values. Then set ISO 400, compare. If you use chdkptp, the devutil dpget and dpcmp commands are useful for this kind of thing.

Quote
ROMLOG attached
The filename in the romlog does seem to be ISO related
Don't forget what the H stands for.

 

Related Topics


SimplePortal © 2008-2014, SimplePortal