Yeah, but I thought a well known function looks less obscure and the additional clock cycles don't really matter much at this point.
like the focus_len_table for stubs_min
and probably the screen info
Boot it working but with the hook in the wrong place
with this it did not crash after boot ( but with the wrong patch after " blo loc_fc02002a\n")
I mean that these lines"ldr r0, =hook_CreateTask\n" // dest: Address to patch (hook_ has thumb bit off)"adr r1, patch_CreateTask\n" // src: Patch data"mov r2, #8\n" // two words"bl _memcpy\n" // shouldn't need to preserve any extra regs, cache func called just beloware after " blo loc_fc02002a\n"
and reyalp sugest they should go after " blo loc_fc020046\n"
But if I put them there the cam wont boot
Here you have it built with trunk 4591
00395650 <patch_CreateTask>: 395650: f8df f000 ldr.w pc, [pc] ; 395654 <patch_CreateTask+0x4> 395654: 00395659 .word 0x00395659
LDR (literal)(...)Encoding T2 ARMv6T2, ARMv7LDR<c>.W <Rt>,<label>LDR<c>.W <Rt>,[PC,#-0](...)<label>The label of the literal data item that is to be loaded into <Rt>. The assembler calculates the required value of the offset from the Align(PC,4) value of this instruction to the label.(...)
".align 2\n" "ldr pc, mylabel\n" "mylabel:\n" ".long 0x12345678\n"
3955f0: f8df f000 ldr.w pc, [pc] ; 3955f4 <mylabel>003955f4 <mylabel>: 3955f4: 12345678 .word 0x12345678
".align 2\n" "nop\n" "ldr pc, mylabel\n" "mylabel:\n" ".long 0x12345678\n"
3955f0: bf00 nop 3955f2: f8df f002 ldr.w pc, [pc, #2] ; 3955f6 <mylabel>003955f6 <mylabel>: 3955f6: 5678 .short 0x5678 3955f8: 1234 .short 0x1234
Great srsa_4c, now it boots, shows a canon logo with some black vertical lines crossing it , shows no file and shuts down with no chdk info, attached romlog
Started by citizenx
« 1 2 ... 10 11 »
General Discussion and Assistance
Started by msaddicted
Started by reyalp
« 1 2 3 »
Started by reyalp
« 1 2 ... 15 16 »
Started by tim dif
« 1 2 »