📣 Firmware Update Release:
Firmware Version v0.17 is now released! Please follow the link here or update via Cloudloop Device Manager.

Firmware Update Process

This page covers the process for local upgrade of Mini firmware, Mini bootloader, Iridium modem firmware and BLE module firmware.

Mini FW	Mini Bootloader	Iridium FW	BLE version	Example User Config	Example Factory file	Connect IoT app
Download Mini(H7) FW Version 0.17 - LATEST	Download Mini(H7) Bootloader Version 0.17 - LATEST	1.5.5 or higher	BLE Version 0.14 - LATEST	User Config File for v0.17	User Factory File for v0.17	Y
v0.15	Factory installed	1.5.5 or higher	BLE Version 0.14 - LATEST	User Config File for v0.15	User Factory File for v0.15	Y
v0.13	Factory installed	1.5.5 or higher	n/a	User config guide		N
v0.12	Factory installed	1.5.5 or higher	n/a	User config guide		N
v0.10	Factory installed	1.3.4 or lower	n/a	User config guide		N

The process to update the Iridium 9770 modem firmware locally is similar to the updating the product firmware.
If this update is required further instructions will be provided by the Ground Control team.

important

In order to avoid issues while updating firmware or supporting files please observe the following: -

1. While the update file transfer is taking place;

• Turn off position reporting.
• Turn off the NMEA stream.
• Avoid sending MO's.
• Avoid making configuration changes either by file update or using the BLE app.

2. File naming. The files are case-sensitive and will have to match the following naming exactly.

• RockREMOTE Mini Firmware = H7-App.new
• RockREMOTE Mini Bootloader = H7-Boot.new
• User Configuration = user.cfg
• BLE Firmware = BLE-App.new
• Iridium Firmware = IRID-App.new

2. If updating from a version PRIOR to v0.17 it is advised to use one of the local methods such as TFTP or serial.
3. Updating to v0.17 brings multiple benefits such as improved resilience and full integration with Cloudloop services.
4. File transfer sequence is IMPORTANT. Ensure that the BOOTLOADER, user.fac and FIRMWARE are updated in that order.
5. Ensure that both user.cfg and user.fac are updated as required. The .fac file provides a reset to factory default path.
   If a factory reset takes place, this file will replace the user.cfg file within the product.
6. If your device was released prior to the RockCONNECT IoT. Follow the local firmware update process to update the Bluetooth Firmware in the same manner, making sure that the file is named "BLE-App.new" - file can be downloaded from the table above.
7. Product shipped after 7th April 2025 will have Iridium firmware version 1.5.5 or higher. These products MUST NOT have the RR Mini firmware downgraded lower than V0.12.
8. The User Configuration will be retained following an update - although it is recommended to check the new user.cfg for any feature additions.
9. Firmware V0.10 and earlier will not gain an Iridium connection with Iridium firmware versions higher than 1.3.4.
10. It is recommended to use a JSON editor when changing the file as invalid JSON will revert to the default User Configuration file with no error

Release Notes:

See Previous Release note here

v0.17

Downloads available in the table above.

Android RockCONNECT IoT App
iOS RockCONNECT IoT App

New Features:

• Ability to upgrade the Bootloader Firmware locally via Kermit, TFTP and USB-C.
• Ability to upgrade the Bootloader Firmware remotely via Cloudloop using CDM. (CDM will guide you through the 3 stage process required for 17.1)
• Option to select and stream individual GNSS sentences via NMEA now available in user configuration. (NOTE: After upgrade users will now need to update the config to continue NMEA streaming)
• BLE idle disconnection timeout is now configurable
• Reset cause is now reported on Stats page and in-App by both Application and Bootloader
• Position reporting intervals now align to the 'clock'. e.g. every 10mins will be 1200, 1210, 1220 etc.

Bug Fixes:

• Resolved: Rare occurances internal flash file corruption which resulted in firmware or config changes not having effect. SEE NOTE BELOW
• Resolved interruption to MO messaging which resulted in a stalled queue
• Resolved SNTP bugs
• Resolved NMEA forwarding bugs
• Resolved Bootloader bugs - Bootloader update required.
• Resolved instability occurring after a soft-reboot either user or application triggered
• Resolved invalid GNSS COG value
• Resolved Location Reports bugs
• All sections of the User Configuration file can now be updated dynamically without requiring a reboot

Known Bugs:

• If the position report interval is changed, the setting will only take effect after the next report at the previously set interval. Rebooting will allow the change to take effect immediately.

