erc32
所属分类:处理器开发
开发工具:UNIX
文件大小:16428KB
下载次数:8
上传日期:2017-11-07 09:42:40
上 传 者:
sunrihui
说明: ERC32源码VHDL 同时包括了leon2的VHDL源码
(VHDL code of erc32 and the source code of leon2)
文件列表:
erc32\bench\bench-1.1.tar.gz (110637, 2008-11-14)
erc32\bench\default.htm (481, 2008-11-14)
erc32\bench\Descr.WD3 (400, 2008-11-14)
erc32\bench\mix_1_0.ada (145813, 2008-11-14)
erc32\bench\rendez.adb (1003, 2008-11-14)
erc32\default.htm (747, 2008-11-14)
erc32\Descr.WD3 (99, 2008-11-14)
erc32\dev\default.htm (192, 2008-11-14)
erc32\dev\Descr.WD3 (99, 2008-11-14)
erc32\doc\aarm.pdf (2766755, 2008-11-14)
erc32\doc\ada_bench4.pdf (39905, 2008-11-14)
erc32\doc\ada_bench4.ps.gz (21995, 2008-11-14)
erc32\doc\app2.ps.gz (8830, 2008-11-14)
erc32\doc\bench1.ps.Z (36309, 2008-11-14)
erc32\doc\bfd.pdf (726822, 2008-11-14)
erc32\doc\binutils.pdf (301874, 2008-11-14)
erc32\doc\board.jpg (198625, 2008-11-14)
erc32\doc\ddd.html (12453, 2008-11-14)
erc32\doc\ddd.pdf (841979, 2008-11-14)
erc32\doc\default.htm (6463, 2008-11-14)
erc32\doc\dem32um.ps.gz (121073, 2008-11-14)
erc32\doc\dem32_layout.ps.gz (83675, 2008-11-14)
erc32\doc\Descr.WD3 (4694, 2008-11-14)
erc32\doc\erc-cba.pdf (204413, 2008-11-14)
erc32\doc\erc-cca.pdf (72143, 2008-11-14)
erc32\doc\erc32cba.pdf (204413, 2008-11-14)
erc32\doc\erc32cca.pdf (72143, 2008-11-14)
erc32\doc\erc32ccs-1.2.pdf (73770, 2008-11-14)
erc32\doc\erc32ccs-1.3.pdf (162178, 2008-11-14)
erc32\doc\erc32ccs-2.0.6.pdf (72040, 2008-11-14)
erc32\doc\erc32ccs-2.0.pdf (82040, 2008-11-14)
erc32\doc\erc32day\default.htm (1014, 2008-11-14)
erc32\doc\erc32day\Descr.WD3 (981, 2008-11-14)
erc32\doc\erc32day\ds_sa.pdf (178906, 2008-11-14)
erc32\doc\erc32day\ds_ss.pdf (271240, 2008-11-14)
erc32\doc\erc32day\ds_tools.pdf (279795, 2008-11-14)
erc32\doc\erc32day\ds_ts.pdf (254336, 2008-11-14)
erc32\doc\erc32day\pres_com.pdf (554550, 2008-11-14)
erc32\doc\erc32day\pres_hrt.pdf (1315971, 2008-11-14)
erc32\doc\erc32day\pres_ts.pdf (981436, 2008-11-14)
... ...
How to use SIS with GDB
-----------------------
1. Building GDB with SIS
To build GDB with the SIS/ERC32 simulator, configure with option
'--target sparc-erc32-aout' and build as usual.
2. Attaching the simulator
To attach GDB to the simulator, use:
target sim [options] [files]
The following options are supported:
-nfp Disable FPU. FPops will cause an FPU disabled trap.
-freq
Set the simulated "system clock" to MHz.
-v Verbose mode.
-sparclite Enable SMUL and DIVSCC instuctions
-nogdb Disable GDB stack and breakpoint handling (see below)
The listed [files] are expected to be in aout format and will be
loaded in the simulator memory prior. This could be used to load
a boot block at address 0x0 if the application is linked to run
from RAM (0x2000000).
To start debugging a program type 'load ' and debug as
usual.
The native simulator commands can be reached using the GDB 'sim'
command:
sim
Direct simulator commands during a GDB session must be issued
with care not to disturb GDB's operation ...
For info on supported ERC32 functionality, see README.sis.
3. Loading aout files
The GDB load command loads an aout file into the simulator
memory with the data section starting directly after the text
section regardless of wich start address was specified for the data
at link time! This means that your applications either has to include
a routine that initialise the data segment at the proper address or
link with the data placed directly after the text section.
A copying routine is fairly simple, just copy all data between
_etext and _data to a memory loaction starting at _environ. This
should be done at the same time as the bss is cleared (in srt0.s).
4. GDB stack and breakpoint handling
GDB inserts breakpoint in the form of the 'ta 1' instruction. The
GDB-integrated simulator will therefore recognize the breakpoint
instruction and return control to GDB. If the application uses
'ta 1', the breakpoint detection can be disabled with the -nogdb
switch. In this case however, GDB breakpoints will not work.
Before control is left to GDB, all register windows are flushed out to the
stack. Starting after the invalid window, flush all windows up to, and
including the current window. This allows GDB to do backtraces and look at
local variables for frames that are still in the register windows. Note that
strictly speaking, this behavior is *wrong* for several reasons. First, it
doesn't use the window overflow handlers. It therefore assumes standard
frame layouts and window handling policies. Second, it changes system state
behind the back of the target program. Typically, this will only create
problems when debugging trap handlers. The '-nogdb' switch disables the
register flushing.
Report problems to Jiri Gaisler ESA/ESTEC (jgais@wd.estec.esa.nl)
近期下载者:
相关文件:
收藏者: