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

Subversion Repositories openrisc

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

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 90 jeremybenn
At the time of writing a total of 21 tests of the standalone simulator compile
16
run and pass and 1 test of the library.
17
 
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
A total of 21 tests:
49
 
50
basic:        A test or a wide range of instructions and registers.
51
cache:        A test of the Or1ksim cache modeling
52
cbasic:       A minimal test in C
53
cfg:          A test of the OR1K configuration register
54
dhry:         Dhrystone 2.1 benchmark using Or1ksim's timing facility.
55
dmatest:      A test of DMA.
56
eth:          A test of the Ethernet interface.
57
except-test:  A test of OR1K exception handling
58
exit:         A test that C program exits correctly
59
ext:          A test of the sign extension (l.ext) instructions.
60
fbtest:       A test of the frame buffer.
61
functest:     A test of the C function calling interface.
62
flag:         A test of Supervision Register (SR) flag bits.
63
int-test:     A test of the programmable interrupt controller.
64
kbdtest:      A test of the PS2 keyboard interface.
65
local-global: A test of C local and global variables.
66
mem-test:     A simple memory test.
67
mmu:          A test of the MMU.
68
mul:          A test of the multiply functionality.
69
mycompress:   A compression program.
70
tick:         A test of the OR1K tick timer.
71
 
72
Tests which build, but do not run to completion
73
===============================================
74
 
75
The following tests rely on VAPI in Or1ksim, so need a client to provide test
76
data over TCP/IP.
77
 
78
acv-gpio:  a test of the GPIO.
79
acv-uart:  a test of the UART
80
 
81
Tests which build, but do not run at all
82
========================================
83
 
84
These tests (which are built by the make file), do not appear to run at
85
all. The problem is in the linker script and/or the configuration for Or1ksim.
86
 
87
mc-async:  a test of the memory controller with asynchronous memory.
88
mc-dram:   a test of the memory controller with DRAM.
89
mc-ssram:  a test of the memory controller with SSRAM.
90
mc-sync:   a test of the memory controller with synchronous memory.
91
uOS:       a microKernel.
92
 
93
Tests which do not build
94
========================
95
 
96
The following test builds with a myriad of warnings.
97
 
98
inst-set-test:  a comprehensive test of the instruction set using C.
99
 
100
 
101
Upated by Jeremy Bennett (jeremy@jeremybennett.com)
102
19 April 2010

powered by: WebSVN 2.1.0

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