S100 porting thread

zpyder

Hello all

I've finally jumped in after reading about CHDK for a while and got it running on my S100. I've managed to get the intervalometer working (which is what I need) but I was wondering, I noticed that when selecting the script, there is no icon/shading etc in the script library to indicate which script is selected, so you kind of have to guess how far you've scrolled to see if you've selected the right script. Is this normal or a bug? Part of the alpha process on the CHDK? (Also, the OSD flickers slightly during use)

Sorry if it's common knowledge, this is all totally new to me!

reyalp

zpyder
I've managed to get the intervalometer working (which is what I need) but I was wondering, I noticed that when selecting the script, there is no icon/shading etc in the script library to indicate which script is selected, so you kind of have to guess how far you've scrolled to see if you've selected the right script. Is this normal or a bug?

The selected item in a menu or file browser should be highlighted with different color background. Note that camera color palettes change depending on what mode the camera is in, so the colors might be right in playback and wrong in record.

Example of what it should look like: http://images2.wikia.nocookie.net/__cb20091206143845/chdk/images/thumb/0/0f/TextFileRead-Change_Font_etc.jpg/830px-TextFileRead-Change_Font_etc.jpg

You can customize all the colors, but the default should allow you to tell which item is selected. The exact colors may be different from what's in the screenshot, because the cameras have a limited palette that varies between models.

(Also, the OSD flickers slightly during use)

This is probably normal, the CHDK and original firmware drawing routines aren't really aware of each other.

colon247

reyalp
One thing you could do is try blinking LEDs at various points to see how far it gets.

How and where do I set that up? Or point me to instructions. 😀 Thanks!

zpyder----Playback mode is fine so if you select the script in playback mode you will see the highlighted scripts. The problem is the shooting mode palette.

reyalp

colon247

reyalp
One thing you could do is try blinking LEDs at various points to see how far it gets.

How and where do I set that up? Or point me to instructions. 😀 Thanks!

http://chdk.wikia.com/wiki/Debugging#LEDs
Probably not worth attempting if you aren't a programmer, if you don't know what you are doing it's very easy to cause new crashes rather than actually discovering where it's crashing now.

colon247

reyalp----it okay I figured as much : )

I will just keep doing what I can

colon247

Figured out how to fix the script highlight issue 😁 :

in \platform\camera\platform_camera.h

we just need to change the 9 to 7:

#undef  CAM_BITMAP_PALETTE
#define CAM_BITMAP_PALETTE              7

With this all menu are readable.

It is not as colorful though. If you don't like the colors change it using.

Alt menu>Visual Setting>

Change "Menu background" and "Symbol Background Color" to change colors

Question ??? :
Can I set individual colors manually in "platform_camera.h" or another file?
Just so I can refine this a little more.

waterwingz

colon247
Question ??? :
Can I set individual colors manually in "platform_camera.h" or another file?

The colors used by CHDK are defined in palettes contained in core/gui_draw.h. These values map against the colors you see when you use the Visual Settings menu to look at any of the color choices. Unfortunately, if you look at that CHDK menu when the camera is in different modes ( shooting, playback, menu, ...) you will get much different colors. For many cameras, the first 32 colors (or so) stay the same across modes so if you can select from them it helps a bit. There is a really complicated fix that philmoz got working for a couple of his cameras but it has not been extended to any other cameras.

colon247

😳 oops....earlier I made a mistake.....I did not update all the files in my chdk folder.....so I ended up with semi transparent window in play.

well turn out it was actually solid grey.....small mistake and I just dont want to give misinformation

I fixed that post for anyone who reads it in the future.

Question:

how long does it take for changes to make it into the trunk?

I ask because c10ud posted a patch/update on may 7th and it still has not gone in.

How do I make one so I can add the palette change to the trunk?

zpyder

Thank you everyone, it's so much easier to set things up in playback mode, I didn't realise!

Will it be likely do you think that there will ever be an option to disable the screen without needing to use the AV socket trick? I ask as I am using the CHDK with an underwater housing, and can't really fit anything in the sockets whilst the camera is in the housing.

waterwingz

colon247
how long does it take for changes to make it into the trunk? I ask because c10ud posted a patch/update on may 7th and it still has not gone in.

It usually takes just a day or two. All depends on how busy the devs are with other things in their lives. Sometimes it goes faster if they know the submitter already and it always goes faster if you submit a patch file to the right forum thread :
[REQ]Adding new cameras, applying patches into trunk (with source code prepared)

