For sx530hs 100c, we can use!con:call_function(0xFF21DE30,0)to turn off, 1 to turn on. In my previous testing, turning off and attempting to access the SD card worked after some delay, so it's possible this causes the firmware to reset it's disk subsystem.
Until then, try reyalp's recent suggestion:
*(int*)(0x2cf4+0x8) = (*(int*)0xc022f48c) & 0x80000 ? 0x400000 : 0x200000;
added a patch with all the changes
Files are attached.
Looks odd.In the 'bad' case:First, I see no attempt to load the file browser module. But I do see the Lua module loading.Second. Files opened for reading appear to open correctly and can be read (I see actual file content and read() returns the number of bytes read). Write() fails and returns -1.Close also returns -1 (which means error), but the next file opens correctly and gets the same file descriptor.Since I don't think any part of code checks for the value returned by close(), reading should - theoretically - be working.It could be that other file related functions (stat, opendir, etc) also misbehave and that is causing the general impression that no file operations work.Plan for the next step is: making a copy of the firmware's Write() or Close() function and trying to find out where it fails.
About your patch: it appears that capt_seq.c was not regenerated (make run-code-gen) after editing capt_seq_hdr.c. You may have edited capt_seq.c afterwards.
Now I started a file browser (with the USB connected) before starting chdkptp. If I try to run a file browser, with running chdkptp, CHDK menu only briefly flashes and nothing happens.
I did not use code-gen.I'll make it again when I find more time.
Can you check if there are any error messages visible on the CHDK console, after you do that?
Okay, I don't want to force you to learn code_gen scripting too. If your capt_seq.c and boot.c changes are meant to be final, I can make the necessary change.
I have added this in changeset 4604.
Some buttons are not mapped yet, some others appear with incorrect names in kbd.c. Debug display of physw_status values can be enabled by uncommenting the section around// debug keymap, KEYS_MASKx, SD_READONLY_FLAG, USB_MASKin core/gui_osd.c.
MEM: 0x1e3c1e3cPS1: 0xffdf9PS2: 0PS3: 44003f4
Started by gvandyk CHDK Releases
Started by Jez General Help and Assistance on using CHDK stable releases
Started by ProfHankD « 1 2 » Feature Requests
Started by eaglesong General Chat
Started by duenyas General Discussion and Assistance