An Ethernet connection is required directly to the product for the TFTP update and a Serial connection is required for the Kermit update.

The User Configuration will be retained following an update - although it is recommended to check the new user.cfg for any additions.

Local update via the LAN - Windows

Local Update - Windows

Firmware updates are distributed in files with .new suffix and can be updated as follows.

1. Set your PC's static IP to a value in the same range as the RockREMOTE Mini or skip to Step 2 if using DHCP.
   • This can be done from the command line with:
     • netsh interface ipv4 set address name="Ethernet" static 192.168.250.10 255.255.255.0 192.168.250.1
     • Or by going to Control Panel -> Network and Internet -> Network and Sharing Centre -> Change adapter settings -> Your adapter -> Properties -> ~IPv4

note

Ethernet is used as an example here. You will need to replace this with the adaptor number you are using.

If you monitor the network connections when you plug in the RockREMOTE Mini's ethernet you will see the name appear.

2. Go to: Control Panel –> Programs –> Turn Windows features on or off and Scroll down to TFTP and select it.
3. You can then use the TFTP client to copy new image over Ethernet. NOTE: -i option for octet transfer

note

When updating firmware the supplied 'user.cfg' file should also be loaded - see instructions and downloads below.

In addition, the command tftp -i 192.168.250.1 put "<path\filename>" user.fac will create a user factory file which is used when factory reset is performed.

important

The downloaded firmware file must be renamed 'H7-App.new' (case-sensitive)

4. Windows command line tftp -i 192.168.250.1 put "<path\filename.new" H7-App.new
   e.g: tftp -i 192.168.250.1 PUT "C:\Users\Major Tom\Documents\H7-App-v0.3.new" H7-App.new
5. LED blinks between BLUE-GREEN and LIGHT BLUE during the TFTP transfer
6. When TFTP reports completion with correct size against our published value the file transfer is complete.
7. Power cycle the unit. Restart after update takes about 30s The LED is red whilst the FLASH is erasing and flashes RED/GREEN for about half a second whilst the new image is programmed.
8. Then continues with normal start - GREEN until modem starts, then LIGHT BLUE.

User config Update - Windows

1. User config load is tftp -i 192.168.250.1 put "<path\filename>" user.cfg
2. To get the current config out use tftp -i 192.168.250.1 get user.cfg "<path\filename>"
   For example: tftp -i 192.168.250.1 get user.cfg "C:\Users\Major Tom\Documents\user.cfg"
3. LED blinks between BLUE-GREEN and LIGHT BLUE during the TFTP transfer
4. Reboot the unit

Local update via the LAN - Linux

Local Update - Linux/IoS

1. Install a TFTP client: sudo apt install tftp (Not required for IoS as tftp is natively installed)
2. Static the IP of the network interface the RR-Mini is connected to, eg if connected to "eth0" use sudo ifconfig eth0 192.168.250.10
3. Launch the TFTP client by running the command tftp. Hit the enter key twice to initialise the prompt.
4. Once TFTP is running it will issue the prompt "tftp>" type the following commands, one by one to complete the transfer:
5. connect 192.168.250.1 (makes the connection with the host)
6. binary (Sets mode to binary)

important

The downloaded firmware file must be renamed 'H7-App.new' (case-sensitive)

7. put <path>H7-App-X-Y-Z.new H7-App.new (Initiates file transfer)
8. After transfer power cycle the unit. Restart after update takes about 30s The LED is red whilst the FLASH is erasing and flashes RED/GREEN for about half a second whilst the new image is programmed.

User config Update - Linux/IoS

1. User config load is put <path><new-config> user.cfg (Initiates file transfer) - Reboot the unit for the change to take effect
2. To get the current config out use get user.cfg <uploaded-file-name> (Initiates file transfer)

Example user.cfg

Refer to the User Configuration Page.

warning

If the firmware or config update fails for any reason:

• Disconnect the power from the device, wait 1 minute and reconnect the power.
• The Mini will restart using the original firmware/config version, you can then attempt to update the firmware/config again following the process above.

Firmware update via Serial Port

important

• In order to minimise the risk of corruption during firmware updates or downgrades ALWAYS use a baud rate of 57600 or less.
• The downloaded firmware file must be renamed H7-App.new (case-sensitive)
• In order to avoid potential issues it is IMPORTANT that the BOOTLOADER, user.fac and FIRMWARE are updated in that order.

