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

EOS M100 porting

  • 194 Replies
  • 32982 Views
*

Offline Ant

  • *****
  • 509
Re: Re: eos M10 port
« Reply #170 on: 25 / June / 2022, 09:47:31 »
Advertisements
But that assumes you have access to the original firmware version, ie the one that CHDK is happy with.
I don't understand why you need the original firmware if CHDK supports 110d, 110f, 110g, 111a

Re: Re: eos M10 port
« Reply #171 on: 25 / June / 2022, 09:49:56 »
I think we are confusing things. I’m talking about an M100 ;-)

*

Offline Ant

  • *****
  • 509
Re: Re: eos M10 port
« Reply #172 on: 25 / June / 2022, 10:43:54 »
@pigeonhill
In theory you can create a fi2 file from M100 100a firmware dump but it's little bit risky.

Re: Re: eos M10 port
« Reply #173 on: 25 / June / 2022, 11:08:15 »
@Ant I’ve taken a punt on an M100, not knowing the firmware version. The only risk is I’ll need to send it back to the seller, ie postage cost.

Should arrive Monday: fingers crossed ;-)


*

Offline c_joerg

  • *****
  • 1220
Re: Re: eos M10 port
« Reply #174 on: 25 / June / 2022, 14:03:40 »
Why M10 can not downgrade if M3 can downgrade?

We talking about the first Firmware of M100.

In theory you can create a fi2 file from M100 100a firmware dump but it's little bit risky.

Sure that it works?

A lot of offtopic for M10...
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 Ant

  • *****
  • 509
Re: Re: eos M10 port
« Reply #175 on: 25 / June / 2022, 15:05:54 »
Sure that it works?
Not sure. I have no FI2 keys for M100. Maybe @srsa_4c can help.
Also fi2enc utility need to be modified to generate fi2 file with multiple data blocks.

*

Offline Caefix

  • *****
  • 856
  • Sorry, busy deleting test shots...
Re: Re: eos M10 port
« Reply #176 on: 25 / June / 2022, 15:35:58 »
https://my.canon/en/support/0400540202
A ptp issue should be solved.
The first canon upgrade of M3, M10 and M100 have that in common.
If the differences are already known/extractable from the other ports, it might be easier to upgrade port then to risk Firmware´s downgrade.
&& Both ways will be more expensive than changing camera... :haha
 
All lifetime is a loan from eternity.

*

Offline srsa_4c

  • ******
  • 4450
Re: Re: eos M10 port
« Reply #177 on: 25 / June / 2022, 15:41:20 »
Also fi2enc utility need to be modified to generate fi2 file with multiple data blocks.
No, that would be unnecessary unless the aim is to possibly destroy the camera. It would be much easier to just reuse the updater extracted from FI2 (the part that runs from RAM) and replace its FI2 parser/flasher code with a custom flasher routine (one could flash back an older ROM dump, completely, leaving out just the bootloader).
I ported most of the 100a port to 110b, but I did not feel like releasing that due to the experimental and buggy nature of the port.

The reason there is still no official release is that I'm not satisfied with stability (and I wasn't working on it lately). For example, a r6048 based build just crashed on me, and it fails to mask the "jogdial" in ALT mode for some unknown reason.


*

Offline Caefix

  • *****
  • 856
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #178 on: 25 / June / 2022, 16:18:30 »
Strange, my 6087 build is fine, jogdial too,
 6112 ... no function at all   :-[ , 1* green LED every 20 sec when trying to start...
« Last Edit: 25 / June / 2022, 16:42:10 by Caefix »
All lifetime is a loan from eternity.

*

Offline Ant

  • *****
  • 509
Re: Re: eos M10 port
« Reply #179 on: 25 / June / 2022, 16:23:48 »
It would be much easier to just reuse the updater extracted from FI2 (the part that runs from RAM) and replace its FI2 parser/flasher code with a custom flasher routine (one could flash back an older ROM dump, completely, leaving out just the bootloader).

As I see fi2enc can pack only one data block - the updater. But we also need at least one more for firmware dump(excluding user data, calibration data etc.)

Did you manage to unpack M1000110.FI2 ?

 

Related Topics