Hi Oleksij, sorry for the late reply. On 2013.07.04 18:44, Oleksij Rempel wrote: > It doesn’t meter what do you use. Just dissas, first part of first stage > boot loader and try to use break points. And compare your results with > disassembled code. > > Here is one example: > reset; sleep 1; halt > bp 0xbfc004b0 0x4 hw > resume 0xbfc00000
I used the following section of code for my test, since it could be used for both purposes: ROM:BFC003C0 li $s0, 0x80120018 ROM:BFC003C8 move $v1, $a0 ROM:BFC003CC sw $v0, 4($s0) > bp 0xBFC003C0 4 hw breakpoint set at 0xbfc003c0 > resume 0xbfc00000 target state: halted target halted in MIPS32 mode due to breakpoint, pc: 0xbfc003c0 So hardware breakpoint seems to work OK, and we know that 0xBFC003C0 is reached > if there is some code on 0xbfc004b0 and it will be executed, then > openocd should stop here. > > Other example: > reset; sleep 1; halt > wp 0xb0404008 0x4 > resume 0xbfc00000 > wp 0x8012001c 4 > resume Error writing unexpected address 0xff202004 target state: halted target halted in MIPS32 mode due to target-not-halted, pc: 0xbfc003e0 0xbfc003e0 looks OK as the stop address, but I'm not too sure if we should be worried about that "Error writing unexpected address". At any rate, this looks fairly good to me. Nice work! Regards, /Pete ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
