ELPH300HS aka IXUS220HS - Porting Thread - page 67 - DryOS Development

c10ud

245

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #660 on: 21 / February / 2012, 14:02:40 »

Advertisements

tried with trunk and autobuild, issue persists. i get the same behaviour by simply connecting the 5v usb so i think we can rule out the ptp part from the issue..

kbd&usb..mmm

Logged

c10ud

245

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #661 on: 22 / February / 2012, 11:21:57 »

edit: my bad, i've been trying the whole day and restoring "stock" wrap_kbd_p1_f() makes the thing work. so the problem is definitely inside my_kbd_read_keys()

« Last Edit: 22 / February / 2012, 14:01:03 by c10ud »

Logged

c10ud

245

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #662 on: 22 / February / 2012, 15:06:56 »

after losing a day, i think i can say this diff fixes the E41 error: excuse the big diff but i restarted the port from scratch to be sure i wasn't missing anything and due to the style difference i am too lazy to check where the tiny diff is.
i suspect it's bot the KEYS0 value and some wrong address in boot.c

please try it out and see if it works for you (firmware 101a): http://pastebin.com/210H2Tn9

Logged

srsa_4c

4451

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #663 on: 23 / February / 2012, 19:37:34 »

Quote from: c10ud on 22 / February / 2012, 15:06:56

after losing a day, i think i can say this diff fixes the E41 error: excuse the big diff but i restarted the port from scratch to be sure i wasn't missing anything and due to the style difference i am too lazy to check where the tiny diff is.
i suspect it's bot the KEYS0 value and some wrong address in boot.c

please try it out and see if it works for you (firmware 101a): http://pastebin.com/210H2Tn9

You've managed to find a typo in boot.c . I think that was the cause of the E41 trouble. KEYS_MASK0 should only affect things when in ALT mode, so I left it out from the patch. Can you please retest the stable release with that patch?

I took a quick look at the port's kbd.c, and unfortunately it looks like it contains some mistakes (IMHO). There aren't any buttons defined that would be related to physw_status[0], yet KEYS_MASK0 is not 0 and physw_status[0] is getting messed with instead of physw_status[2]. I don't think this is correct. Same goes for the Ixus230 port.

« Last Edit: 23 / February / 2012, 22:06:43 by srsa_4c »

Logged

c10ud

245

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #664 on: 24 / February / 2012, 06:51:00 »

yup, i noticed that that too, i corrected the keymask0 because i thought it was sort of related to play mode..but i really didn't know what was happening in there. that's probably because of some copypaste (?)

however, thanks for finding the difference, i'll try trunk asap - out of curiosity did you inspect code visually or you just did some regexp magic? if that's the case, i should really learn how to master them, oh well..

Logged

c10ud

245

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #665 on: 24 / February / 2012, 08:56:24 »

tested latest trunk, it works

Logged

David01

6

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #666 on: 24 / February / 2012, 09:31:16 »

Hi all,
I am new in CHDK and I must say that I bought this camera only because it was possible to generate RAW file with the CHDK firmware...
I tried to use the DNG conversion for RAW. I succeeded to create the badpixel.bin (14244 badpixels) but when I compared the result between the DNG loaded in Lightroom and the direct JPEG output, the DNG still have badpixels while the JPEG is clean?
The badpixel.bin was generated in the camera at different iso levels, but always exactly the same number of badpixels. Did it happen for anyone else? Is it due to a wrong usage of DNG?
Thank you for your help.

Logged

hiker_jon

284

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #667 on: 24 / February / 2012, 10:35:10 »

Hi,
I was able to successfully create badpixel.bin and take raw files. (See above for my unfortunate wasting of Phil's time).
Jon

Quote from: David01 on 24 / February / 2012, 09:31:16

Hi all,
I am new in CHDK and I must say that I bought this camera only because it was possible to generate RAW file with the CHDK firmware...
I tried to use the DNG conversion for RAW. I succeeded to create the badpixel.bin (14244 badpixels) but when I compared the result between the DNG loaded in Lightroom and the direct JPEG output, the DNG still have badpixels while the JPEG is clean?
The badpixel.bin was generated in the camera at different iso levels, but always exactly the same number of badpixels. Did it happen for anyone else? Is it due to a wrong usage of DNG?
Thank you for your help.

Logged

David01

6

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #668 on: 24 / February / 2012, 13:59:32 »

Quote from: hiker_jon on 24 / February / 2012, 10:35:10

Hi,
I was able to successfully create badpixel.bin and take raw files. (See above for my unfortunate wasting of Phil's time).
Jon

Hi Jon,
Not sure to understand, but in my case I also succedded to create the DNG. The issue I have is that I still have the bad pixels in the DNG when I open it in Lightroom and the same image in Jpeg is totally clean...
Thanks again.

Logged

philmoz

3450

Re: ELPH300HS aka IXUS220HS - Porting Thread

« Reply #669 on: 24 / February / 2012, 14:39:50 »

Quote from: David01 on 24 / February / 2012, 13:59:32

Quote from: hiker_jon on 24 / February / 2012, 10:35:10
Hi,
I was able to successfully create badpixel.bin and take raw files. (See above for my unfortunate wasting of Phil's time).
Jon

Hi Jon,
Not sure to understand, but in my case I also succedded to create the DNG. The issue I have is that I still have the bad pixels in the DNG when I open it in Lightroom and the same image in Jpeg is totally clean...
Thanks again.

Are you talking about bad pixels or noise?
Post a 100% crop from a sample image showing the problem.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)