SD 4000 IS / IXUS 300 HS / IXY 30S porting thread - page 8 - DryOS Development - CHDK Forum

SD 4000 IS / IXUS 300 HS / IXY 30S porting thread

  • 322 Replies
  • 199963 Views
*

Offline brent5000

  • *
  • 3
  • SD400 and IXUS 300 HS
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #70 on: 15 / September / 2010, 13:42:26 »
Advertisements
Installed Beta 1 and played around a bit.  Tried to run a .BAS script that just takes some pictures - could load and start the script - print statements worked, but the script hung when I did the shoot command.

I also checked out out the ixus300_sd4000 branch from your git repository.  Was able to build and load onto my camera, but didn't get any further than that today.

Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #71 on: 18 / September / 2010, 06:41:38 »
If you have specific things you would like me to experiment with let me know.
Please everyone report your Firmware Version.

Sorry about that. CameraVersion v1.2 says:
Firmware version: 100 D
Firmware revision: 1.00 rev 4.00

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #72 on: 18 / September / 2010, 13:13:38 »
No big news currently, slowly making progress...

  • FreeSpace fixed
  • Startup Sound fixed
  • working on capt_seq.c

Thanks for reporting Firmware Version.
Looks like there is currently only one Firmware Version for SD4000.

I've checked some PropertyCase. Looks like propset 3 is correct.
« Last Edit: 18 / September / 2010, 13:23:18 by pixeldoc2000 »

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #73 on: 18 / September / 2010, 16:10:33 »
I've changed boot.c like SX210 and other and enabled all Task Hooks.
capt_sec.c and movie_rec.c finished (overrides).

http://github.com/pixeldoc2000/chdk/commit/5fdfe8e069aec253bb42f7e5ac1923c69afac3d9

I still don't have any CHDK OSD in rec mode (picture or movie) and can't find a reason for it.  :-[
ALT mode does work normal in rec mode.
playrec_mode, movie_status and modemap should be correct.

Any ideas?
« Last Edit: 18 / September / 2010, 16:45:48 by pixeldoc2000 »

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #74 on: 19 / September / 2010, 04:43:22 »
When did you loose chdk in rec mode?

Have you tried to change :
Quote
void vid_bitmap_refresh()
{
 extern int enabled_refresh_physical_screen;
 enabled_refresh_physical_screen=1;
 _RefreshPhysicalScreen(1);
}

to

Code: [Select]
void vid_bitmap_refresh()
{
extern int enabled_refresh_physical_screen;
extern int full_screen_refresh;

extern void _LockAndRefresh(); // wrapper function for screen lock
extern void _UnlockAndRefresh(); // wrapper function for screen unlock

_LockAndRefresh();

enabled_refresh_physical_screen=1;
full_screen_refresh=3;

_UnlockAndRefresh();
}

I look at the addreses you may need and in your cam I found:

NHSTUB(UnlockAndRefresh, 0xFFA13398)   // In sx20 102 : FFA0498C
NHSTUB(LockAndRefresh, 0xFFA13354)    // In sx20 102 : FFA048E8

in stubs_min

DEF(enabled_refresh_physical_screen, 0x92AC+0x20) //found at FFA133D4

Hope it helps!


Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #75 on: 19 / September / 2010, 13:30:35 »
Hi


7 - I tried changing the time display via the CHDK Menu from 24hr to 12 hr - on exiting CHDK menu there was no change to displayed or logged time.


7 - change clock format does work for me and is retained

I was looking for the changes in the Canon display - the format changes are visible in the CHDK OSD shown in OSD Editor. My mistake.

One other observation is that in the CHDK menu for Extra Photo Operations there is no Aperture Override - my understanding is the SD4000 has an iris (source e.g. Canon USA and Asia spec's on website) though it also confusingly refers to an ND filter too. Assuming it does indeed have an iris do you plan to add that to the features ? One thing I really would like is to be able to set the aperture using a method other than by the jog wheel (same for EV values) - I am limited to using the cardinal keys left, right, up and down as the camera is in a housing and they are the only controls I have have available.

I have now downloaded CHDK-Shell, had a look at your source and started to play around though for me it is very slow going - your work is much appreciated !

« Last Edit: 19 / September / 2010, 13:37:47 by Beaver »

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #76 on: 19 / September / 2010, 20:36:29 »
@asm1989
Thanks, but i already did that...
I fixed the issus by adding CAM_SHOW_OSD_IN_SHOOT_MENU in camera.h .


One other observation is that in the CHDK menu for Extra Photo Operations there is no Aperture Override - my understanding is the SD4000 has an iris (source e.g. Canon USA and Asia spec's on website) though it also confusingly refers to an ND filter too. Assuming it does indeed have an iris do you plan to add that to the features ? One thing I really would like is to be able to set the aperture using a method other than by the jog wheel (same for EV values) - I am limited to using the cardinal keys left, right, up and down as the camera is in a housing and they are the only controls I have have available.
I'll look for it!
« Last Edit: 19 / September / 2010, 20:38:16 by pixeldoc2000 »

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #77 on: 19 / September / 2010, 20:37:04 »
Beta v2

A lot issus should be fixed with Beta v2.

Fixed
  • CHDK OSD didn't show in record mode
  • CHDK Menu did partly disappeard while feather osd
  • Jogdial didn't work in CHDK Menu
  • Override didn't work
  • more stuff

ToDo
  • still Crash / shutdown under certian condition
  • some stub address are probably still wrong
  • Sometimes wrong CHDK OSD
  • RAW
  • overrides not tested
  • more stuff

Git: here.

Download: first Post.
« Last Edit: 20 / September / 2010, 13:01:43 by pixeldoc2000 »

Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #78 on: 20 / September / 2010, 08:10:26 »
Very happy to see and load up beta V2. Here is my initial feedback.

CHDK OSD

1 - The CHDK OSD now displays in RECORD and PLAYBACK. It occasionally and seemingly randomly fails - mostly the camera freezes - lens still out - pressing DISPLAY brings it back to life along with CHDK menu retained. On a couple of occasions it has crashed and needs to be rebooted. Is their a debug file I can set that would help to isolate what was happening at the time? Other values set to display are shown and look correct though I have to go over in a bit more detail e.g. Tv as set in CHDK is correct, battery, files.

2 - With the CHDK OSD displayed in RECORD mode the normal camera controls work e.g. in Av can set aperture, EV, mode (macro etc), flash and switch between the Canon menu's.

CHDK Menu

3 - Not as stable as beta v1 - ocassionaly disappears when navigating though menu items. If that happens by pressing the up \ down buttons for example the CHDK menu comes back - sometimes part of it, sometimes in stages and other times all of it in one go.

4 - Jogwheel does always seem to work when navigating all menu items. I will test this again later and try to provide some specific examples when I can repeat.

Overrides :)

5 - Tv. Appears that on a single shot the camera is not exposing as set in CHDK. If the shutter is half-depressed it first does show the Tv value set but then changes to what the Canon system calculates. On taking the picture the exposure value shown is as set in CHDK but the image appears to have been exposed by the Canon calculation. I did a couple of shots where the Tv value should have produced for example an under exposure. I made sure safety shift was off on the Canon menu.

6 - Bracketing. This is nearly working as I expected :) For me this is great - OSD \ Histogram are move to have but secondary - having this functionality gives us control of the exposure. Even though single Tv exposures do not seem to be taken as per the CHDK value set when in bracketing mode with continuous exposure it is working. It looks like that in each of my first shots in the sequence though is as in 1) above it is not made according to the Tv override value set in CHDK - however the rest of the sequence is correct ! I will look at this in a bit more depth later and run some better test sequences and play around with other Tv functions in CHDK and see how they perform.

