On Thu, Jan 2, 2014 at 1:08 AM, Jose Teixeira de Sousa <[email protected]> wrote: > Hi Olof, all, > > I have a first drop of the SystemC verilator testbench. > Please see https://github.com/jjts/orpsoc-cores and > https://github.com/jjts/orpsoc-3.1 > > > I started off from jtag_vpi.c/v and running the (slow) icarus simulator and > then I wrote them in SystemC/C++. > > So now communicating with the Verilator model is similar to communicating to > icarus or De0_nano. > > I use openocd with telnet or gdb to connect to it. > Hi Jose,
Your work is very appreciated. I took a quick glance at your repos, and it looks like you have implemented tons of good stuff that would be great to have upstreamed. It would be great if you could prepare some pull requests that I can look at. > > Some observations: > > 1) With openocd and telnet I did not detect abnormal behavior so far. > > 2) with the stable toolchain I get the following gdb mesg : > > "some target registers not supported by current architecture", or something > alike. > > with the recent toolchain I don't. > > I need to set remotetimeout 15 in order for it to load the program > > Running and breakpoints work. > > "step" and "next" have funny behavior - I wonder why. Breaking at printf and > then doing "next" causes it to stop somewhere in printf rather than jumping > over and stopping on the next command. I don't remember seeing this on the > board and need to chack again... > > Any clues? Thanks > I'm not completely up to date with the different GDB versions, but I know that Franck Jullien has done some fancy stuff with register groups and XML descriptions in the new GDB version and.OpenOCD. This is probably not back-ported to the old GDB version, and I suspect that is the reason for the warnings. Can't help you with the next/step problem though, but I know that there has been some fixes in that area the last year. Could be worth checking a slighly older or later version of or1200 Looking forward to integrating your code. I will probably release version 3.2 once it's done Regards, Olof _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
