From e8a7a466a2b18a20ee9acc1ee796d7f1a95cb6f9 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 24 Jan 2001 19:10:38 +0000 Subject: 2001-01-24 Ralf Corsepius * Makefile.am, README, console/console-io.c, start/start.S, startup/linkcmds: Update to make shsim closer to functional. --- c/src/lib/libbsp/sh/shsim/README | 28 +++++++++++++++++++++++++--- 1 file changed, 25 insertions(+), 3 deletions(-) (limited to 'c/src/lib/libbsp/sh/shsim/README') diff --git a/c/src/lib/libbsp/sh/shsim/README b/c/src/lib/libbsp/sh/shsim/README index b1143cd94b..217db75fac 100644 --- a/c/src/lib/libbsp/sh/shsim/README +++ b/c/src/lib/libbsp/sh/shsim/README @@ -6,9 +6,31 @@ Simple BSP for the SH simulator built into gdb. Simulator Invocation ==================== -target sim +sh-rtems[elf|]-gdb +(gdb) target sim +(gdb) set archi [sh|sh2] +(gdb) load +(gdb) run Status ====== -Does not link yet. libcpu/sh code needs to be addressed so we can -get context switch code. + +* The simulator invocation procedure outlined above produces error messages +with gdb-5.0, nevertheless seems to work. With gdb versions > 5.0 these +error messages are gone. I.e. if you plan to seriously work with the gdb +simulator better use gdb versions > 5.0. + +* gdb's simulator is not able to correctly emulate memory areas esp. shadowing +and 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 of +accesses to on-chip peripherials. + +* Due to limitations of the simulator you will only be able to run +applications which do not try to access any SH control registers. + +Currently, this excludes all applications, which apply timers and serial +devices, i.e. almost any real world application. + +* The simulator currently uses gdb's trap34 interface for console I/O. This +could be replaced with polled sci1 I/O for SHes > SH1. -- cgit v1.2.3