1 | -- |
---|
2 | -- EISCAT Scientific Association. M.Savitski |
---|
3 | -- |
---|
4 | -- This material is a part of the MVME162 Board Support Package |
---|
5 | -- for the RTEMS executive. Its licensing policies are those of the |
---|
6 | -- RTEMS distribution. |
---|
7 | -- |
---|
8 | -- Updated by Joel Sherrill (jsherril@redstone.army.mil) after |
---|
9 | -- inclusion in the standard release. |
---|
10 | -- |
---|
11 | -- $Id$ |
---|
12 | -- |
---|
13 | |
---|
14 | This is a README file for the MVME162 port of RTEMS. |
---|
15 | |
---|
16 | Disclaimer |
---|
17 | ---------- |
---|
18 | This is my first attempt at porting RTEMS. The resulting code obviously |
---|
19 | contains bugs (know and unknown) and limitations. I assume no |
---|
20 | responsibility for quality and support of the software in question. |
---|
21 | |
---|
22 | Now on more optimistic note: |
---|
23 | |
---|
24 | I have run most of the standard RTEMS sptests, and neither of them |
---|
25 | failed. My present (short) experience of developing RTEMS applications |
---|
26 | is essentially positive and suggestive of a long-term commitment. In |
---|
27 | any case I am ready to answer questions regarding the port and intend |
---|
28 | to follow the future RTEMS versions. I will do my best to provide |
---|
29 | whatever support I can afford time-wise. |
---|
30 | |
---|
31 | MVME162FX and DMA on the IP bus |
---|
32 | ------------------------------- |
---|
33 | |
---|
34 | From Eric Vaitl <eric@viasat.com>: |
---|
35 | |
---|
36 | If you have any customers that will be using the 162FX, tell them to |
---|
37 | be careful. The main difference between the 162 and the 162FX is DMA |
---|
38 | on the IP bus. I spent over a month trying to write a DMA HDLC driver |
---|
39 | for GreenSprings IP-MP and couldn't get it to work. I talked to some |
---|
40 | people at GreenSprings, and they agreed that there really is no way to |
---|
41 | get DMA to work unless you know the size of the packets in advance. |
---|
42 | Once the IP2 chip DMA controller is given the character count and |
---|
43 | enabled, it doesn't accept further commands until all of the |
---|
44 | characters have arrived. The only way to terminate a DMA transfer |
---|
45 | prematurely is by raising DMAEND* during the last read. None of the IP |
---|
46 | modules that I know of are currently able to do that. GreenSprings is |
---|
47 | working on the problem, but nothing is going to available for a few |
---|
48 | months. |
---|
49 | |
---|
50 | Installation |
---|
51 | ------------ |
---|
52 | Nothing unique to the MVME162. It has been incorporated into the |
---|
53 | standard release. |
---|
54 | |
---|
55 | Port Description |
---|
56 | ---------------- |
---|
57 | The port was done using already existing ports to the M68020 boards, |
---|
58 | DMV152 and MVME136. |
---|
59 | |
---|
60 | The host system was SUN/Solaris 2.3, and the cross-development |
---|
61 | environment consisted of Free Software Foundation (FSF)'s GNU C |
---|
62 | compiler (version 2.6), GNU Assembler (version 2.3) and GNU binary |
---|
63 | utilities binutils version 2.5.2, built with m68k as a target. The |
---|
64 | recent/latest versions of other GNU programs (flex, make, etc) were |
---|
65 | also used at the build stage. |
---|
66 | |
---|
67 | In all subdirectories of the RTEMS distribution tree, the directories |
---|
68 | mvme136 were duplicated as mvme162. |
---|
69 | |
---|
70 | Essential modifications are detailed below: |
---|
71 | |
---|
72 | - the MVME162-specific hardware registers were described in bsp.h |
---|
73 | |
---|
74 | - timer and clock routines were made to use the MVME162's Tick Timers 1 |
---|
75 | and 2, respectively |
---|
76 | |
---|
77 | - shared memory support was replaced by stubs for the time being |
---|
78 | |
---|
79 | - console IO was lifted entirely from the DMV152 support code, thanks |
---|
80 | to the fact that Z8530 SCC used in DMV152 is upwards compatible with |
---|
81 | the Z85230 SCC of the MVME162. (Only the memory mapping of the SCC |
---|
82 | registers had to be changed.) |
---|
83 | |
---|
84 | - symbols in several *.s files were prepended with underscores to |
---|
85 | comply with the xgcc configuration used (it prepends underscores to all |
---|
86 | symbols defined in c code) |
---|
87 | |
---|
88 | - linkcmds file was modified to place the linked code into the memory |
---|
89 | configured for the board in use |
---|
90 | |
---|
91 | - bspstart.c was modified as follows: |
---|
92 | |
---|
93 | monitors_vector_table = (m68k_isr *)0xFFE00000; |
---|
94 | |
---|
95 | was made to point to the power-up location of MVME162 interrupt vector |
---|
96 | table. |
---|
97 | |
---|
98 | - The shutdown is a temporary solution. To exit cleanly, it has to disable |
---|
99 | all enabled interrupts and restore the board to its power-up status. |
---|
100 | Presently this is not done satisfactorily, as a result, the board needs |
---|
101 | a hardware reset from the external VMEbus master or from the front |
---|
102 | panel to ensure correct operation for subsequent downloads. |
---|
103 | |
---|
104 | Host System |
---|
105 | ----------- |
---|
106 | The VMEbus master used to externally control and download the MVME162 |
---|
107 | is a FORCE CPU-2CE board running Solaris 2.3. A simple program to load |
---|
108 | s-records and start/reset the MVME162 was written. The code is in the |
---|
109 | file tools/sload.c |
---|
110 | |
---|
111 | This code depends on the external VMEbus master's vme driver and is |
---|
112 | provided as an example, without the Makefile. The bulk of the program |
---|
113 | which parses the s-records is courtesy of Kym Newbery, |
---|
114 | (8918927y@lux.levels.unisa.edu.au). |
---|
115 | |
---|
116 | In general, apart from x-gcc, the tools most often used while building |
---|
117 | RTEMS for MVME162 were: find, grep, diff, and, of course |
---|
118 | |
---|
119 | MVME162 Embedded Controller Programmer's Reference Guide, |
---|
120 | Motorola, MVME162PG/D1. |
---|
121 | |
---|
122 | Thanks |
---|
123 | ------ |
---|
124 | - to On-Line Applications Research Corporation (OAR) for developing |
---|
125 | RTEMS and making it available on a Technology Transfer basis; |
---|
126 | - to Joel Sherril, the leader of the RTEMS development group for |
---|
127 | stimulating and helpful discussions; |
---|
128 | - to Kym Newbery (8918927y@lux.levels.unisa.edu.au) for his s-record |
---|
129 | parser; |
---|
130 | - to Gerd Truschinski (gt@first.gmd.de) for creating and running the |
---|
131 | crossgcc mailing list |
---|
132 | - to FSF and Cygnus Support for great free software; |
---|
133 | |
---|
134 | What's new |
---|
135 | ---------- |
---|
136 | - 28.07.95 BSP adjusted to rtems-3.2.0. |
---|
137 | - Now console driver uses interrupts on receive (ring buffer |
---|
138 | code lifted with thanks from the IDP BSP next door (../idp)) |
---|
139 | - both front-panel serial interfaces are supported |
---|
140 | - serious bug in timer interrupts fixed |
---|
141 | - interrupt test tm27 now supported |
---|
142 | |
---|
143 | +----------------------------------+-------------------------------+ |
---|
144 | | Dr. Mikhail (Misha) Savitski | Voice : +46-980-79162 | |
---|
145 | | Software Systems Engineer | Fax : +46-980-79161 | |
---|
146 | | EISCAT Svalbard Radar Project | E-mail: mms@eiscathq.irf.se | |
---|
147 | | EISCAT Scientific Association |----------- /\_/\ -----------| |
---|
148 | | Box 812 S-98128 Kiruna, Sweden | EIS { o o } CAT | |
---|
149 | +----------------------------------+-------oQQQ--(>I<)--QQQo-------+ |
---|
150 | |
---|
151 | |
---|