Powershot N Porting Thread - page 14 - DryOS Development - CHDK Forum supplierdeeply

Powershot N Porting Thread

  • 212 Replies
  • 78234 Views
Re: Powershot N Porting Thread
« Reply #130 on: 24 / August / 2014, 14:28:47 »
Advertisements
After reading the last postings, I will confirm that I have the same Problems with my non FB N.
I set my color scheme to blue-gray to have the menue buttons visible.

attached my Palette, it is a little different then koshy┬┤s



Regards, Andreas
« Last Edit: 24 / August / 2014, 14:31:10 by baumandr »

Re: Powershot N Porting Thread
« Reply #131 on: 25 / August / 2014, 12:45:34 »
After reading the last postings, I will confirm that I have the same Problems with my non FB N.
I set my color scheme to blue-gray to have the menue buttons visible.
That looks a lot better!    I probably selected blue-gray when I initially configured my N and never realized it would later affect how the custom palette worked.   That's probably a good thing as we recognized the issue early and it should be simple to fix.  For the next week or so,  N owners need to use the blue-gray scheme if they want to use CHDK.   
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline zeno

  • *****
  • 891
Re: Powershot N Porting Thread
« Reply #132 on: 25 / August / 2014, 15:05:56 »
It turns out that the Powershot N Facebook camera breaks both ACID and STICK's firmware detection routine. The integer EXIf value that they decode (and which works fine for all other cameras) is a negative value which produces rubbish - instead of "100a". I have a work-around which uses special case code to deal with the problem, but I'm not happy with it - who knows if Canon will produce other cameras that cause the same problem.

The EXIF id field for both N cameras is the same (0x338000).

The firmware version of a 'standard' Powershot N is detected properly by ACID and STICK.

Dave

PS EXIFTOOL also fails to produce the 'right' firmware version info - it reports "Alpha 1.50 rev 0.00" instead of "Alpha 1.00 rev 1.00" (or "Alpha 100a")
« Last Edit: 25 / August / 2014, 18:16:12 by zeno »
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline zeno

  • *****
  • 891
Re: Powershot N Porting Thread
« Reply #133 on: 26 / August / 2014, 04:04:12 »
Thinking about it a bit more, how do you developers know what the firmware version of the N Facebook camera is? You can't use ACID, so does the ver.req method work? Is it somewhere in the firmware dump?
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit


Re: Powershot N Porting Thread
« Reply #134 on: 26 / August / 2014, 09:22:50 »
Thinking about it a bit more, how do you developers know what the firmware version of the N Facebook camera is? You can't use ACID, so does the ver.req method work? Is it somewhere in the firmware dump?
I'd assume you could find it somewhere in the firmware dump but I've never tried.  I guess in this case I just assumed it was 1.00A (the conversation about that is probably somewhere in this thread) but it really didn't matter to me as I created the port from the firmware dump.

For all I know at this point - it could actually be 1.03C or something.  :o

Edit :  Koshy originally reported that it had 1.00A based on using ACID
« Last Edit: 26 / August / 2014, 09:28:11 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline koshy

  • *****
  • 1096
Re: Powershot N Porting Thread
« Reply #135 on: 26 / August / 2014, 10:51:00 »
Edit :  Koshy originally reported that it had 1.00A based on using ACID
And he didn't make that up. Screenshot attached. Facebook edition reports Powershot N 100A.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline zeno

  • *****
  • 891
Re: Powershot N Porting Thread
« Reply #136 on: 26 / August / 2014, 11:48:37 »
But that's the Powershot N 100a, which ACID does properly identify.

However when you test ACID with a photo taken with the Powershot N Facebook camera, it does not work. I tried it with the sample photos on the Canon website here:
http://www.usa.canon.com/cusa/consumer/products/cameras/digital_cameras/powershot_n_facebook_ready_blue_jacket_bundle#SampleImages

It's possible that these sample images were taken with a prototype camera. Does anyone have a photo taken with a production Powershot N Facebook camera that they could email me?

daveATzenoshrdlu.com


« Last Edit: 26 / August / 2014, 11:54:16 by zeno »
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline koshy

  • *****
  • 1096
Re: Powershot N Porting Thread
« Reply #137 on: 26 / August / 2014, 11:53:56 »
But that's the Powershot N 100a, which ACID does properly identify.
No it certainly is the N Facebook edition. I never had any other camera and this is the one I dumped the FW of and for which we developed the N FB port. It reports to be a plain N but is not which is why automatic detection is bound to fail anyway.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)


*

Offline zeno

  • *****
  • 891
Re: Powershot N Porting Thread
« Reply #138 on: 26 / August / 2014, 12:01:07 »
Koshy - could you email me a couple of images taken with your camera?

Dave
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline koshy

  • *****
  • 1096
Re: Powershot N Porting Thread
« Reply #139 on: 26 / August / 2014, 12:12:24 »
Koshy - could you email me a couple of images taken with your camera?
Sure. I sent you one. I'm attaching another one for everyone. I overexposed it to make it tiny at full resolution. Since this is about meta data it's irrelevant what it shows.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

 

Related Topics