6.2. Upgrading Bootloader Example
An example p session is shown below:
e Bootloader is upgraded using
rom.bin
. Transfer must always be in binary mode set by the
bin
command. Not using binary mode will corrupt the firmware and make the unit unusable. Notice
the syntax of the p
put
command. When
put
is entered without arguments, it first prompts for
the
Local file
which is the new bootloader, and second prompts for the
Remote file
which must
always be
rom.bin
, when upgrading the bootloader. To restate, the
Remote file
for upgrading the
bootloader must always be
rom.bin
. If
image.bin
is used instead it will overwrite the application.
e units application firmware will have to be recovered using the tp recovery method.
>ftp 10.0.2.42
Connected to 10.0.2.42.
220 NET+OS 6.3 FTP server ready.
User (10.0.2.42:(none)): GRouter
230 User GRouter logged in.
ftp> bin
200 Type set to I.
ftp> hash
Hash mark printing On ftp: (2048 bytes/hash mark) .
ftp> put
Local file GR4_4_12_048_C_eth_rom.bin
remote file rom.bin
200 PORT command Ok.
150 About to open data connection.
###########################
226 Transfer complete
ftp: 55444 bytes sent in 0.13Seconds 443.55Kbytes/sec.
ftp> bye
221 Goodbye.
At this point the GRouter will continue writing flash for a minute or two and then reboot on its
own. Once it has finished rebooting the status page will display the new bootloader version.
-86-
Summary of Contents for GRouter4
Page 25: ...Fig 2 8 Status Page 25...
Page 26: ...Fig 2 9 Status Page with Bridge and Twin Mode Enabled 26...
Page 42: ...Fig 2 19 Group Forwarding Table 42...
Page 57: ...Fig 3 4 Side A Channel List Page in Manual Mode 57...
Page 72: ...Fig 4 2 Initial LonMaker Drawing Fig 4 3 Router Channel Setup 72...
Page 78: ...Fig 4 10 New Virtual Functional Device Dialog Fig 4 11 Functional Blocks NV Shapes Dialog 78...
