the sx20 porting thread

viulian

acid2000
Can anyone with the 100f tell me if you can see the script console output -- see this image for example:

http://chdk.wikia.com/wiki/File:Work_of_script.jpg

For those in the know you don't need LUA support for this, you can use the DEFAULT.BAS file.

Yes, works.
You always mentioned LUA somewhere close to the 'missing script output' in the posts - so I thought only lua scripts don't have it. Now that you said all scripts, yes, the output is there.

acid2000

Yes, works.

Well if the 100f has script out and I don't then at least I've narrowed the problem down to some file in the 102 directory. I went back to the original netzt code and it doesn't work there either.

Do you get zebra output as well?

stotes57

Lectrichead

I hope that the "shutter button halfway" after it's powered on is something that can be changed so it doesn't have to do that, at some point?

I wouldn't count on it, my wife's A2000IS works the same way.

The OSD menu seems to stay on the screen when I bring it up, unless I mes around with a few of the settings that seems to update the screen.

Same problem here.

Now to try all of the other functions. Great job so far guys.

Yes indeed - great job.

acid2000

OK so I've fixed the scripting console not showing any output. I'll release a new build in a few days.

savalangh

thanks dear acid2000
do you think it'll solve grid problem -grids are not able in my camera-
and one more question:
what about freezing the osd, after alt mode?

viulian

@acid2000 - No zebra output for me ...

acid2000

I think if we can fix Zebra it will also fix the symbols issue.

lienso

Firstly, many thanks to all who make SX20 port happen. 😀

I have downloadad the sources from bitbucket to compile in Release mode and check for processing speed (I am a professional software engineer, but my SX20 is my first serios camera, and I have no prior experience with CHDK). Works great: the CRW save to Lexar high-speed 4G card is under 1 second.

I have aparticular question: in lib.c, there is a line: *(int)0x9cec=3; It seems breaking the camera standard Function key menu (ISO, white balance, etc). I understand it is used for some kind of debugging. Appreciate if someone could drop a line on its functon and if it is save to kill it in Release build.

Thanks again.

acid2000

vid_bitmap_refresh() doesn't work correctly at all!

All that function should do it completely redraw the screen, my guess is that magic number is completely wrong. Check the comments its been a bug for a long time. We should either get rid of the line or understand why its there and change the the appropriate magic number if its not correct.

acid2000

Anyone with the 100f. If you run badpixels.lua does it actually work ie rename the file correctly?

I ask this as the rename function seems to point to garbage memory in the dump I have.

0xFF834B74

Is this the correct address or is my firmware dump corrupted?

viulian

I am sorry but we're not LUA lucky 😁 - I didn't have time to port your release and include the 100f build code and get LUA support... And for the following weeks, not a chance.

Rick OBanion

I created a badpixel.bin file but CHDK still doesn't see it as being there when trying to select the 'convert to DNG'. Tried to run the LUA hoping it may see it then, but now..suddenly..the LUA doesn't do a thing. Well..it didn't do anything MUCH before, but does nothing. I may try putting the badpixel file ina few different places and see what happens.

lienso

It seems to me the placing 3 at 0x9cec location does not do anything good. The symptom: if you press ISO, nothing happens on the screen, but the ISO actually changes. The same for timer shot and manual focus. The Func button works, but in "blind mode" too - no Func menu on screen. I will continue hacking away in direction of RefreshPhysicalScreen call.

The questions I have to the community (excuse me the triviality, I am 1 week user of CHDK, and only have one camera SX20):

1. I understand, in Alt mode, the main menu is supposed to appear after Menu press and dosappear after another Menu press - right? The menu not disappearing / screen not redrawn is called "tearing" - right?
2. To the owners of 100f cameras - do you have the same problem (tearing = menu not going away after Menu second press) on your cameras too?

Regards in advance.

lienso

I have created badpixel.bin on PC, as acid2000 suggested. The correct location on the card for it: in CHDK folder. Now shoot DNGs with no problems. badpixel.lua works half way. On my camera it created a tmp file at the right location, but never got it renamed to badpixel.bin.

Markisha

Hello everyone! First I have to say thank you! you guys are awesome for taking time and making this CHDK possible!
I have a SX20 1.02b with a 8Gb card. I have never used CHDK and I have 0 programming experience. But I would like to be a tester if anything!
I know you have probably explained this a 1000 thimes but can you tell a total noob how to put this ona a card or point me to a place where I could see how to do this!
thank you so much!

acid2000

lienso, it's worth noting that the current address for RefreshPhysicalScreen is not actually for RefreshPhysicalScreen but ScreenUnlock which seemed to give a better effect. In my current source code the commented one is RefreshPhysicalScreen.

stotes57

Markisha
Hello everyone! First I have to say thank you! you guys are awesome for taking time and making this CHDK possible!
I have a SX20 1.02b with a 8Gb card. I have never used CHDK and I have 0 programming experience. But I would like to be a tester if anything!
I know you have probably explained this a 1000 thimes but can you tell a total noob how to put this ona a card or point me to a place where I could see how to do this!
thank you so much!

Markisha, you can start here

http://chdk.wikia.com/wiki/CHDK_in_Brief

beegdaddy

I downloaded Acid's beta build and installed it successfully on my SX20 (v1.02b)

I've encountered some of the more common bugs (eg. OSD not disppearing after MENU button is pressed, upside-down EXIF orientation, Zebra mode not working etc).

My favourite mode now is being able to use the ISO 3200 function in SCN and overriding the ISO (set at 160) to capture multiple lower-noise pics.

Being a little more daring, I downloaded the Tele-macro script written for the S3 (http://chdk.wikia.com/wiki/UBASIC/Scripts:_Tele-Macro-Mode) and ran it on my sx20.

After running it, nothing happened (no crunching sound, no broken lens etc). However, every time I power up CHDK and put it in photo capture mode, it will shutdown automatically after 5-10 seconds.

However, if it is kept in playback mode or CHDK is disabled (either using a non-CHDK SD card or the lock switch disabled), the camera works fine.

FYI.

acid2000

OK guys another build for everyone on 102b to test. Fixes include:

Script console is now displayed!
Badpixels.lua now correctly runs
Colours now finally fixed, RGB histogram draws correctly

I'm uploading the complete CHDK install ZIP as a lot of people are having problems. To install this use the card tricks application.

If you have found any problems in this build, excluding zebra and OSD refresh issues please post them here.

Latest build here:
http://bitbucket.org/acid2000/chdk_sx20/downloads

-revelation-

could someone tell me if there is a CHDK for my sx20? My firmware now is GM 1.00F?

Or is it possible to port the 102B to 102F?
Please help?

« Previous Page Next Page »