EOS M100 porting - page 7 - DryOS Development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 ... 20   Go Down

EOS M100 porting

  • 194 Replies
  • 35449 Views
*

Offline c_joerg

  • *****
  • 1233
Re: EOS M100 porting
« Reply #60 on: 20 / October / 2020, 05:35:13 »
Advertisements
Quote from: srsa_4c on 19 / October / 2020, 17:28:12
I'll surely add zoom/focal length support
But I already get the right focal lengths on M100…

In the first approach I would use an average get_focus_distace_upper and get_focus_distace_lower (from M3M10M100_Focus.lua) for the focus.
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 c_joerg

  • *****
  • 1233
Re: EOS M100 porting
« Reply #61 on: 20 / October / 2020, 12:39:37 »
Quote from: srsa_4c on 10 / October / 2020, 18:20:30
It looks like memory is getting corrupted, but only when booting with the above mentioned conditions (closing card door or battery out->in->closing door). Need to investigate...
Perhaps this information is helpful:
If I use
EF-S 55-250mm IS STM or EF-M 11-22mm IS STM
instead of
EF-M 15-45mm IS STM
the power on time increases massively (10 to 15s) without crashes.

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 srsa_4c

  • ******
  • 4450
Re: EOS M100 porting
« Reply #62 on: 20 / October / 2020, 13:43:31 »
Quote from: c_joerg on 20 / October / 2020, 12:39:37
Perhaps this information is helpful:
If I use
EF-S 55-250mm IS STM or EF-M 11-22mm IS STM
instead of
EF-M 15-45mm IS STM
the power on time increases massively (10 to 15s) without crashes.
:(
Have you tried getting a romlog to see if a new one is generated? That delay is huge.
I'd say don't use those lenses until I can post an update...
Logged
*

Offline c_joerg

  • *****
  • 1233
Re: EOS M100 porting
« Reply #63 on: 20 / October / 2020, 14:28:15 »
Quote from: srsa_4c on 20 / October / 2020, 13:43:31
Have you tried getting a romlog to see if a new one is generated?
I got always different logs, most read and write access…
Quote from: srsa_4c on 20 / October / 2020, 13:43:31
I'd say don't use those lenses until I can post an update...
My EFM 15-45 is currently in use with the M3 for some time ...
Maybe it's communication with the lens. Correction tables or a slower interface.
Have you ever tried different lenses?

Update:
If I have no lens on M100, the LED blinks only once and I can switch on M100 immediately.
« Last Edit: 20 / October / 2020, 14:32:08 by c_joerg »
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

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #64 on: 21 / October / 2020, 11:17:18 »
Quote from: c_joerg on 20 / October / 2020, 14:28:15
Update:
If I have no lens on M100, the LED blinks only once and I can switch on M100 immediately.
++ electronic adapter: No Led, No delay, confirms lens comunication.  :)
++ EF-100-300         : 1*Led, NO delay.
++ EF- 50  1.8 II       : 1*Led, NO delay.
--  :blink:  Edit2: Is it IS? ("Noise in the lens")
++ EF_M_15_45        :2*Led+ Romlogs.
Romlogs look like usual.
I think, the delay (Edit: If any) depends on card, nevertheless.

EDIT§: IT IS IS! Just closed a door, expected 2*LED, got one. Switch ON at once! (EF50+100-300)

Edit4:
++ EF_S_18_55         :2*Led+ Romlogs if IS on
++ EF_S_18_55         :2*Led+ ON at once if IS off.
If Romlog, then delay. Maybe cam scans the whole filesystem to find the best place.  :haha
« Last Edit: 22 / October / 2020, 11:13:16 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline c_joerg

  • *****
  • 1233
Re: EOS M100 porting
« Reply #65 on: 23 / October / 2020, 13:40:06 »
Quote from: Caefix on 21 / October / 2020, 11:17:18
IT IS IS! Just closed a door, expected 2*LED, got one. Switch ON at once! (EF50+100-300)

Edit4:
++ EF_S_18_55         :2*Led+ Romlogs if IS on
++ EF_S_18_55         :2*Led+ ON at once if IS off.
If Romlog, then delay. Maybe cam scans the whole filesystem to find the best place.  :haha
I can't see any difference on EF-S 55-250mm, if IS Switch is on or off.


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

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #66 on: 23 / October / 2020, 14:23:04 »
 ??? Got romlog with it? Probably here is NEED to test with 'slow' card.
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 13793
Re: EOS M100 porting
« Reply #67 on: 26 / October / 2020, 01:34:53 »
Quote from: reyalp on 18 / October / 2020, 14:22:09
That said, CHDK does a lot of things that are bad and scary in a multi-core environment, for example, all the things that wait in a loop on a variable set in another task.
This was a silly comment  on my part :-[ That kind of thing would only be a problem if there was no coherency between the cores, but the Canon firmware likely wouldn't work that way either.

FWIW, I did some digging in the documentation.

CHDK cpuinfo (from phil's g7x2) says
Code: [Select]
Mem model feature 0 0x00100103
  VMSA support         0x3 3
  PMSA support         0x0 0
  Cache coherence      0x1 1
...
"ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition" (ARM DDI 0406C.c) section "B4.1.89 ID_MMFR0, Memory Model Feature Register 0, VMSA" calls bits 8-11 (labeled above as "Cache coherence")  "Outermost shareability"  with 0b0001  meaning "Implemented with hardware coherency support."

What does "hardware coherency support" mean?
"ARM® Cortex™-A Series Version: 4.0 Programmer’s Guide" (ARM DEN0013D) section "18.5 Cache coherency"
Suggests should be pretty much automatic as long as the SMP bit is set (which it is) and the MMU tables have the appropriate shareability settings.

Whether things like modules where we do explicit cache maintenance are OK is less clear. If the L2 cache is shared between cores, and unified, it seems like it might be.
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 1233
Re: EOS M100 porting
« Reply #68 on: 02 / November / 2020, 12:11:31 »
With my manually lens Samyang 12mm F/2 the M100 works very well…

Where can I find the address for the powerdown function for the M100?
https://chdk.setepontos.com/index.php?topic=12542.msg137151#msg137151
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

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #69 on: 02 / November / 2020, 12:17:49 »
 :D No crashing without IS. All my EF Lenses boot fine.
Some other lense issues: https://chdk.setepontos.com/index.php?topic=14123.msg144440#msg144440
Logged
All lifetime is a loan from eternity.
Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 ... 20   Go Up
« previous next »
 

Related Topics