IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch - page 32 - General Discussion and Assistance - CHDK Forum
supplierdeeply

IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch

  • 381 Replies
  • 116192 Views
*

Offline sylikc

  • **
  • 66
  • SX230HS 1.00c, SD750 1.02a ;)
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #310 on: 12 / November / 2008, 15:17:32 »
Advertisements
auto mode is for wussies anyway ;)
While I agree with you, unfortunately, Auto, Manual, and Stitch modes are all considered "auto" on the SD750... there's only 3 switch places, Movie, SCN, Auto ... so even doing Manual is on the "Auto" switch

we can fix this somehow, you have to assist though.
Login run the attached build from this link, while in record mode and in auto mode. what is the output?

--SCN--
rec: true vid: false
mode: 256 nil

--MOVIE--
rec: true vid: true
mode: 265 VIDEO_STD

--AUTO--
rec: false vid: false
mode: 513 AUTO

(btw, in AUTO mode, the display goes away as soon as it would usually say "finished".  Like the output doesn't stay on screen for whatever reason)


/sylikc
props to TPC + PhyrePhox for SD750 work: IXUS75/SD750 1.01a | 1.00b | 1.02a Thread
props to quietschi for multipartition support + button fixes!
SD750 bracketing issues

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #311 on: 12 / November / 2008, 15:40:29 »
hm, thats odd. i dont really know how to tackle that bug, but maybe another dev has an idea.

edit: well chdk thinks it is in playmode when you are in automode, thats also whats causing the script bug with the finished thingy.
« Last Edit: 12 / November / 2008, 15:44:07 by PhyrePhoX »

*

Offline reyalp

  • ******
  • 12162
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #312 on: 12 / November / 2008, 17:12:11 »
In CHDK menu->miscellaneous->debug

select memory browser
enter 56910 (zoom lever adjusts how much left and right add)
report the hex value of the DWORD section as you go through the different modes.
Don't forget what the H stands for.

*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #313 on: 12 / November / 2008, 19:58:47 »
Hmm, in platform/ixus75_sd750/sub/nnn we have "long" Makefile(s), for other cameras we have there "short" Makefile(s).

p.s.  message "CAUTION! 'stubs_entry.S' is not uptated due to target firmware binary not found!" contains typo or not?


Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #314 on: 12 / November / 2008, 20:04:35 »
(to Cohen's "Hallelujah")

Yaaay, it works, it works! Joined up just so i could say that.

1.01B, #562 autobuild boots up fine, autoboots fine. Happy to assist with any debugging if you tell me what to do! Haven't tried anything past the basics yet tho...

---report the hex value of the DWORD section as you go through the different modes.
If by modes you mean movie, scene, auto, the values are 0040EFF[E|D], 0040FFF[E|D], 0040BFF[E|D] respectively. The last bit keeps switching between E and D all by itself.

I'm not sure if this is a CHDK thing or a canon thing, but does anyone know how to turn off the 4-way pad display on the screen, as it messes up the CHDK menu display?
IXUS 75, 1.01B, latest autobuild :)

*

Offline reyalp

  • ******
  • 12162
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #315 on: 12 / November / 2008, 20:23:00 »
Gowachin: what does it show in playback mode, for each position of the record mode switch ?


@ewavr yes, that's a typo, should be updated. Good catch on the makefile too, looks like it should be including makefile_sub.inc
Don't forget what the H stands for.

Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #316 on: 12 / November / 2008, 20:49:24 »
Gowachin: what does it show in playback mode, for each position of the record mode switch ?

The values are as per my previous post, in both playback and record mode.
IXUS 75, 1.01B, latest autobuild :)

*

Offline reyalp

  • ******
  • 12162
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #317 on: 12 / November / 2008, 20:58:16 »
The values are as per my previous post, in both playback and record mode.
OK, that helps.
Can you do the same for 5690C and 56908 ?
Don't forget what the H stands for.


Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #318 on: 12 / November / 2008, 21:53:45 »
OK, that helps.
Can you do the same for 5690C and 56908 ?

In playback mode,
5690C gives [F|D]300Dx28 (x is fast switching between multiple values, [a|b] is between 2 values)
56908 gives x01C0040

In record mode,
5690C gives [D|F]300Dx[2|0]8
56908 gives x0FC0[2|6]45

Sorry if my notation is confusing - the buggers won't hold still!
IXUS 75, 1.01B, latest autobuild :)

*

Offline reyalp

  • ******
  • 12162
Re: IXUS75/SD750 1.01a | 1.00b | 1.02a - Update 09Nov2008 - Passing the Torch
« Reply #319 on: 12 / November / 2008, 23:08:20 »
In playback mode,
5690C gives [F|D]300Dx28 (x is fast switching between multiple values, [a|b] is between 2 values)
56908 gives x01C0040

In record mode,
5690C gives [D|F]300Dx[2|0]8
56908 gives x0FC0[2|6]45

Sorry if my notation is confusing - the buggers won't hold still!
No, that's great. I assume the above two don't do anything different depending on auto/movie/scene mode ?

From the above, it looks like we might be able to use record = (physw_status[0] & 0x00E00000) or one of those bits.

But it looks like some cameras use a different address entirely, called playrec_mode
Can you check D2A0 ?
Don't forget what the H stands for.

 

Related Topics