Configure uC5282 NVRAM
Note: Alternately, with more recent versions of rtems (Example: 4.9.x) , you can directly flash the netboot.flashimg.bin file.
(Much of this document is from an email from Till, 13 March 2008)
The syntax to set variables is:
B$ setenv ENVVAR value
To clear an environment variable:
B$ setenv ENVVAR
To show a list of all variables:
B$ printenv
To show the value of a single variable:
B$ printenv ENVVAR
^h1. How-to setup the ColdFire uC5282 to run EPICS and RTEMS
To FLASH the uC5282:
If the CPU has already been flashed, skip to step 5.
STEP 1: Set the uC5282 IP address (in this example, it is 172.27.9.232):
B$ setenv IPADDR0 172.27.9.232
STEP 2: Start the the tftp server running on the ColdFire:
B$ tftp
uCTFTP Console 1.0 is running ...
IPADDRESS is 172.27.9.232
Downloading...
STEP 3: Next generate a cramfs image on your host (need the mkcramfs utility on the host):
...
mkdir cramfs_top
cp /usrafs/localslac/lclspackage/rtems/rtems-4.9.1<version>/target/ssrlAppsssrlApps<lvl>/m68k-rtems/uC5282/img/netboot.flashimg.bin cramfs_top/netboot.bin
Note: If your board is a 80MHz version of Coldfire, then you want to use netboot and rtems from 4.9.4/target/rtems_p1/ssrlApps_p3/
mkcramfs cramfs_top cramfs.img
STEP 4: Next run the tftp client on your host and copy the image to the ColdFire:
$ tftp 172.27.9.232
tftp> bin
tftp> verbose
tftp> put cramfs.img
NOTE: in spite of the coldfire being a big-endian machine and cramfs internal data structures being susceptible to endianness, uCbootloader seems to expect a LITTLE-endian cramfs image (which is directly created by mkcramfs on a little-endian machine such as a x86 box)
Note: For more recent vesions of the rtems (for example 4.9.x), one can tftp in netboot.flashimg.bin directly, without having to compress it first.
Connect serial port (Example: on BPM chassis) to serial port on your computer. (It must be a straight-through cable.) Connect to your local serial port using a terminal emulation program (Tera Term Pro on Windows works).
Note: If connecting through DIGI Terminal Port Server, connect the serial port of device/chassis containing Coldfire module, to one of the serial ports of the DIGI.
To use iocConsole program to do serial communications with the DIGI:
(a) Add your Coldfire EIOC to screeniocs file, the configuration file for iocConsole.
For development environment, this file is in /afs/slac/g/lcls/epics/ioc/iocCommon/screeniocs.
This file lets association of a DIGI Serial Port number with your <coldfire_eioc_nodename>
(b) From a development linux host, such as lcls-dev2:
> source /afs/slac/g/lcls/tools/script/ENVS.bash
> iocConsole <coldfire_eioc_nodename>
Example: iocConsole 134.79.219.81
Power up the Coldfire device/chassis (Example: BPM chassis).
B$ setenv IPADDR0 134.79.219.81
Start the tftp program:
B$ tftp-- Now you should see the following on the coldfire's console:
uCTFTP Console 1.0 is running ... IPADDRESS is 172.27.9.232
(These instructions are for using tftp. To use the serial connection,
use the uCdimm Coldfire 5282 manual)
From your host:
hostname$tftp 134.79.219.81
tftp> verbose
Verbose mode on.
tftp> binary
mode set to octet
tftp> tra
Packet tracing on.
tftp> put cramfs.img
NOTE: Use 'put netboot.flashimg.bin' if you are directly tftping the binary image (and not the compressed image) per Step 2.
You will see messages like these in your host session:
putting cramfs.img to 134.79.219.81:cramfs.img octet
Sent 270336 bytes in 20.2 seconds []
tftp>
You will see messages like these on your serial session:
..........................
donePress the ESC key once you see that it is done.
Next you need to actually program and verify it
It sometimes times out and takes a few tries before it works. In your serial session, press ESC to exit tftp and return to the B$ prompt
B$ program
erase... done.
write... done.
Select boot file:
B$ verifysetenv KERNEL 0:netboot.flashimg.bin
The board has now been flashed. Next you can do one of three things (four things counting nothing):
(7a) Test that you can boot the netboot image.
(7b) Set up for production. (Do this only if you feel confident that the
flashing worked.)
(7c) Boot up to test on development.
verify...
done.
B$Next select the boot file:
B$ setenv KERNEL 0:netboot.flashimg.bin
STEP 5: Once the uC5282 is flashed, you will need to set the environment variables.
--To show your current environment variables, type:
B$ printenv
--To change an environment variable, type:
B$ setenv VARIABLE_NAME VARIABLE_VALUE
for example:
B$ setenv NETMASK 255.255.252.0
--Set the following environment variables for LCLS production (some of these will already be set; use printenv to see which need to be set):
setenv BP_SRVR 134.79.19.29
setenv BP_FILE afsnfs2:/afs/slac:package/rtems/4.9.1/target/ssrlApps/m68k-rtems/uC5282/bin/rtems.ralf
setenv NETMASK 255.255.252.0
B$ printenv
FACTORY=Arcturus Networks Inc.
REVISION=uC5282 Rev 1.1 16MB External Flash
SERIAL=X49E5FA37-01080
CONSOLE=ttyS0
KERNEL_ARGS=root=/dev/mtdblock0 quiet
HWADDR0=00:06:3B:00:F0:80
FW_VERSION=010808012
_0=10000000:1000000:RW
CACHE=on
KERNEL=0:netboot.flashimg.bin
BP_SRVR=134.79.19.29
BP_FILE=afsnfs2:/afs/slac:package/rtems/4.9.1/target/ssrlApps/m68k-rtems/uC5282/bin/rtems.ralf
IPADDR0=134.79.219.113
NETMASK=255.255.252.0
Note: There is a slight difference in setting up the flash partition for a 4 M Coldfire and a 16 M Coldfire:
For 4M Coldfire, the partition as above will work - so nothing needs to be set up specifically.
For 16M Coldfire, the partition must be setup as follows:
_0=10000000:100000:RW
_1=10100000:F00000:RW
Read the manual /afs/slac/package/rtems/<version>/src/ssrlApps<lvl>/netboot/README.uC5282 which explains how to deal with 16M of flash.
B$ go
uncompress... go! 0x40000
RTEMS bootloader by Till Straumann <strauman@slac.stanford.edu>
$Id: netboot.c,v 1.33 2009/02/05 08:39:20 strauman Exp $
CVS tag $Name: rtems-4-9-1-p2 $
Press 's' for showing the current NVRAM configuration
Press 'b' for manually entering filename/cmdline parameters only
Press '@' for continuing the netboot (BOOTP flag from NVRAM)
Press 'd' for continuing the netboot; enforce using BOOTP
Press 'p' for continuing the netboot; enforce using BOOTP
but use file and cmdline from NVRAM
Press 'm' for continuing the netboot; enforce using NVRAM config
Press 'R' to reboot now (you can always hit <Ctrl>-x to reboot)
Press any other key for this message
This example is a 4MB uC5282 named eioc-in20-bp221 that is not using DHCPB$ printenv
FACTORY=Arcturus Networks Inc.
REVISION=uC5282 Rev 1.0 4MB 1 16MB External Flash
SERIAL=X4436BE72-018A9 (this value may be different)X4747745D-01DC9
CONSOLE=ttyS0
KERNEL=0:netboot.flashimg.bin*
KERNEL_ARGS=root=/dev/mtdblock0 (this probably doesn't matter)quiet
HWADDR0=00:06:3B:00:68:A9 (this value may be different)AD:C9
FW_VERSION=180008 (this value may be different)010808004
_0=10000000:4000001000000:RW (this value may be different)
CACHE=on
(next three are optional; depends whether you want the ioc to boot up on its own the first time; also depends on whether or not dhcp will be set up in advance)
DO_BOOTP=Y
AUTOEXEC=2
AUTOBOOT=2
B$ printenv
FACTORY=Arcturus Networks Inc.
REVISION=uC5282 Rev 1.1 16MB External Flash
SERIAL=X4747745D-01DC9
CONSOLE=ttyS0
KERNEL=0:netboot.flashimg.bin
RAMIMAGE=yes
CACHE=on
NETMASK=255.255.252.0
DO_BOOTP=N
AUTOBOOT=5
BP_SRVR=172.27.8.11 KERNEL_ARGS=root=/dev/mtdblock0 quiet
HWADDR0=<macaddress>
FW_VERSION=010808004
_0=10000000:1000000:RW
CACHE=on
IPADDR0=<ipaddress>
DNS_SERVER=134.79.151.1112
NTP_SERVER=134.79.151.1113
GATEWAY NETMASK=172255.27255.8252.10
IPADDR0 GATEWAY=172134.2779.9219.2321
HOSTNAME=eioc-in20-bp221<hostname>
BP_PARM=INIT=/boot/g/lcls/epics/iocCommon/eioc-in20-bp221/startup.cmd
/iocTop/<appname>/<tagname>/iocBoot/<eiocname>/st.cmd
LOGHOST=syslog-host
DNS_DOMAIN=slac.stanford.edu
BP_FILE=afsnfs2:/afs/slac:/package/rtems/4.9.1/target/ssrlApps/m68k-rtems/uC5282/bin/rtems.ralf
DNS BP_DOMAINSRVR=slac134.79.stanford.edu
A 16 MB uC5282 is the same except that RAMIMAGE=no.
References
19.148
DO_BOOTP=N
Here are some useful links that discuss flashing 16M Coldfire and 80 MHz Coldfire:
^