Histogram and other OSD items

7 - The display area comes up on the OSD but I am not getting a live histogram - its a single color box. I have tried various color settings in the Menu items for the histogram background, border, lines etc but nothing actually gives me a viewable live histogram. Nothing on zebra or outline either but I didn't expect to see those.

RAW

8 - While set up in CHDK I am unable to save a RAW image file - also the OSD says "RAW DISABLED" on stat values on the CHDK OSD even though as I said the CHDK Menu is set up to save RAW images. Strange.


Conclusion to date

V2 is a big improvement - OSD values shown and Tv \ bracketing. If you could get Av \ aperture overrides to work in the same way, and I assume aperture bracketing as per Tv above would also work, this would at least give a high degree of control and would be a great start. Will do some more extensive tests later and update this post.

Thanks again !!

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #79 on: 20 / September / 2010, 12:56:05 »
@Beaver
Thanks for your intensive feedback!

I'm gonna look for it and anser in this post.

1 - debug log (called romlog) could be created with lua script, but i noticed it does not work (http://chdk.wikia.com/wiki/LUA/Scripts:Standard/Test/Romlog)... gonna fix that...
But http://chdk.wikia.com/wiki/Canon_Basic#RomLog does work, because it uses Canon native basic script. Best to prepare a second sd-card as "script_disk". Thats how i do currently. If camera does shutdown, camera does write a so called assert to romlog. On crash sadly camera does not write romlog most of the time.

3 - i noticed chdk menu does (partly) disappears if canon firmware does show "special" thing on display like face detection. Either we have to disable (suspend) all this stuff in ALT mode or there is an easier methode to do this, dunno.

5 & 6 - did not much testing on overrides... most of the code related to overrides is just "guesswork"...

7 - histogram and simpular stuff issus are related to video buffer. This has changed on recent cameras like SD4000... also lot of guesswork here currently...

8 - missed to write earlier, raw hooks not are done yet

EDIT: corrected some typo's...  :haha
« Last Edit: 20 / September / 2010, 18:31:47 by pixeldoc2000 »

 

Related Topics


SimplePortal © 2008-2014, SimplePortal