EOS M3 porting [M3] [EOS_M3]

LordPsycke

reyalp

LordPsycke
Edit: one thing I noticed is that when I set the disable LCD off to always, when I turn off the camera and turn back on again, that is still set to always but doesn't work. The screen turns off at set interval. I have to set it back to never, go back out of the menus, then go back in and set to always, then it sticks.

FWIW, this has been reported before: https://chdk.setepontos.com/d/13993/9

It may be sufficient to just enter and exit alt after starting up.

Since this has now come up more than once, maybe it would be worth adding code to delay the initial call.

thanks - but I have confirmed that going into alt mode and exiting does not fix it. You actually have to go and change the setting on it and exit alt mode, turn off the camera, then turn it on again and then go back in and change it before it works.

srsa_4c

reyalp
Since this has now come up more than once, maybe it would be worth adding code to delay the initial call.

Apparently, not everyone is affected by this issue. We'd need someone who is experiencing the issue and willing to assist with tests (starting with answering the "does it happen with a different card" question I tried to ask in the other thread).
The M10 port has extra code for delaying spytask until task_Startup finishes, but I added that to prevent a crash.

peeveetee

WillFilms
Hello. Clean HDMI script is working well on my Canon M3. Has anyone managed to output 60fps?

The M3 only supports 25 & 50, not 60.

Ant

peeveeteeThe M3 only supports 25 & 50, not 60.

You can try to switch from PAL to NTSC there:
Menu -> SETUP1 -> Video system

Caefix

reyalp

Ant
So these values are obtained directly from the lens and are not stored anywhere.

If someone want to get all distance info values using LUA there need to add new lua script command.

Or make the underlying shooting.c functions get_dofinfo / get_focus do something different under the hood for EOS cams.

... :😀 We already have a lot: https://chdk.setepontos.com/d/14123/11
How to touch main.c and recycled Luafunctions included.

Caefix

😉 Other ILCs have zoom_points = 1;

D:\hostluaPortable\CHDK-Shell\trunk\trunk-5695\platform\M3\main.c
-- #define NUM_FL      101
-- #define NUM_DATA    2  
-- const int zoom_points = NUM_FL;
++ const int zoom_points = 1;

// M100 platform_camera.h has
    #undef  CAM_CIRCLE_OF_CONFUSION
    #define CAM_CIRCLE_OF_CONFUSION             19

M3 & M10 keep default=5...?

carolinedebs

Hey everyone, I've been trying to get my canon M3 to boot from SD card but nothing I'm doing is working.

I was hoping someone could explain in very clear and detailed step by steps the exact process of setting up the card and getting it to launch, along with any common issues that could be causing it to not work, and before you ask yes the card was locked - no dice.

I have spent an entire day on this, followed all instructions, re-read this thread more times than I can count. Tried on two different cards, on both mac and PC etc, and I am having absolutely no luck here and am at my wits end. I can't even begin to figure out what it is that isnt working, and neither can anyone else I've spoken to about it today.

I'm just trying to disable the camera display going to sleep along with clean HDMI.

srsa_4c

carolinedebs
Hey everyone, I've been trying to get my canon M3 to boot from SD card but nothing I'm doing is working.

I was hoping someone could explain in very clear and detailed step by steps the exact process of setting up the card and getting it to launch, along with any common issues that could be causing it to not work, and before you ask yes the card was locked - no dice.

I have spent an entire day on this, followed all instructions, re-read this thread more times than I can count. Tried on two different cards, on both mac and PC etc, and I am having absolutely no luck here and am at my wits end. I can't even begin to figure out what it is that isnt working, and neither can anyone else I've spoken to about it today.

I'm just trying to disable the camera display going to sleep along with clean HDMI.

How large is your card? What does "nothing is working" mean?
Cards larger than 32GB are formatted with exFAT filesystem by default. For autoboot, you need FAT32.
Also, the camera needs to have either the 1.1.0 or the 1.2.0 official Canon firmware.

Ant

Who are willing to test the port for the latest firmware 1.2.1.a?

Source code also available in attachment...

Please create firmware dump and upload it there.

CHDK-M3-121a-r5849.zip

717.54KB

Patch_EOS_M3_121a.zip

85.9KB

c_joerg

Ant
Who are willing to test the port for the latest firmware 1.2.1.a?

I'm still happy with my 101a...
Everthinks works fine.

Ant
Please create firmware dump and upload it there.

Didn't you need a firmware dump for the port?

Ant

c_joergDidn't you need a firmware dump for the port?

