PowerShot SX230 HS - Porting Thread - page 55 - General Discussion and Assistance - CHDK Forum

PowerShot SX230 HS - Porting Thread

  • 706 Replies
  • 326241 Views
Re: PowerShot SX230 HS - Porting Thread
« Reply #540 on: 01 / April / 2012, 12:54:20 »
Advertisements
I have tryed this so far but i do not find the right place/function in kbd.c for the routine to close ALT-menu. It would be great if have a suggestion for me where i should search for the right place in kbd.c to put in the code for closing ALT-menu
You are into some serious hacking here. You pretty much have to read and understand the code at the start of kbd_process() in kbd.c.  And you need to make sure that whatever you insert into the menu code to trigger the exit from alt mode cleans up after itself.  Its pretty much up to you to work that out - sorry.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: PowerShot SX230 HS - Porting Thread
« Reply #541 on: 01 / April / 2012, 14:22:47 »
With changeset 1785/1786 is the default <ALT> button the playback button. A short press is for the <ALT> mode, a longer press is for the original playback funktion.

You can select a alternative <ALT> button in menu 'Miscellaneous stuff' -> <ALT> mode button [Playback, Video, DISP.] .

The combination [DISP. + SET] is no longer available.

msl
CHDK-DE:  CHDK-DE links

*

Offline true

  • *
  • 35
  • SX230, SX260, 5DmkII, and more :)
Re: PowerShot SX230 HS - Porting Thread
« Reply #542 on: 02 / April / 2012, 00:29:03 »
Good to hear. I don't even know why DISP+SET was even an option. Play is superior and I've used it since day one on my camera.

Any ideas yet on the GPS logger turns camera on by itself bug? Any resolution even possible? Or is this what the CHDK-GPS is supposed to resolve (as in, use it instead of the built-in logger function)?
« Last Edit: 02 / April / 2012, 00:56:57 by true »
Canon P&S: 110HS, SX260HS, SX230HS, 2x A720 IS, 2x A590 IS
Canon DSLR: 5D Mark II, 300D IR-converted, 8x glass
MFT: DMC-GF1, DMC-G3, 7x glass

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX230 HS - Porting Thread
« Reply #543 on: 06 / April / 2012, 01:18:37 »
I'm porting chdk for sx260 based on sx230

Regarding gps stuff I wasn't able to find this 3 address,

can someone tell me where did you find it.
Code: [Select]
char * camera_jpeg_current_latitude()
{
return (void*)0xCA890;
}
char * camera_jpeg_current_longitude()
{
return (void*)0xCA8AC;
}
char * camera_jpeg_current_height()
{
return (void*)0xCA668;


*

Offline genie

  • *
  • 43
Re: PowerShot SX230 HS - Porting Thread
« Reply #544 on: 06 / April / 2012, 02:25:57 »
Hi asm1989,

can someone tell me where did you find it.

You have to be in Playback-Mode and looking at a picture with GPS - Coordinates.
Next you have to make a RAM-LOG.

Now you can search in the RAM-LOG for the GPS-Coordinates or the picture - filename you looked before.
If you find it; you have th address.

genie
Sorry for my bad English.I am a Bavarian and German is the only foreign language i speak.

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: PowerShot SX230 HS - Porting Thread
« Reply #545 on: 06 / April / 2012, 02:59:12 »
Thanks genie,

I thought it will be at some point hardcoded in the firmware.

I will do it as you said, once the camera loads chdk

Good work with your port!

*

Offline srsa_4c

  • ******
  • 4451
Re: PowerShot SX230 HS - Porting Thread
« Reply #546 on: 10 / April / 2012, 14:20:55 »
Apparently the camera doesn't like to draw pixels on an inactive buffer. I fixed the code in gui_draw.c and works on my sx220. I couldn't crash it as far as I could test. I uploaded an experimental build for sx230 100c and 101a. I build it from reyalp_ptplive branch because it has the active buffer addresses already in stubs_min.s. Can somebody try it and report back? It fixes the crash on sx220 so it should on sx230.
I created a build of CHDK-DE with #define DRAW_ON_ACTIVE_BITMAP_BUFFER_ONLY 1, because of a recent bugreport on an SX230 (in German): http://forum.chdk-treff.de/viewtopic.php?f=3&t=2519&p=25349#p25321 . It didn't seem to help, camera crashed again during movie record.
draw_hline() is not fixed (see changeset 1762) in -DE (or CHDK stable), and IMHO it can corrupt a word right after the bitmap buffer. But I don't think that causes this problem...


The romlog is nearly useless, the crash happens in an interrupt-routine (Dispcon.c) ...
« Last Edit: 10 / April / 2012, 14:32:10 by srsa_4c »

*

Offline funnel

  • ****
  • 349
Re: PowerShot SX230 HS - Porting Thread
« Reply #547 on: 10 / April / 2012, 16:14:18 »
Strange, this solved the problem on sx220. I can't crash it anymore it even if I try hard. Right now I did a successful 1280 recording until it reached the 4Gb limit - 23minutes and 48 seconds.

Tell him to try to disable the osd in Menu->OSD Param->Show OSD . This worked for me too.

And yes, I tried first to disable everything I could think of - all tasks including kbd task + bitmap refresh in lib.c. It didn't help, it still crashed while recording.


Re: PowerShot SX230 HS - Porting Thread
« Reply #548 on: 12 / April / 2012, 21:34:01 »
Turning off the OSD has worked so far, with an SX230HS with firmware 1.01c and version 1803. The videos reach either the 30 minute limit or the 4 GB limit. But there's another little problem. Even with the OSD completely off, turning on Video Without Timelimit results in the videos ending prematurely, sometimes within a few seconds and sometimes after many minutes. These shortened videos do get saved, though. I have yet to see a crash with the OSD turned off.

Re: PowerShot SX230 HS - Porting Thread
« Reply #549 on: 31 / July / 2012, 16:53:55 »
Video Without Timelimit seems to work now (using version 2020), with the OSD turned off. This is great. Thanks to whoever solved this. (With the OSD on, video still crashes and files are not saved.)

When setting video quality using the 4-way wheel, some (maybe half) of the left and right keypresses aren't recognized. This appears to be specific to CHDK, because wheel keypresses are always recognized properly in the camera's normal menus. Could it be a key debouncing or other timing problem? It's not only normal keypresses - often I have to press repeatedly before CHDK will recognize a sustained keypress to actuate the automatic key repeat when scrolling the video quality setting numbers. This is also noticeable in the OSD Layout Editor when making a series of wheel-key keypresses to move an object in any of the four directions. The central Function Set button in the wheel also misses keypresses in the same way. The rotating function of the wheel works normally. No other keys have this problem.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal