EOS M100 porting - page 14 - DryOS Development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 9 10 11 12 13 [14] 15 16 17 18 19 20   Go Down

EOS M100 porting

  • 198 Replies
  • 40887 Views
*

Offline reyalp

  • ******
  • 13950
Re: EOS M100 porting
« Reply #130 on: 14 / September / 2021, 15:34:59 »
Advertisements
Quote from: Caefix on 14 / September / 2021, 12:18:56
Unexpected fun detected...  :D
md_tune.bas tells min 10, max 150, avg ~70.
md_detect works fine in <play> && with the touchscreen.
:blink:
There is no meaningful way MD can "work" in play, but as so often happens, I really have no idea what you are trying to describe.

Quote
Since my cam´s CRC has "changed", I have turned the check off in debug menu & turned it on again for the updated build.
As I previously explained
Quote from: reyalp on 11 / August / 2021, 15:44:22
That said, it looks like the first difference in the dump (at offset 0x204dc) corresponds to an address modified by MMU hacks in the m100 source I have (sub/100a/replaced.c BL_INSTR_T1(0xE00204DC, 0xE04470E2); )

So it seems the CRC check is not compatible with this port.
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • *****
  • 940
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #131 on: 14 / September / 2021, 16:07:17 »
Quote from: reyalp on 14 / September / 2021, 15:34:59
So it seems the CRC check is not compatible with this port.
Maybe to #ifdef out that address?

md_tune.bas tells nice min 10, max 150, avg ~70 on M100...      :-X
Somthing seems strange on M3-X, couldn´t trap it yet, maybe tomorrow...

