the sx20 porting thread

neszt

It it not clear to me, who steps the state_shooting_progress from 0 to 3 one by one? In particular,

state_shooting_progress == SHOOTING_PROGRESS_PROCESSING

is not true (because state_shooting_progress == SHOOTING_PROGRESS_NONE), that's why

if ((state_shooting_progress == SHOOTING_PROGRESS_PROCESSING) && (!shooting_in_progress()))

is not true.

That's why

state_shooting_progress = SHOOTING_PROGRESS_DONE;

is not executed.

#define SHOOTING_PROGRESS_NONE 0
#define SHOOTING_PROGRESS_STARTED 1
#define SHOOTING_PROGRESS_PROCESSING 2
#define SHOOTING_PROGRESS_DONE 3

I don't find, who steps SHOOTING_PROGRESS_NONE to SHOOTING_PROGRESS_STARTED.

reyalp

I suggest grep, or something like grepwin

SHOOTING_PROGRESS_STARTED does not appear to be used by the current code. I guess it's either a leftover, or something that was not completed.

in raw.c, raw_savefile()
state_shooting_progress = SHOOTING_PROGRESS_PROCESSING;

neszt

reyalp
I suggest grep, or something like grepwin

SHOOTING_PROGRESS_STARTED does not appear to be used by the current code. I guess it's either a leftover, or something that was not completed.

in raw.c, raw_savefile()
state_shooting_progress = SHOOTING_PROGRESS_PROCESSING;

😀 Ohh, i have experiance, searching special values, i use grep with regular expressions. (most the time, under linux)

I saw the raw.c hit, but i ignored it, because i thought, shooting basic token available with simple jpeg saving.
It that means, raw_savefile() called even without raw option enabled?

Anyway, i tried to switch on raw save, but shoot still not works, and the raw file was not created.

reyalp

neszt
It that means, raw_savefile() called even without raw option enabled?

Yes, it use for other things that have to hook into that point of the shooting process.

It is called from capt_seq_task.

neszt

Thanks the info, i realized, that capt_seq_hook_raw_here never called. I commented the relevant code (the very begining of the capt_seq_task), to see, what happens.

"loc_FF87CE10:	B	loc_FF87D048\n"
"loc_FF87CE14:	B	loc_FF87D050\n"
"loc_FF87CE18:	B	loc_FF87D05C\n"
"loc_FF87CE1C:	B	loc_FF87D090\n"
"loc_FF87CE20:\n"

		"BL	sub_FF87D6A8\n"
		"BL      shooting_expo_param_override\n"  // +
		"BL	sub_FF87A4E0\n"
 //  this code added to avoid some incorrect behavior if overrides are used.
 //  but it can cause some unexpected side effects. In this case, remove this code!
                 "MOV     R0, #0\n"
                 "STR     R0, [R4,#0x24]\n"  // fixes overrides  behavior at short shutter press
 //  end of my code

		"LDR	R0, [R4,#0x24]\n"
		"CMP	R0, #0\n"
		"b my_blink\n"               // THIS IS EXECUTED
		"BEQ	loc_FF87D090\n"
		"b my_blink\n"               // THIS IS NOT EXECUTED
		"BL	sub_FF87C1F0\n"
		"MOV	R5, R0\n"
		"LDR	R0, [R4,#0x24]\n"
		"CMP	R0, #0\n"
		"BEQ	loc_FF87CE68\n"
		"MOV	R0, #0xC\n"
		"BL	sub_FF882154\n"
		"TST	R0, #1\n"
		"STRNE	R9, [R6,#0x10]\n"
		"LDRNE	R0, [R5,#8]\n"
		"ORRNE	R0, R0,	#0x40000000\n"
		"STRNE	R0, [R5,#8]\n"
		"BNE	loc_FF87D090\n"
"loc_FF87CE68:\n" //
		"MOV	R0, R5\n"
		"BL	sub_FF961AF4\n"
		"MOV	R0, R5\n"
		"BL	sub_FF87C5D0\n"
		"MOV	R0, R5\n"
//		"BL	sub_FF962390\n"
		"BL	sub_FF962390_my\n"
		"BL      capt_seq_hook_raw_here\n"      // +
		"TST	R0, #1\n"
		"STRNE	R9, [R6,#0x10]\n"
		"B	loc_FF87D090\n"

