Difference between revisions of "Readout Controller Configuration"
(→Error) |
(→Error) |
||
| Line 156: | Line 156: | ||
{| border="1" cellpadding="4" | {| border="1" cellpadding="4" | ||
|- | |- | ||
| − | + | |Pin|| Name ||Setting | |
|- | |- | ||
| − | + | |1|| norm env ||on | |
|- | |- | ||
| − | + | |2 ||boot a ||off | |
|- | |- | ||
| − | 4 ||wpb ||off | + | |3|| wpa ||on |
| + | |- | ||
| + | |4 ||wpb ||off | ||
|} | |} | ||
Revision as of 22:32, 20 August 2007
MVME 6100
ROC1 ethernet address: 0001AF1998B5
ROC1 ethernet address: 0001AF1998B6
MPC7457 RISC G4 processor (PPC family)
Download files from JLAB
I downloaded the boot file and VXworks kernel from JLAB
/site/coda/kern/5.5/boot/boot6100_122.bin /site/coda/kern/5.5/vx6100_v4.1
and put in /tftpboot subdirectory on Host computer
Debug Connector
I then used the serial port on the host computer to interface with the MVME6100 via the "DEBUG" port. The debug port took an RJ45 standard cable so I got and RJ45-DB9 converter. This seemed to work out of the box. Just in case I ever need to make my own connector record the pinouts below.
Information below is Table 5-11 pg 92 of this reference
| ROC Pin# | DB9 Pin # | DB9 shell | Signal |
| 1 | 1 | Blue | DCD (Carrier Detect) |
| 2 | 7 | Orange | RTS (Request to Send) |
| 3 | 5 | Black | GNDC |
| 4 | 3 | Red | TX (Transmit) |
| 5 | 2 | Green | RX (Recieve) |
| 6 | 5 | Yellow | GNDC |
| 7 | 8 | Brown | CTS (Clear to Send) |
| 8 | 4 | White | DTR (Data Terminal Ready) |
MVME6100 BOOT screen
Copyright Motorola Inc. 1999-2007, All Rights Reserved MOTLoad RTOS Version 2.0, PAL Version 2.1 RM02 Wed Feb 7 11:32:02 MST 2007
MPU-Type =MPC74x7 MPU-Int Clock Speed =1266MHz MPU-Ext Clock Speed =133MHz MPU-Int Cache(L2) Enabled, 512KB, L2CR =C0000000 MPU-Ext Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026000
PCI bus instance 0 =64 bit, 133 Mhz, PCI-X PCI bus instance 1 =64 bit, PCI
Reset/Boot Vector =Flash1
Local Memory Found =20000000 (&536870912) User Download Buffer =006B7000:008B6FFF
Basic commands
setting the time
The command below will print the help screen for the time set command
he set
for example
MVME6100> set -t082604163100
08 = Month
26 = day
04 = year
16 = hour (24 hour clock)
31 = min
00 = seconds
MVME6100> time
THU AUG 26 16:31:02.00 2004
Ping another computer to check network
I was inable to ping unless I used the "LAN1" RJ45 etherenet port
MVME6100> ping -c134.50.3.216 -s134.50.3.210 Client (Source) IP Address = 134.50.3.216 Server (Destination) IP Address = 134.50.3.210 Server/Host Found, E-Address = 0030487A9468 170 (128+42) bytes from 134.50.3.210: icmp_seq=0 time=179 us Packets Transmitted =1, Packets Received =1, Packets Lost =0 (0%) Round-Trip Min/Avg/Max = 179/179/179 uS
show the flash memory
MVME6100> flashShow Device-Name Base-Address,Size Device-Size,Count Boot Type /dev/flash0 F4000000,04000000 02000000,00000002 No Intel 28F256 /dev/flash1 F8000000,04000000 02000000,00000002 Yes Intel 28F256
Load in the VxWorks boot kernel
MVME6100> tftpGet -cCLIENT_IP_ADDRESS -sSERVER_IP_ADDRESS -fFILENAME
CLIENT_IP_ADDESS is the IP address of the computer receiving the file
SERVER_IP_ADDRESS is the IP address of the computer hosting the file (by default tftp uses the subdirectory /tftpboot)
MVME6100> tftpGet -c134.50.3.216 -s134.50.3.210 -fboot6100_122.bin Network Loading from: /dev/enet0 Loading File: boot6100_122.bin Load Address: 006B7000 Download Buffer Size = 00200000
Client IP Address = 134.50.3.216 Server IP Address = 134.50.3.210 Gateway IP Address = 134.50.3.253 Subnet IP Address Mask = 255.255.255.0
Network File Load in Progress...
Bytes Received =&594768, Bytes Loaded =&594768 Bytes/Second =&594768, Elapsed Time =1 Second(s)
Flash the RAM with the program
>MVME6100>flashProgram -d/dev/flash0 -o03f00100 -nfff00
After flashing you flip dipswitch #2 on S4 fo off and powercycle
MVME6100> flashProgram -d/dev/flash0 -o03f00100 -nfff00 Source Starting/Ending Addresses =006B7000/007B6EFF Destination Starting/Ending Addresses =F7F00100/F7FFFFFF Number of Effective Bytes =000FFF00 (&1048320)
Program Flash Memory (Y/N)? Y
=== set BOOTA dip switch===
I moved the dip switch on S4 labeled "BOOT A" to OFF
Error
MVME6100> sysMotVpdInit: Unable to read Vital Product Data (VPD). sysMotVpdInit: Unable to read Vital Product Data (VPD).
The above error results when the "Normal" dip switch on S4 is set to "OFF". The S4 dipswitch are now set to
| Pin | Name | Setting |
| 1 | norm env | on |
| 2 | boot a | off |
| 3 | wpa | on |
| 4 | wpb | off |
The VxWorks Boot screen
VxWorks System Boot
Copyright 1984-2002 Wind River Systems, Inc.
CPU: Motorola MVME6100-0163 - MPC 7457 Version: VxWorks5.5.1 BSP version: 1.2/2 Creation date: Feb 2 2007, 16:49:27
Press any key to stop auto-boot... 7
[VxWorks Boot]:
Setting VxWorks Parameters
view the boot parameters
[VxWorks Boot]: p
boot device : geisc unit number : 0 processor number : 0 host name : host file name : /tornado/mv6100/vxWorks inet on ethernet (e) : 90.0.0.2 host inet (h) : 90.0.0.1 user (u) : vxworks flags (f) : 0x0
[VxWorks Boot]:
set the boot parameters
[VxWorks Boot]: p
boot device : geisc unit number : 0 processor number : 0 host name : daq1 file name : /home/daq/CODA/VXWorks/vx6100_v4.1 inet on ethernet (e) : 134.50.3.216 inet on backplane (b): fffffc00 host inet (h) : 134.50.3.210 user (u) : daq flags (f) : 0x0 target name (tn) : roc1 startup script (s) : /home/daq/CODA/bootscripts/roc1.boot
[VxWorks Boot]: