IXUS160/ELPH160 Porting attempt

reyalp

14080

Re: IXUS160/ELPH160 Porting attempt

« Reply #330 on: 13 / December / 2015, 20:09:53 »

Advertisements

Quote from: srsa_4c on 13 / December / 2015, 18:25:56

I believe that no framebuffers (= those we're using) have a height over 240 pixels, so the 480 in the source is not correct. (but that's probably not all)

Agreed. This really needs someone to go through all the viewport/bitmap values. I'll try get around to it eventually if no one else does. Maybe after that is a good point to add it to the autobuild.

Quote

The firmware update boot can be useful sometimes (I usually use that to make a card bootable). Due to our unwritten rules, we don't publish those files here.

FWIW, I avoid posting the keys, but I don't see any problem posting FI2 files. (disclaimer: not a lawyer

)

Logged

Don't forget what the H stands for.

harpmaster

4

Re: IXUS160/ELPH160 Porting attempt

« Reply #331 on: 15 / December / 2015, 20:33:19 »

hallo, i am very new in handling with a camera, but in the short time i am working with the ixus 160 and the last chdk-built i want to report what i did yet:

made a sd-card bootable with cardtricks144, installed ptpcam and ptpcamgui on my pc and let this gui work for me.
all the possible buttons are working very good, slow, but they are doin their job. also the dng-captures are working. so far so good, i am very happy that you sent me this maybe instable built to test but i didn't recognized any problem. thanks a lot!

« Last Edit: 15 / December / 2015, 20:40:42 by harpmaster »

Logged

waterwingz

12139

Re: IXUS160/ELPH160 Porting attempt

« Reply #332 on: 15 / December / 2015, 21:24:52 »

Quote from: harpmaster on 15 / December / 2015, 20:33:19

made a sd-card bootable with cardtricks144

Thanks for the report.

Be aware that the CardTricks program is very old and does not correctly handle SD cards larger than 4G in size. If you would like to use a better utility to correctly format and setup CHDK on a larger card, the STICK Utility is highly recommended.

For loading an unofficial build like the ixus160, you will also need to read this as well : STICKX

Logged

Ported : A1200 SD940 G10 Powershot N G16

harpmaster

4

Re: IXUS160/ELPH160 Porting attempt

« Reply #333 on: 16 / December / 2015, 03:27:52 »

thank you waterwingz
it seems i had a little bit luck, i used a 4 gb card. so the next time i am warned.

Logged

duerig

19

Re: IXUS160/ELPH160 Porting attempt

« Reply #334 on: 16 / December / 2015, 23:05:14 »

I just ran into a crash myself during capture. It is flaky, but it happened during remote capture after I had just AF-locked the focus. I have attached the romlog.log. Ideas?

-D

ROMLOG.LOG (3.3 kB - downloaded 22 times.)

Logged

srsa_4c

4451

Re: IXUS160/ELPH160 Porting attempt

« Reply #335 on: 17 / December / 2015, 12:06:24 »

Quote from: duerig on 16 / December / 2015, 23:05:14

I just ran into a crash myself during capture. It is flaky, but it happened during remote capture after I had just AF-locked the focus. I have attached the romlog.log.

The crash was a consequence of the AF lock procedure.

For devs: DoAFLock sends message #0x11 to captseqtask, and one of the fw routines there failed. The failed routine is in ImgSensDrvConv.c, could be related to something like 'sensor operating mode' (that's a guess).

Question:
Can you reproduce it?

Logged

duerig

19

Re: IXUS160/ELPH160 Porting attempt

« Reply #336 on: 17 / December / 2015, 12:51:39 »

It happened twice in a row (once on one camera, once on a second camera), but didn't happen again over a dozen or so trials. I'll try a more systematic stress test and see if I can reliably get it to happen once every N trials.

Two other kinds of problems that I've heard about, but don't have crash logs for:

(1) is the auto-focus going wonky when AF-lock is left off. The camera can look at a scene and take several crisp shots with AF on, but then start taking blurry shots. The blurry shots consistently happen until the camera is power cycled.

(2) is random crashes after a large number of remote captures (>30). No AF Locking is used in these cases from what I hear. I haven't got any crash logs back from one of these cases yet. Could be the out of memory bug from before. Could be something else.

So far, I have distributed a build to a number of users and nobody has reported a bricked camera yet.

-D

Logged