ELPH300HS aka IXUS220HS - Porting Thread - page 37 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 32 33 34 35 36 [37] 38 39 40 41 42 ... 90   Go Down

ELPH300HS aka IXUS220HS - Porting Thread

  • 899 Replies
  • 399470 Views
*

Offline jstanley0

  • **
  • 71
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #360 on: 29 / November / 2011, 08:25:14 »
Advertisements
Quote from: dotslashcow on 29 / November / 2011, 01:06:40
The scene gets darker with the filter in. I tested a fairly dim scene where the camera automatically swings the filter out, but CHDK forces it in, making it too dark (=> it works)

My mistake.  I thought "in" means it's stowed, and "out" means it's deployed.  The image was not made any darker with the filter "out", so it must not be working.  ::)

Quote from: dotslashcow on 29 / November / 2011, 01:06:40
A couple of days ago, when I was trying one of the older builds (don't remember which one now :'() I could actually set the "aperture" to THREE different values, not two. F16, F8, and F2.7.
I even used the F16 stop for a long exposure shot of traffic in the night with a 10 second shutter!
Which would mean that there is something other than the ND filter at work in this camera?

There is something at work, namely the fact that, despite there not being an aperture diaphragm, the effective aperture is narrower when you zoom the lens.  The front of the lens is labeled F2.7-F5.9; that's roughly two stops, so equivalent to the difference between the fake apertures F8 and F16.
Logged
*

Offline dotslashcow

  • *
  • 21
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #361 on: 29 / November / 2011, 09:33:37 »
Quote from: jstanley0 on 29 / November / 2011, 08:25:14
The image was not made any darker with the filter "out", so it must not be working.  ::)
:haha :)
That didn't strike me at all, or I might have thought the same thing :P

Quote from: jstanley0 on 29 / November / 2011, 08:25:14
the effective aperture is narrower when you zoom the lens.

This is very interesting.

I played around with the aperture settings and found something a bit strange:


  • I set the aperture override to OFF and:
    • The camera sets it to F2.7
  • I set the aperture override to 16.00 and:
    • The camera sets it to F8.0
    • The photo is darker than the previous one

So I think, hmm maybe the ND filter is being deployed and the camera is pretending that the ND filter makes it F8.0?
So I set the CHDK ND filter override to "Out" and try again, and I get exactly the same results!

Aperture override: Off
Aperture value used by camera: F2.7
Shutter speed: 1/10
ND filter override: Out


Aperture override: 16.00
Aperture value used by camera: F8.0
Shutter speed: 1/10
ND filter override: Out




Am I missing something here?   ???

Update: I'm very confused.
Taking photos without aperture override (auto-set to F2.7) and WITH the ND filter yields exactly the same results as an aperture override of 16.0 (auto-set to F8.0).
This leads me to believe that the camera is for some reason trying to fool me into believe it can set the aperture to values that it actually cant, while simply using the ND filter.
Or CHDK is fooling the camera into believing that it can do things it can't?  ???
« Last Edit: 29 / November / 2011, 12:45:23 by dotslashcow »
Logged
*

Offline FreakDBB

  • *
  • 1
  • Ixus 220 HS FW 1.01d
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #362 on: 29 / November / 2011, 13:24:23 »
Hi there,

first of all, i want to thank everyone working hard to get CHDK running on this camera!

My camera has FW-Version 1.01d and I'm using yesterdays build. When I use the autoload function, and start up the camera already connected to the pc or connect it after starting, I just get:

Code: [Select]
A camera error was detected
Will shut down automatically
Restart camera
E41
The short "splashscreen" giving mit the CHDK - Version and so on is in this case red and not orange.

In case I load CHDK manually and connect the camera to the PC, it just goes the review - mode, shows one picture and does not react to anything but the ALT-key. It is also not being "recognized" by the computer.

Any idea about that?

Keep up the good work!


Logged
*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #363 on: 29 / November / 2011, 14:41:29 »
Quote from: waterwingz on 28 / November / 2011, 23:16:44
You are correct - there are a number of ports where one firmware version matches another.  Checking the stubs and maybe the three C task files should be all that is necessary to assure a match.

I'm wondering if creating a separate 101d variant would make sense?

Until now we only know that some 101d users are satisfied with 101c firmware.
Should we stay with three variants (100c, 101a, 101c) and wait with creating 101d variant until 101d users report differences or problems we don't see on other variants? Or should we add 101d variant immediately to our platform that Autobuild server can create 101d builds as well?

I would prefer to add the 101d variant to our platform to avoid confusion for 101d users.
Logged
*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #364 on: 29 / November / 2011, 15:15:06 »
I was reading this thread http://chdk.setepontos.com/index.php?topic=7124.0 and remembered my own problems with creating badpixel.bin file.

Phil provided a solution for my bad RAW images:
Quote from: philmoz on 27 / November / 2011, 14:22:57
In this case the RAW buffer addresses looks OK; but the location of the active buffer is wrong.
From looking at the firmware is should probably be 0x2E94 not 0x3F04 (see sub_FF884C18 in 1.00c firmware).

