URL
https://opencores.org/ocsvn/or1k_old/or1k_old/trunk
Subversion Repositories or1k_old
[/] [or1k_old/] [trunk/] [rtems-20020807/] [c/] [src/] [lib/] [libbsp/] [sh/] [shsim/] [README] - Rev 1782
Compare with Previous | Blame | View Log
## README,v 1.3 2001/05/09 13:12:23 joel Exp#Simple BSP for the SH simulator built into gdb.Simulator Invocation====================sh-rtems[elf|]-gdb <executable>(gdb) target sim(gdb) set archi [sh|sh2](gdb) load <executable>(gdb) runStatus======* The simulator invocation procedure outlined above produces error messageswith gdb-5.0, nevertheless seems to work. With gdb versions > 5.0 theseerror messages are gone. I.e. if you plan to seriously work with the gdbsimulator better use gdb versions > 5.0.* gdb's simulator is not able to correctly emulate memory areas esp. shadowingand non-consecutive memory. I.e. access to memory areas besides area 0 will(bogusly) generate SIGBUS exceptions. This includes access to area 5(On-chip peripherials) and prevents simulation of configuration and accessto on-chip peripherials.* Due to limitations of the simulator you will only be able to runapplications which do not try to access any SH control registers.Currently, this excludes all applications, which apply timers and serialdevices, i.e. almost any real world application.* This BSP supports 3 different console devices (cf. configure --help):- trap34, an interface base on gdb's trap34 emulation. Known to work withgdb-5.0.- gdbsci1, a stripped down sci device driver adapted to apply gdb's sci1emulation. This is known to fail with gdb-5.0, because of a bug in gdb-5.0'ssh-sim, a patch is submitted, but .. ~==- devnull, redirection of console io to /dev/null. Try to single step this,if you want to understand the details on how SH-RTEMS console redirectionworks.NOTE: the trap34 interface is incomplete and is temporarily disabledinside of configure.in.
