target.nr

860最小系统的bsp

'\" t
.so wrs.an
.\" ads860/target.nr - Motorola MPC8xx(F)ADS target specific documentation
.\"
.\" Copyright 1984-1996 Wind River Systems, Inc.
.\"
.\" modification history
.\" --------------------
.\" 01i,19mar99,cn   added information on sysMotCpmEnd (SPR# 25839).
.\" 01h,01mar99,cn   added information on known problems/limitations.
.\" 01g,22feb99,cn   added information on 8xx Errata and data cache patch.
.\" 01f,30jan99,cn   updated documentation (SPR# 8746 and SPR# 20751)
.\" 01e,28apr98,yp   added info on TFFS.
.\" 01d,25nov97,map  added info on 860 devices used.
.\" 01c,12sep97,map  info about problems with the "go" command
.\" 01b,24jul96,tpr  added Aux Clock Doc + corrected typo.
.\" 01a,16jun96,tpr  created from mv1604.
.\"
.\"
.TH "ads860" T "Motorola MPC821/860ADS and MPC8xxFADS" "Rev: 17 Jun 96" "VXWORKS REFERENCE MANUAL"

.SH "NAME"
.aX "Motorola MPC821/860ADS & MPC8xxFADS "

.SH "INTRODUCTION"
This note provides board-specific information necessary to run
VxWorks.  Before running VxWorks, verify that the board runs in the
factory configuration.
The ads860 BSP produces a VxWorks image running on either the PowerPC 8xx 
processors. From the VxWorks perspective these processors are equivalent.
The URL: http://www.mot.com/SPS/RISC/netcomm/support/index.html#errata_group 
provides information on all MPC8xx, MPC860T, and MPC860SAR device errata 
from Rev. A onwards.  Please, check which ones apply to your particular 
device/revision before using VxWorks. WRS has not implemented any of the 
workarounds suggested there for any of the known hardware problems.

.SH "BOOT ROMS"
No VxWorks Boot ROM is provided with this BSP release. Nevertheless VxWorks
boot code is working if downloaded into the SIMM Flash ROM.

To program the SIMM Flash ROM, the ADI card from Motorola is required.
This debug card is available for Sun workstation or PC. Connect this ADI card
to the MPC821/860ADS board via the ADI port. Check that a 12V potential is
provided to the MPC8xx(F)ADS board; otherwise the SIMM Flash will not be erased
and/or re-programmed. On the host, start the mpc8bug executable (mpc8bug.exe on
PC). Once the prompt appears, reset the board with the following command:
.CS
	821Bug> reset:h
.CE

Then download the bootrom_uncmp.hex file to the Flash:

	821Bug> loadf /<PATH_TO_THE_ADS860_BSP>/bootrom_uncmp.hex 100000

The 100000 value is the address in DRAM memory where the bootrom_uncmp.hex
file is temporarily downloaded before it is moved to Flash. A message
like the following copy should appear:

.CS
	loadf: Loading Srecords file . . .
	Loading flash mapped sections to ram memory buffer:
	Loading block : at 00100000 
		      : 0004efd0 bytes loaded
	Programming flash : 0004efd0 bytes  at 02800100-0284f0cf 
	Flash programming completed 

	Loading ram mapped sections to ram memory:
	Entry point (IP) is not set 
	Heap start address set to 0284f0d0
	821Bug> 
.CE

Now the SIMM Flash memory is programmed with the new boot program. To execute
this new boot program turn the board off and on. If the board is still 
connected to the ADI card then the processor is stopped at the first instruction
to execute. From the mpc8bug prompt call the "go" command to resume FLASH
code execution.

.SH "Jumpers"
No jumpers are relevant to VxWorks configuration. However, the dip switch DS1
on the FADS8xxDB Daughter Board should not be changed from its factory 
configuration, otherewise erratic behaviour of the LXT970 , which implements 
the physical layer device for the FEC, may derive. See also "Special
Considerations" below.
 
.PP


This board doesn't have non-volatile RAM; thus boot parameters
are not preserved when the system is powered off.
.PP

To load VxWorks, and for more information, follow the instructions in the
"Getting Started"
chapter of the
.I "VxWorks Programmer's Guide."

.PP
An alternative way to load vxWorks is through the ADI debug card. Plug the ADI
connector in the ADI port of the board, power on the board and start the
mpc8bug executable on the host. Execute the reset command to initialize the
board:

.CS
	821Bug> reset:h
.CE

Then download VxWorks:

.CS
	821Bug> load /<ADS860_BSP_PATH>/vxWorks
	Loading ELF file . . .
	Entry point set to 00100000
	Loading section 1 (.text) : 0005fcec bytes at 00100000 
	Loading section 2 (.rodata) : 0000263c bytes at 0015fcec 
	Loading section 4 (.data) : 00001058 bytes at 00162328 
	Loading section 5 (.got) : 00000010 bytes at 00163380 
	Loading section 7 (.sbss) : 00000298 bytes at 00163390 (not loaded)
	Loading section 8 (.bss) : 000079e8 bytes at 00163628 (not loaded)
	Heap start address set to 0016b010
	Loaded 000008da symbols into the symbol table
	Duplicated symbols (-103) expanded with enumerated suffixes 
	r3 and r5 are set to 0
.CE

Then reset the DER register 

.CS
	821Bug> rms DER 0
.CE

And finally start VxWorks execution:

.CS
	821Bug> go 100000
.CE

On some ADI configurations, resuming execution with the "go" could
result in exceptions or other problems. In such cases, unplug the ADI
connector, and reset the target board to start VxWorks.
	
.PP

.SH "TrueFFS support"
.PP
This BSP supports the optional product TrueFFS for Tornado. To use TrueFFS
install the product, add sysTffs.o to MACH_EXTRA in the Makefile and define
INCLUDE_TFFS in config.h. 

TrueFFS is set up to use the PCMCIA slots and the half of the Flash SIMM that
is not used by the bootrom as drives for use with dosFs.

If you use the function tffsBootImagePut, the "offset parameter should be
computed as (ROM_TEXT_ADRS - ROM_BASE_ADRS) and should evaluate to 0x100 
for the default configuration. The boot-image (i.e. bootrom, bootrom_uncmp
etc) should be filtered using elfToBin prior to using tffsBootImagePut.

.PP

.SH "DEVICES"
.PP
The chip drivers included are: