I'm thinking about making everything call draw_restore rather than vid_bitmap_refresh, so the check disabling drawing can be in one place rather than in every affected port's vid_bitmap_refresh.
I was initially confused for a bit how clean overlay could trigger the crash at startup, since it's only active in rec mode, but I guess the M ports start in rec by default
The m10 (and I'd guess the m3 too) starts in rec when started via ON/OFF, and in playback when started via the playback button.Without the fix (and clean overlay set to 'rec'), the m10 crashes when started in rec mode with HDMI connected. That crash no longer happens with clean-overlay-hdmi-crash-reyalp-work-1.patch applied. I checked in the HDMI bit definition in r5429.
I'm running into this issue — but only on one specific lens, the EF-M 22mm f/2.0 STM "pancake".On my other lenses (and without a lens installed) I do not run into this problem:EF-M 18-55 IS STMEF-S 18-200mm IS (with the EF mount adapter)no lens contact (e.g. a fully manual lens)I've also read about the timing issue and have tried four different SD cards (from a fast, recent 32GB microSD, to a very ancient 32MB freebie card ) but none of them seem to improve the issue.
--[[@title Startup log to file@chdk_version 1.3]]name="A/log.txt"uartr=require("uartr")uartr.start(name,false)call_event_proc("ShowCameraLog")sleep(1000)uartr.stop()
I am sorry to bring this up again, but I was able to get always working screen by doing this:1) Power on EOS M3, switch to CHDK2) Go to CHDK settings -> Disable LCD Off -> From always to never3) Switch to Normal shooting mode, go back to CHDK3) CHDK settings -> Disable LCD Off -> From never to alwaysHope it will help someone too.
Is there a way to make it work as it should though? I read through the earlier posts in the thread and didn't really understand it.
Index: platform/m3/sub/101a/boot.c===================================================================--- platform/m3/sub/101a/boot.c (revision 5707)+++ platform/m3/sub/101a/boot.c (working copy)@@ -252,6 +252,15 @@ ); } +// notifies spytask on its second invocation+void spytask_notifier() {+ static int ncnt = 0;+ ncnt++;+ if (ncnt == 2) {+ core_spytask_can_start();+ }+}+ //fc04f194 ?????????????? void __attribute__((naked,noinline)) sub_fc062f48_my() { @@ -464,6 +473,7 @@ " bl sub_fc0638a8\n" " bl sub_fc362db4\n" " bl sub_fc130c90\n"+" bl spytask_notifier\n" // + "ldmia.w sp!, {r4, lr}\n" //" b.w sub_fc130f1e\n" // - (not recognized automatically yet, transformed into ldr pc) "ldr pc, =0xfc130f1f\n" // + thumb address must be used@@ -511,7 +521,7 @@ " bl sub_fc37e834\n" " loc_fc0f79b6:\n" " bl sub_fc0f9e16\n"-" BL core_spytask_can_start\n" // + CHDK: Set "it's-safe-to-start" flag for spytask+" bl spytask_notifier\n" // + " cmp r4, #0\n" " bne.n loc_fc0f79ca\n" " mov r0, r5\n"Index: platform/m3/sub/120f/boot.c===================================================================--- platform/m3/sub/120f/boot.c (revision 5707)+++ platform/m3/sub/120f/boot.c (working copy)@@ -252,6 +252,15 @@ ); } +// notifies spytask on its second invocation+void spytask_notifier() {+ static int ncnt = 0;+ ncnt++;+ if (ncnt == 2) {+ core_spytask_can_start();+ }+}+ //fc04f194 ?????????????? void __attribute__((naked,noinline)) sub_fc062f48_my() { @@ -463,6 +472,7 @@ " bl sub_fc363020\n" " bl sub_fc130d78\n" // " bl agent_orange\n"+" bl spytask_notifier\n" // + " pop.w {r4,lr}\n" //" b.w sub_fc131006\n" // - (not recognized automatically yet, transformed into ldr pc) "ldr pc, =0xfc131007\n" // + thumb address must be used@@ -510,7 +520,7 @@ " bl sub_fc37eba4\n" " loc_fc0f79b6:\n" " bl sub_fc0f9e16\n"-" BL core_spytask_can_start\n" // + CHDK: Set "it's-safe-to-start" flag for spytask+" bl spytask_notifier\n" // + " cmp r4, #0\n" " bne locret_fc0f79ca\n" " mov r0, r5\n"
Started by koy1 DSLR Hack development
Started by TMHKR General Discussion and Assistance
Started by joverserafico General Help and Assistance on using CHDK stable releases
Started by ronspdx CHDK Releases
Started by stevem Script Writing