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

EOS M100 porting

  • 136 Replies
  • 22055 Views
*

Offline c_joerg

  • *****
  • 1146
Re: EOS M100 porting
« Reply #100 on: 31 / May / 2021, 14:04:16 »
Advertisements
I can only agree. I even sometimes have problems understanding him in his nativ language. Offtopic off ...

Sometimes I used the M100 with a 4m selfie stick via Bluetooh. The problem is that the camera emits a sound when focusing, although all sounds are switched off in the Canon menu. Is there a way to prevent this with CHDK?
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 reyalp

  • ******
  • 13387
Re: EOS M100 porting
« Reply #101 on: 31 / May / 2021, 14:24:37 »
Sometimes I used the M100 with a 4m selfie stick via Bluetooh. The problem is that the camera emits a sound when focusing, although all sounds are switched off in the Canon menu. Is there a way to prevent this with CHDK?
Interesting. I noticed the same forcing rec mode over wifi (https://chdk.setepontos.com/index.php?topic=14294.msg145499#msg145499). Similarly reported with the official app in https://www.dpreview.com/forums/post/60937949

Maybe a Canon feature to prevent creep shots.

It doesn't seem to be directly described in the manuals, but some of them say the the camera will make a sound, with no mention of turning it off.

I don't know of a way to disable this offhand, but it seems likely it would be possible by poking a variable somewhere.
Don't forget what the H stands for.

*

Offline c_joerg

  • *****
  • 1146
Re: EOS M100 porting
« Reply #102 on: 31 / May / 2021, 14:48:38 »
Maybe a Canon feature to prevent creep shots.

Although the shutter is much louder. The noise is annoying when you want to photograph animals.
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

  • *****
  • 596
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #103 on: 28 / June / 2021, 15:12:56 »
 ;) ... Here md_detect grid always fits full display, untouched by chosen aspect ratio ...
Edit -->> Set to 1:1 triggered fields are displayed in the black colums...
« Last Edit: 28 / June / 2021, 15:39:05 by Caefix »
All lifetime is a loan from eternity.


*

Offline Caefix

  • *****
  • 596
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #104 on: 07 / July / 2021, 14:20:01 »
 :D Back with photo, M100 + EF-M 18-150 + Leitz Elpro3 (16543, means 55mm filtersize)
All lifetime is a loan from eternity.

*

Offline c_joerg

  • *****
  • 1146
Re: EOS M100 porting
« Reply #105 on: 08 / August / 2021, 05:14:49 »
I've tried rawopint.lua and MDFB2013.lua. Works very well on the usual.
I have a problem with the M100 and rawopint. So far I've only used the EFM 15-45 for this. There are no problems with that.

With the EFS 55-250 or a manual lens, the camera goes out on the second shot. After the crash, the camera's mechanical shutter is closed. This doesn't happen with a normal interval script.

I created a ROMLOG. There was also a GK.log that I haven't noticed before.
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

  • ******
  • 4426
Re: EOS M100 porting
« Reply #106 on: 08 / August / 2021, 11:55:18 »
I've tried rawopint.lua and MDFB2013.lua. Works very well on the usual.
I have a problem with the M100 and rawopint. So far I've only used the EFM 15-45 for this. There are no problems with that.

With the EFS 55-250 or a manual lens, the camera goes out on the second shot. After the crash, the camera's mechanical shutter is closed. This doesn't happen with a normal interval script.

I created a ROMLOG. There was also a GK.log that I haven't noticed before.
It's not crashing here, but there's a raw hook related fix in my source - perhaps that's why. I'll attempt to post updated source in a few days - will have to check trunk changes first.
In the meantime, if you still have the source snapshot, replace following in replaced.c
Code: [Select]
void __attribute__((naked,noinline,aligned(4))) hook_E004E928()
{
    asm volatile (
    "bl         capt_seq_hook_raw_here\n" // +
    "bl         clear_current_raw_addr\n" // +
    "mov        r0, r4\n"
    "bl         sub_e004c680\n"
    "mov        r0, r4\n"
    "ldr        pc, =0xE004E931\n"  // -> back to ROM
    );
}

void plant_hacks_for_e0040000(unsigned addr)
{
    place_fw_patch_t2_64b(hook_E004B840, addr+0xB840);
    place_fw_patch_t2_64b(hook_E0045B18, addr+0x5B18);
    place_fw_patch_t2_64b(hook_E004E6A8, addr+0xE6A8);
    place_fw_patch_t2_64b(hook_E004E750, addr+0xE750);
    place_fw_patch_t2_64b(hook_E004E820, addr+0xE820);
    place_fw_patch_t2_64b(hook_E004E928, addr+0xE928);
}
with this
Code: [Select]
void __attribute__((naked,noinline,aligned(4))) hook_E004E95C()
{
    asm volatile (
    "bl         capt_seq_hook_raw_here\n" // +
    "bl         clear_current_raw_addr\n" // +
    "ldr.w      r0, [r7, #0x184]\n"
    "cbz        r0, loc_e004e96a\n"
    "movs       r2, #1\n"
    "movs       r1, #0\n"
    "ldr        pc, =0xe004e965\n"  // -> back to ROM
    "loc_e004e96a:\n"
    "ldr        pc, =0xe004e96b\n"  // -> back to ROM
    );
}

void plant_hacks_for_e0040000(unsigned addr)
{
    place_fw_patch_t2_64b(hook_E004B840, addr+0xB840);
    place_fw_patch_t2_64b(hook_E0045B18, addr+0x5B18);
    place_fw_patch_t2_64b(hook_E004E6A8, addr+0xE6A8);
    place_fw_patch_t2_64b(hook_E004E750, addr+0xE750);
    place_fw_patch_t2_64b(hook_E004E820, addr+0xE820);
    place_fw_patch_t2_64b(hook_E004E95C, addr+0xE95C);
    *(unsigned short*)(addr+0xE95A) = 0xbf00; // nop (benign 16-bit instruction, added to replace 1st half of destroyed 32-bit instruction)
}

*

Offline c_joerg

  • *****
  • 1146
Re: EOS M100 porting
« Reply #107 on: 08 / August / 2021, 12:29:13 »
In the meantime, if you still have the source snapshot, replace following in replaced.c
I mean I did everything right. But the crash remains.
However, I'm on trunk 5616. Would I have had to update that too?
I'll attempt to post updated source in a few days - will have to check trunk changes first.
No rush. I am waiting for 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 srsa_4c

  • ******
  • 4426
Re: EOS M100 porting
« Reply #108 on: 08 / August / 2021, 12:43:23 »
I mean I did everything right. But the crash remains.
In that case, can you detail the script and camera settings? Use a manual lens (= no electric contacts) as I don't have the 55-250.
Quote
However, I'm on trunk 5616. Would I have had to update that too?
No, that source is not compatible with current trunk.

*

Offline c_joerg

  • *****
  • 1146
Re: EOS M100 porting
« Reply #109 on: 08 / August / 2021, 13:24:30 »
In that case, can you detail the script and camera settings? Use a manual lens (= no electric contacts) as I don't have the 55-250.

After your changes, the cam now also crashes with the EFM 15-45.
Script is just rawopint 0.25 with default Params
https://chdk.fandom.com/wiki/Lua/Scripts:_Raw_Meter_Intervalometer

Cam Settings: AV Mode, only RAW, AWB, ISO100,

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