supplierdeeply

A4000IS porting thread

  • 205 Replies
  • 15360 Views
*

Offline nafraf

  • *****
  • 1257
  • Publish
    A4000IS porting thread
    « on: 10 / February / 2013, 16:42:02 »
    Advertisements
    I started a blind port for A4000IS fw version 100c and 101a, source code is available here.

    Compiled version for 100c is in attachment, to load it, it is necessary to use bootable sd card method.
    If someone can test it, please report the results.

    EDIT
    Files for fw 101a in attachment.
    These are limited version of CHDK, I'll continue the porting after having feedback.

    EDIT 2
    101a file deleted, it can be downloaded from autobuild server
    « Last Edit: 22 / June / 2013, 08:15:45 by nafraf »

  • Publish
    Re: A4000IS porting thread
    « Reply #1 on: 14 / February / 2013, 12:32:12 »
    pm

    *

    Offline nafraf

    • *****
    • 1257
  • Publish
    Re: A4000IS porting thread
    « Reply #2 on: 14 / February / 2013, 18:35:15 »
    File for test CHDK boot in a4000 101b.

    To load it, it is necessary to use bootable sd card method.


    EDIT: CHDK for a4000 101b ALPHA is available in download page
    « Last Edit: 03 / March / 2013, 22:09:41 by nafraf »

  • Publish
    Re: A4000IS porting thread
    « Reply #3 on: 05 / March / 2013, 03:01:30 »
    I just bought a couple of A4000IS cameras in the hopes of using them for scanning documents and books.  I'm very new to CHDK, but am willing to do some testing to help move this along.

    For practice, I got CHDK working on an old S3IS to make sure I could cope with it before buying the new A4000 models.  I was able to get it working there without much trouble.  Doing the same on the A4000 has been more troublesome.  To start with, I wasn't able to figure out which firmware version is on the camera.  I created both the ver.req and vers.req files in the top level directory in the first partition of a 4GB card, but pressing FUNC.SET and DISP doesn't produce the version number like it does on the S3.  I've tried FUNC.SET along with each of the other buttons, but no luck.  So, I decided to wing it and install the files from a4000-101b-1.1.0-2618-full_ALPHA.zip even though I wasn't sure my camera has the 101b firmware.

    The camera came out in 2012, so I thought I could use a single FAT32 partition on the 4 GB SD card, but I wasn't able to get the camera to boot with CHDK.  I had to create a small FAT16 partition for the DISKBOOT.BIN file and a separate FAT32 partition for the data to get the booting to work properly.  I can see the CHDK splash screen for about a second as the camera boots.  I can also see the diskspace, battery level, time and temperature icons at the top of the screen.  Each is surrounded by a grey rectangular patch, so it doesn't look like the transparency is working properly for them.  There is some flashing of the icons as others appear  that I didn't see on the S3.  The Play button works to put the camera into and out of Alt mode.  In Alt mode, pressing FUNC.SET brings up the menu for running scripts.  If I do that while the camera is in shooting mode, then the focus rectangle erases parts of the menu as it moves around (perhaps this is normal, I don't know).  If I bring up that menu while the camera is in playback mode, then the menu behaves nicely.

    It's late, and I'll do more testing and report back tomorrow.  If any can tell me how to get the firmware version number, I would be grateful.  Also, any tips on what to test are welcome.

    Cheers,
    Rob


    *

    Offline zeno

    • *****
    • 847
  • Publish
    Re: A4000IS porting thread
    « Reply #4 on: 05 / March / 2013, 04:19:34 »
    Rob

    you should have a much easier time if you use my STICK app which will do the whole job from downloading the right build to installing it - formatting the card if necessary. You're right, the A4000 should boot fine from a FAT32 card.

    See http://www.zenoshrdlu.com/stick/stick.html
    A570, S100, Ixus 127
    Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

    *

    Offline nafraf

    • *****
    • 1257
  • Publish
    Re: A4000IS porting thread
    « Reply #5 on: 05 / March / 2013, 07:39:30 »
    In Alt mode, pressing FUNC.SET brings up the menu for running scripts.  If I do that while the camera is in shooting mode, then the focus rectangle erases parts of the menu as it moves around (perhaps this is normal, I don't know).  If I bring up that menu while the camera is in playback mode, then the menu behaves nicely.
    That's normal. Comments about it: http://chdk.setepontos.com/index.php?topic=8450.msg96389#msg96389

  • Publish
    Re: A4000IS porting thread
    « Reply #6 on: 05 / March / 2013, 08:56:06 »
    To start with, I wasn't able to figure out which firmware version is on the camera. 
    Try using the ACID utility

    Quote
    The camera came out in 2012, so I thought I could use a single FAT32 partition on the 4 GB SD card, but I wasn't able to get the camera to boot with CHDK.
    Actually, you can use a FAT32 partition on any size card with cameras released after 2010.  Did you follow the instruction here :  http://chdk.wikia.com/wiki/Prepare_your_SD_card#For_Cameras_Released_After_2010_:

    Quote
    I can see the CHDK splash screen for about a second as the camera boots.  I can also see the diskspace, battery level, time and temperature icons at the top of the screen. 
    Pretty much indicates you found the correct firmware version.  Typically wrong versions won't boot at all 99% of the time.

    Quote
    Each is surrounded by a grey rectangular patch, so it doesn't look like the transparency is working properly for them.
    You can set your colors up in the CHDK menus - just pick ones transparent backgrounds for the icon background.


    Quote
    There is some flashing of the icons as others appear  that I didn't see on the S3. 
    The Play button works to put the camera into and out of Alt mode.  In Alt mode, pressing FUNC.SET brings up the menu for running scripts.  If I do that while the camera is in shooting mode, then the focus rectangle erases parts of the menu as it moves around (perhaps this is normal, I don't know).  If I bring up that menu while the camera is in playback mode, then the menu behaves nicely.
    Normal - per nafraf's post above (and manyhundreds of others in this forum).

  • Publish
    Re: A4000IS porting thread
    « Reply #7 on: 05 / March / 2013, 12:56:25 »
    Rob

    you should have a much easier time if you use my STICK app which will do the whole job from downloading the right build to installing it - formatting the card if necessary. You're right, the A4000 should boot fine from a FAT32 card.

    See http://www.zenoshrdlu.com/stick/stick.html

    I'm running slackware64 with jdk-7u11 installed.  I find that both STICK and LICKS fail to locate the SD card on my system (I ran both as root).  Only /dev/sda, one of my hard drives was detected.  I'm not sure what's different between my system and Ubuntu to cause this problem.  I may try STICK from a virtual machine running Ubuntu if I get desperate enough.


  • Publish
    Re: A4000IS porting thread
    « Reply #8 on: 05 / March / 2013, 13:02:45 »
    Rob

    you should have a much easier time if you use my STICK app which will do the whole job from downloading the right build to installing it - formatting the card if necessary. You're right, the A4000 should boot fine from a FAT32 card.

    See http://www.zenoshrdlu.com/stick/stick.html

    I'm running slackware64 with jdk-7u11 installed.  I find that both STICK and LICKS fail to locate the SD card on my system (I ran both as root).  Only /dev/sda, one of my hard drives was detected.  I'm not sure what's different between my system and Ubuntu to cause this problem.  I may try STICK from a virtual machine running Ubuntu if I get desperate enough.
    Or you could use the ACID utility I linked above to get your firmware version and then follow one of the many other installation methods described here :  http://chdk.wikia.com/wiki/Prepare_your_SD_card

  • Publish
    Re: A4000IS porting thread
    « Reply #9 on: 05 / March / 2013, 13:27:48 »
    Hi waterwingz,
    thanks for the info.  I tried ACID and it did indeed show that my firmware was 1.01B.

    As far as setting up the SD card, as I noted above, I'm having trouble running STICK or LICKS on my 64-bit Slackware system, so I have been setting things up by hand using fdisk and the echo command to make the partition bootable.  I am able to create a single FAT16 partition on the 4GB card and make it boot CHDK now (I probably mistakenly ran the "echo -n BOOTDISK" command before mkdosfs when it failed to work last time).  However, if I create a FAT32 filesystem instead, it doesn't boot into CHDK.  I intend on using larger capacity SD cards in the future, so I'll have to figure this out before then, but I can leave things as they are while testing.

    Edit: Doh!  I didn't look closely enough to notice that the seek offset is different for FAT32 from FAT16 for the echo command.  If I use the right offset, then the camera does boot into CHDK with the FAT32 filesystem.  Sorry for an confusion.
    « Last Edit: 05 / March / 2013, 13:42:01 by rkomar »

     

    Related Topics