SX170 porting - page 2 - DryOS Development - CHDK Forum

SX170 porting

  • 266 Replies
  • 56118 Views
Re: SX170 porting
« Reply #10 on: 07 / July / 2014, 04:24:05 »
Advertisements
Progress so far. While booting the camera shows Canon logo, extends lens, and goes blank. Does not hang though.

Files contain a lot of TODO-s, still working on it.

Re: SX170 porting
« Reply #11 on: 09 / July / 2014, 05: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.

*

Offline nafraf

  • *****
  • 1308
Re: SX170 porting
« Reply #12 on: 09 / July / 2014, 08:53:42 »
2) RAW works but distorts pictures - top half is okay, bottom is garbage. Could it be related to insufficient memory?
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 here

Re: SX170 porting
« Reply #13 on: 09 / July / 2014, 17:41:32 »
hook_raw_image_addr seems okay, both stubs_entry.S suggestion and comparison to other camera firmwares gives the same pointer. Since my camera crashes after taking 2 to 4 raw shots I still suspect some resource limit hit. Will experiment with EXMEM tomorrow.

EDIT Capturing in P does not give much better results than other modes.

Thanks for your sources! I will take time and compare them to mine, maybe this way can get rid of current firmware issues.
« Last Edit: 09 / July / 2014, 17:46:28 by aarmot »


*

Offline nafraf

  • *****
  • 1308
Re: SX170 porting
« Reply #14 on: 09 / July / 2014, 19:44:17 »
I have not received any feedback of 100a testers, maybe the 100a has the same RAW capture bug.

Re: SX170 porting
« Reply #15 on: 10 / July / 2014, 16:09:04 »
am new to this part ... how can I work to test the port. and I have the machine.  8)
« Last Edit: 10 / July / 2014, 17:19:04 by janeoyuri »

Re: SX170 porting
« Reply #16 on: 18 / July / 2014, 08:04:38 »
Good thing CHDK for this model is already advanced in a way, that was the experience with EXMEN?
Hope all fence track. thanking the developers.

Re: SX170 porting
« Reply #17 on: 26 / July / 2014, 18:17:01 »
My parents gift me this camera and I want raw/dng, timelapse e full time video or other hack but whit original firmware it's not possible :(
Any news for stable/mature version ? Thanks for the porting ! ;)
PS: sorry for my english i'm italian member ::)


Re: SX170 porting
« Reply #18 on: 26 / July / 2014, 22:23:16 »
aarmot what is developing ... has not posted news, I guess only time you need and do not see it online, at this point I can not understand this part of the development and I have very little experience that would help with taste, I hope aya news soon.

Re: SX170 porting
« Reply #19 on: 28 / July / 2014, 12:39:50 »
summer, people prefer to go to the beach, I hope a mature firmware hack later or now :lol
Thanks again ;)

 

Related Topics