G16 Porting Thread - Test Versions Available

  • 215 Replies
  • 55453 Views
Re: G16 Porting Thread - Test Versions Available
« Reply #50 on: 01 / July / 2017, 01:20:19 »
Advertisements
Did you try to run the java jar file directly or did you use the bash script (which sets up the directory stuff and invokes java using sudo).

I did this:
sudo java -jar stick.jar

Since the .zip had windows stuff I only extracted stick.jar and stickx.sh.  Anything else required?

Used stickx this time and get this:
   return code was 0
Command 'rm -r /media/guy/CANON_DC1' = ''
   return code was 0
Command 'mkdir /media/guy/CANON_DC1' = ''
   return code was 0
Command 'mount /dev/sdd1 /media/guy/CANON_DC1' = ''
   return code was 0
drives=1
Cards scanned - 1 cards found

Setting preparation tasks ...
   p2=false
   f32=true
   si=31914
   fmt1=3
   bootable = FAT32
   no formatting required
awaiting permission to install
Preparing /dev/sd/dev/d 32GB - please wait ...
Making card bootable  as FAT32
Command 'umount /dev//dev/sd/dev/d1' = '!Error

umount: /dev//dev/sd/dev/d1: mountpoint not found'
   return code was 32
Command 'printf "BOOTDISK" | dd bs=1 count=8 seek=480 conv=notrunc of=/dev//dev/sd/dev/d1' = '!Error

dd: failed to open ‘/dev//dev/sd/dev/d1’: No such file or directory'
   return code was 1
Command 'rm -r /media/guy/CANON_DC1' = '!Error

rm: cannot remove ‘/media/guy/CANON_DC1’: Device or resource busy'
   return code was 1
Command 'mkdir /media/guy/CANON_DC1' = '!Error

mkdir: cannot create directory ‘/media/guy/CANON_DC1’: File exists'
   return code was 1
Command 'mount /dev//dev/sd/dev/d1 /media/guy/CANON_DC1' = '!Error

mount: special device /dev//dev/sd/dev/d1 does not exist'
   return code was 32
Installation failed - see log for details

Re: G16 Porting Thread - Test Versions Available
« Reply #51 on: 01 / July / 2017, 01:31:24 »
About stickx.sh...
The "cd" line ends up doing:
cd /md0/guy/bin

That is the same directory I was in, so no change.

Just to be sure, here is the stickx.sh:
#!/bin/bash
cd "$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
sudo java -jar stick.jar

I started it like this:
./stickx.sh

Thanks,
Guy

G16 Porting Thread - Test Versions Available
« Reply #52 on: 01 / July / 2017, 01:33:24 »
I'll send an email to STICK's author asking him for help.   

Meanwhile, i've used Linux method 2B from this link successfully: http://chdk.wikia.com/wiki/Prepare_your_SD_card#Other_methods_for_preparation_a_Bootable_SD_card

Edit : as you already have a FAT32 formatted SD card you don't even need to do the fdisk & mkdosfs part of those instructions.  Just write the BOOTDISK string to the start of the card as specified, unzip the distribution file, lock the card, and start your camera.
« Last Edit: 01 / July / 2017, 01:56:55 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: G16 Porting Thread - Test Versions Available
« Reply #53 on: 01 / July / 2017, 02:14:24 »
I'll send an email to STICK's author asking him for help.   

Meanwhile, i've used Linux method 2B from this link successfully: http://chdk.wikia.com/wiki/Prepare_your_SD_card#Other_methods_for_preparation_a_Bootable_SD_card

Edit : as you already have a FAT32 formatted SD card you don't even need to do the fdisk & mkdosfs part of those instructions.  Just write the BOOTDISK string to the start of the card as specified, unzip the distribution file, lock the card, and start your camera.

Linux Method #2b - worked

The main thing I wanted is time-lapse, but interval.lua crashes when I try to run it.  Powers down with lens still out.

Motion might be cool.  Need sleep, might play with it tomorrow.

Thanks all.


G16 Porting Thread - Test Versions Available
« Reply #54 on: 01 / July / 2017, 02:24:45 »
Linux Method #2b - worked

The main thing I wanted is time-lapse, but interval.lua crashes when I try to run it.  Powers down with lens still out.
Be aware that you are the first person to try the 101a code.  It's a "blind" translation of the working 101c code so completely untested.

