SmartNode 4300 Series User Manual
Start-up with factory configuration
Step
1
RedBoot> fis load
2
RedBoot> go -s factory-config
Load a new application image (SmartWare) via TFTP
The following procedure downloads the application image (SmartWare) for the mainboard. See the note below
on how to download the respective CLI description file.
Step
1
RedBoot> ip_address - l local_ip_address
optional
[/mask_len]
2
RedBoot> ip_address -g gateway
optional
3
RedBoot> ping -h tftp-server_ip_address
optional
4
RedBoot> load -r -v -h host -b base_ad-
dress file_name
5
RedBoot> fis delete -n 1
6
RedBoot> fis create
7
RedBoot> fis list -l
Bootloader
Command
Command
4 • Getting Started with the SmartNode 4300 Series
Purpose
Copies the SmartWare application image from the
persistent memory (flash:) to the volatile memory
(RAM) from where it will be executed.
Starts the SmartWare application telling it to use
'factory-config' as startup configuration.
You can also start-up with any other configuration
available in the persistent memory (nvram:) by
providing its name instead of 'factory-config' .
Sets the IP address and subnet mask of the
Ethernet interface 0/0 which shall be used to
receive the new application image.
mask_len is the length of the network address
(or the number of 1's within the subnet
mask).
See Note below.
Sets the IP address of the default gateway.
Tests the connectivity to the TFTP server.
Downloads an application image into the vol-
atile memory (RAM) from where the Smart-
Node could directly execute it.
host: IP address of the TFTP server
base_address: memory location where to
store the application image. Use the default
address 0x1800100
file_name: path and name of the file on the
TFTP server. Note: use the image file that
contains the whole application, not the image
parts.
Deletes the first application image.
Reply with 'y' to the confirmation request.
Stores the downloaded application image to
the permanent memory (flash:).
Reply with 'y' to the confirmation request.
Checks whether the image has been suc-
cessfully stored, whether it is the desired
Release and Build, and whether it is valid.
Purpose
39