On Wed, Apr 30, 2014 at 2:42 PM, Jose Teixeira de Sousa <[email protected]> wrote: > On Tue, Apr 29, 2014 at 11:47 PM, Stefan Kristiansson > <[email protected]> wrote: >> >> Both breakpoints and single stepping works for me on the de0 nano >> board with mor1kx, could you please be more precise? >> https://github.com/openrisc/orpsoc-cores/pull/35 is using or1200, I >> can't see how that's going to help debug an issue with mor1kx? >> > > > > Please you need just switch it to mor1kx in orpsoc-defines.v. I left it to > OR1200 because that what last was working for me. Please confirm you see the > issue. >
No, it's not enough to just switch the define in orpsoc-defines.v 1) or1200_monitor is included in orpsoc_tb.v 2) the verilator testbench only have support for or1200 Those two facts made me make the conclusion that this branch was or1200 specific. Now, I'm experiencing strange problems with jtag_vpi together with mor1kx, but that's unrelated to this. > You need to create a function f() and set a breakpoint where this function > is called, say line 10. > > (gdb) break 10 > > It actually stops at line 10 > > (gdb) next > > Here instead of moving over f and stopping again at line 11 it actually > enters inside function f(), that is, it behaves sort of like ""step" instead > of like "next". > Thanks, that was a lot better description! ;) Yes, I can now reproduce the behaviour above with mor1kx with the de0_nano board. I'll investigate further. Stefan _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
