1 | # |
---|
2 | # $Id$ |
---|
3 | # |
---|
4 | |
---|
5 | BSP NAME: mvme5500 |
---|
6 | BOARD: MVME5500 by Motorola |
---|
7 | BUS: PCI |
---|
8 | CPU FAMILY: ppc |
---|
9 | CPU: MPC7455 @ 1GHZ |
---|
10 | COPROCESSORS: N/A |
---|
11 | MODE: 32/64 bit mode (support 32 bit for now) |
---|
12 | DEBUG MONITOR: MOTLoad |
---|
13 | SYSTEM CONTROLLER: GT64260B |
---|
14 | |
---|
15 | OTHER README FILES: README.booting,README.rtems-4.6.0-patch,README.VME, |
---|
16 | README.irq |
---|
17 | |
---|
18 | PERIPHERALS |
---|
19 | =========== |
---|
20 | TIMERS: Eight, 32 bit programmable |
---|
21 | SERIAL PORTS: 2 NS 16550 on GT64260B |
---|
22 | REAL-TIME CLOCK: MK48T37V |
---|
23 | 32K NVSRAM: MK48T37V |
---|
24 | WATCHDOG TIMER: use the one in GT-64260B |
---|
25 | DMA: 8 channel DMA controller (GT-64260B) |
---|
26 | VIDEO: none |
---|
27 | NETWORKING: Port 1: Intel 82544EI Gigabit Ethernet Controller |
---|
28 | 10/100/1000Mb/s routed to front panel RJ-45 |
---|
29 | Port 2: 10/100 Mb ethernet unit integrated on the |
---|
30 | Marvell's GT64260 system controller |
---|
31 | |
---|
32 | DRIVER INFORMATION |
---|
33 | ================== |
---|
34 | CLOCK DRIVER: PPC internal |
---|
35 | IOSUPP DRIVER: N/A |
---|
36 | SHMSUPP: N/A |
---|
37 | TIMER DRIVER: PPC internal |
---|
38 | TTY DRIVER: PPC internal |
---|
39 | |
---|
40 | STDIO |
---|
41 | ===== |
---|
42 | PORT: Console port 0 |
---|
43 | ELECTRICAL: na |
---|
44 | BAUD: na |
---|
45 | BITS PER CHARACTER: na |
---|
46 | PARITY: na |
---|
47 | STOP BITS: na |
---|
48 | |
---|
49 | |
---|
50 | Jumpers |
---|
51 | ======= |
---|
52 | |
---|
53 | 1) The BSP is tested with the 60x bus mode instead of the MPX bus mode. |
---|
54 | ( No jumper or a jumper across pins 1-2 on J19 selects the 60x bus mode) |
---|
55 | |
---|
56 | 2) On the mvme5500 board, Ethernet 1 is the Gigabit Ethernet port and is |
---|
57 | front panel only. Ethernet 2 is 10/100 BaseT Ethernet. For front-panel |
---|
58 | Ethernet2, install jumpers across pins 1-2 on all J6, J7, J100 and |
---|
59 | J101 headers. |
---|
60 | |
---|
61 | 3) Enable SROM initialization at startup. (No jumper or a jumper across |
---|
62 | pins 1-2 on J17) |
---|
63 | |
---|
64 | In fact, (if I did not miss anything) the mvme5500 board should function |
---|
65 | properly if one keeps all the jumpers at factory configuration. |
---|
66 | One can leave out the jumper on J30 to disable EEPROM programming. |
---|
67 | |
---|
68 | Notes |
---|
69 | ===== |
---|
70 | |
---|
71 | BSP BAT usage |
---|
72 | ---------------------- |
---|
73 | DBAT0 and IBAT0 |
---|
74 | 0x00000000 |
---|
75 | 0x0fffffff 1st 256M, for MEMORY access (caching enabled) |
---|
76 | |
---|
77 | DBAT1 and IBAT1 |
---|
78 | 0x00000000 |
---|
79 | 0x0fffffff 2nd 256M, for MEMORY access (caching enabled) |
---|
80 | |
---|
81 | UPDATE: (2004/5). |
---|
82 | The BSP now uses page tables for mapping the entire 512MB |
---|
83 | of RAM. DBAT0 and DBAT1 is hence free for use by the |
---|
84 | application. A simple 1:1 (virt<->phys) mapping is employed. |
---|
85 | The BSP write-protects the text and read-only data |
---|
86 | areas of the application. Special acknowledgement to Till |
---|
87 | Straumann <strauman@slac.stanford.edu> for providing inputs in |
---|
88 | porting the memory protection software he wrote (BSP_pgtbl_xxx()) |
---|
89 | to MVME5500. |
---|
90 | |
---|
91 | |
---|
92 | The default VME configuration uses DBAT0 to map |
---|
93 | more PCI memory space for use by the universe VME |
---|
94 | bridge: |
---|
95 | |
---|
96 | DBAT0 |
---|
97 | 0x90000000 PCI memory space <-> VME |
---|
98 | 0x9fffffff |
---|
99 | |
---|
100 | Port VME-Addr Size PCI-Adrs Mode: |
---|
101 | 0: 0x20000000 0x0F000000 0x90000000 A32, Dat, Sup |
---|
102 | 1: 0x00000000 0x00FF0000 0x9F000000 A24, Dat, Sup |
---|
103 | 2: 0x00000000 0x00010000 0x9FFF0000 A16, Dat, Sup |
---|
104 | |
---|
105 | |
---|