SX170 porting - page 4 - DryOS Development - CHDK Forum  

SX170 porting

  • 266 Replies
  • 56116 Views
Re: SX170 porting
« Reply #30 on: 13 / August / 2014, 08:46:37 »
Advertisements
I am trying to download CHDK-Shell and I get always corrupted link or files not available.
Can anybody, please, send a link to download the CHDK-Shell last version ?

Re: SX170 porting
« Reply #31 on: 13 / August / 2014, 08:50:09 »
I am trying to download CHDK-Shell and I get always corrupted link or files not available.
Can anybody, please, send a link to download the CHDK-Shell last version ?
Posted a note where whim is likely to see it : http://chdk.setepontos.com/index.php?topic=845.msg115595#msg115595

Meanwhile, there is an older version here :  CHDK_Shell on Google Drive
« Last Edit: 13 / August / 2014, 08:54:35 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: SX170 porting
« Reply #32 on: 13 / August / 2014, 10:20:44 »
Hi Garden & waterwingz

Thanks to msl there are backups on the German forum:
latest full version (3.40)
latest version (3.44)

hope that helps,

wim

edit: regular links should be back to normal now
« Last Edit: 13 / August / 2014, 11:09:22 by whim »

Re: SX170 porting
« Reply #33 on: 13 / August / 2014, 16:48:50 »
raw is rubbish, looks like a memory issue, and ya check char *hook_raw_image_addr().
this reduced to upload.


Re: SX170 porting
« Reply #34 on: 14 / August / 2014, 10:33:57 »
CHDK-Shell Link established!
Thanks guy.

Re: SX170 porting
« Reply #35 on: 14 / August / 2014, 18:39:22 »
Garden, sorry ... my english is bad !!  :D
I said that a firmware beautiful and full of new features (raw,hdr etc) is that of the Canon SX220 and I was hoping it was possible to do/make similar for our canon sx170. I don't think will work on sx170 ...unfortunately :'(

Re: SX170 porting
« Reply #36 on: 16 / August / 2014, 08:48:58 »
I am trying to build the SX170 code but I am getting this message. Any clue?

gmake.exe: *** loader/sx170is: No such file or directory.  Stop.
gmake: *** [clean-recursive] Error

The directory is .

C:\Desenv\CHDK_SHELL\trunk\trunk3582\platform\sx170is

and the camera_list.csv entry is:

sx170is,101a,BETA,,

I can compile for sx160 without any problem.

Thanks


*

Offline srsa_4c

  • ******
  • 4142
Re: SX170 porting
« Reply #37 on: 16 / August / 2014, 09:04:29 »
I am trying to build the SX170 code but I am getting this message. Any clue?

gmake.exe: *** loader/sx170is: No such file or directory.  Stop.
gmake: *** [clean-recursive] Error

The directory is .

C:\Desenv\CHDK_SHELL\trunk\trunk3582\platform\sx170is
You need to copy both sx170is subdirs from nafraf's repo to the CHDK trunk tree: platform/sx170is and loader/sx170is. Not sure if the source files attached in this thread are newer or older than that.
Quote
and the camera_list.csv entry is:

sx170is,101a,BETA,,
The csv file is only used for batch building.


Re: SX170 porting
« Reply #38 on: 16 / August / 2014, 10:44:03 »
Thanks for the help.
Now I am getting this error.

C:\Desenv\CHDK_SHELL\gcc4\bin\gmake.exe[1]: *** No rule to make target `boot.c', needed by `boot.o'.  Stop

The SX170IS files are incomplete. So does anybody has the complete sx170is files?

Thanks

*

Offline srsa_4c

  • ******
  • 4142
Re: SX170 porting
« Reply #39 on: 16 / August / 2014, 11:08:08 »
Thanks for the help.
Now I am getting this error.

C:\Desenv\CHDK_SHELL\gcc4\bin\gmake.exe[1]: *** No rule to make target `boot.c', needed by `boot.o'.  Stop

The SX170IS files are incomplete.
nafraf is using the code_gen utility that can create source files from a text based instruction file (code_gen.txt). To recreate the missing files:
- copy the sx170is 101a PRIMARY.BIN to platform/sx170is/sub/101a
- gmake run-code-gen (you may need to type this in a command prompt window in case CHDK-SHELL doesn't support this target from its GUI).
- if you plan to change source files, watch out for any "automatically generated" warnings in the file headers: those files will be erased and re-created by code_gen

 

Related Topics