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

4.104.114.84.95
Last change on this file since 50b5f9d was 50b5f9d, checked in by Joel Sherrill <joel.sherrill@…>, on Aug 4, 1997 at 9:57:06 PM

Trying to support all models

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