the sx20 porting thread

f_m_b

ultimA
Again, I am missing something. Sorry I feel so stupid. But I just tried and I don't seem to be having a problem with this. I have
- Fast Ev Enabled
- Show Ev enabled in OSD settings (Misc.)
- Zebra enabled (both Solid or Blink)

No, i think it's my problem to describe the problem well.

I try to say it in other words:
With "Fast Ev Enabled" i can change the EV-Value when shutter is half pressed with jogwheel.
But i can only see the Value "EV: xxx" on the Display when shutter isn't pressed.
I have this problem with and without zebra. (I just realised that my patch only helps in zebra mode.)
So why we can't show this value while changing it with the jogwheel and half shutter pressed?

When pressing once the hardware "+/-" button i can change it from -2 to +2 and can see it although in the "EV: xxx" form.
But the fast mode works only with half shutter pressed? And there is this information not displayed.

You described, that in misc i can activate this information...
Please give me the full menu-path for it.
I only found the absolute values "Show Set Exposure Ev" and "Show Measured Ev". But the relative changes of it i can't find.

ultimA

f_m_b
You described, that in misc i can activate this information...
Please give me the full menu-path for it.

* OSD parameters->Miscellaneous Values->Show Overexp. Value
* OSD parameters->Miscellaneous Values->Show Canon overexp. Value

f_m_b
With "Fast Ev Enabled" i can change the EV-Value when shutter is half pressed with jogwheel.
But i can only see the Value "EV: xxx" on the Display when shutter isn't pressed.
I have this problem with and without zebra. (I just realised that my patch only helps in zebra mode.)
So why we can't show this value while changing it with the jogwheel and half shutter pressed?

Once you have enabled the above two options, they are shown whenever the OSD is shown, even with Fast Ev switch. Although they sometimes do not update. In this case a release and half press will update it.

f_m_b
But the fast mode works only with half shutter pressed?

Yes, shutter must be half pressed. This is documented behaviour, so I think this is okay. It is of course subjective how people like it better.

f_m_b

ultimA
...* OSD parameters->Miscellaneous Values->Show Overexp. Value...
Once you have enabled the above two options, they are shown whenever the OSD is shown, even with Fast Ev switch. Although they sometimes do not update. In this case a release and half press will update it.

Thank you. You are right.
While changing Fast Ev the shown values often are not updated, but with the workaround "release and half press" it works.
I think the update problem with Fast Ev changings in zebra is the same .

f_m_b

f_m_b Aug 27: RAW "Dark Frame subtr." = off doesnt works. Function is maybe not ported well.
I think i can't fix it.
Maybe someone can find the correct Code in the Firmware and port this? 😀

gimzo

f_m_b Aug 27: RAW "Dark Frame subtr." = off doesnt works. Function is maybe not ported well.

Joining the wishlist for this to work. 1.02D here.

Other than that, I've been playing with ultimA's 913 and 919 and everything seems to work (zebra seems to lock the camera when I first try to shoot after turning it on, after reboot everything works, but anyway I turned zebra off, everything else works fine).

Thanks a lot for your hard work, I'll try to help with testing when anything new comes out.

f_m_b

Hello gimzo

I dont' know if in ultimA's 913 and 919 the zebra patch is included.

Please try following version based on release 926:
- includes my zebra patch for sx20.
- includes patchV5 "edge detection" from ultimA.

Full Version for 1.02b
Full Version for 1.02d

So the memory crashes for the sx20 should be past... !!!???
To see if it works with "lower" memory conditions, this version although includes all other Stuff like Games, Kalender,... 😉

Edit: Sorry, i had forgotten to "free" the games in camera.h. Link is actualized.

ultimA

I also had a build posted on 22/Aug which included zebra+edge patches.

f_m_b
So the memory crashes for the sx20 should be past... !!!???

Yes, they should be a thing of the past. I checked the source of the games, they do not make dynamic memory allocations (except for sokoban), and since the memory won using the patches is much larger than the code size of the games, it should be fine. Although we cannot guarantee it. As for sokoban, from what I can tell reading the source the largest memory reservation it makes is 255 bytes, but it can make many of them, so I cannot tell how much it reserves in total. The proof of the pudding is in the eating.

Anyway, I can hopefully start today working on the last patch to mark the SX20 stable, but I am still missing some tools for it. Also, I didn't yet check/try the "Dark Frame subtr." bug and I have no idea what it is. Can someone summarize it in short?

f_m_b

ultimAI also had a build posted on 22/Aug which included zebra+edge patches.

You are right. I had forgotten that. 😀

ultimAAnyway, I can hopefully start today working on the last patch to mark the SX20 stable, but I am still missing some tools for it. Also, I didn't yet check/try the "Dark Frame subtr." bug and I have no idea what it is. Can someone summarize it in short?

Some links to darkframe subtraction:
http://chdk.wikia.com/wiki/CHDK_firmware_usage#RAW_parameters_menu
http://chdk.wikia.com/wiki/CHDK_User_Manual#Dark_Frame_Subtraction

...or in my more simple words:
There a 3 modes for "Dark Frame subtraction" [on, off, auto]

"auto": camera use the darkframe-correction of the original canon firmware.
To reduce the noise with longer exposure time (t>1s) the camera shoots after the real foto another foto with closed aperture and same settings (altogether: double time for shooting a foto). In this time the camera is disabled and displays "Busy". With this darkframe-correction the camera eliminates noise errors like "glow amp", badpixel (which appears after longer exposure time),....

"on:" camera always get a darkframe.

