EOS M100 porting - page 2 - DryOS Development - CHDK Forum supplierdeeply

EOS M100 porting

  • 67 Replies
  • 6802 Views
*

Offline srsa_4c

  • ******
  • 4285
Re: EOS M100 porting
« Reply #10 on: 04 / September / 2020, 11:57:47 »
Advertisements
Is a funcs_by_name.csv available for the M100?
A somewhat outdated version is in the .diff attached to 2nd post (it is a text file). Or, you could compile finsig_thumb2 using CHDK trunk source and use it on your fw dump.
I'm currently planning to make use of the MMU of the CPU and try a non-traditional port.

*

Offline srsa_4c

  • ******
  • 4285
Re: EOS M100 porting
« Reply #11 on: 11 / September / 2020, 14:49:06 »
It turned out that this camera does not allow permanent exmem allocations. For example, it's possible to trigger an assert by using the backup module and then trying to record a video. So, OPT_EXMEM_MALLOC is out of the question. There's 1GB RAM in this thing, but I'm having a hard time finding a few MB of it that isn't used for something.

*

Offline Caefix

  • ****
  • 288
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #12 on: 12 / September / 2020, 11:52:21 »
There's 1GB RAM in this thing, but I'm having a hard time finding a few MB of it that isn't used for something.
:o Seems to be a mainstream brain?  :-X  :haha

Code: [Select]
int i=0; while (i<1); {i++;}  // No compilerwarning, but... Exception!! Vector 0x0C
« Last Edit: 12 / September / 2020, 15:14:04 by Caefix »
All lifetime is a loan from eternity.

*

Offline srsa_4c

  • ******
  • 4285
Re: EOS M100 porting
« Reply #13 on: 13 / September / 2020, 06:02:57 »
Code: [Select]
int i=0; while (i<1); {i++;}  // No compilerwarning, but... Exception!! Vector 0x0C
Can you please not post unrelated things in this thread?
Anyway, I don't know where you placed that line of code, but it does something you may not have intended. Look for an extra character...


Re: EOS M100 porting
« Reply #14 on: 17 / September / 2020, 02:21:23 »
A somewhat outdated version is in the .diff attached to 2nd post (it is a text file).

Thanks.
I’m locking for GetCameraInformationData_FW which I found in .diff.

On my M3 I called the function by address and made a memory dump with chdkptp.
Code: [Select]
rmem 0x10 0x02000000 -f=filenameIn the dump I look for <CameraInfo> with gives a lot of information about shutter count and errors.
https://chdk.setepontos.com/index.php?topic=12542.300

Is it possible to call the function with Canon Basic and make a memory dump like a firmware dump?
M100 100a, M3 101a, 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 srsa_4c

  • ******
  • 4285
Re: EOS M100 porting
« Reply #15 on: 17 / September / 2020, 11:48:12 »
In the dump I look for <CameraInfo> with gives a lot of information about shutter count and errors.
(...)
Is it possible to call the function with Canon Basic and make a memory dump like a firmware dump?
I found a related eventproc that can produce an xml file. I don't know if the content is the same, but it's worth a try.
Code: [Select]
private sub Initialize()
    System.Create()
    CamInfo_Debug(1)
end sub

Re: EOS M100 porting
« Reply #16 on: 17 / September / 2020, 14:18:03 »

Thanks :)
That’s works very well on M100.
Two differences to my old M3 dump:

1) No ErrorLog, but maybe there are no Errors
2) No Battery Authentication

Should the script also work with the M3?
It didn't work with the M3 but, as always, with the M100 I needed several attempts. :(


Would that also work with the EOS R cameras?
« Last Edit: 17 / September / 2020, 14:26:25 by c_joerg »
M100 100a, M3 101a, 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

  • ****
  • 443
Re: EOS M100 porting
« Reply #17 on: 17 / September / 2020, 15:07:30 »
2) No Battery Authentication

This is because M100 uses LP-E12.
AFAIK LP-E17 still hasn't been fully cloned
« Last Edit: 17 / September / 2020, 15:13:04 by Ant »


*

Offline srsa_4c

  • ******
  • 4285
Re: EOS M100 porting
« Reply #18 on: 17 / September / 2020, 15:14:41 »
Would that also work with the EOS R cameras?
Apparently, yes. All DIGIC 8 (and X) models I have a dump for have this eventproc. The same script would work on all of them (PowerShot, EOS M, EOS R).

Re: EOS M100 porting
« Reply #19 on: 18 / September / 2020, 02:27:03 »
« Last Edit: 18 / September / 2020, 02:32:57 by Yourboylloyd »

 

Related Topics