So if it isn't isn't confirmed, can you try on the current trunk: CHDK installed, card unlocked. Run firm update to start CHDKPlug in USB
Can you check on a trunk build:Under CHDK Miscellaneous -> tools -> Memory browser, set the address to 0x2488.Report the value after DWORD
Nothing happens. The PC does not see the camera. Remote is not enabled.
Quote from: reyalp on 21 / November / 2019, 23:18:58Can you check on a trunk build:Under CHDK Miscellaneous -> tools -> Memory browser, set the address to 0x2488.Report the value after DWORD1
Is it just me or does the memory browser have a small bug? You start out with increments 4 which is the minimum stepping you can use, using the zoom setting you can select larger increments. While 100 and 1000 and so forth are multiples of 4 the second choice - 10 - is not. So, I got myself entangled in a place where I could not reach 0x2488 but only 0x2486 and I then had to fiddle with the 10 again to correct this. Long story short: Should the ten be a twelve or an eight?
Edit: I figured I'd try this just in case. When I display the 0x2488 value and then plug in the USB cable the value's display stays at one until the screen goes black from the crash. I can't see it going to 0. It still migh in the moment the screen goes black.
QuoteIs it just me or does the memory browser have a small bug? You start out with increments 4 which is the minimum stepping you can use, using the zoom setting you can select larger increments. While 100 and 1000 and so forth are multiples of 4 the second choice - 10 - is not. So, I got myself entangled in a place where I could not reach 0x2488 but only 0x2486 and I then had to fiddle with the 10 again to correct this. Long story short: Should the ten be a twelve or an eight?It's all hex, so 0x10 is 16. You should not be able to get 0x2486?!? If you have "0x10" selected, the last digit should not change. It certainly doesn't on my cams.On some of these displays it can be hard to tell some digits like B, 8, 0 apart.
Quote from: koshy on 23 / November / 2019, 07:13:31Nothing happens. The PC does not see the camera. Remote is not enabled. That's interesting. Can you try the same test with A2200?
Sure, loaded trunk CHDK 5296 on A2200 by FW update, plugged a USB cable in connected with CHDKPTP, switched to Rec nothing out of the ordinary. Figured that's nuts and with earlier confusion re-tried Ixus 220 in the same way but no nothing. No crash no, camera on Windows device manager, none for CHDKPTP.
Here's another test build. Please report the values shown for AD, M1 and M2.
Quote from: reyalp on 28 / November / 2019, 01:27:57Here's another test build. Please report the values shown for AD, M1 and M2.When CHDK is invoked by FW Update all four values are 0 (or 0x00000000)Upon USB Plug-in AD: cycles 0x1ff through 0x205M1: 0x10100M2: 0USB: 1Camera not seen by PC.When CHDK is loaded on boot with a locked SD card. M2 is 0x1 instead of 0.
Quote from: reyalp on 23 / November / 2019, 00:01:15CHDK installed, card unlocked. Run firm update to start CHDKNothing happens.
CHDK installed, card unlocked. Run firm update to start CHDK
Overige parameters ->Gebruikersmenu ->
// from Ix265int vid_get_viewport_display_xoffset_proper() { return vid_get_viewport_display_xoffset()<<1; }int vid_get_viewport_display_yoffset_proper() { return vid_get_viewport_display_yoffset() * vid_get_viewport_yscale(); }int vid_get_viewport_height_proper() { return vid_get_viewport_height() * vid_get_viewport_yscale(); }int vid_get_viewport_fullscreen_height() { return 240 * vid_get_viewport_yscale();}
Started by acseven General Discussion and Assistance
Started by ELPH300 « 1 2 » Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by VincentD « 1 2 3 » General Help and Assistance on using CHDK stable releases
Started by yoshiharra General Help and Assistance on using CHDK stable releases
Started by igb General Help and Assistance on using CHDK stable releases