I just thought that badpixel.bin generation could now also be possible after shooting RAW images was fixed.

And I'm happy to tell you that a badpixel.bin file has been generated during the first try. :)

Who hasn't generated a badpixel.bin file until now should try it once again.

Logged
*

Offline tommi2water

  • ***
  • 157
  • IXUS 220 HS Firmware: 1.00c
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #365 on: 29 / November / 2011, 15:49:30 »
Currently I'm working on the Modemap table from shooting.c file which is checked and reported in stubs_entry.S file. As Phil mentioned we get many errors reported. I didn't mind about that until now because I never knew what these modes are necessary for. ;)

How to find out correct values or verify existing Modemap table (CapturemodeMap modemap[]) entries in shooting.c :
I found out that in <ALT> Menu -> Misc -> Debug Parameters these mode values can be made visible very easy. Just activate "Debug Data Display [Props]" and "Propcase Page 5". Entry no. 50 will show the value for the current active mode. I will check each mode which can be activated in the Canon software and update shooting.c file.

My battery just died so I will work on this task tomorrow when my battery is recharged again. :D
Logged
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #366 on: 29 / November / 2011, 16:35:17 »
Quote from: tommi2water on 29 / November / 2011, 14:41:29
Quote from: waterwingz on 28 / November / 2011, 23:16:44
You are correct - there are a number of ports where one firmware version matches another.  Checking the stubs and maybe the three C task files should be all that is necessary to assure a match.

I'm wondering if creating a separate 101d variant would make sense?

Until now we only know that some 101d users are satisfied with 101c firmware.
Should we stay with three variants (100c, 101a, 101c) and wait with creating 101d variant until 101d users report differences or problems we don't see on other variants? Or should we add 101d variant immediately to our platform that Autobuild server can create 101d builds as well?

I would prefer to add the 101d variant to our platform to avoid confusion for 101d users.


There are a number of cameras where one CHDK version will work for two or more Canon firmware versions.
If 1.01c loads and runs on a 1.01d camera then it's likely the firmware differences don't affect CHDK (possibly just some corrections to different language text).

If this is the case then the autobuild process can be set up to automatically generate a 1.01d version by copying the 1.01c files - this is a convenience so people can find their version without constantly asking which one to use. It also saves creating and maintaining another firmware version directly.

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)
*

Offline unARMed

  • *
  • 9
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #367 on: 29 / November / 2011, 17:07:53 »
Quote from: tommi2water on 29 / November / 2011, 15:49:30
How to find out correct values or verify existing Modemap table...

Here's the values I get on 1.01c going down the modes:

P - 32772
Digest - 33333
Portrait - 32783
Kids&Pets - 32786
Smart Shutter - 33321
High-Speed Burst - 33288
Best Image Selection - 33289
Handheld Nightscene - 33325
Low Light - 32801
Fish-eye Effect - 33323
Miniature Effect - 33324
Toy Camera Effect - 33327
Monchrome - 33330
Super Vivid - 33318
Poster Effect - 33319
Color Accent - 33309
Color Swap - 33310
Beach - 32791
Underwater - 32793
Foliage - 32789
Snow - 32790
Long Shutter - 32774
Stitch Assist --> - 33292
Stitch Assist <-- - 33292
Super Slow Motion Movie - 2626
Logged
*

Offline siloxr

  • *
  • 6
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #368 on: 29 / November / 2011, 19:27:40 »
Hello all, I found out about this CHDK thing today, spent some time looking around for info on my specific camera (the ELPH300) and found out that I apparently have firmware version 1.01e.  If one of y'all can point me to a fairly painless way to pull and dump this for y'all if you're interested, I'd be happy to do so.

I'm going to try to use the 1.01c on it to see if it works.

Ok, so I put the 1.01c on it and loaded it using the manual mode (having to go through the firmware update to turn it on) and I got the splash screen (it was up for too short of a time to tell exactly what it said), and now I've got what I assume to be my open memory (962M) the always own battery display with percentage, the time, and "opt:28°".  I haven't discovered any other differences yet (not in the menus or function).

Alrighty, so I got into the menu for CHDK, the histogram options work, I've not been able to get RAW to work though, but that might just be me.  I'll stop playing with trying to figure out what options work and which ones don't for a bit to attempt to get this firmware up to y'all.
« Last Edit: 29 / November / 2011, 20:14:01 by siloxr »
Logged
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #369 on: 29 / November / 2011, 19:52:23 »
Quote from: siloxr on 29 / November / 2011, 19:27:40
If one of y'all can point me to a fairly painless way to pull and dump this for y'all if you're interested, I'd be happy to do so.

http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
Pages: 1 ... 32 33 34 35 36 [37] 38 39 40 41 42 ... 90   Go Up
« previous next »
 

Related Topics