reyalp

I hope "b my_blink\n" is pseudocode, since it would have no way to return ? It would also potentially trash R0 and the CPSR register.

Anyway, with the fast shutter press hack, the BEQ following your first my_blink will clearly always be true. In the SX10 port, there is another call to the raw hook (SD990 doesn't have it, but this is a bug which causes the "intermittent raw" problem)

neszt

reyalp
I hope "b my_blink\n" is pseudocode, since it would have no way to return ? It would also potentially trash R0 and the CPSR register.

Oh, yes, i forgot to comment that the two "my_blink()" debug code was tested in two separated builds. It is endlenss blink code. (I read in the guide, that in asm not recommended to return from debug because of registers)

Anyway, with the fast shutter press hack, the BEQ following your first my_blink will clearly always be true. In the SX10 port, there is another call to the raw hook (SD990 doesn't have it, but this is a bug which causes the "intermittent raw" problem)

Yes, i made my sentesnces poorly again, i forgot to write, that i tested also with commenting out that two lines.

But your hint was really usefull. I checked the sx10 code, and i found the two raw hooks. Now i got freeze my camera, hooking also at the same place as sx10. (long AF light before freeze)

So, now, i got my raw hook executed, i need more debug.

neszt

neszt
But your hint was really usefull. I checked the sx10 code, and i found the two raw hooks. Now i got freeze my camera, hooking also at the same place as sx10. (long AF light before freeze)

So, now, i got my raw hook executed, i need more debug.

One part of the problem solved. I switch off raw save in the chdk menu, and i got capture work, and i got basic script shoot work!

Now, i need, to debug why the camera freezes when raw save is on.

Thanx, for help.

neszt

neszt
Now, i need, to debug why the camera freezes when raw save is on.

I got it. It is SetFileTimeStamp wrong address. I spent time, to find it, but no success.. Now i set it to

NHSTUB(SetFileTimeStamp, 0xFF810B04) // BX LR

RaduP

Oh, yes, I thought I did nullsub it in the code I gave you?
And I spent a lot of time trying to find it too.

neszt

RaduP
Oh, yes, I thought I did nullsub it in the code I gave you?
And I spent a lot of time trying to find it too.

Yes it was nullsub in your code too.

Can you pls tell me, where from

DEF(enabled_refresh_physical_screen, 0x1B34C+0x20)

address comes from in you firmware?

My guess:

loc_FF9F8554
sub_FF9F8694

I have canon menu refresh problems when this address is set to

DEF(enabled_refresh_physical_screen, 0x9D60 + 0x2😎

Regarding my frimware, but, i'am sure, this is the correct address.

edit: I mean, i have problems with original canon menu, not chdk menu. (when not in alt mode)

RaduP

Yes, it is from sub_FF9F8694

What issues do you have with your menu? Can you describe?

neszt

RaduP
Yes, it is from sub_FF9F8694

What issues do you have with your menu? Can you describe?

The canon menu does not appear. It works, i know, because it beeps. This happens with all the canon menu elements, including the manual focus, iso values, etc..

The canon menu refreshes only when switch to alt mode.

For example, i push the menu button, beeps, and nothing visual happens. I switch to alt mode, press the menu button, and boot the canon menu and the chdk menu appears.

RaduP

Well, remember that thing I told you about setting that new variable to make the screen be refreshed correctly? Try to comment out the code that does that, and see if it works..

neszt

RaduP
Well, remember that thing I told you about setting that new variable to make the screen be refreshed correctly? Try to comment out the code that does that, and see if it works..

It is not regarding your code. That's ok. When i removed, i got yet another problem, with chdk menu refreshing..

neszt

I found the reason of games freezes. It was because of wrong VbattGet address.

neszt

Actually, the following main things works and tested:

- Shutter speed override
- Override ISO value
- Save RAW (without SetFileTimeStamp)
- Visual settings
- Scripts, including motion detection
- Filebrowser, calendar, textfilreader, draw palette
- Benchmark, and others in Debug parameters
- Startup sound. 😀
- Games

yakabmarci

This is great news.
Can you please share your SW?
I'M very anxious to try this out.

jan

I would as well like to try it out.

neszt

Ok, give me a few time, to make the actual source publicable.

« Previous Page Next Page »