...
Now we'll get the software that the SBC will need to boot, and write it to flash memory. In the example output
that follows, the text that you need to enter is highlighted and in bold. Please note that the mvme5500 does requires a few different commands from the mvme6100. To flash an mvme5500 click here.
The terminal emulation software allows you to see the output from the SBC, and to type commands to the firmware monitor.
| Panel |
|---|
|
Copyright Motorola Inc. 1999-2007, All Rights Reserved
RTOS Version 2.0, PAL Version 2.1 RM02
Feb 7 11:32:02 MST 2007 MPU-Type =MPC74x7
Clock Speed =1266MHz
Clock Speed =133MHz
Cache(L2) Enabled, 512KB, L2CR =C0000000
Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026000 PCI bus instance 0 =64 bit, 133 Mhz, PCI-X
bus instance 1 =64 bit, PCI Reset/Boot Vector =Flash1 Local Memory Found =20000000 (&536870912)
Download Buffer =006B7000:008B6FFF MVME6100> |
| Panel |
|---|
MVME5100>set -t110305142700 |
Next, download the NetBoot program into the IOC. Use the network address that you obtained during "Inventory".
It needs to be entered with the tftpGet command, after the "-c" (for client) on the command line. Note that the backslash () is put at the end of the line as a continuation marker. You can simply type the remainder of the command without the backslash.
In order to use the tftp server your ethernet wall connection MUST be on the lclsdev subnet (ie 134.79.219.xxx) or the lclsdmz subnet (ie 134.79.151.xxx). Note that the "xxx" needs to be replaced with the correct value from your own address. If your ethernet wall connection is NOT on the lclsdev or lclsdmz subnet then you can load the flash in your cpu from another configured cpu (of the same model). This is done by copying the flash in the configured cpu over the VME backplane to the cpu you intend to flash. Instructions on how to perform this operation can be found by clicking here.
...
Subnet | TFTP Server |
...
Subnet
...
Server
Gateway | RTEMS Image | |
Development | lclsdmz | lcls- |
|---|
...
dev1 134. |
...
79.219. |
...
136 | 132.79.219.1 | /rtems/4. |
...
10. |
...
2/powerpc-rtems/beatnik/img/netboot.flashimg.bin |
...
LCLS |
|---|
...
lclsioc | lcls- |
...
srv04 172.27.8. |
...
28 | 172.27.8.1 | /rtems/rtems-4. |
...
10. |
...
2/target/ssrlApps/powerpc-rtems/beatnik/img/netboot.flashimg.bin |
...
| FACET | facetca | lcls-srv04 172.27.8.28 | 172.27.72.1 | /rtems/rtems-4.10.2/target/ssrlApps/powerpc-rtems/beatnik/img/netboot.flashimg.bin |
The "-s" parameter allows us to specify the server address. For the lclsdev subnet, it is 134.79.219.12
...
, the address of the lcls-dev2 server. For the lclsdmz subnet, it is 134.79.155.15, the address of the mccdev VMS server. The "-m" parameter indicates a netmask to use to access the server.
Finally, the "-f" parameter indicates the name of the file (under /tftpboot on lcls-dev, elsewhere on mccdev) containing the sequence of values to be loaded into memory.
| Panel |
|---|
|
MVME6100> {color:#ff00ff}{*}tftpGet \-c<cpu_ip> \- s1<servers<tftp server_ip> \-g<gateway_ip> *{color} {color:#ff00ff}*\-m255.255.252.0 \-f<rtems_flash_image> *{color} Network LoadingNetwork Loading from: /dev/enet0
File: mv6100/netboot-mve.flashimg.bin
Address: 005C3000 Client IP Address = <cpu_ip>
IP Address = <server_ip>
IP Address = <gateway_ip>
IP Address Mask = 255.255.252.0 Network File Load in Progress... Bytes Received =&614736, Bytes Loaded =&614736
=&204912, Elapsed Time =3 Second(s)
|
For the mvme6100 processor, the command is identical. The same version of the NetBoot program is downloaded, although the output on the screen will be slightly different.
At this point, we'll disable the network activity on all adapters, to ensure nothing interrupts us while we copy the image to flash memory. This is not essential, because it is not likely that any network activity would have an effect on the system at this point.
Example:
MVME6100> tftpGet -c134.79.219.146 -s134.79.219.136 -g132.79.219.1 -m255.255.252.0 -f/rtems/4.10.2/powerpc-rtems/beatnik/img/netboot.flashimg.bin
Network Loading from: /dev/enet0
Loading File: /rtems/4.10.2/powerpc-rtems/beatnik/img/netboot.flashimg.bin
Load Address: 006B7000
Download Buffer Size = 00200000
Client IP Address    = 134.79.219.146
Server IP Address    = 134.79.219.136
Gateway IP Address   = 132.79.219.1
Subnet IP Address Mask = 255.255.252.0
Network File Load in Progress...
Bytes Received =&824776, Bytes Loaded =&824776
Bytes/Second  =&824776, Elapsed Time =1 Second(s)
MVME6100>
| Panel | |
|---|---|
MVME6100> netShut Code Block | MVME6100> |
Now we can actually copy the memory image that we downloaded in step 4 above from RAM into Flash. That is, we're copying it from temporary memory into a more permanent memory that will last after power failures or restarts. If you notice in the tftpGet output, it tells us the load address, in this example for the mvme5500, it was 005C3000. The load address is the location to which the file was copied.
We'll copy this file from that memory location into the Flash memory, so it won't be lost. In this example, the flashProgram command is used; the "-s" parameter indicates the source of the data to be copied, in our example 0x005C3000. The "-v" parameter tells the software to be verbose about what it's doing. It prints a few lines, then asks you to confirm.
| Panel |
|---|
MVME5500> {color:#ff00ff}{*}flashProgram \-s5C3000 \-v {*}{color} Source
Addresses =005C3000/006C2FFF
Starting/Ending Addresses =F2000000/F20FFFFF
of Effective Bytes =00100000 (&1048576) Program Flash Memory (Y/N)? {color:#ff00ff}{*}Y{*}{color} Y =00
=89
=18
=01
=89
=18
=FE000000
Memory Programming Complete
|
For
...
the
...
mvme6100,
...
the
...
load
...
address
...
is
...
006B7000.
...
Accordingly,
...
for
...
that
...
processor,
...
the command would be:
| Panel |
|---|
MVME6100> flashProgram -s6B7000 -v =006B7000/007B6FFF
Starting/Ending Addresses =F4000000/F40FFFFF
of Effective Bytes =00100000 (&1048576) Program Flash Memory (Y/N)? {color:#ff00ff}{*}Y{*}{color} Y =00
|
You've "flashed" the processor. Now, you can emulate the boot process to test that it will work.
| Panel |
|---|
| MVME6100> {color:magenta}*bmw -af4000000 -bf40fffff -c4000000 *{color}
|
| Panel |
|---|
MVME6100> {color:#ff00ff}{*}go \-a4000000 {*}{color} Exception handling initialization done ---- Welcome to
Welcome to rtems-4.7(PowerPC/PowerPC 7455/mvme5500) on MVME5500-0163
Date: 20050506PDT18:52:37 ---- NowNow BSP_mem_size = 0x1FE00000
= 15000
/dev/console as minor 0 (==/dev/ttyS0) RTEMS bootloader by Till Straumann <strauman@slac.stanford.edu>
netboot.c,v 1.21 2005/04/26 02:05:03 till Exp $
tag $Name: $
CPU Temperature calibration changed or was not initialized...
calibrate the CPU TAU (thermal assist unit), you must observer the following steps: {{
Type any character to abort netboot : {color: #ff00ff}*<press any keyboard character here> *{color}2 Press2 Press 's' for showing the current NVRAM configuration
'c' for changing your NVRAM configuration
'b' for manually entering filename/cmdline parameters only
'@' for continuing the netboot (BOOTP flag from NVRAM)
'd' for continuing the netboot; enforce using BOOTP
'p' for continuing the netboot; enforce using BOOTP {{
'm' for continuing the netboot; enforce using NVRAM config
'R' to reboot now (you can always hit <Ctrl>-x to reboot)
any other key for this message code ** |
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
(booting from NFS): INIT=/boot/epics/iocCommon/user
...
,
...
followed
...
by
...
a
...
path
...
to
...
your
...
boot-up
...
script.
...
If
...
you're
...
using
...
the
...
AFS
...
filesystem,
...
which
...
is
...
common
...
at
...
SLAC,
...
then
...
your
...
path
...
will
...
typically
...
be
...
something
...
like
...
/u/
...
<two-chars>
...
/
...
<login
...
user-id>
...
/path-to-example
...
.
...
If
...
you
...
are
...
booting
...
out
...
of
...
the
...
shared
...
lcls
...
group
...
space,
...
the
...
boot-up
...
script
...
is
...
/boot/g/lcls/epics/iocCommon/"<your-node-name>"/st.cmd
...
.
...
See
...
the
...
example
...
below.
...
| Panel |
|---|
Changing NVRAM configuration NVRAM configuration updated |
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Panel |
|---|
Cexp>rtemsReboot() code h2. |
...
...
...
...
...
Those
...
few
...
steps
...
that
...
you
...
took
...
before
...
changing
...
the
...
NVRAM
...
are
...
all
...
that
...
are
...
needed
...
to
...
reboot
...
the
...
computer
...
again.
...
Now,
...
we
...
can
...
save
...
those
...
steps
...
so
...
the
...
processor
...
can
...
perform
...
them
...
automatically
...
each
...
time
...
it
...
restarts.
...
The
...
MOTLoad
...
firmware
...
in
...
Motorola
...
processors
...
makes
...
use
...
of
...
environment
...
variables
...
to
...
do
...
various
...
things.
...
These
...
variables
...
retain
...
their
...
values
...
between
...
restarts,
...
and
...
when
...
the
...
power
...
is
...
off.
...
They
...
are
...
stored
...
in
...
a
...
reserved
...
area
...
of
...
NVRAM.
...
In
...
particular,
...
the
...
environment
...
variable
...
named
...
mot-script-boot
...
contains
...
a
...
string
...
of
...
characters
...
that
...
are
...
interpreted
...
as
...
commands.
...
These
...
commands
...
are
...
executed
...
each
...
time
...
the
...
processor
...
starts.
...
The
...
gevEdit
...
command
...
is
...
used
...
to
...
create
...
or
...
change
...
an
...
environment
...
variable.
...
These
...
are
...
different
...
for
...
each
...
type
...
of
...
processor,
...
because
...
of
...
the
...
Flash
...
memory
...
address.
...
Type
...
the
...
following:
| Panel |
|---|
MVME6100> gevEdit mot-script-boot Update Global Environment Area of NVRAM (Y/N)? Y |
Confirm that the mot-script-boot variable is set correctly. You can type gevShow, and the contents of the environment variables will be printed. Reboot the processor:
| Panel |
|---|
MVME6100> {color:#ff00ff}{*}reset {*}{color}code |
You can power cycle the crate or if you have a "Cexp>" prompt, you can type rtemsReboot() and the processor will restart. It will boot up automatically, loading the rtems.exe file specified in the NVRAM. Change that filename to boot another file as your IOC development proceeds.
