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

Firmware Update Process

This page describes the process for updating the RB-Pro's Application Firmware, Bootloader Firmware, Iridium Transceiver Firmware, and BLE module Firmware, either locally or via over-the-air updates.

RB-Pro FW	RB-Pro Bootloader	Iridium Firmware	BLE Firmware	Example User Config	Example Factory file	RockCONNECT IoT app
Download RB-Pro(L4) FW Version 0.18 - LATEST	Download RB-Pro(L4) Bootloader Version 0.18	1.5.5 or higher	BLE Version 0.14	User Config File for v0.18	User Factory File for v0.18	Y
Download RB-Pro(L4) FW Version 0.17 - LATEST	Download RB-Pro(L4) Bootloader Version 0.17	1.5.5 or higher	BLE Version 0.14	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

The process to update the Iridium 9704 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 naming exactly.
3. If updating from a version PRIOR to v0.17 it is advised to use one of the local methods such as transfer via MSD or serial.
4. 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.
5. If you are upgrading to V0.15 and above, you will need to follow the local firmware update process to be able to use our new RockCONNECT IoT App. Follow the local firmware update process to update the Bluetooth Firmware, making sure that the file is named "BLE-App.new" - file can be downloaded from the table above.
6. 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.
7. The User Configuration will be retained following an update - although it is recommended to check the new user.cfg for any feature additions.
8. Firmware V0.10 and earlier will not gain an Iridium connection with Iridium firmware versions higher than 1.3.4.

Firmware Release Notes

v0.18

Download latest Firmware bundle here

tip

Individual Firmware files can be found in the table above

New Features

• Ability to toggle (Enable/Disable) the Startup Events to Cloudloop Device Manager in User Configuration.
• Internal temperature and memory usage now available via the REST API.
• Ability to configure Serial baudrate settings for NMEA streaming in Cloudloop Device Manager.

New Features – RockBLOCK Pro APNT

• Improvements to APNT settings to increase position accuracy in DYNAMIC mode.
• Updated Kalman filter parameters for improved performance under the DRIVING preset.

Bug Fixes

• CRBT functionality restored matching documentation
• Queue handling enhancements for improved message stability.
• Internal BLE improvements.
• Internal Kalman filter optimisations.
• APNT now waits longer to acquire a position under poor signal conditions.

See Previous Release notes here

---

File Naming

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

• RockBLOCK Pro Firmware = L4-App.new
• RockBLOCK Pro Bootloader = L4-Boot.new

note

The Bootloader Firmware file must always be loaded with a manifest.txt file when updating via MSD

• RockBLOCK Pro manifest = manifest.txt
• Example RockBLOCK Pro APNT License Key = APNT-Key.txt
• User Configuration = user.cfg
• BLE Firmware = BLE-App.new
• Iridium Firmware = IRID-App.new

important

It is recommended to use a JSON editor when changing the user.cfg file as invalid JSON will revert to the default User Configuration file with no error

---

Mass Storage Drive (MSD) via USB Type-C

The RockBLOCK Pro will enumerate as a mass storage drive under the name of "RockBLOCK P" once connected to an end device via USB Type-C.

This can currently serve to upload a Firmware or User Configuration file to, and after a reboot (or a power-cycle by removing the USB-C and re-plugging after 10 seconds) the RockBLOCK Pro will find the new file and update to it.

tip

You can drag and drop - or copy and paste the file to the "RockBLOCK P" drive

---

Local Firmware update via the Serial Port

A Serial connection is required for the Kermit update.

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 L4-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.

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.

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 'L4-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 L4-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:L4-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:L4-App.new /BINARY L4-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 L4-App-Test-0-0-0.new with the correct name of the file

---

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

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 RockBLOCK PRO functionality can be configured and managed via the RockCONNECT IoT (From FW v0.15)