Obviously no need. But I will not publish a firmware dump from my camera.

c_joerg

Ant
But I will not publish a firmware dump from my camera.

I wasn't aware that anything in the dump pointed to my camera (except maybe the serial number)
Can you go back to 101a?
If no one else does it then I can try it at the beginning of May.

Ant

c_joergCan you go back to 101a?

yes

121a port is based on 120f. If that port works without problems, this one should also.
I just used the modern finsig_thumb2 tool.
I did not check RAM addresses. Addresses in ROM were shifted by 12 - 48 bytes

c_joerg

I made update to 121a.
I haven't noticed any abnormalities so far.
Have to change some of my scripts.

Interval Script with power down
https://chdk.setepontos.com/d/13956
Looks like I can use same address as for the others firmware versions

      if cam_ver=="101a" or cam_ver=="120f" or cam_ver=="121a" then
            func=0xFC0F824F
        end

Whats about upper and lower focus_distace?
https://chdk.setepontos.com/d/13756

function get_focus_distace_upper()
  if (bi.platform=="m3") and (bi.platsub=="101a") then
    x=peek(0x00244916, 2)
  end

function get_focus_distace_lower()
  if (bi.platform=="m3") and (bi.platsub=="101a") then
    x=peek(0x00244918, 2)
  elseif (bi.platform=="m3") and (bi.platsub=="120f") then
    x=peek(0x0024495C, 2)
  end

Ant

c_joergWhats about upper and lower focus_distace?
https://chdk.setepontos.com/d/13756
[code]function get_focus_distace_upper()
if (bi.platform=="m3") and (bi.platsub=="101a") then
x=peek(0x00244916, 2)
end

function get_focus_distace_lower()
if (bi.platform=="m3") and (bi.platsub=="101a") then
x=peek(0x00244918, 2)
elseif (bi.platform=="m3") and (bi.platsub=="120f") then
x=peek(0x0024495C, 2)
end[/code]

I can't check now because I already flashed 101a firmware.
But looking into RAM and ROM dumps I think that these addresses in RAM are the same for 120f and 121a.

c_joerg

Ant
But looking into RAM and ROM dumps I think that these addresses in RAM are the same for 120f and 121a.

Looks like...

reyalp

Couple things I noticed adding the 121a port:

The platform/shooting.c modemap appears to be a copy/paste of G7X. If someone can go through and get the actual modes present on this camera, that would be appreciated.

The procedure is just set each available shooting mode in the canon UI, and note the PROPCASE_SHOOTING_MODE (53) value. You can use the debug menu propcase display. This will allow scripting to correct get and set modes by name, among other things.

Also, boot.c contains contains this thing

void CreateTask_spytask()
{
	if ( *(int*)(0x9e7😎 & 0x00600000 )  
		{
		if (( *(int*)(0xD20BF4A0) & 0x00002000) == 0) _CreateTask("SpyTaskMY", 0x19, 0x2000, spytask_my, 0);
		_CreateTask("SpyTask", 0x19, 0x2000, spytask, 0);
		}
}

It appears to only start spytask if the *(int*)(0x9e7😎 & 0x00600000 condition is true, and appears to have some special shortcut to generate a romlog.

Starting spytask conditionally seems incorrect. CHDK running with all the other hooks but not spytask will be broken in unpredictable ways.

If this is required for some reason, some explanation would be very welcome. If it's a development leftover, it should removed. M10 does not have similar code.

The romlog dump shortcut seems like development thing that should be #if 0'd for normal builds, but if for some reason it is kept, it should be documented.

Thanks

Ant

reyalpIt appears to only start spytask if the *(int*)(0x9e7😎 & 0x00600000 condition is true

The camera can also wake up briefly after closing the battery cover or after attaching / removing the lens. In this case we don't need start CHDK.

development thing that should be #if 0

Maybe there is a special condition for autobuild server?

reyalp

Ant
The camera can also wake up briefly after closing the battery cover or after attaching / removing the lens. In this case we don't need start CHDK.

Does starting spytask (CHDK is started regardless) cause some problem in these cases? If so, useful to document.

development thing that should be #if 0

Maybe there is a special condition for autobuild server?

No, there isn't, and IMHO, shouldn't be. But if you want to put it under #ifdef BOOT_ROMLOG_SHORTCUT or something and set it in your own localbuildconf, that's fine with me.

Ant

reyalpDoes starting spytask (CHDK is started regardless) cause some problem in these cases?

Yes. The spytask causes "ASSERT!! KerSem.c Line 312"

« Previous Page Next Page »