EOS M100 porting

psxpetey

Not really, I tried chimp doesnâ€™t seem to be supported

Caefix

😀 Well, Use chimp different. It needs a known cam to complete. Use IMG_100.jpg to get bootable card.
Then replace all files with available build for Your cam. (Hopefully Fw100a) :😀
https://chdk.setepontos.com/d/13943/135
Lock SD-card ... 🤣

psxpetey

Huh in chimp itself it said can was not supported I do have fw100a Iâ€™ve done a dump before

Img-100

So do I just call one of the imgs img100 in dcim and use eos card to make it bootable before using chimp?

Caefix

If You know to use Eos-Card then no need for Chimp.
Jump to .zip... 😁

Caefix

[unknown]
Plus 😉

[code]
function lens_name()
local pname = 0
if (bi.platform=="m3") then
if (bi.platsub == "101a") then
pname = 0x00244969
else
pname = 0x002449ad
end
elseif (bi.platform=="m10") then
pname = 0x272065
end
local len = peek(pname-1,1)
local i = 0
local t = {}
while i < len do
local c = peek(pname + i, 1)
if c == 0 then break end
table.insert(t, string.char(c))
i = i + 1
end
local name = table.concat(t)
return name
end
[/code]

Is the "pname" available for M100, too? :-*

pigeonhill

Caefix

[unknown]
Plus 😉

[code]
function lens_name()
local pname = 0
if (bi.platform=="m3") then
if (bi.platsub == "101a") then
pname = 0x00244969
else
pname = 0x002449ad
end
elseif (bi.platform=="m10") then
pname = 0x272065
end
local len = peek(pname-1,1)
local i = 0
local t = {}
while i < len do
local c = peek(pname + i, 1)
if c == 0 then break end
table.insert(t, string.char(c))
i = i + 1
end
local name = table.concat(t)
return name
end
[/code]

Is the "pname" available for M100, too? :-*

srsa_4c

pigeonhill
Could you help me out on the peek addresses for lens name on the M10 and M100?

M10 (all supported fw versions): 0x272065
M100 100a: 0x1FC84E

Caefix

Need lenses,... 🤣
https://chdk.setepontos.com/d/13638/229

pigeonhill

Caefix
Need lenses,... 🤣
https://chdk.setepontos.com/d/13638/229

All the M lenses are registered in the script 😉

pigeonhill

pigeonhill

Caefix
Need lenses,... 🤣
https://chdk.setepontos.com/d/13638/229

All the M lenses are registered in the script 😉

@Caefix

If you are saying you donâ€™t own any of the registered M lenses, then you can still use exposure bracketing.

pigeonhill

@Caefix

https://photography.grayheron.net/2022/06/landscape-bracketing-script-now.html

Plus I'll be tweaking the code today to give manual lenses an ETTR meter.

UPDATE: ETTR meter feedback now working on fully manual lenses 😀

pigeonhill

@c_joerg

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.

c_joerg

pigeonhill
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

pigeonhill

c_joerg

pigeonhill
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 😉

pigeonhill

@c_joerg

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

Do you see lots of flickering?

Cheers

Garry

Caefix

pigeonhill
... 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. 😀

pigeonhill

Caefix

pigeonhill
... 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

Caefix

pigeonhill
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/d/13943/134

Caefix

Tried to compile with #6112, got 😳


../../../../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              ,0x0000bbe😎 // (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 ...

//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, ... 😁

Edit: Compiles, but built broken. 🙁 That happens with #6094 already.
So my last running version is with 6087. 😳

c_joerg

pigeonhill
Do you see lots of flickering?

Not more than M3.

c_joerg

pigeonhill
Once I get the camera, I may be looking to you or @c_joerg to throw a build my way 😉

Take care about the Firmware. Only M100 100a is supported!

« Previous Page Next Page »