SX170 porting - page 10 - DryOS Development - CHDK Forum supplierdeeply

SX170 porting

  • 266 Replies
  • 79855 Views
Re: SX170 porting
« Reply #90 on: 25 / August / 2014, 08:57:04 »
Advertisements
said this aarmot
« Reply #11 on: 09 / July / 2014, 10:38:55 »
Attached is sx170is source directory tree. All files have been modified and values adjusted (unless there's a TODO mark - not too many of them really).

Did take sx510hs port as reference because keyboard layout is same. But sensor is more similar to the a2500 and, as it turned out, keyboard codes were identical to the sx160is. Optical tables (shooting.c) were copied from sx160is. Closest mature (non-alpha) CHDK port was ixus140, so it was taken to comparison also.

The above work was not too hard, mostly pattern matching :) Many thanks to the CHDK core developers for making porting this easy!

CHDK in camera kindof works. Some problems still remain and I'm surely too rookie to resolve them by myself. Can anybody help please?

1) All pictures are extremely dark, like some 4 or more stops uderexposed. Disabled all overrides and custom auto ISO but no avail. Since it is my first Canon camera, I'm not familiar with CHDK options also, surely must read more manuals.

2) RAW works but distorts pictures - top half is okay, bottom is garbage. Could it be related to insufficient memory? Camera has only 64M RAM and before switching to OPT_ARAM_MALLOC=1 the raw shooting always crashed camera. Misc->MemInfo displays 244kB free.

In case someone likes to test, I'm attaching image also.

said this nafra
Check char *hook_raw_image_addr(), and test capture in P mode, in some cameras there are problems with RAW in AUTO mode.
Source code for sx170is 100a is https://subversion.assembla.com/svn/nafraf/chdk/platform/sx170is/
« Last Edit: 25 / August / 2014, 09:26:11 by janeoyuri »

Re: SX170 porting
« Reply #91 on: 27 / August / 2014, 11:52:34 »
Any news ?  :(
Canon kills all developers for our sx170  :blink: .. aarmot, garden where are 'u ? :'(

Re: SX170 porting
« Reply #92 on: 01 / September / 2014, 07:06:51 »
Santana21

I haven´t managed to generate CHDK for the SX170. I will try to get into the makefiles to see why I am getting this error:

========== C:\DESENV\CHDK_SHELL\TRUNK\TRUNK3584\BIN\LOGS\ERR-SX170IS-100A.TXT ==========

cp: cannot stat `./loader/sx170is/main.bin': No such file or directory
gmake: *** [firsub] Error 1

It is some kind of silly thing but still consume some time.

Re: SX170 porting
« Reply #93 on: 01 / September / 2014, 08:52:45 »
I managed to generate CHDK for SX170IS but the câmera hungs. It does not work.
In order to compile and link CHDK I had to copy the loader/sx160is directory to loader/sx170is. The entry point addresss may be wrong.


Re: SX170 porting
« Reply #94 on: 01 / September / 2014, 08:58:43 »
I managed to generate CHDK for SX170IS but the câmera hungs. It does not work.
In order to compile and link CHDK I had to copy the loader/sx160is directory to loader/sx170is. The entry point addresss may be wrong.
The code that I reposted here :  http://chdk.setepontos.com/index.php?topic=11164.msg115903#msg115903  has a different set of loader files than the sx160is.   I've attached a copy of those here.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX170 porting
« Reply #95 on: 02 / September / 2014, 07:19:49 »
waterwingz

It didn´t work. Can you send the platform tree also so that I can generate a working tree here?
I would sugest to create a full sx170is tree in subversion ready to run. I think this can help other people advance without having to patch or use any tool.

Many thanks

Re: SX170 porting
« Reply #96 on: 02 / September / 2014, 08:12:07 »
Can you send the platform tree also so that I can generate a working tree here?
I would sugest to create a full sx170is tree in subversion ready to run. I think this can help other people advance without having to patch or use any tool.
I attached it previously to my earlier posts.  It's still there as both a Zip file and a Patch file.  The link in my post yesterday will take you there.   

If it didn't work for you, are you sre that you are using the right firmware version?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX170 porting
« Reply #97 on: 02 / September / 2014, 08:41:28 »
Quote
If it didn't work for you, are you sre that you are using the right firmware version?


Version 1.00A

The tree you sent me was for the 1.01A because I misled you giving the wrong caemr firmware.
Can you please send me the 1.00A tree?
Thanks


Re: SX170 porting
« Reply #98 on: 02 / September / 2014, 08:56:53 »
Quote
If it didn't work for you, are you sre that you are using the right firmware version?

Version 1.00A
The tree you sent me was for the 1.01A because I misled you giving the wrong caemr firmware.
Can you please send me the 1.00A tree?
I don't have either tree - I just reconstructed the 1.01A tree using attachments posted in this forum thread.  I suppose I can try the same for the 1.00A (assuming it's all there) but it won't be for a day or two.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX170 porting
« Reply #99 on: 02 / September / 2014, 10:49:31 »
I am trying to do it myself. I have done some of the steps you directed me before and I got this :

>> Entering to core
../makefile.inc:362: warning: overriding recipe for target `Makefile'
../makefile.inc:361: warning: ignoring old recipe for target `Makefile'
entry.S \-> entry.o
\-> main.elf
   text    data     bss     dec     hex filename
 113253   31048    6736  151037   24dfd main.elf
main.elf \-> main.bin
<< Leaving core
>> Entering to loader/sx170is
../../makefile.inc:362: warning: overriding recipe for target `Makefile'
../../makefile.inc:361: warning: ignoring old recipe for target `Makefile'
main.c \-> main.o
lib.c \-> lib.o
wrappers.c \-> wrappers.o
kbd.c \-> kbd.o
shooting.c \-> shooting.o
main.o lib.o wrappers.o kbd.o shooting.o \-> libplatform.a
<< Leaving loader/sx170is
**** cria diretorio  ./bin )
**** copia o  main  sx170is
cp: cannot stat `./loader/sx170is/main.bin': No such file or directory
gmake: *** [firsub] Error 1

 

Related Topics