EOS M100 porting - page 5 - DryOS Development - CHDK Forum

EOS M100 porting

  • 104 Replies
  • 16704 Views
*

Offline c_joerg

  • *****
  • 1105
Re: EOS M100 porting
« Reply #40 on: 11 / October / 2020, 05:58:37 »
Advertisements
I've never seen it blinking twice. Maybe it depends on card...?
Good hint. I have now tested two SD cards:
1) SanDisk Extreme PRO 32GB SD (Fast)
2) SanDisk Ultra 32GB Mirco SD with Adapter (Slow)

Blinking of booth cards is the same but

On the fast SD I have to wait only around 2s (after second LED).
With the slow SD card, I have to wait at least 10s after closing SD door.

That's probably a lockup or crash (never seen that either). Do you get new romlog with matching timestamp after that (I suspect not)?
I got always a romlog with matching timestamp. I got different results on both cards.
Romlog attached.


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 srsa_4c

  • ******
  • 4416
Re: EOS M100 porting
« Reply #41 on: 11 / October / 2020, 19:05:46 »
After (lots of) trials, I don't have anything conclusive.
It seems certain that the "classic" boot method (using copied asm code) has no such booting issues.
It does not seem to matter where in RAM I put the CHDK core, the copied ROM pages or the L2 translation tables. A certain combination either has one or more of the boot problems or has (seemingly) none.
In the attached update, I added some more cache cleaning operations, now executed on both cores. It seems to have no issue with card door boot or battery door boot - on my camera.

I feel that the camera's design is making this research harder, adding an additional point of uncertainty. The DIGIC's start in this camera is controlled by the subcpu (which handles some of the buttons and detects the door switches).

*

Offline Ant

  • ****
  • 491
Re: EOS M100 porting
« Reply #42 on: 12 / October / 2020, 11:44:51 »
Quote from: srsa_4c link=topic=13943.msg144278#msg144278
  DIGIC's start in this camera is controlled by the subcpu (which handles some of the buttons and detects the door switches).
In EOS M3 the subcpu also handles lens detection when the camera is switched off.

*

Offline c_joerg

  • *****
  • 1105
Re: EOS M100 porting
« Reply #43 on: 12 / October / 2020, 12:38:25 »
In the attached update, I added some more cache cleaning operations, now executed on both cores.

I compared the update with my sources and I only see differences in black level calculation…
Black Level at ISO100 is now 511.

But now I've discovered another problem. Sometimes setting the exposure time and ISO doesn't work in RAWOPINT. All images then have the same exposure time and ISO.

I once did three runs in a behind with changing some parameters. Setting Tv and ISO only worked in the second run. The camera was not switched off in the meantime.
Here is an example. The values read by the camera fluctuate slightly.

Code: [Select]
tv 821 != cam 840
tv 797 != cam 839
tv 769 != cam 839
tv 739 != cam 839
tv 708 != cam 839
tv 676 != cam 840
tv 644 != cam 839
tv 612 != cam 841
tv 580 != cam 838
tv 548 != cam 840

During the fourth run, the camera crashed for the first time. ROM log is attached.
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 Caefix

  • *****
  • 526
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #44 on: 12 / October / 2020, 12:51:06 »
Booting Romlog.Lua...  ???
At the moment both doors´ activity seems to prepare Romlog in background.
(The 'slow' card is my fastest...)
Same condition, not same Romlog? Some lines differ more or less.
(& there is always some 'noise' in the lens.)
All lifetime is a loan from eternity.

*

Offline srsa_4c

  • ******
  • 4416
Re: EOS M100 porting
« Reply #45 on: 12 / October / 2020, 13:23:42 »
I compared the update with my sources and I only see differences in black level calculation…
Black Level at ISO100 is now 511.

But now I've discovered another problem. Sometimes setting the exposure time and ISO doesn't work in RAWOPINT. All images then have the same exposure time and ISO.

I once did three runs in a behind with changing some parameters. Setting Tv and ISO only worked in the second run. The camera was not switched off in the meantime.
Were you using a build made from the latest source? (it has more changes under platform/m100/sub/100a). In that source, I replaced the classic capt_seq_task code with minimal ROM hooks. If, for some reason, the MMU is switched to the ROM tables, those hooks will fail to work. But I don't see why it would switch to the ROM tables.
Quote
During the fourth run, the camera crashed for the first time. ROM log is attached.
It's due to an unexpected value (don't know what it's supposed to be), not a disaster-like exception that I see in the other romlogs. Anyway, it's not good.

At the moment both doors´ activity seems to prepare Romlog in background.
Does this happen while using the latest source?

The short romlogs are all exceptions, CPU is wandering off executing garbage (for some reason, the exception addresses are all in uncached RAM).

If the latest source is that bad, downgrade to a stabler source until I have an idea what to do...

*

Offline c_joerg

  • *****
  • 1105
Re: EOS M100 porting
« Reply #46 on: 12 / October / 2020, 13:54:54 »
Were you using a build made from the latest source? (it has more changes under platform/m100/sub/100a). In that source, I replaced the classic capt_seq_task code with minimal ROM hooks.
You are right. I missed the subdirectory by comparing with Beyond compare.
But I updated the whole zip by copying over the old version.
If the latest source is that bad, downgrade to a stabler source until I have an idea what to do...
I can't say it's that bad. I've just looked at rawopint's older logs once again. I had the error even before the update.
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 Caefix

  • *****
  • 526
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #47 on: 12 / October / 2020, 13:55:17 »
The door issue isn´t very disturbing ( :xmas me  ).
It could overwrite a crashlog in the worst case I see.
I enjoy a tool for a single key...
All lifetime is a loan from eternity.


*

Offline c_joerg

  • *****
  • 1105
Re: EOS M100 porting
« Reply #48 on: 13 / October / 2020, 11:41:45 »
If the latest source is that bad, downgrade to a stabler source until I have an idea what to do...
I went back to the first version (m100_100a_201002_filesonly.7z.).
Here, too, there was already the problem with ISO and Tv at rawopint.
The only difference is that the problem with the SD card door didn't exist. But that is Ok for me.

With the last version, it looks like, I don’t have problems with rawopint,
if the interval is not too short and I avoid the continuous mode.
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 srsa_4c

  • ******
  • 4416
Re: EOS M100 porting
« Reply #49 on: 13 / October / 2020, 13:29:15 »
I went back to the first version (m100_100a_201002_filesonly.7z.).
Here, too, there was already the problem with ISO and Tv at rawopint.
The only difference is that the problem with the SD card door didn't exist. But that is Ok for me.

With the last version, it looks like, I don’t have problems with rawopint,
if the interval is not too short and I avoid the continuous mode.
Thanks for the observations. It seems likely that the capt_seq hooks need better placement. I'll add debug output in the next release. But my main concern is the boot issues - I need to find out what I'm doing wrong when I do the memory remapping.

 

Related Topics