EOS M3 porting - page 27 - DryOS Development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 22 23 24 25 26 [27] 28 29 30 31 32 ... 75   Go Down

EOS M3 porting

  • 746 Replies
  • 417397 Views
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #260 on: 31 / January / 2017, 12:19:43 »
Advertisements
Quote from: c_joerg on 31 / January / 2017, 06:20:46
As @reyalp describes in Reply #81, the propcases for Sv is still wrong.
There were some changes in propcases since Reply #81.
Tv sholuld  be ok.
For Sv try this build.
Logged
*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #261 on: 31 / January / 2017, 12:57:42 »
No sv doesn’t work  :(
But the focal length is still OK. At this time, I used my adapted EF-S 10-18 on 10mm and 18mm.
And the values in the log file are correct. Great job!!!  :) :)
Where does this information come from?
Logged
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
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #262 on: 31 / January / 2017, 13:15:13 »
Quote from: c_joerg on 31 / January / 2017, 12:57:42
No sv doesn’t work  :(
Now PROPCASE_SV and PROPCASE_SV_MARKET are equal to G7X.
You better should ask reyalp about it.

All that I found in firmware according Sv is:
Code: [Select]
loc_FC099EDE
      LDRSH.W R0, [SP,#0x20+var_18]
      MOVS    R2, #2
      ADD     R1, SP, #0x20+var_1C
      STR     R0, [R4,#(dword_1258EC - 0x1258E0)]
      MOVS    R0, #0xFF
      BL      GetPropertyCase_NOEP
      LSLS    R0, R0, #0x1F
      BEQ     loc_FC099EF6
      ADR     R0, aErrorGetsvresult ; "\n\rError : GetSvResult"
      B       loc_FC099F0C
; ---------------------------------------------------------------------------

loc_FC099EF6
      MOVS    R2, #2
      LDRSH.W R0, [SP,#0x20+var_1C]
      MOV     R1, SP
      STR     R0, [R4,#(dword_1258F0 - 0x1258E0)]
      LSLS    R0, R2, #7
      BL      GetPropertyCase_NOEP
      LSLS    R0, R0, #0x1F
      BEQ     loc_FC099F16
      ADR     R0, aErrorGetsvfixresult ; "\n\rError : GetSvFixResult"



Quote
Where does this information come from?
Which information?
Logged
*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #263 on: 31 / January / 2017, 13:31:55 »
Quote from: Ant on 31 / January / 2017, 13:15:13
Which information?

The focal length?
Logged
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
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #264 on: 31 / January / 2017, 13:58:23 »
Previously I was using modified function EFLensComGetFocalLength, because M3 firmware doesn't contain GetLensCurrentFocalLength function.

But it's present in M10 firmware. So now I use the function equal to one of subfunction called from GetLensCurrentFocalLength  on M10.
« Last Edit: 31 / January / 2017, 15:21:02 by Ant »
Logged
*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #265 on: 01 / February / 2017, 11:53:58 »
What’s about the ISO Base?
https://chdk.setepontos.com/index.php?topic=12170.0
Is the ISO Base 200?
Logged
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
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #266 on: 01 / February / 2017, 12:38:25 »
it looks like

Logged
*

Offline reyalp

  • ******
  • 14114
Re: EOS M3 porting
« Reply #267 on: 01 / February / 2017, 16:09:51 »
Quote from: Ant on 01 / February / 2017, 12:38:25
it looks like
It's confusing, but the script tells you what it *should* be, not what it is.

However, camera.h defaults to 200 for DryOS >= 49, so it should be OK.

Another thing to check would be the market to real conversion factors. (SV96_MARKET_OFFSET, ISO_MARKET_TO*, ISO_REAL_TO*)

These can be found by comparing the market and real values after setting ISO in the UI and half pressing. See core/shooting.c for how they are defined and used.


Quote
Now PROPCASE_SV and PROPCASE_SV_MARKET are equal to G7X.
Did you verify that the values look like SV96 values?
« Last Edit: 01 / February / 2017, 16:11:22 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #268 on: 01 / February / 2017, 20:54:17 »
FWIW, market and real ISO seems to be equal on the m10.
Logged
*

Offline c_joerg

  • *****
  • 1251
Re: EOS M3 porting
« Reply #269 on: 02 / February / 2017, 03:52:38 »
Quote from: srsa_4c on 01 / February / 2017, 20:54:17
FWIW, market and real ISO seems to be equal on the m10.

Could you try to run rawopint on the M10, just a couple of shoot, and post the log file….
Logged
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
Pages: 1 ... 22 23 24 25 26 [27] 28 29 30 31 32 ... 75   Go Up
« previous next »
 

Related Topics
SimplePortal 2.3.6 © 2008-2014, SimplePortal