EOS M3 porting [M3] [EOS_M3]

Ant

reyalp
Here's some "blind" cleanup and notes

At least it works after building DISKBOOT.BIN
Will you commit your patch?
I'm planning to add current_fb_d variable but it's better to do it step by step.
For features like this there need to make platform specific menu. Any suggestions how to do it?

reyalp

Ant
At least it works after building DISKBOOT.BIN

Thanks, checked in.

I'm planning to add current_fb_d variable but it's better to do it step by step.
For features like this there need to make platform specific menu. Any suggestions how to do it?

I'd put it under camera.h / platform_camera.h ifdefs, like the other conditional menu items. If you need a whole submenu (rather than just some items) CAM_TOUCHSCREEN_UI is an example of one that does that. Any the M3 needs are potentially applicable to M10 as well, at least.

reyalp

I undef'd the CAN_SD_OVER_IN options, updated the notes as far as I understand the status of the port, disabled FI2 building, and enabled in the autobuild.
It's currently labeled PREALPHA, hopefully this doesn't break anything.

Ant

reyalpIt's currently labeled PREALPHA, hopefully this doesn't break anything.

Binary from autobuild for fw 101a works at all:

There need a tester with fw 120f because I don't want to reflash my camera to 120f every time.

Please give for it the correct name: M3 & M10 aren't PowerShots. They are EOS.

reyalp

Ant
Please give for it the correct name: M3 & M10 aren't PowerShots. They are EOS.

I noticed this, but those labels actually come from some hairy TCL code in the mighty-hoernsche autobuild rather than the CHDK source, so I'm not in a hurry to fix it 😉

I did consider calling the platform eosm... rather than m...

Hardware_Hacker

Ant
There need a tester with fw 120f because I don't want to reflash my camera to 120f every time.

I have two "Good" EOS M3-100d and one "Faulty (Power-On)" EOS M3-101a.
The EOS M3-100d are now (i.e. today) booting Ok but not much more.
Also I have been following the progress of EOS M3-120f port.
And so I might have discovered some porting typos and/or errors for the 101a and 120f.

Is there any point of having a EOS M3-100d port when a better option is just to upgrade to the 101a and 120f.

Should I:-

a/ Don't up grade any of the EOS M3's, yet.
b/ Upgrade a "Good" EOS M3-100d to a "Good" EOS M3-120f.
c/ Just upgrade the "Faulty" EOS M3-101a to "Faulty (Power-On)" EOS M3-120f.

H-H
Lenses, 2x Canon 22mm STM, 1x Sigma 4.5mm fisheye, 1x Canon Ef Fisheye.
Just got a Buspirate for testing Canon Ef-Comms.

Ant

Hardware_HackerIs there any point of having a EOS M3-100d port when a better option is just to upgrade to the 101a and 120f.

Should I:-

a/ Don't up grade any of the EOS M3's, yet.
b/ Upgrade a "Good" EOS M3-100d to a "Good" EOS M3-120f.
c/ Just upgrade the "Faulty" EOS M3-101a to "Faulty (Power-On)" EOS M3-120f.

I have no reason to make 100d port. So my suggestion is "b/".

reyalp

Ant
I have no reason to make 100d port. So my suggestion is "b/".

I agree with that. In the past CHDK practice has been to not make new ports for earlier versions after a Canon firmware update becomes available.

c_joerg

reyalp
disabled FI2 building

Is this a great thing to make it work?

Ant

I was trying few times - no success. Camera crashes during restart. Don't see any reasons to spend my time trying again.
Maybe disassembling of flasher from official fi2 file will be helpfull...

reyalp

c_joerg

reyalp
disabled FI2 building

Is this a great thing to make it work?

All digic 6 ports so far have unresolved issues with .FI2 loading.

c_joerg

reyalp
All digic 6 ports so far have unresolved issues with .FI2 loading.

Yes, I know but when I had G7x it works very well in M, TV and AVâ€¦

Ant

c_joergwhen I had G7x it works very well in M, TV and AVâ€¦

They have different hardware. For example G7X does not have FPGA for servo AF. Why do you need .FI2 loading?

reyalp

c_joerg
Yes, I know but when I had G7x it works very well in M, TV and AVâ€¦

FWIW, I disabled FI2 building in G7x before adding it to the autobuild, because I'm not comfortable handing out builds with apparent hardware initialization issues.

c_joerg

reyalp
FWIW, I disabled FI2 building in G7x before adding it to the autobuild, because I'm not comfortable handing out builds with apparent hardware initialization issues.

Ok...

Ant
They have different hardware. For example G7X does not have FPGA for servo AF.

Understandâ€¦

Ant
Why do you need .FI2 loading?

I can borrow in my company 256G SD card for time-lapse. I then have to format each time from exFAT to FAT32 and vice versa.

c_joerg

Even without a lens, the EOS M3 delivers continuous temperature values â€‹â€‹for the optics. The temperature sensor is then probably not in the lens.

Ant

I managed to start CHDK from *.FI2 file, but it doesn't work well:
camera can shoot still pictures, but trying to record movies causes "Memory card error" and then "E09". Trying to open movie in playback mode causes "ASSERT!! MoviePlayer.c Line 6097".

I also managed to make reboot function working on M3. But rebooting process takes too much time: 15 - 30s.
After rebooting movie functions are working normally.

It's strange, because firmware update uses the same "Restart" function (0xFC1311DC), but with different argument. I was trying to write 0x12345678 signature at 0x4ffc after restarting from FI2 - it doesn't help. Previously camera did not start from FI2 because of checking the switches.

Here you can find PS.FI2 for fw101a. Not sure it's safe for the camera. Use it at your own risk...

fi2.diff

1.42KB

PS.FI2

78.25KB

c_joerg

Ant
Here you can find PS.FI2 for fw101a. Not sure it's safe for the camera. Use it at your own risk...

Thanks â€¦ great â€¦
I've just made a few time-lapse with different settings(single, continuous, Display off ). Could not find any problems. I'll keep watching ...

lapser

Ant
Here you can find PS.FI2 for fw101a.

That's great! Can you post the file for fw200f when you get the time (no rush)?

The only use I have for the "firmware update" method of starting CHDK is to be able to set the boot flag on a newly formatted SD card. From then on, it's not needed. It would actually be a good option to have the PS.FI2 file just set the boot flag, and exit.
======
I also can't thank you enough for producing this port for the M3. It's the first CHDK camera that can use external lenses, and can be attached to a telescope. And you got it into the trunk just in time for me to be able to compile a modified version of your CHDK build that allowed me to photograph the recent total solar eclipse. This was a once in a lifetime opportunity made possible by you, and the others who contributed to the CHDK project over the years.

I especially want to thank reyalp, who wrote some incredible code for measuring exposure and controlling shot timing, not to mention him keeping the CHDK project going for all these years. And I was only able to make the small improvements to reyalp's code that I needed because of MSL writing and updating the "Windows GUI for gcc toolchain."

Everything came together just in time for the eclipse. You can watch the result here:

/>

Ant

lapserThat's great! Can you post the file for fw200f when you get the time (no rush)?

Where did you found fw200f ?
The latest version I know is 120f.

It would actually be a good option to have the PS.FI2 file just set the boot flag, and exit.

M3 has no bootflag (excepting "gaonisoy" signature) because there is powershot-like firmware inside it, not EOS.

« Previous Page Next Page »