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

Last change on this file since 218c346 was fc7cbef, checked in by Ralf Corsepius <ralf.corsepius@…>, on 01/28/04 at 02:46:03

2004-01-28 Ralf Corsepius <corsepiu@…>

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