Edit: It´s more the total runtime, that surprises me... :-[
The Mins are due to different uBasic, maybe even the total?
Edit2: Added table researched on modified M3 classic, very close to M3-X.
Edit3: M3-X+other uBasic reproduced the last table a bit better. :haha
Edit4: Now M100 with reduced Pixel Step (was 6 so far) to slow it down to M3´s speed, next  :blink:, appended tables.
Code: [Select]
!MD_tune.bas           Min, Max, Avg, Total sec/20triggers
M100-0xCAEF-6014
 "Channel: U chroma"     0, 90, 20,    21
 "Channel: Y Luminance"  0, 30, 15,    21
 "Channel: V chroma"     0,130, 19,    21
 "Channel: Red"         10,130, 63,    22
 "Channel: Green"       60,110, 80,    31
 "Channel: Blue"        10,140,100,    24

M3-Ximr-6006
 "Channel: U chroma"    40, 80, 60,    26
 "Channel: Y Luminance" 40, 80  56,    26
 "Channel: V chroma"    30, 70, 55,    27
 "Channel: Red"         50, 70, 60,    33
 "Channel: Green"       60,110, 82,    47
 "Channel: Blue"        50, 80, 60,    34
 "Channel: Blue"       110,180,154 ,   30
M3-0xCAEF-6014
 "Channel: U chroma"    30, 70, 55,    25
 "Channel: Y Luminance" 40, 70, 56,    25
 "Channel: V chroma"    30, 70, 54,    26
 "Channel: Red"         50, 70, 60,    33
 "Channel: Green"       50,110, 70,    46
 "Channel: Blue"        50, 80, 62,    33
PS9  PID:12953 Dig60
2 IS0 ND0 (6)<1
Av=13 Tv=5  |-> 0
Channel: Blue
20 Total: 33 Sec ----


Pixel Step=5
 "Channel: U chroma"     0,130,100,    25
 "Channel: Y Luminance" 80,130,114,    24
 "Channel: V chroma"    30,130,112,    24
 "Channel: Red"          0,130, 60,    25
 "Channel: Green"       10,100, 45,    42
 "Channel: Blue"        10,120, 57,    25
Pixel Step=4
 "Channel: U chroma"    50,110, 77,    32
 "Channel: Y Luminance" 50,110  78,    32
 "Channel: V chroma"    20,100, 72,    32
 "Channel: Red"         10,130, 75,    41
 "Channel: Green"       40,120, 83,    61
 "Channel: Blue"        10,140, 78,    41

!MD_tune tuned to log...
Quote
PS12  PID:13009 Dig70
2 IS2 ND0 (3)<1
Av=11 Tv=16  |-> 0
Channel: V chroma
20 Total: 21 Sec ----
« Last Edit: 18 / September / 2021, 13:51:49 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 13950
Re: EOS M100 porting
« Reply #132 on: 18 / September / 2021, 18:12:39 »
Quote from: Caefix on 14 / September / 2021, 16:07:17
Quote from: reyalp on 14 / September / 2021, 15:34:59
So it seems the CRC check is not compatible with this port.
Maybe to #ifdef out that address?
You should be able to define FIRMWARE_CRC_DISABLED in firmware_crc_data.h to disable the check, or use the --custom-blocks option to make-fw-crc.py to manually create a firmware_crc_data.h that avoids the MMU hacked regions.

If this port ever gets added to SVN, we should implement a way to do this that doesn't involve modifying the auto-generated file (like bin_comp_fix.h) but for now I don't really care.

I am unable to parse the rest of the post.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M100 porting
« Reply #133 on: 19 / September / 2021, 18:11:39 »
Hooktest seems to succeed with the relocated remote hook (, but only if "Unsafe IO" is enabled in the Misc menu. Without that enabled, the script halts because it can't write the log file. I also defined FIRMWARE_CRC_DISABLED as suggested by reyalp.
Logged
*

Offline Caefix

  • *****
  • 940
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #134 on: 20 / September / 2021, 14:25:35 »
Now my M100 seems compatible with rawopint.lua in cont / 4sec interval...  :)
« Last Edit: 20 / September / 2021, 14:48:58 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline c_joerg

  • *****
  • 1241
Re: EOS M100 porting
« Reply #135 on: 23 / September / 2021, 10:15:20 »
Quote from: srsa_4c on 19 / September / 2021, 18:11:39
Hooktest seems to succeed with the relocated remote hook (, but only if "Unsafe IO" is enabled in the Misc menu. Without that enabled, the script halts because it can't write the log file. I also defined FIRMWARE_CRC_DISABLED as suggested by reyalp.
Rawopint works now very well also with my manual lens.  :)
Tested with cont and normal mode.
Good job  :)
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 Caefix

  • *****
  • 940
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #136 on: 29 / September / 2021, 11:41:32 »
Code: [Select]
exec require'camtests'.runbatch{bench=true,shoot=true,filexfer=true,xfersizebugs=true} :) 26/0  with "cam does not support remote capture, skipping"
Logged
All lifetime is a loan from eternity.
*

Offline c_joerg

  • *****
  • 1241
Re: EOS M100 porting
« Reply #137 on: 07 / November / 2021, 11:33:52 »
An interesting behavior that I only noticed with the M100 so far:

A time lapse (rawopint) with an interval of 6s and a maximum exposure time of 4s. Recordings only RAW. All of my other cameras have no problem with that.

The M100 couldn't get around with the settings at the beginning (see sleep curve). The interval then went to 7s. I find the shape of the sleep curve interesting.

It does not seem to be directly dependent on ISO or TV. All automatic settings such as noise reduction were switched off.

I'll try to see if I can reproduce it.
The log file can be found here:
https://chdk.setepontos.com/index.php?topic=12761.msg147263#msg147263


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 psxpetey

  • *
  • 20
Re: EOS M100 porting
« Reply #138 on: 20 / April / 2022, 15:12:33 »
looks like the m100 is really coming along is there a working nonwrking feature list and current file I can use to boot chkd with the ost working features for testing?:)
Logged
*

Offline Caefix

  • *****
  • 940
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #139 on: 20 / April / 2022, 16:12:14 »
Logged
All lifetime is a loan from eternity.
Pages: 1 ... 9 10 11 12 13 [14] 15 16 17 18 19 20   Go Up
« previous next »
 

Related Topics