I'm guessing the other simple scripts also crash when they try to shoot? If you can dump a ROMLOG using the CHDK Miscellaneous menu and post it here, that might help with fixing the problem.

Edit : does the camera also crash if you try to shoot normally (via the shutter button) with CHDK  loaded?
« Last Edit: 01 / July / 2017, 02:29:38 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: G16 Porting Thread - Test Versions Available
« Reply #55 on: 01 / July / 2017, 02:33:16 »
Linux Method #2b - worked

The main thing I wanted is time-lapse, but interval.lua crashes when I try to run it.  Powers down with lens still out.
Be aware that you are the first person to try the 101a code.  It's a "blind" translation of the working 101c code so completely untested.

I'm guessing the other simple scripts also crash when they try to shoot? If you can dump a ROMLOG using the CHDK Miscellaneous menu and post it here, that might help with fixing the problem.

Edit : does the camera also crash if you try to shoot normally (via the shutter button) with CHDK  loaded?

Ok, crashed it again and powered up again and saved crash log.  Seems power-down would clear any info, but maybe not.  ROMLOG.LOG attached.

Edit: I used motion this time.  It also crashed, but took maybe 5 seconds.
« Last Edit: 01 / July / 2017, 02:35:10 by LethalDosage »

Re: G16 Porting Thread - Test Versions Available
« Reply #56 on: 01 / July / 2017, 09:38:12 »
Ok, crashed it again and powered up again and saved crash log.  Seems power-down would clear any info, but maybe not.  ROMLOG.LOG attached.

Edit: I used motion this time.  It also crashed, but took maybe 5 seconds.

Does the camera also crash if you try to shoot normally (via the shutter button) with CHDK  loaded?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline zeno

  • *****
  • 884
Re: G16 Porting Thread - Test Versions Available
« Reply #57 on: 01 / July / 2017, 10:20:47 »
My apologies for the delay in responding. Looking at the log fragments, it's clear there is still a problem with my code for parsing the response to linux commands like 'fdisk' (which STICK issues under the covers to find out about cards). Trouble is there are a variety of different formats for '/dev/...' names and my code clearly didn't handle this one properly.


If you could email the full STICK log (sticklog.txt in the same dir as stick.jar) to me - daveATzenoshrdluDOTcom - I'll see if I can figure out what's going wrong. Glad you managed to get CHDK installed anyway.


Dave
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit


Re: G16 Porting Thread - Test Versions Available
« Reply #58 on: 04 / July / 2017, 16:40:12 »
You can't use the G15 ps.fi2 or ps.fir - that will only work with a g15.   If CHIMP set the card up correctly then you should be able to unzip the files, lock the card, and have it boot.  You don't need either file for that to work.

Edit : if that doesn't work, we'll have to try some test builds to narrow down the problem.  PM me an email address so we can speed up the process?
Hi Waterwings,

here are the methods I used to make the card (4GB) bootable
CHIMP, Stick, HDHacker+xvi32
After that, I copied the CHDK files onto it.
The result with all 3 methods is the same as last time (no PS.FIR or PS.FI2 on it):
Non responsive, black screen, switch off possible only by pulling the battery.
So, I presume that it loads CHDK but stops somewhere.
I will send you my email address via PM right away.

Thanks,

Harald

Re: G16 Porting Thread - Test Versions Available
« Reply #59 on: 26 / July / 2017, 09:44:51 »
Mind if another 101A user join the fray?  :D

I've so far load CHDK into card with STICK. Camera shoot stills and video fine, DNG works. OSD/Menu flickers badly with exposure changes (both bright -> dark and dark -> bright. tested by covering the lens; doesn't flicker when lens is covered). So far haven't tried any scripts but if you provide me some i'll happily run it. Zebra stripes doesn't actually draws over over/underexposed areas, but rather areas that are going to be (and i have to crank the treshold to 20 to actually see anything). ALT menu takes 4-5 seconds to load (not sure if typical).

This is what i managed to test so far (flickering menus is hard to navigate with and my lack of CHDK knowledge doesn't help). If you have anything you want me to test, i will try to get back to you asap.

Thanks for (the start to) making my camera great again!

 

Related Topics