EOS M100 porting

pigeonhill

1155

Re: eos M10 port

« Reply #150 on: 23 / June / 2022, 01:58:26 »

Advertisements

@c_joerg

Quote

You could then also insert the M100 right away. It's my favorite camera right now.

@c_joerg I may have spoke too soon on the M100, as it looks like I could get it IR converted.

The question now comes down to knowing if the M100 can make it into the XIMR set of cams.

I believe you have an M100? If so, do you have CHDK running on it?

If this is the case, what is the chance @philmoz can ‘port’ the M100 to the XMIR branch.

I won’t get an M100 for IR conversion unless it runs on an XIMR version of CHDK.

« Last Edit: 23 / June / 2022, 02:01:40 by pigeonhill »

Logged

c_joerg

1248

Re: Re: eos M10 port

« Reply #151 on: 23 / June / 2022, 05:58:00 »

Quote from: pigeonhill on 23 / June / 2022, 01:58:26

I believe you have an M100? If so, do you have CHDK running on it?

Yes, I have an M100 with self-compiled CHDK. There is no official version yet.
I can do anything I need with it. For me it runs reliably.
But I would not like to mix it with the XIMR version now. I don't have time to test right now either

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

pigeonhill

1155

Re: Re: eos M10 port

« Reply #152 on: 23 / June / 2022, 06:20:12 »

Quote from: c_joerg on 23 / June / 2022, 05:58:00

Quote from: pigeonhill on 23 / June / 2022, 01:58:26
I believe you have an M100? If so, do you have CHDK running on it?

Yes, I have an M100 with self-compiled CHDK. There is no official version yet.
I can do anything I need with it. For me it runs reliably.
But I would not like to mix it with the XIMR version now. I don't have time to test right now either

Thanks, it’s good to know that you have an M100 test version up and running, albeit just for you ;-)

I’m vacillating as to whether I get my M10 IR converted or wait until there is an XIMR version for the M100, if ever?

The M100 is more attractive for me, especially as I’ve already got an IR converted (ML) M, because of its higher pixel density.

BTW the reason I’m looking to convert the M10 or 100 is because of the tilting screen and the fact, I believe, that CHDK has the edge over ML from a Lua scripting perspective, ie for photography.

Bottom line: I’m in no rush, so I’ll likely wait and see what unfolds in CHDK M100 land ;-)

Logged

pigeonhill

1155

Re: Re: eos M10 port

« Reply #153 on: 24 / June / 2022, 11:33:03 »

@c_joerg

I forgot to ask, how does CHDK handle itself on the non-XIMR M100?

Do you see lots of flickering?

Cheers

Garry

Logged

Caefix

945
Sorry, busy deleting test shots...

Re: Re: eos M10 port

« Reply #154 on: 24 / June / 2022, 11:42:28 »

Quote from: pigeonhill on 24 / June / 2022, 11:33:03

... how does CHDK handle itself on the non-XIMR M100?

Do you see lots of flickering?

CHDK is stable, flickering not worse then other non-ximr builds.

Logged

All lifetime is a loan from eternity.

pigeonhill

1155

Re: Re: eos M10 port

« Reply #155 on: 24 / June / 2022, 11:54:08 »

Quote from: Caefix on 24 / June / 2022, 11:42:28

Quote from: pigeonhill on 24 / June / 2022, 11:33:03
... how does CHDK handle itself on the non-XIMR M100?

Do you see lots of flickering?

CHDK is stable, flickering not worse then other non-ximr builds.

@Caefix

Thanks for clarifying. I’ve decided to get an M100 for IR conversion.

Once I get the camera, I may be looking to you or @c_joerg to throw a build my way ;-)

Cheers

Garry

Logged

Caefix

945
Sorry, busy deleting test shots...

Re: Re: eos M10 port

« Reply #156 on: 24 / June / 2022, 11:58:30 »

Quote from: pigeonhill on 24 / June / 2022, 11:54:08

Once I get the camera, I may be looking to you or @c_joerg to throw a build my way ;-)

Maybe it´s released until then ...

Edit: Until then ... https://chdk.setepontos.com/index.php?topic=13943.msg147007#msg147007

« Last Edit: 24 / June / 2022, 12:10:05 by Caefix »

Logged

All lifetime is a loan from eternity.

Caefix

945
Sorry, busy deleting test shots...

Re: EOS M100 porting

« Reply #157 on: 24 / June / 2022, 12:53:54 »

Tried to compile with #6112, got

Code: [Select]


../../../../platform/m100/libplatform.a(lib.o):(.data+0x0): multiple definition of `bitmap_buffer'
../../../../platform/m100/libplatform.a(wrappers.o): In function `DeleteSemaphore':
wrappers.c:(.text+0x890): undefined reference to `_DeleteSemaphore'
collect2.exe: error: ld returned 1 exit status


Search results: /../platform/m100/..
//extern char* bitmap_buffer[]; // not suitable, filled with NULLs when a non-GUI mode is started
    _transfer_src_overlay(active_bitmap_buffer&1);
char *bitmap_buffer[2] = { (char*)0x7FE80000, (char*)0x7FD00000 };
    return bitmap_buffer[active_bitmap_buffer&1];
    return opacity_buffer[active_bitmap_buffer&1];
    #define DRAW_ON_ACTIVE_BITMAP_BUFFER_ONLY   1           // Draw pixels on active bitmap buffer only.
DEF(active_bitmap_buffer              ,0x0000bbe8) // (0xbb9c+0x4c) Found @0xe033ebc2
DEF(bitmap_buffer                     ,0x0000bbec) // (0xbb9c+0x50) Found @0xe033ebc8

Undefined reference to `_DeleteSemaphore' disappears with PRIMARY_ROOT on.
So, how to handle bitmap_buffer?

Edit:
It worked with #6014, there it´s commented out in stubs_entry.s ...

Code: [Select]

//DEF(bitmap_buffer ,0x0000bbec), ** != ** stubs_min = 0x00000000 ()
After compiling with error need to set PRIMARY_ROOT off first.
Then modify stubs_entry.s, compile again, ...