SX50 HS porting thread - page 12 - DryOS Development - CHDK Forum supplierdeeply

SX50 HS porting thread

  • 350 Replies
  • 152433 Views
*

Offline lapser

  • *****
  • 1093
Re: SX50 HS porting thread
« Reply #110 on: 27 / February / 2013, 17:14:02 »
Advertisements
it looks like the script is the same as holding the shutter button......
I need FAST the HQ Burst knocks off 10 in a ZIP.
The point is to try holding the shutter button in a script. CHDK is in a different state, and it might not crash. It's worth testing the script with the camera in Burst mode. It might give you the result you want.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

Re: SX50 HS porting thread
« Reply #111 on: 27 / February / 2013, 20:14:49 »
with that i get >>>     uBASIC:7 Unk  Key   <<<

Re: SX50 HS porting thread
« Reply #112 on: 27 / February / 2013, 20:22:08 »
with that i get >>>     uBASIC:7 Unk  Key   <<<
The little script he posted is written in Lua.  You can't run it as uBASIC. Rename the file with a .lua extension - something like  fastshot.lua

Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX50 HS porting thread
« Reply #113 on: 28 / February / 2013, 00:44:41 »
Still One Click and CrAsH .


*

Offline nafraf

  • *****
  • 1308
Re: SX50 HS porting thread
« Reply #114 on: 28 / February / 2013, 08:42:35 »
Maybe this is not related to radioman193 crash, but calls to wait_until_remote_button_is_released and capt_seq_hook_set_nr in sx50 100b are in different point if compared to sx260 implementation.

Patch file and compiled version in attachment.

EDIT Compiled version deleted. Wrong file.
« Last Edit: 28 / February / 2013, 17:06:05 by nafraf »

Re: SX50 HS porting thread
« Reply #115 on: 28 / February / 2013, 09:06:23 »
I wanted to report what is happening with the CDHK for the 100c SX50 firmware.  CDHK worked great yesterday with no problems.  I took a couple hundred photos with good results.  Great list of options and no untoward quirks. 

Today CDHK seems to be lost.  Red flashing display with random pixels on the display.  One shot then crash.  I had to go back to the unlocked position on the card and disable the CDHK.

I'm not even the slightest bit proficient when it comes to programming but am happy to give more details of the situational quirks.

*

Offline srsa_4c

  • ******
  • 4451
Re: SX50 HS porting thread
« Reply #116 on: 28 / February / 2013, 10:24:55 »
Today CDHK seems to be lost.  Red flashing display with random pixels on the display.  One shot then crash.  I had to go back to the unlocked position on the card and disable the CDHK.
DISKBOOT.BIN and/or other files on the card may have become corrupted. Can you compare it/them to the original copies? If not, can you upload them somewhere? Also check your recorded files (pictures) for corruption.

Re: SX50 HS porting thread
« Reply #117 on: 28 / February / 2013, 11:59:31 »
I attached the DiskBoot.bin file as it is currently on the SD card.  My computer is sending .bin files to VLC player so I can't seem to read it myself to compare the original to the current file.

Any other files I should attach for analysis?

Thanks for the help!



*

Offline lapser

  • *****
  • 1093
Re: SX50 HS porting thread
« Reply #118 on: 28 / February / 2013, 14:34:28 »
Maybe this is not related to radioman193 crash, but calls to wait_until_remote_button_is_released and capt_seq_hook_set_nr in sx50 100b are in different point if compared to sx260 implementation.

Patch file and compiled version in attachment.
The patch worked on my SX50 100b. I didn't have the crash before, though. Will you do a patch for 100c and we can see if it fixes gestatin's crash.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline srsa_4c

  • ******
  • 4451
Re: SX50 HS porting thread
« Reply #119 on: 28 / February / 2013, 14:46:41 »
I attached the DiskBoot.bin file as it is currently on the SD card.
Not corrupted, it's from the build provided by yukia10.
Quote
Any other files I should attach for analysis?
Erase CCHDK3.CFG from the card (it's in the CHDK folder). Try starting CHDK. If it works, and the display is not showing the random pixels, a CHDK setting is responsible for your problem (zebra?).
Try nafraf's new build when it becomes available.

@nafraf
Please retain core/main.bin.dump for the builds you provide, they might be useful for analysing romlogs.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal