source: rtems/c/src/lib/libbsp/m68k/mvme162/README @ bf3a7a5a

4.104.114.84.95
Last change on this file since bf3a7a5a was bf3a7a5a, checked in by Joel Sherrill <joel.sherrill@…>, on Jul 10, 1997 at 7:16:40 PM

Added information on different MVME162 models.

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