ELPH300HS aka IXUS220HS - Porting Thread - page 64 - DryOS Development - CHDK Forum  

ELPH300HS aka IXUS220HS - Porting Thread

  • 899 Replies
  • 399439 Views
*

Offline fe50

  • ******
  • 3147
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #630 on: 01 / February / 2012, 14:55:59 »
Advertisements
Are 16gb cards useable on the Ixus 220 HS?
Yes.
The ELPH300 can boot from FAT32 partitions, so partitioning the card is not necessary (and also not supported).

... - cameras released this year can autoboot CHDK from FAT32 partitioned cards.

If the port has been done correcly you should be able to set up autoboot from within CHDK:
- format the card in the camera
- copy the full build to the card
- lock the card and perform a manual boot (Firm Update...)
- Select 'Make Card Bootable' from the 'Miscellanous stuff' menu
- Restart the camera

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #631 on: 01 / February / 2012, 15:11:38 »
Cool. I assumed it wouldnt work as I used chdk on a Canon S95 before and it needed to be dual partitioned etc. Many thanks. This is much easier!

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #632 on: 01 / February / 2012, 19:08:46 »
I've tried the long exposure, for around 4 secconds at 400 ISO, and it seemed fine, just overexposed.  No artifacts.

What firmware version do you have? I have 100c and as you saw it's ugly :(


but then later i wen't back to the menu and i couldnt get the long exposure to come ?! WTF. it's not comming any more, and how did you get down to 80ISO? i couldnt. :(


Again what version of firmware do you have? After reboot I have to Enabled Overrides in Extra photo Operations. Also I have to set Valuve factor to 1 in order for Override shutter speed to work. I set ISO to 80 Like this in Extra Photo Operations:

Override ISO Value: 8
Value Factor: 10

Then you see in gray orange that ISO is 80.


the Script should mark those bad pixels and either override them or save their position so processing software later can remove them. second option didn't work for Camera raw


What script?

Lens Profiles:

Thanks to danistuta we have profiles & readme here:
http://chdk.setepontos.com/index.php?topic=6341.msg79233#msg79233

Hm since I use gimp + ufraw I'll have to find a way to include those profiles in gimp.


Can someone cofirm with version 100c that when shooting long exposures and dng enabled the picture is like mine in the attachment? (Or am I the only one with this weird problem?)



Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #633 on: 01 / February / 2012, 23:50:03 »
Hi,
Just got a loan of this camera.  Firmware 101a.  When I checked (in lib.c)
void *vid_get_viewport_fb_d()
{
   //FF06C580 dword_FF06C580  DCD 0x3C70
   //FF06D300                 STR     R12, [R5,#0x58
   return (void*)(*(int*)(0x3C70+0x58));                 

}
in my tests this always returns 0.  So I think the address may be wrong.
Has anyone else checked this? This is the play viewport address.  As far as I know it only affects
the edge overlay in play mode.  Probably not an often used feature.  I use it to display stereo pairs in
play mode.

I know that someone (reyalp?) worked some magic (without even having the camera) for the SX150 and found out the right address.  What did he do?  I'd like to know that and would like to fix this.

EDIT:
Found it.  The address should be 0x2C60.  Found it by searching memory for two adjacent addresses pointing to the same memory address that was in a reasonable range: 0x40xxxxxx.  I took the higher address.

Jon
« Last Edit: 02 / February / 2012, 01:23:55 by hiker_jon »


Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #634 on: 02 / February / 2012, 01:45:24 »
Hi,
Now that I know the play viewport address I still have a problem: not enough buttons on the camera!  I want to use the func/set button in play mode, but Canon uses that for erase in this camera.  So my idea is to do the following:  the camera has a switch in the upper right that switches between auto and non-auto mode when in record mode.  I don't think it does anything in play mode.  So I would like to use that switch like a button in play mode.  Anyone know how to sense the position of that switch?  I want to sense that it has changed twice within some small amount of time.  Any suggestions on how to do that?

Thanks,
Jon

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #635 on: 02 / February / 2012, 02:04:56 »
Hi,
Another correction to the port:  From stubs_entry.S:
//DEF(recreview_hold                          ,0x00003828) // Found @0xff8a6510, ** != ** stubs_min = 0x000094c4 (0x93D4+0xF0)

stubs_min should be edited to the correct value:DEF(recreview_hold, 0x3828)

Jon

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #636 on: 02 / February / 2012, 03:07:34 »
Found it.  The address should be 0x2C60.  Found it by searching memory for two adjacent addresses pointing to the same memory address that was in a reasonable range: 0x40xxxxxx.  I took the higher address.

Looks good to me (from firmware 1.00c):
ROM:FF878880                 LDR     R5, =0x2C08
....
ROM:FF8788B8                 STR     R12, [R5,#0x58]

0x2C08 + 0x58 = 0x2C60

Hi,
Now that I know the play viewport address I still have a problem: not enough buttons on the camera!  I want to use the func/set button in play mode, but Canon uses that for erase in this camera.  So my idea is to do the following:  the camera has a switch in the upper right that switches between auto and non-auto mode when in record mode.  I don't think it does anything in play mode.  So I would like to use that switch like a button in play mode.  Anyone know how to sense the position of that switch?  I want to sense that it has changed twice within some small amount of time.  Any suggestions on how to do that?

You can enable display of the phsyw_status values in the gui_draw_debug_vals_osd() function in gui.c.
From this you can determine which bit(s) are used for the switch status. This is the easy part.

You will then need to add custom code to platform/ixus220_elph300hs/kbd.c that detects the change you want to trigger on, and then returns a standard KEY_xxx value to the rest of the CHDK code. This is the hard part :)

Phil.
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)

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #637 on: 02 / February / 2012, 12:24:38 »
Thanks Phil,
I followed your suggestion and found the bit: physw_status[2] & 0x002000


Jon


You can enable display of the phsyw_status values in the gui_draw_debug_vals_osd() function in gui.c.
From this you can determine which bit(s) are used for the switch status. This is the easy part.

Phil.



Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #638 on: 02 / February / 2012, 19:43:00 »
Can somebody help me?

I have a canon ELPH 300hs/IXUS 220hs and i want to know if there is any way i could lock AE in video mode.

Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #639 on: 07 / February / 2012, 05:54:41 »
Is it possible to lock the exposure in movie mode?


if there is any way i could lock AE in video mode.
You don't need CHDK to do this.
In P mode (not Auto), half press the shutter button and hold it, then press the macro button.
You will then get "AFL" in the top right of your display, which means focus is locked.

« Last Edit: 07 / February / 2012, 05:57:59 by Kerosene »

 

Related Topics