summaryrefslogtreecommitdiffstats
path: root/c/src/lib/libbsp/powerpc/virtex4/README
blob: 68a0c24e2eea271cc7267aca80597b1d82848791 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
# Adapted from virtex BSP

BSP NAME:           virtex4
BOARD:              N/A
BUS:                N/A
CPU FAMILY:         ppc
CPU:                PowerPC 405D5
COPROCESSORS:       N/A
MODE:               32 bit mode

DEBUG MONITOR:

PERIPHERALS
===========
TIMERS:             405 internal
SERIAL PORTS:       none
REAL-TIME CLOCK:    none
DMA:                Xilinx virtex internal
VIDEO:              none
SCSI:               none
NETWORKING:         none

DRIVER INFORMATION
==================
CLOCK DRIVER:       PPC Decrementer
IOSUPP DRIVER:      N/A
SHMSUPP:            N/A
TIMER DRIVER:       N/A
TTY DRIVER:         N/A

STDIO
=====
PORT:               N/A
ELECTRICAL:         N/A
BAUD:               N/A
BITS PER CHARACTER: N/A
PARITY:             N/A
STOP BITS:          N/A

Notes
=====

Board description
-----------------
clock rate:	350 MHz
ROM:		N/A
RAM:		128MByte DRAM

Virtex only supports single processor operations.

Porting
-------
This board support package is written for a naked Virtex 4/PPC FPGA
system. The rough features of such a board are described above.
The BSP itself makes no assumptions on what is loaded in the FPGA,
other than that the CPU has access to some memory, either on-board
or external, from which code can be run.

This BSP has been constructed so that an application of both firmware
and software can be layered on top of it by supplying implementations
for the various 'weak' symbols.  These symbols are prefaced with the
term 'app_'.  Applications can thus be built outside of the RTEMS
directory tree by linking with the appropriate libraries.

The linkcmds file describes the memory layout.  Included in this
definition is a section of memory named MsgArea.  Output sent to
stdout is recorded in this area and can be dumped using the JTAG
interface, for example.

For adapting this BSP to other boards, the following files should be
modified:

- c/src/lib/libbsp/powerpc/virtex4/startup/linkcmds
	for the memory layout required

- c/src/lib/libbsp/powerpc/virtex4/startup/bspstart.c
	Here you can select the clock source for the timers and the
        serial interface (system clock or external clock pin), the
        clock rates, etc.

- c/src/lib/libbsp/powerpc/virtex4/include/bsp.h
	some BSP-related constants

- c/src/lib/libbsp/powerpc/virtex4/*
	well, they should be generic, so there _should_ be no reason
	to mess around there (but who knows...)