Starting in playback mode, the green LED blinks twice. Using on/off button to start, the lens extends immediately and other than the card being locked, appears ready to shoot.
Quote from: LDBenjamin on 09 / March / 2018, 06:32:01Starting in playback mode, the green LED blinks twice. Using on/off button to start, the lens extends immediately and other than the card being locked, appears ready to shoot.Those two results strongly suggest that you do not have your SD card correctly configured to autoboot CHDK. Given your issues with getting STICK running, that seems to be the most likely scenerio.The initial bootstrap code for the G16 is common to all four camera models. If there was an bug in the G16 1.01b startup code I would expect the camera to simply crash. While it is tchnically possible that a bug could cause the camera to load normally and not hook in CHDK, I don't believe that is what is happening. I can add blinking LED code to the G16 boot loader and post a test build to confirm that if necessary.Did you hear anything back from zeno (Dave) about your STICK issues? He is usually pretty responsive and I have his direct email address somewhere if you have not heard from him. The usual ulprit here is not running STICK with admin privileges. I'm not sure you can do that via the Windows right click "Run as admin" option - you might need to pick the right script from the STICK install. Unfortunately Dave bundles everything for Windows / Linux / iMac into the same directory with similar nondescript names so people sometimes get this step confused. Also, STICK produces a log file - it would be interesting if you could post that here as an attachment.This should not be so difficult - sorry about that. There are other methods of configuring a bootable SD card (listed on the wiki page that I linked) but they require a lot more patience to get them to work correctly.
The log is attached.
Failure checking device '\\.\PHYSICALDRIVE1' - error 5
Quote from: LDBenjamin on 09 / March / 2018, 19:05:03The log is attached.A quick google search of the error line in your log file Code: [Select]Failure checking device '\\.\PHYSICALDRIVE1' - error 5gets me to this post :Help: How to install CHDK in IXUS 240 HSThat one and the post before it looks kind of familiar?Also : https://chdk.setepontos.com/index.php?topic=12377.msg122366#msg122366
That worked, thanks. The camera now starts up and loads CHDK. Unfortunately, it returns the message that the test build (Canon G16 firmware version 101b) has expired.
Quote from: LDBenjamin on 09 / March / 2018, 22:17:34That worked, thanks. The camera now starts up and loads CHDK. Unfortunately, it returns the message that the test build (Canon G16 firmware version 101b) has expired.Yah !! Don't worry about the test build expired message - you can safely ignore it. We put that into test builds of new ports so that people don't download a new port and use it forever without reporting back.But if it makes you uncomfortable, as reward for sticking with us and getting this far, I can post a version with the timer reset.
Quote from: waterwingz on 09 / March / 2018, 22:23:18Quote from: LDBenjamin on 09 / March / 2018, 22:17:34That worked, thanks. The camera now starts up and loads CHDK. Unfortunately, it returns the message that the test build (Canon G16 firmware version 101b) has expired.Yah !! Don't worry about the test build expired message - you can safely ignore it. We put that into test builds of new ports so that people don't download a new port and use it forever without reporting back.But if it makes you uncomfortable, as reward for sticking with us and getting this far, I can post a version with the timer reset. It doesn't bother me; the problem is that after it displays for a moment, the camera returns to its normal state with a locked card without loading CHDK.
Quote from: LDBenjamin on 09 / March / 2018, 22:33:05Quote from: waterwingz on 09 / March / 2018, 22:23:18Quote from: LDBenjamin on 09 / March / 2018, 22:17:34That worked, thanks. The camera now starts up and loads CHDK. Unfortunately, it returns the message that the test build (Canon G16 firmware version 101b) has expired.Yah !! Don't worry about the test build expired message - you can safely ignore it. We put that into test builds of new ports so that people don't download a new port and use it forever without reporting back.But if it makes you uncomfortable, as reward for sticking with us and getting this far, I can post a version with the timer reset. It doesn't bother me; the problem is that after it displays for a moment, the camera returns to its normal state with a locked card without loading CHDK.That is, not its normal state, but one where the lens doesn't extend and the menus are grayed out.
Yes, I would appreciate if you could post a build with the timer reset. I would like to test the build which would hopefully allow a final version for this firmware to be released.
"That is, not its normal state, but one where the lens doesn't extend and the menus are grayed out."
That is, not its normal state, but one where the lens doesn't extend and the menus are grayed out.
Started by waterwingz « 1 2 ... 54 55 » DryOS Development
Started by pittguy578 General Help and Assistance on using CHDK stable releases
Started by Christian72D General Help and Assistance on using CHDK stable releases
Started by vga71 Script Writing
Started by Fortesque General Discussion and Assistance