I see c10us submitted a file there but did not use a .patch or .diff extension (even though it appears to be a valid patch file) so it might have been overlooked.

After a suitable wait, you can always ping one of the devs via PM - there are really only three of them who are active these days. Just don't abuse that option obviously.

How do I make one so I can add the palette change to the trunk?

You basically need to have a download of the svn source tree and a working development environment to test things. On windows the easiest way to do that is to use CHDK-Shell. Or find somebody who is setup correctly to do it for you ? Here's an example of what I think you want. Feel free to submit it to the patch thread if so :

S100_pallete7_trunk_1849.patch

523b

colon247

Thanks! That is exactly what I needed. I submitted it to the patch thread with thanks given to you for preparing the patch file 😀

chat2joe

Hey guys,

I'm very interested in contributing and helping test this. However I'm getting nowhere getting this installed! ???

When trying to check the firmware installed using the Play, then Set + Disp buttons I get nothing but the clock. I have vers.req on my formatted 2GB card.

Even if I go to look for the Firmware Update menu item, it's not there. I tried pressing Play button twice as per the Readme with no joy.

Any anyone got S100 specific step-by-step instructions to get this loaded?

Thanks!

waterwingz

Take a look at this : http://chdk.wikia.com/wiki/Prepare_your_SD_card

You probably want to pay particular attention to the part about using the Acid application to determine your firmware version.

colon247

I just prepared a quick guide for this camera 😀

chat2joe
Any anyone got S100 specific step-by-step instructions to get this loaded?

Thanks!

It is the step by step you were looking for

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

mv3830

Thanks for your hard work guys. I had a s95 that I used for time lapse until sand killed it.

It was a task to get the 16GB SD card bootable, partitions did not work. HDHacker and xvi32 worked, however.

Appreciate the work you guys are putting into getting this out.

colon247

What would it take to make this a BETA build?

It seems pretty stable and most of the issues seem to be minor in my opinion.
The only big issue I can think of is maybe the movie override quality.

Here are the issues below. I just have no idea where to start.....if I can attack this at all.

I have seen some of the disassembled dump. 😛
How do you guys find anything in there?
I think I need to go back to a school for this...haha

From Notes.txt

CAMERA TODO/KNOWN ISSUES:
- manual loading with "firm update" loading crashes (confirmed on 100d and 101a), so PS.FI2 is not included in the autobuild. (to be fixed soon https://chdk.setepontos.com/d/7889/166)
- various defines in platform_camera.h needs to be checked
- value for SleepTask in kbd.c instead of hardcoded 10 (minor issue)
- values for Jogdial events in lib.c

- 100d, 100e, 101a: movie override quality seems to be working but values might be wrong (stock Canon reaches 4MB/s, CHDK quality 99 2MB/s)
- 100d, 100e, 101a: jogdial is untested and needs correct rear_dial_position address in stubs_min.S

c10ud

Quick comments:
Just note i've been wrong with the PS.FI2 issue, it's been found it's not the same as SX260HS so it's not "easy" nor "soon".
The defines must be checked with features and so far they turned out pretty good.
The value for SleepTask is a non-issue.
Jogdial values/rear dial position: unknown and untested.. (and useless?)

Movie override quality is interesting though, even if i wonder if overriding quality is needed..

colon247

I would personally like to know the LED address for the AF led.....I have no idea how to look for it though.

I also think we should update the note.txt removing SleepTask and platform_camera.h

The rear Jogdials don't seem to have a use right now......but in the future you never know.

Last is how do we verify if we need movie override quality setting?

edit:

quick question I keep getting unable to split patch.txt in chdk shell when trying to make diff......anybody ever get that?

ADamb

sx200is 100c
Full display EdgeOverlay if CHDK in EXMEM.
SCREEN_COLOR to 15 (was white in playback mode).

sx200_bkgd_exmemedge.diff

1.2KB

waterwingz

colon247
quick question I keep getting unable to split patch.txt in chdk shell when trying to make diff......anybody ever get that?

I gave up on the CHDK-Shell diff function some time ago. Maybe whim has improved it since but I now use Tortoise_svn (on windows) or svn command line (on Linux) to get the latest source versions, edit those and then use the built-in patch functions to make patch files.

« Previous Page Next Page »