I found a workaround to the problem. Just turn on the camera pressing more than one second the ON/OFF button.
There appears to be a usable workaround for the sx530 camera. See this and the preceding (long) discussion.
That, and your latest logs appear to tell the following (this is still just a guess though):On some cards, the WriteEnableMedia control event appears to arrive too late. The routine that evaluates the state of WriteEnableMedia therefore decides that the card is not writable, and sets a flag accordingly. The responsible routines are called from sub_FF0B0B84 in InitFileModules task. The flag is located at 0x1d60, and is evaluated each time WriteSDCard is called (this happens in sub_ff0300dc).The current workaround is: setting the flag to 1 right after sub_FF0B0B84, in the InitFileModules task.
Something I've noticed but haven't investigated deeply is a bunch of the functions called from kdb_task are also (possibly) called once at startup via a different code path. Since these aren't hooked, I wonder if they could see the write protect before kbd_task gets going?
Started by phyzome
Started by christiacob
General Help and Assistance on using CHDK stable releases
Started by reyalp
General Discussion and Assistance
Started by Andre-K
Started by alvm
« 1 2 ... 5 6 »