"off:" camera doesn't get a darkframe.
The foto needs only the exposure time and has more noise.
This feature is often used from Astro-photographer to avoid spare times between foto series. Noisreduction is later the job of the PC with manual created darkframes.

@fe50: Thank you for explaining me this feature. I hope i had transfered it in a correct way.

ultimA

I meant to explain the bug, not what dark frame subtraction is 😁 It would have been enough to say something like "the settings are not honored, but no crash". anyway, thank you. I had my trouble with it, but I fixed dark frame.

It turned out that many things were wrong in the port, I am even surprised that they didn't result in crashes up until now. First, the address of the NR flag was obviously wrong, it was unchanged from the SX10 port even though that address was not used even once in the firmware code. Second, just before the line where capt_seq_hook_set_nr was called in the ASM, the PC was written directly (!!!) so the call after that to capt_seq_hook_set_nr might not have even been made. Also, this ASM is referenced in two places in the factory FW, but the custom code in the port was only called from one place. And if that wasn't enough, lastly, a BL jump of the same ASM function was totally wrong, jumping to some bogus address instead of the valid function. But these are all corrected now.

I am starting to get the hang of reading ASM. CHDK is a nice excercise 😀

fe50

ultimAIt turned out that many things were wrong in the port, I am even surprised that they didn't result in crashes up until now.

Therefore the SX20 port is still in beta state (much longer than some other new ports) and i've disabled it for the autobuild server 😉

BTW - good work, i guess the SX20 port will soon be grown-up...

ultimA

@fe50: Things really work now, crashes haven't been seen for a while (except for zebra+edge but those are corrected since then) and many people are using the builds without problems. So I *do* think it is almost mature. The only thing left to make work is the remote shutter, and I am planning to do that today. The bug list on the wiki page is practically cleared. So after I finish the remote shutter, I would like you to make it stable and enable the autobuild. Would that be possible? I understand why it was marked as beta so I never asked to make it stable before, but the issues are solved now and I see no reason not to any more.

@f_m_b: Can I post your zebra patch together with everything so that they can be applied in one go?

fe50

ultimA
So after I finish the remote shutter, I would like you to make it stable and enable the autobuild. Would that be possible?

Yes, of course !
Just post a diff / your code when you're ready, i'll update the trunk & enable the port in the main makefile for auto building 😁

f_m_b

ultimA@f_m_b: Can I post your zebra patch together with everything so that they can be applied in one go?

Just do it. You are welcome.

f_m_b

ultimABut these are all corrected now.

Remote USB does not work? Was this only a problem from 1.02d? Because i have already used this feature with 1.02b.
Your changes with NR=off belongs only to 1.02d or although to 1.02b? 😀

ultimA

Two people have separately reported it not to work. Also, the changes I had to make yesterday to make dark frame subtraction work also touched parts of remote usb. Dark frame and remote both had the same issues (except for the NR flag address of course). So I can imagine that remote usb only worked depending on which function called the corresponding ASM, depending on the camera configuration. For example wait_until_remote_button_is_released() was not called when necessary just as capt_seq_hook_set_nr() wasn't.

It is true that when I tried remote usb today it worked, but I definitely know that I have already done fixes to it as part of the dark frame. You will see the changes in the diffs. Even if it worked for you, it probably didn't work with another configuration. Now it is fixed alright.

BTW I updated the wiki with the minimum voltage I found in the camera features chart.

For ON/OFF button, remote and NR I had to change ASM in the firmware specific files. For each version of the SX20 the memory addresses might be different. And even if I ported them over, the same features might not be fixed there because of other porting bugs that are not present in 1.02d (if any). What I mean is that I find it very risky to edit those files for other cameras and assume that the same problems have been fixed withouth being able to test, so I only did that to 1.02d since I cannot test the other cameras. I leave that as an excercise to the maintainers of those versions. However, it will be easy to spot differences I have made by looking at the diff.

ultimA

Oh mighty gods of CHDK. Please accept our humble sacrifice on https://chdk.setepontos.com/d/650/88 and make all SX20 owners happy. Let there be joy and light.
... and let's cross our fingers.

Here is an advice for all sx20 porters. Although the sx20 is often compared to the sx10, in many places the factory fw of the two are very different. I've found that the sx200 often has much more similarities to the sx20. The sx200 is often a better reference port.

ultimA

The changes are in the trunk!!!!!!!! Yeahhhhhh................

For 1.02b owners, I'm gonna try and make a port of some ASM changes (because we haven't seen acid2000 in a while), but somebody else will need to do the testing and commiting it to the trunk.

f_m_b

ultimAThe changes are in the trunk!!!!!!!! Yeahhhhhh................

Yeahhhhhh................ too. 😀

ultimAFor 1.02b owners, I'm gonna try and make a port of some ASM changes (because we haven't seen acid2000 in a while), but somebody else will need to do the testing and commiting it to the trunk.

That's great. I will test it.

ultimA

ON/OFF, remote, darkframe for 102b, *untested* (i don't have the camera): http://www.mediafire.com/?w7pub2g5scup3o9

Just replace the files in sub/102b with the two files in the zip.

f_m_b

Darkframe: ok.
I shoot fotos with [off,on,auto] and [Tv=10s,0.8s,1s,1.3s]
off: without darkframe
on: with darkframe
auto: Tv <= 1s without darkframe Tv > 1s with darkframe

One question about the setting "Dark frame subtraction". It shows although effect without option "saving RAW = set" . Is this correct?

ON/OFF: ok.
short press -> play mode
longer press -> record mode

remote: ???
How can i test wait_until_remote_button_is_released and capt_seq_hook_set_nr?

« Previous Page Next Page »