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

EOS M100 porting

  • 96 Replies
  • 11578 Views
*

Offline reyalp

  • ******
  • 13142
Re: EOS M100 porting
« Reply #90 on: 02 / March / 2021, 15:10:45 »
Advertisements
:-[ How to avoid...
Quote
d:/hostluaportable/chdk-shell/trunk/gcc1021_host920/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/bin/ld.exe: ../../../../platform/m100/libplatform.a(wrappers.o): in function `GetFreeCardSpaceKb':
wrappers.c:(.text+0x308): undefined reference to `live_free_cluster_count'
collect2.exe: error: ld returned 1 exit status
?
finsig_thumb2 finds this value, so you could make rebuild-stubs
Don't forget what the H stands for.

*

Offline Caefix

  • ****
  • 438
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #91 on: 03 / March / 2021, 13:00:12 »
 :) Fine, found
Code: [Select]
stubs_entry.S:  line 141
DEF(live_free_cluster_count           ,0x00125b50) // (0x125b18+0x38) Found @0xe002d03e
old line 200 deleted:
NHSTUB(GetDrive_FreeClusters                  ,0xe033b889) //  0
and 4kb plus in funcs_by_*
Compiles successfully but still fails on cam.

/* Last working with #5670.  :blink: Since then seems to happen...
Code: [Select]
// core/main.c line 147
    while((i++<100[0]) && !spytask_can_start) msleep(10);
// Edit: NO, not that, if commented out or modified then also nothing happens but 1*green LED every ~15secs +keypress.
before cam turns off without romlog. */
« Last Edit: 01 / April / 2021, 14:43:22 by Caefix »
All lifetime is a loan from eternity.

*

Offline c_joerg

  • *****
  • 1069
Re: EOS M100 porting
« Reply #92 on: 20 / March / 2021, 09:08:01 »
I don't know if it makes sense to post it, just want to inform.

I ran the M100 with the PowerDown script. Interval was 60s. https://chdk.setepontos.com/index.php?topic=13956.0

The first 550 recordings were made without any problem. Then one shot was left out of one cycle. You can recognize it by the 'exp' column in the log file. It is also interesting that in this case the 'tick' value is quite large. These dropouts grew more and more towards the end.
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

  • ******
  • 4396
Re: EOS M100 porting
« Reply #93 on: 20 / March / 2021, 15:21:25 »
Then one shot was left out of one cycle. You can recognize it by the 'exp' column in the log file. It is also interesting that in this case the 'tick' value is quite large. These dropouts grew more and more towards the end.
There are even more anomalies, sometimes exp goes back and forth. You're instructing the camera to wake in rec mode, but is it in rec when it fails to shoot? Observing the camera's behaviour toward the end would probably be useful.


*

Offline c_joerg

  • *****
  • 1069
Re: EOS M100 porting
« Reply #94 on: 20 / March / 2021, 18:22:10 »
The problem occurs the first time after 547 shots. Before that everything is fine. In the end, it just keeps getting worse. The RAW files count up continuously. None is missing. I haven't seen that with the M3 before.
There are even more anomalies, sometimes exp goes back and forth
Yes, this case occurs when many errors come together. I suspect that the file counter is not correct in this case.
You're instructing the camera to wake in rec mode, but is it in rec when it fails to shoot?
Yes, the script wakes up in rec mode.
But I don't know if that was really the case. The script ran with display off. Maybe I should write the mode into the logfile. The longer tick value suggests that it was not the rec mode.
But why should the mode change?
Observing the camera's behaviour toward the end would probably be useful.
How? In the end, I just noticed that the camera no longer triggers as often.


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

  • ******
  • 4396
Re: EOS M100 porting
« Reply #95 on: 21 / March / 2021, 17:50:06 »
Observing the camera's behaviour toward the end would probably be useful.
How? In the end, I just noticed that the camera no longer triggers as often.
I'd guess the condition is triggered by either a large number of files on card or lower voltage (less likely).
Quote
The RAW files count up continuously. None is missing.
Is that CHDK DNG? If so, you could try adding a delay before the script turns the camera off.
I don't have a good explanation for the odd exposure data you get when the jpeg is missing. Perhaps hooks fail for some reason. You could also check for possible camera crash (make a romlog and look at the timestamp).

*

Offline c_joerg

  • *****
  • 1069
Re: EOS M100 porting
« Reply #96 on: 22 / March / 2021, 03:04:33 »
I'd guess the condition is triggered by either a large number of files on card or lower voltage (less likely).
550 is not really a large number of files and voltage was at first time 7709mV (6439mV on the end).

Is that CHDK DNG?

No. I used only Canon native RAW.

Perhaps hooks fail for some reason. You could also check for possible camera crash (make a romlog and look at the timestamp).

No crash happens. The timestamp in romlog is from last year.

It must be some timeout. The ‘start’ value in the logfile is get_tick_count() just before shoot. The ‘tick’ value just after shoot. Only get_dofinfo between.

Normal condition 1550/2260
When it fails        1390/6390
Average M3        2900/4250 (Needs much longer for start)

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

 

Related Topics