EOS M3 porting [M3] [EOS_M3]

reyalp

Ant

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

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

Thanks. That's definitely worth avoiding. Interesting M10 doesn't have similar code, but it does have some other special stuff related to spytask start.

I've added a comment and put the romlog stuff under #ifdef BOOT_ROMLOG_SHORTCUT

Caefix

(mod edit: please try to make your posts easily readable)

Ahje, my 1st hour with M3_121a.
Tried todays version & homebuilt #5879,5891, lenses 15-45 & 18-55.
Always "sd-card locked" only... 😳

Ant

@Caefix

Probably there is something wrong with your SD card.

Try to start CHDK using the firmware update method.(see attachment)

Add:
PS.FI2 updated

PS.zip

83.41KB

Ant

@reyalp
How to check inside boot.c, was the OPT_FI2 option activated?

Caefix

:😀 SD-card was not bootable. Now it starts at once.
But there is no WF-update enrty in the <play>menues 1..4.

Ant

CaefixBut there is no WF-update enrty in the <play>menues 1..4.

FW update entry is not allowed in playback mode. Switch to rec mode.

Caefix

🧑‍🎄 Thanks, found it & it works.

reyalp

Ant
@reyalp
How to check inside boot.c, was the OPT_FI2 option activated?

If you mean whether the camera was booted from FI2, I'm not aware of anything really simple, though there's very likely lots of memory values that are different. The MMIO from the FI2 might be an option https://chdk.setepontos.com/d/11316/148 (this doesn't appear to be implemented on M3, but is on M10)

Ant

reyalpIf you mean whether the camera was booted from FI2

I mean something like #ifdef OPT_FI2 inside boot.c for marking the code which used for building FI2 only.

It looks like the compiler options can't be accessed from boot.c

But anyway, there is a bigger problem with FI2: the firmware update can't start when the battery is low.

reyalp

Ant
I mean something like #ifdef OPT_FI2 inside boot.c for marking the code which used for building FI2 only.
It looks like the compiler options can't be accessed from boot.c

Defines can be accessed in boot.c like any other file, you just need to make sure -Dwhatever gets in the right CFLAGS. But that won't help you because DISKBOOT.BIN and PS.FI2 are the same binary, encoded differently after compile. I guess we could theoretically edit some magic bytes in the unencoded main.bin before encoding each one.

But anyway, there is a bigger problem with FI2: the firmware update can't start when the battery is low.

That does make sense for an actual firmware update 😉

Caefix

😖 (1.21a, Ximr build)
md grid fits perfect in 3:2, other aspect ratios need adjustment.
Values of the lower half are spooky ...
Edit: Ximr build only ...

reyalp

Caefix
md grid fits perfect in 3:2, other aspect ratios need adjustment.

I can confirm this happens on other ximr builds when the aspect ratio isn't the native LCD aspect.

Values of the lower half are spooky ...

Can you clarify what you mean by "spooky"? Does MD trigger when there is no motion?

philmoz

Caefix
md grid fits perfect in 3:2, other aspect ratios need adjustment.
Edit: Ximr build only ...

I have checked in a fix for this in the ximr branch and updated the build images on Google Drive.

Caefix

reyalp
Can you clarify what you mean by "spooky"? Does MD trigger when there is no motion?

Yes, even with the lenshood.

😛 Ahje, the charger is dead, no LED, no charching, spare bat at 40%...
The cam is more robust, recently it crashed from good 1/2 meter on asphalt, on the flashside corner. Flash opened, lenscap jumped around, cam with 18-55 IS STM bounced back in a loop and landed on the bottom. NO damage at all. Flash and AF beem still working.
The reason was, that the bagÂ´s hook wasnÂ´t hooked right, when I took it out of the rucksack.
Please donÂ´t repeat to confirm that...

Edit: No AF-beam at MD-tune.bas ...

reyalp

Caefix

reyalp
Can you clarify what you mean by "spooky"? Does MD trigger when there is no motion?

Yes, even with the lenshood.

Found a bug, should be fixed in ximr build 5973. This likely explains some of the issues @pigeonhill had with histograms (but the current svn ximr and trunk have other histogram bugs unfixed).

The cam is more robust, recently it crashed from good 1/2 meter on asphalt, on the flashside corner. Flash opened, lenscap jumped around, cam with 18-55 IS STM bounced back in a loop and landed on the bottom. NO damage at all. Flash and AF beem still working.
The reason was, that the bagÂ´s hook wasnÂ´t hooked right, when I took it out of the rucksack.
Please donÂ´t repeat to confirm that...

😛 🙁 Better than my g7x that took flight, I guess.

Edit: No AF-beam at MD-tune.bas ...

Does chdkptp =set_led(1,1) turn it on?

It could maybe be affected if the canon firmware thinks something is in the hot shoe, or Canon flash or AF assist settings.

Caefix

reyalp

Caefix

Edit: No AF-beam at MD-tune.bas ...

Does chdkptp =set_led(1,1) turn it on?

It could maybe be affected if the canon firmware thinks something is in the hot shoe, or Canon flash or AF assist settings.

set_led performs fine in Lua, ubasic & chdkptp, but no beem in MD-tune.bas loop ... ??? (last Bat now 22%)
Edit: ximr build only...

reyalp
😛 🙁 Better than my g7x that took flight, I guess.

Edit3: Independently it happens that booting to <Rec> tells since bat ~20% "Charge Bat", while booting to <Play> & switching to <Rec> still works. (now 11%)

Edit4: I think, that platform_camera.h needs from M100:

    #undef  CAM_CIRCLE_OF_CONFUSION
    #define CAM_CIRCLE_OF_CONFUSION             19  // CoC value for camera/sensor (see http://www.dofmaster.com/digital_coc.html)

Edit2: REally not the best moment to drop cam that way. Noise shocked family...

Caefix

😉 Ximr notes: Temp. set to Bat seems to display 60Â°C too much or ~triple value.
Histogram looks all right now.
Edit: Now Bat=-4Â°C 🤣 😐:

Caefix
😛 Ahje, the charger is dead, no LED, no charching, ...
The cam is more robust, recently it crashed from good 1/2 meter on asphalt,

Scene remetered: ~80cm crash. Luckily neither display nor glass touched the ground.
The charger is okay, too, but does not recognize 3rd party Bonacell-akku.
Edit2: md_tune.bas works fine now. 😀

pigeonhill

@reyalp

Iâ€™ve been rather neglecting my CHDK and M3 for awhile, as I traded my 5D3 in for an EOS R, and have been spending time setting this camera system up, eg cage, handle, adapters etc.

Anyway, my question is, does the M3 trunk now cover the XIMR â€˜stuffâ€™, or do I still need to seek out the @philmoz builds?

BTW has there been any XIMR major updates, are are things roughly the same as they were earlier in the year?

Cheers and I hope you and your family have the best Christmas you can

Garry

reyalp

pigeonhill
Anyway, my question is, does the M3 trunk now cover the XIMR â€˜stuffâ€™, or do I still need to seek out the @philmoz builds?

Still not in the trunk.

BTW has there been any XIMR major updates, are are things roughly the same as they were earlier in the year?

No major changes for a long time. It looks like the last change for M3 specifically was in August.

Ant

@reyalp
What is the reason not to merge philmoz's branch?

« Previous Page Next Page »