supplierdeeply

CHDK corrupted after starting camera with clock

  • 21 Replies
  • 1066 Views
  • Publish
    CHDK corrupted after starting camera with clock
    « on: 15 / June / 2013, 19:02:08 »
    Advertisements
    The SX10IS's "clock" feature is really handy for checking the time, and when exiting clock mode, everything usually works correctly.  However, the camera sometimes locks up when trying to load CHDK (with the clock still on the screen.)  Less frequently the (disabled) CHDK splash screen appears (minus the logo on top), and then the camera starts without CHDK.  The display layout tends to get randomly corrupted...and the "Layout Editor" can't recover the missing items.  Restarting the camera doesn't fix the layout.

    Any ideas?  FWIW, I am using a dual-boot 8GB SDHC card, and the patched CHDK release for the SX10IS.
    « Last Edit: 15 / June / 2013, 19:07:31 by MotCan10 »

    *

    Offline reyalp

    • ******
    • 9809
  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #1 on: 15 / June / 2013, 20:03:30 »
    FWIW, I'm pretty I've experienced weirdness using the "clock" feature on D10, never bothered to investigate it because it's not something I use regularly.

    I just tried it a couple times now and it worked fine  though :-[
    Don't forget what the H stands for.

  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #2 on: 15 / June / 2013, 21:20:20 »
    It's not a big problem, except that it has messed up the CHDK screen layout, and such important OSD things as the battery indicator, zoom amount, and clock are now hidden (although enabled.)  It seems that the screen layout file is corrupted (wherever it's located), as restarting the camera does not fix the screen layout.  The "Layout Editor" is all confused, selecting nonexistent items. 

  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #3 on: 15 / June / 2013, 21:46:22 »
    It's not a big problem, except that it has messed up the CHDK screen layout, and such important OSD things as the battery indicator, zoom amount, and clock are now hidden (although enabled.)  It seems that the screen layout file is corrupted (wherever it's located), as restarting the camera does not fix the screen layout.  The "Layout Editor" is all confused, selecting nonexistent items. 
    Delete the CCHDK2.CFG or CCHDK3.CFG  file from the CHDK directory.   Or use the "Reset to Default" menu item in the CHDK Settings menu.


    *

    Offline reyalp

    • ******
    • 9809
  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #4 on: 15 / June / 2013, 21:52:54 »
    It's not a big problem, except that it has messed up the CHDK screen layout, and such important OSD things as the battery indicator, zoom amount, and clock are now hidden (although enabled.)  It seems that the screen layout file is corrupted (wherever it's located), as restarting the camera does not fix the screen layout.  The "Layout Editor" is all confused, selecting nonexistent items.
    Resetting the CHDK configuration file should fix this, though of course you will lose all your other CHDK settings as well. This doesn't explain how it got messed up in the first place, or prevent it happening again of course.

    Just to be clear we are talking about the same, the clock mode I'm talking about is
    1) press the set button
    2) click the power button or play button
    3) release the set button

    Without CHDK, this displays the clock until I press another button. The camera then stays on in whatever mode it would normally have powered up in.

    With CHDK, my D10 shows the clock for a few seconds, then the debug led flashes and it shuts down.
    The clock displays for a few seconds, then the debug LED flashes and the camera shuts down (crashing, presumably).

    I can also display the clock by holding the set button after booting CHDK. As far as I can tell this works fine.
    Don't forget what the H stands for.

  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #5 on: 16 / June / 2013, 05:03:10 »
    I wanted to check this in S2IS, but it seems it doesn't have the feature. Is this true or I'm just missing it?
    if (2*b || !2*b) {
        cout<<question
    }

    Compile error: poor Yorick

  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #6 on: 16 / June / 2013, 08:07:50 »
    Just to be clear we are talking about the same, the clock mode I'm talking about is
    1) press the set button
    2) click the power button or play button
    3) release the set button

    Yes, that is what I am referring to. 

    Without CHDK, this displays the clock until I press another button. The camera then stays on in whatever mode it would normally have powered up in.

    With CHDK, my D10 shows the clock for a few seconds, then the debug led flashes and it shuts down.
    The clock displays for a few seconds, then the debug LED flashes and the camera shuts down (crashing, presumably).

    I can also display the clock by holding the set button after booting CHDK. As far as I can tell this works fine.

    If your D10 shuts down or locks up when CHDK is enabled, that's the problem.  Yes, the clock can be displayed after booting CHDK (which always works), but sometimes I just want to read the clock, not turn the camera on.

    OK, delete the config file or "Reset to Default" to fix the layout...but then all the general settings are lost, too.

    *

    Offline srsa_4c

    • ******
    • 3103
  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #7 on: 16 / June / 2013, 15:27:41 »
    Romlog on the a3200 (100d):
    Code: [Select]
    ASSERT!! FileSem.c Line 139
    Occured Time  2011:03:17 06:20:38
    Task ID: 14090269
    Task name: SpyTask
    SP: 0x00308D84
    StackDump:
    0x00000000
    0xFF86E1B8
    0x0000008B
    0x00002950
    0x00000000
    0xFFFFFFFF
    0x19980218
    0x19980218
    0x19980218
    0x19980218
    0x19980218
    0xFF86E0D0
    0x00000000
    0xFF8369C0
    0x09400015
    0xFF836664
    0x03CC507C
    0x00000000
    0x19980218
    0x03CACC54
    0x03CA4DA9
    0x19980218
    0x19980218
    0x19980218
    0x19980218
    0x19980218
    0x002F29C0
    0x19980218
    0x19980218
    0x19980218
    0xFF816B78
    0x19980218
    0x19980218
    0x00002008
    ShootConDump:
    0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
    0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
    CameraConDump:
    08 0f 0f 0f 0f 0f 0f 0f 0f 0f
    It feels like the camera is uninitialized at this point. The crash happens in the first MakeDirectory_Fut call. Perhaps letting spytask continue before spytask_can_start gets set is not such a good idea?
    Same thing happens on the ixus65_sd630 ...


    *

    Offline reyalp

    • ******
    • 9809
  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #8 on: 16 / June / 2013, 15:59:42 »
    It feels like the camera is uninitialized at this point. The crash happens in the first MakeDirectory_Fut call. Perhaps letting spytask continue before spytask_can_start gets set is not such a good idea?
    Same thing happens on the ixus65_sd630 ...
    That makes sense, the clock display could hold up regular startup. I think continuing without  spytask_can_start is for cameras that don't have the hook to set it at all, so it falls back to a hard coded delay
    Don't forget what the H stands for.

    *

    Offline srsa_4c

    • ******
    • 3103
  • Publish
    Re: CHDK corrupted after starting camera with clock
    « Reply #9 on: 16 / June / 2013, 17:02:35 »
    It feels like the camera is uninitialized at this point. The crash happens in the first MakeDirectory_Fut call. Perhaps letting spytask continue before spytask_can_start gets set is not such a good idea?
    Same thing happens on the ixus65_sd630 ...
    That makes sense, the clock display could hold up regular startup. I think continuing without  spytask_can_start is for cameras that don't have the hook to set it at all, so it falls back to a hard coded delay
    Trouble is, we can't be sure that all ports implement that core_spytask_can_start() call correctly, so making spytask_can_start mandatory could make CHDK unusable on some of them. Making mkdir / open fail when spytask_can_start is not set is not any better. Should this be camera specific (make the delay a #define defaulting to 4 seconds which could be overridden in platform_camera.h)?

     

    Related Topics