SX160 IS porting thread

  • 94 Replies
  • 9707 Views
  • Publish
    Re: SX160 IS porting thread
    « Reply #80 on: 30 / December / 2013, 23:38:57 »
    Advertisements
    Here it is again, it didn't crash, and I think it ran better this time in "P" mode.


  • Publish
    Re: SX160 IS porting thread
    « Reply #81 on: 30 / December / 2013, 23:47:58 »
    Here it is again, it didn't crash, and I think it ran better this time in "P" mode.
    Much better - thanks.  Same results as the SX50 - only "SS.MFOn" works for set_focus().

    We are still collecting data here.  Getting both scripting and CHDK menus working correctly for all cameras will take some time I suspect.  Stay tuned.

  • Publish
    Re: SX160 IS porting thread
    « Reply #82 on: 31 / December / 2013, 00:04:09 »
    Sounds good, waterwingz.
    Thanks! :xmas

  • Publish
    Re: SX160 IS porting thread
    « Reply #83 on: 18 / January / 2014, 03:30:29 »
    Greetz to waterwingz et al,  I am ready to volunteer for occasional testing
    esp. of 'remoteshoot' feature  (seeing that task_FileWrite is defined since rev. 2927).

    EDIT: The problem raised in my original msg. was not camera-specific, so it doesn't belong on this thread.
    The reply was exactly right:  thanks to srsa_4c.  (Next time I search first)
    « Last Edit: 19 / January / 2014, 14:34:38 by Vigil »


    *

    Offline srsa_4c

    • ******
    • 3104
  • Publish
    Re: SX160 IS porting thread
    « Reply #84 on: 18 / January / 2014, 09:15:22 »
    but the "rec" command after a few seconds pause always gives the generic message
    ERROR: switch failed
    so it is not possible to shoot or rs.   Suggestions ?
    Something in your OS communicates with the camera after it's connected, and brings it into a state where it can't switch modes. Start reading from here.

    *

    Offline nafraf

    • *****
    • 1255
  • Publish
    Re: SX160 IS porting thread
    « Reply #85 on: 22 / April / 2014, 12:23:25 »
    Memory corruption during remote capture?
    If remote capture used (resolution=L,  or resolution=M1 and Quality=Superfine), image is saved to PC without errors, but camera crashes when camera backs to play mode.  It is possible to capture a sequence of images without errors, camera crashes just when backs to play mode.
    If low resolution used, camera does not crash.

    This is the sequence of commands to generate the crash:
    Code: [Select]
    con> =return get_meminfo()
    1:return:table:{chdk_start=63222700,free_size=1235688,chdk_size=148560,allocated_size=1538248,free_block_count=14,name="combined",allocated_count=1493,chdk_malloc=true,free_block_max_size=748896,allocated_peak=1563520,total_size=2774048,}
    con 1> rec
    con 2> =set_prop(require('propcase').QUALITY, 0)
    con 3> =set_prop(require('propcase').RESOLUTION,  0)
    con 4> rs -jpg /tmp
    con 7> =return get_meminfo()
    8:return:table:{chdk_start=63222700,free_size=1238368,chdk_size=148560,allocated_size=1535568,free_block_count=15,name="combined",allocated_count=1512,chdk_malloc=true,free_block_max_size=748680,allocated_peak=1587536,total_size=2774048,}
    con 8> play

    If normal shoot command used, it is possible to back to play mode without problem.

    *

    Offline srsa_4c

    • ******
    • 3104
  • Publish
    Re: SX160 IS porting thread
    « Reply #86 on: 22 / April / 2014, 14:56:00 »
    If remote capture used (resolution=L,  or resolution=M1 and Quality=Superfine), image is saved to PC without errors, but camera crashes when camera backs to play mode.  It is possible to capture a sequence of images without errors, camera crashes just when backs to play mode.
    If low resolution used, camera does not crash.
    My guess: there is a bug in the modified fwt code which confuses some parts of the firmware. The various CTG tasks are for maintaining information about the images on card (or something like that).

    Superfine quality tends to cause multiple fwt invocations, the bug must be connected to that.

    Can you reproduce this on another camera (same or newer generation would be the best)?


    *

    Offline nafraf

    • *****
    • 1255
  • Publish
    Re: SX160 IS porting thread
    « Reply #87 on: 22 / April / 2014, 15:49:47 »
    It is possible to reproduce the bug in sx510. Superfine quality is not needed, just L size image is enough to camera crash.
     
    For sx240hs, after camera tries to back to play mode, green LED blinks for ever, there is no crash, but camera does not answer to any command or button.  Even with lower resolution camera has that behavior, I missed that during previous tests.

    A1400 and A810 work without problems. 

    I don't have access to A2200, but a similar bug was detected by diybookscanner users.


    *

    Offline srsa_4c

    • ******
    • 3104
  • Publish
    Re: SX160 IS porting thread
    « Reply #88 on: 22 / April / 2014, 18:18:21 »
    For sx240hs, after camera tries to back to play mode, green LED blinks for ever, there is no crash, but camera does not answer to any command or button.
    Reproduced this variant on the a3200, it's not related to
    multiple fwt invocations
    as the file only had 1 chunk.

  • Publish
    SX160IS DNG calibration
    « Reply #89 on: 06 / February / 2015, 18:42:34 »
    Is DNG calibration done for the SX160IS? Does it make a big difference?




     

     

    Related Topics