The PRO and Mini products support various different functions via the serial interface (e.g. AT command set, FW update via Kermit and NMEA streaming). Each function should be used independently. Attempting to use 2 or more functions simultaneously can result in unexpected behaviour. For example, NMEA streaming should always be turned off before using AT commands or serial FW update.

Serial port update using Windows

Windows

Requires connection to a terminal application that supports Kermit file transfer. Example below uses Teraterm for Windows

• Serial port settings are 115200,n,8,1

• Terminal settings are:

1. Put the RockREMOTE Mini or RockBLOCK Pro in "Kermit Receive" Mode:

Command:

AT+CTOK

Expected response:

+CTOK: <token number>

OK

Note that the token number will only be valid for 30s

Command:

AT+CDFU=<insert token number>

Expected Response:

+CDFU: READY

2. Click File > Transfer > Kermit > Send ... Select the firmware file in the dialog.

important

The downloaded firmware file must be renamed 'H7-App.new' (case-sensitive)

3. Progress bar will reach 100% and the dialogue will close.
   • The RockREMOTE Mini or RockBLOCK Pro will automatically reboot on completion.

Serial port update using Linux

Linux

1. Save Kermit script to "fw-update.kerm"

#!/usr/bin/kermit +
if < \v(argc) 4 {
    echo "Usage: \%0 <serial port> <baudrate> <*.new app file>"
    echo "eg. \%0 /dev/ttyUSB0 115200 H7-App.new"
    exit 1
}
assign SERIAL_PORT \%1
assign SERIAL_BAUD \%2
assign FILENAME \%3
# Set the communication parameters
set line \m(SERIAL_PORT)
set speed \m(SERIAL_BAUD)
set flow none
set parity none
set stop-bits 1
set carrier-watch off
set file names literal
set window-size 1
set receive packet-length 94
send /AS-NAME:H7-App.new /BINARY \m(FILENAME)
# Uncomment this for stats to be displayed at the end
# statistics /VERBOSE
close
exit

2. Put the RockREMOTE Mini or RockBLOCK Pro in "Kermit Receive" Mode:

Command:

AT+CTOK

Expected response:

+CTOK: <token number>

OK

Note that the token number will only be valid for 30s

Command:

AT+CDFU=<insert token number>

Expected Response:

+CDFU: READY

3. Run the script by:

./fw-update.kerm /dev/ttyUSB0 115200 /<filepath>/<Firmware File>

4. Progress bar will reach 100% and the dialogue will close.
   • The RockREMOTE Mini or RockBLOCK Pro will automatically reboot on completion.

note

Replace ttyUSB0 with your correct serial device name (run dmesg | grep tty to find)
Also replace baudrate and other parameters if required

Serial port update using Linux Mac OS X

Mac OS X

MacOS, including older versions of C-Kermit (v9) running on Linux require the following:

kermit -l /dev/tty.usbserial-FT4WLSEC -b 115200 -i -C "set carrier-watch off, set flow none, set parity none, set stop-bits 1, set file names literal, set window-size 1, set receive packet-length 94, send /AS-NAME:H7-App.new /BINARY H7-App-Test-0-0-0.new, close, exit"

note

Replace /dev/tty.usbserial-FT4WLSEC with your correct serial device name (run dmesg | grep tty to find)
Also replace baudrate and other parameters if required
Also replace H7-App-Test-0-0-0.new with the correct name of the file

Firmware and Config update Over the Air via Cloudloop Device Manager

Firmware and Config update Over the Air via Cloudloop Device Manager

Cloudloop Device Manager (CDM) allows remote management and troubleshooting of devices and uses Iridium Messaging Transport (IMT)

warning

Any use of Cloudloop Device Manager will result in data usage

User Configuration update over IMT and CDM

User Configuration update over IMT and CDM

Optimising for lowest possible satellite data usage, the user configuration file is split by sections in CDM.

Each section can be individually requested, and updated.

Firmware update over IMT and CDM

CDM allows the upgrade and downgrade of Firmware with the option to check the current version, see the release notes of new versions and the estimated size of the new version.

Note that from v0.17 each FW update is likely to also require an update to the Bootloader. The Bootloader MUST be downloaded to the unit BEFORE the FW update, therefore when the FW update is requested from CDM it will begin by transferring the Bootloader, this will trigger a re-boot once complete, after this re-boot the remaining files including the new FW will be transferred, resulting in a final re-boot when all files will be installed simultaneously.

User Configuration via Bluetooth App

A subset of RockREMOTE Mini functionality can be configured and managed via the RockCONNECT IoT (From FW v0.15)