OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [or1ksim/] [testsuite/] [README] - Blame information for rev 97

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 82 jeremybenn
                              Or1ksim Test Suite
2
                              ==================
3
 
4
This is the Or1ksim test suite, which is now integrated with the main Or1ksim
5
development package. It operates using a standard DejaGNU framework within the
6
GNU autoconf/automake/libtool structure.
7
 
8 90 jeremybenn
A separate configuration file is needed for the OpenRISC programs used in
9
testing, since these use the OR1K tool chain, rather than the host tool
10
chain. This can be found in the "test-code-or1k" directory.
11 82 jeremybenn
 
12 90 jeremybenn
Tests are provided for the standalone simulator (or1ksim) and for the library
13
(libsim.a).
14 82 jeremybenn
 
15 93 jeremybenn
At the time of writing a total of 21 tests of the standalone simulator and 14
16
tests of the library compile, run and pass.
17 90 jeremybenn
 
18 82 jeremybenn
Configuration and make files are provided for further test programs. These
19
come in three categories.
20
- Tests which compile correctly, but will not run to completion.
21
- Tests which compile, but will not run at all.
22
- Tests which will not compile correctly.
23
 
24
File Organization
25
=================
26
 
27 90 jeremybenn
Each test program has its own directory under test-code (for native tests,
28
typically of the library) or test-code-or1k (for OpenRISC code, which must use
29
the OpenRISC tool chain). This builds the test program. If necessary it copies
30
data files to the main build/testsuite directory.
31 82 jeremybenn
 
32 90 jeremybenn
Each test then has a DejaGNU expect script in or1ksim.tests (for standalone
33
tests) and libsim.tests (for library tests), which loads and runs the
34
test. Support script procedures are in lib/or1ksim.exp and lib/libsim.exp.
35 82 jeremybenn
 
36
Libraries
37
=========
38
 
39
Within the test-code there are several libraries:
40
 
41
support:    A minimal C library.
42
except:     Exception handling and startup code.
43
mc-common:  A library to support the memory controller tests.
44
 
45
Working tests
46
=============
47
 
48 97 jeremybenn
A total of 63 tests of the libsim library:
49 82 jeremybenn
 
50 93 jeremybenn
int-edge:    6 tests of edge triggered interrupts.
51
int-level:   5 tests of level triggered interrupts.
52
lib-iftest:  A test of the basic library interface functions.
53 97 jeremybenn
jtag-basic:  17 tests of JTAG reset and instruction selection
54
jtag-full:   32 tests of higher level JTAG functions
55 93 jeremybenn
upcalls:     2 tests of the upcall interface.
56
 
57
A total of 21 tests of standalone Or1ksim:
58
 
59 82 jeremybenn
basic:        A test or a wide range of instructions and registers.
60
cache:        A test of the Or1ksim cache modeling
61
cbasic:       A minimal test in C
62
cfg:          A test of the OR1K configuration register
63
dhry:         Dhrystone 2.1 benchmark using Or1ksim's timing facility.
64
dmatest:      A test of DMA.
65
eth:          A test of the Ethernet interface.
66
except-test:  A test of OR1K exception handling
67
exit:         A test that C program exits correctly
68
ext:          A test of the sign extension (l.ext) instructions.
69
fbtest:       A test of the frame buffer.
70
functest:     A test of the C function calling interface.
71
flag:         A test of Supervision Register (SR) flag bits.
72
int-test:     A test of the programmable interrupt controller.
73
kbdtest:      A test of the PS2 keyboard interface.
74
local-global: A test of C local and global variables.
75
mem-test:     A simple memory test.
76
mmu:          A test of the MMU.
77
mul:          A test of the multiply functionality.
78
mycompress:   A compression program.
79
tick:         A test of the OR1K tick timer.
80
 
81
Tests which build, but do not run to completion
82
===============================================
83
 
84 93 jeremybenn
The following tests of standalone Or1ksim rely on VAPI in Or1ksim, so need a
85
client to provide test data over TCP/IP.
86 82 jeremybenn
 
87
acv-gpio:  a test of the GPIO.
88
acv-uart:  a test of the UART
89
 
90
Tests which build, but do not run at all
91
========================================
92
 
93 93 jeremybenn
These tests of standalone Or1ksim (which are built by the make file), do not
94
appear to run at all. The problem is in the linker script and/or the
95
configuration for Or1ksim.
96 82 jeremybenn
 
97
mc-async:  a test of the memory controller with asynchronous memory.
98
mc-dram:   a test of the memory controller with DRAM.
99
mc-ssram:  a test of the memory controller with SSRAM.
100
mc-sync:   a test of the memory controller with synchronous memory.
101
uOS:       a microKernel.
102
 
103
Tests which do not build
104
========================
105
 
106 93 jeremybenn
The following test of standalone Or1ksim builds with a myriad of warnings.
107 82 jeremybenn
 
108
inst-set-test:  a comprehensive test of the instruction set using C.
109
 
110
 
111 93 jeremybenn
Updated by Jeremy Bennett (jeremy@jeremybennett.com)
112
28 April 2010

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.