Skip to main content

RAK811 Module Quick Start Guide

This guide covers the following topics:

Prerequisites

What do you need?

Before going through the step in the installation guide of the RAK811 WisDuo LPWAN Module, make sure to prepare the necessary items listed below:

Hardware Tools

  1. RAK811 WisDuo LPWAN Module
  2. Windows PC
  3. USB to UART TTL adapter

Software Tools

  1. RAK Serial Port Tool
  2. RAK811 Firmware
  3. RAK Device Firmware Upgrade (DFU) Tool

List of Acronyms

AcronymDefinition
DFUDevice Firmware Upgrade
JTAGJoint Test Action Group
LoRaLong Range
OTAAOver-The-Air-Activation
ABPActivation-By-Personalization (ABP)
TTNThe Things Network
TTSThe Things Stack

Product Configuration

Interfacing with RAK811

RAK811 module can be configured using AT commands via the UART interface. You need a USB to UART TTL adapter to connect the RAK811 to the PC's USB port and a serial terminal tool. It is highly recommended to use RAK Serial Port Tool so you can easily send AT commands and view the replies from the console output.

Connect to the RAK811

  1. Connect the RAK811 to the serial port of a general-purpose computer (USB port) using a USB to UART TTL adapter, as shown in Figure 1.
Figure 8372: RAK811 Module Connection
  1. Any serial communication tool can be used; but, it is recommended to use the RAK Serial Port Tool.

  2. Configure the serial communication tool by selecting the proper port detected by the computer and configure the link as follows:

  • Baud Rate: 115200 baud
  • Data Bits: 8 bits
  • Stop Bits: 1 stop bit
  • Parity: NONE
  1. The RAK811 console output can be read in the RAK Serial Port Tool, as shown in Figure 2.
Figure 8373: RAK Serial Port Tool Connected to RAK811 module

Configuring RAK811

To connect the RAK811 module to a LoRa P2P connection or a LoRaWAN network, the module must be configured and LoRa parameters must be set by sending AT commands. Connect the RAK811 module to the computer as described in the previous section. Using the serial communication tool, for example, the RAK Serial Port Tool, it is possible to send commands to the RAK811. For example, sending the at+set_config=device:restart and at+version commands will display the current firmware version as shown in Figure 3. For more supported commands, refer to the AT Commands for RAK811.

Figure 8374: AT Command response

Connecting to The Things Stack (TTN V3)

This section will show how to connect the RAK811 module to The Things Stack (TTN V3) platform.

Figure 8375: The Things Stack diagram

As shown in Figure 4, The Things Stack is an open-source LoRaWAN Network Server suitable for global, geo-distributed public and private deployments as well as for small, local networks. The architecture follows the LoRaWAN Network Reference Model for standards compliancy and interoperability. This project is actively maintained by The Things Industries.

LoRaWAN is a protocol for low-power wide-area networks. It allows for large-scale Internet of Things deployments where low-powered devices efficiently communicate with Internet-connected applications over long-range wireless connections.

The RAK811 module can be part of this ecosystem as a device, and the objective of this section is to demonstrate how simple it is to send data to The Things Stack using the LoRaWAN protocol. To achieve this, the RAK811 module must be located inside the coverage of a LoRaWAN gateway connected to The Things Stack server.

Registration to TTN and Creating LoRaWAN Applications

  1. The first step is to go to The Things Network platform and select a cluster, as shown in Figure 5. The Things Industries adds more clusters from time to time so select the one closes to your location. In this guide, Europe 1 is selected.
Figure 8376: Selecting Cluster in TTN V3

You can use the same login credentials on the TTN V2 if you have one. If you have no account yet, you need to create one.

  1. To register as a new user to TTN, click on Login with The Things ID then select register on the next page, as shown in Figure 6 and Figure 7.
Figure 8377: Login using TTN account
Figure 8378: Registration of new account
  1. You should now be on the step of creating your TTN account. Fill in all the necessary details and activate your account.

  2. After creating an account, you should log in on the platform using your username/email and password then click Submit, as shown in Figure 8.

Figure 8379: Logging in to TTN platform
  1. You need to click Authorize to proceed.
Figure 8380: Authorization to TTN
  1. Now that you are logged in to the platform, the next step is to create an application. Click Create an application.
Figure 8381: Creating TTN application for your LoRaWAN devices
  1. To have an application registered, input first the specific details and necessary information about your application then click Create application.
Figure 8382: Details of the TTN application

If you have no error on the previous step, you should now be on the application console page. The next step is to add end-devices to your The Things Stack application. LoRaWAN specifications enforce that each end device has to be personalized and activated. There are two options in registering devices depending on the activation mode selected. Activation can be done either via Over-The-Air-Activation (OTAA) or Activation-By-Personalization (ABP).

NOTE

Once you have the application in The Things Stack (TTN V3), you need to ensure that you are in coverage of a LoRaWAN gateway that is registered to The Things Stack (TTN V3) as well. Without the coverage of that LoRaWAN gateway, you cannot activate any device that you will register in your application.

RAKwireless has LoRaWAN gateways that you can connect to The Things Stack (TTN V3) if no LoRaWAN gateway coverage is available in your location.

The Things Stack OTAA Device Registration

  1. Go to your application console to be able to register a device. To start adding an OTAA end device, you need to click + Add end device, as shown in Figure 12.
Figure 8383: Add end device
  1. To register the module, click first Manually then configure the activation method by selecting Over the air activation (OTAA) and compatible LoRaWAN version then click Start button, as shown in Figure 13 and Figure 14.
Figure 8384: Manually register device to The Things Stack
Figure 8385: Device activation configuration
  1. Input a unique End device ID and EUIs (DevEUI and AppEUI), as shown in Figure 15. Check if your module has a DevEUI on sticker or QR that you can scan then use this as the device unique DevEUI.

Optionally, you can add a more descriptive End device name and End device description about your device.

  1. After putting all the details, click Network layer settings to proceed to the next step.
NOTE

It is advisable to use a meaningful End device ID, End device name, and End device description that will match your device purpose. The End device ID rak-device is for illustration purposes only.

Figure 8386: OTAA Device Information
  1. Next step is to set up Frequency plan, compatible Regional Parameter version, and LoRaWAN class supported. Then you can click Join settings.
Figure 8387: OTAA Configuration
  1. The last step in the registration of a new OTAA end-device is the configuration of the AppKey. To get the AppKey, you must click the generate button. Then click Add end device to finish your new device registration.
Figure 8388: OTAA AppKey generation and device registration
  1. You should now be able to see the device on The Things Stack console after you fully register your device, as shown in Figure 18.
NOTE

The AppEUI, DevEUI, and AppKey are the parameters that you will need to activate your LoRaWAN end device via OTAA. The AppKey is hidden by default for security reasons, but you can easily show it by clicking the show button. You can also copy the parameters quickly using the copy button.

The three OTAA parameters on The Things Stack device console are MSB by default.

These parameters are always accessible on the device console page, as shown in Figure 18.

Figure 8389: OTAA device successfully registered to The Things Stack

RAK811 OTAA Configuration for The Things Stack

The RAK811 module supports a series of AT commands to configure its internal parameters and control the functionalities of the module. To set up the RAK811 module to join The Things Stack using OTAA, start by connecting the RAK811 module to the Computer (see Figure 1) and open the RAK Serial Port Tool. Wait for the communication to start. It is recommended to test the serial communication and verify the current configuration by sending either of these two AT commands:

at+set_config=device:restart
at+version
Figure 8390: AT Command response

As an example, these are the list of the parameters you need to configure in RAK811:

  • LoRa join mode: OTAA
  • LoRa class: Class A
  • LoRa region: EU868
  • Device EUI: 1133557799224466
  • Application EUI: 1000000000000009
  • Application Key: 04FA4E626EF5CF227C969601176275C2
  1. Set the LoRa join mode to OTAA.
at+set_config=lora:join_mode:0
  1. Set the LoRa class to Class A.
at+set_config=lora:class:0
  1. Set the frequency/region to EU868.
at+set_config=lora:region:EU868
  1. Set the Device EUI.
at+set_config=lora:dev_eui:1133557799224466
  1. Set the Application EUI.
NOTE

All zero value Application EUI at+set_config=lora:app_eui:0000000000000000 is not supported and will return error.

at+set_config=lora:app_eui:1000000000000009
  1. Set the Application Key.
at+set_config=lora:app_key:04FA4E626EF5CF227C969601176275C2
Figure 8391: Configuring LoRa Parameters
NOTE

After configuring all the parameters, you need to reset your RAK811 Module to save the the parameters.

  1. After resetting, join in OTAA mode.
at+join

After 5 or 6 seconds, if the request is successfully received by a LoRa gateway, then you should see the messages, shown in Figure 21.

  1. Try to send a message from the RAK811 module.
at+send=lora:2:1234567890
Figure 8392: OTAA Test Sample Data Sent via RAK Serial Port Tool

You can see the data sent by the RAK811 module on The Things Stack platform, as shown in Figure 22.

Figure 8393: OTAA Test Sample Data Sent Viewed in The Things Stack

The Things Stack ABP Device Registration

  1. To register an ABP device, you need to go to your application console and select the application where you want your device to be added. Then click + Add end device, as shown in Figure 23.
Figure 8394: Add end device
  1. To register the module, click first Manually then configure the activation method by selecting Activation by personalization (ABP), compatible LoRaWAN version, and click Start button, as shown in Figure 24 and** Figure 25**.
Figure 8395: Add end device
Figure 8396: Manually register device to The Things Stack
  1. At this step, input a unique End device ID and DevEUI, as shown in Figure 26. Check if your module has a DevEUI on sticker or QR that you can scan then use this as the device unique DevEUI.

Optionally, you can add a more descriptive End device name and End device description about your device.

  1. After putting all the details, click Network layer settings to proceed to the next step.
NOTE

It is advisable to use a meaningful End device ID, End device name, and End device description that will match your device purpose. The End device ID rak-device-abp is for illustration purposes only.

Figure 8397: Device Information
  1. Next step is to set up Frequency plan, compatible Regional Parameter version, and LoRaWAN class supported. In an ABP device, you also need to generate Device Address and NwkSKey (Network Session Keys). Then you can click Application layers settings.
Figure 8398: ABP Configuration in The Things Stack
  1. The last step in the registration of a new ABP end-device is the configuration of the AppSKey. To get the AppSKey, you must click the generate button, then click Add end device to finish your new device registration.
Figure 8399: ABP Configuration in The Things Stack
  1. You should now be able to see the device on The Things Stack console after you fully register your device, as shown in Figure 29.
Figure 8400: RAK811 registered at The Things Stack

RAK811 ABP Configuration for The Things Stack

To set up the RAK811 module to join The Things Stack using ABP, start by connecting the RAK811 module to the Computer (see Figure 1) and open the RAK Serial Port Tool. It is recommended to test the serial communication by sending either of these two AT commands:

at+set_config=device:restart
at+version
Figure 8401: AT Command response

As an example, these are the list of the parameters you need to configure in RAK811:

  • LoRa join mode: ABP
  • LoRa class: Class A
  • LoRa region: EU868
  • Device address: 260BDE80
  • Network Session Key: 433C7A924F7F6947778FE821525F183A
  • Application Session Key: A585653A949C2B2D44B55E99E94CB533
  1. Set the LoRa join mode to ABP.
at+set_config=lora:join_mode:1
  1. Set the LoRa class to Class A.
at+set_config=lora:class:0
  1. Set the frequency/region to EU868.
at+set_config=lora:region:EU868
  1. Set the Device Address.
at+set_config=lora:dev_addr:260BDE80
  1. Set the LoRa Network Session Key.
at+set_config=lora:nwks_key:433C7A924F7F6947778FE821525F183A
  1. Set the LoRa Application Session Key.
at+set_config=lora:apps_key:A585653A949C2B2D44B55E99E94CB533
Figure 8402: AT Command for ABP LoRa parameters via RAK Serial Port Tool
NOTE

After configuring all the parameters, you need to reset the RAK811 Module to save the parameters.

  1. After resetting, join in ABP mode.
at+join
NOTE

By using the ABP mode in LoRaWAN, it doesn’t require to join a network before sending a LoRaWAN package. But to keep the consistency of internal states of the firmware of the RAK811 module, it is still required to send the at+join command in the ABP mode. This time, the firmware should reply almost immediately with an “OK”.

  1. Try to send data from the RAK811 to The Things Network in ABP mode.
at+send=lora:2:1234567890
Figure 8403: ABP Test Sample Data Sent via RAK Serial Port Tool

You can see the data sent by the RAK811 module on The Things Stack device console Live data section and the Last seen info should be few seconds ago.

Figure 8404: OTAA Test Sample Data Sent Viewed in The Things Stack

Connecting with ChirpStack

In this section, it shows how to connect the RAK811 module to the ChirpStack platform.

Figure 8405: RAK811 Module in the Context of the ChirpStack Platform

The ChirpStack or previously known as the LoRaServer project provides open-source components for building LoRaWAN networks. Like the case of The Things Stack, the RAK811 module is located in the periphery and will transmit the data to the backend servers through a LoRa gateway. Learn more about ChirpStack.

NOTE

It is assumed that you are using RAK Gateway and its built-in ChirpStack or RAK cloud testing ChirpStack. Also, the gateway with the ChirpStack must be configured successfully. For further information, check the RAK documents for more details.

  • In summary, these are the requirements:

    1. Have ChirpStack online gateway, the frequency band of the nodes should be consistent with the frequency band of the gateway in use.
    2. The RAK Serial Port Tool provided by RAK
    3. RAK811 module
NOTE

The frequency band used in the demonstration is EU868. Use a high-frequency version of RAK811. The product number should be “RAK811 (H)”.

Before you start, you must choose which mode you are going to use, whether in OTAA or ABP mode, to register the device to the network server.

Sign up and login

Login to the ChirpStack server using your account and password.

Create a new Application

Go to the Application section, as shown in Figure 35.

Figure 8406: Application Section

By default, you should create a new application, although you can reuse the existing ones. For this setup, create a new Application by clicking on the “CREATE” button, and filling the required parameters, as shown in Figure 36 and Figure 37.

Figure 8407: Creating a New Application
  • For this setup, create an Application named “rak_node_test”.

ChirpStack LoraServer supports multiple system configurations, with only one by default.

  • Service profile: Field is to select the system profile.
  • Payload codec: It is the parsing method for selecting load data such as parsing LPP format data.
Figure 8408: Filling Parameters of an Application
Register a New Device
  1. Choose the Application created in the previous step, then select the DEVICES tab as shown in Figures 38 and 39.

  2. Once done, click “+ CREATE”.

Figure 8409: List of Applications Created
Figure 8410: Device Tab of an Application
  1. Once inside of the DEVICE tab, create a new device (LoRaWAN node) by clicking on the “+ CREATE” button.
Figure 8411: Add a New Device
Figure 8412: Chirpstack Adding Node into the RAK811 Module
  1. Once the node is created, fill in the necessary data. You can generate a Device EUI automatically by clicking the following icon, or you can write a correct Device EUI in the edit box.

Fill in the parameters requested:

  • Device name and Device description: These are descriptive texts about your device.

  • Device EUI: This interface allows you to generate a Device EUI automatically by clicking the icon highlighted in red in Figure 42. You can also add a specific Device EUI directly in the form.

  • Device Profile:

    • If you want to join in OTAA mode, select “DeviceProfile_OTAA”.
    • If you want to join in ABP mode, select “DeviceProfile_ABP”.
Figure 8413: Generate a New Device EUI

LoRaWAN Join Mode

In LoRaWAN, there are two ways a node can connect itself to the LoRaWAN network. This is referred to as Join Mode. LoRaWAN allows the OTAA mode and the ABP mode. In this section, the configuration process of these two modes, both on the platform side and the node side will be explained.

OTAA Mode
Configure the OTAA Mode on the Platform
  1. If you have selected “DeviceProfile_OTAA” as shown in Figure 43, then after the device is created, an Application Key must be also created for this device.
Figure 8414: Chirpstack OTAA Activation
  1. A previously created Application Key can be entered here, or a new one can be generated automatically by clicking the icon highlighted in red in Figure 44:
Figure 8415: Chirpstack OTAA Set Application Keys
  1. Once the Application Key is added to the form, the process can be finalized by clicking on the “SET DEVICE-KEYS” button.
  • As shown in Figure 45, a new device should be listed in the DEVICES tab. The most important parameters, such as the Device EUI are shown in the summary.
Figure 8416: Chirpstack OTAA List of Device in the Device Tab
  1. To end the process, it is a good practice to review that the Application Key is properly associated with this device. The Application Key can be verified in the KEYS(OTAA) tab, as shown in Figure 46.
Figure 8417: Application Key Associated with the New Device
NOTE

Standard OTAA mode requires the Device EUI, Application Key, and Application EUI, but in the ChirpStack’s implementation, only the Device EUI and the Application Key are mandatory. The Application EUI is not required and not recorded in the Application tab. Nevertheless, the Application EUI is a mandatory parameter in the RAK811 module’s firmware. In order to resolve this mismatch, you can reuse the Device EUI as the Application EUI during the configuration on the side of the node.

Configure the OTAA mode on the RAK811

The RAK811 module supports a series of AT commands to configure its internal parameters and control the functionalities of the module.

To set up the RAK811 module to join ChirpStack using OTAA, start by connecting the RAK811 module to the Computer (see Figure 1) and open the RAK Serial Port Tool. Wait for the communication to start. It is recommended to test the serial communication by sending either of these two AT commands:

at+set_config=device:restart
at+version
Figure 8418: at+version command response

As an example, these are the list of the parameters you need to configure in RAK811:

  • LoRa join mode: OTAA
  • LoRa class: Class A
  • LoRa region: EU868
  • Device EUI: 5e9d1e0857cf25f1
  • Application EUI: 5e9d1e0857cf25f1
  • Application Key: f921d50cd7d02ee3c5e6142154f274b2
  1. Set the LoRa join mode to OTAA.
at+set_config=lora:join_mode:0
  1. Set the LoRa class to Class A.
at+set_config=lora:class:0
  1. Set the frequency/region to EU868.
at+set_config=lora:region:EU868
  1. Set the Device EUI.
at+set_config=lora:dev_eui:5e9d1e0857cf25f1
  1. Set the Application EUI.
at+set_config=lora:app_eui:5e9d1e0857cf25f1
NOTE

Remember, the Application EUI parameter was not required in the ChirpStack platform; therefore, it is possible to use the same id as the Device EUI. Otherwise, the firmware will complain.

  1. Set the Application Key.
  • Get the Application Key from the ChirpStack console.
at+set_config=lora:app_key:f921d50cd7d02ee3c5e6142154f274b2
Figure 8419: Chirpstack OTAA configuration via RAK Serial Port Tool
NOTE

After configuring all parameters, you need to reset the RAK811 Module to save the parameters.

  1. After resetting, start to join.
at+join
Figure 8420: Chirpstack OTAA configuration via RAK Serial Port Tool
  1. You can then see the JoinRequest and JoinAccept on the ChirpStack page.
Figure 8421: Checking LoRaWAN Joint Request in Chirpstack OTAA Console
  1. Try to send data from RAK811 Module to ChirpStack.
at+send=lora:2:1234567890
Figure 8422: Send a LoRaWAN Message via RAK Serial Port Tool
  • On the ChirpStack platform, you should also see the messages in the LORAWAN FRAMES tab as shown in Figure 52. By convention, messages sent from nodes to gateways are considered as Uplinks while messages sent by gateways to nodes are considered as Downlinks.
Figure 8423: Chirpstack Data Received Preview

This concludes the exercise to send data in the OTAA mode.

ABP Mode
Configure the ABP Mode on the Platform

During the registration of a new device, if you select “DeviceProfile_ABP”, as shown in Figure 53, then the ChirpStack platform will assume that this device will join the LoRaWAN network using the ABP mode.

NOTE

Check “Disable counting frame verification”. During the test, when the module is restarted, the frame counting number will be also be restarted from zero. This would cause a synchronization problem with the ChirpStack server treating it as a replay attack. For the testing purpose, it is safe to disable this feature, but remember to activate it in a production environment.

Figure 8424: ChirpStack Console, Configuring a Device

After selecting the ABP mode, the following parameters appear in the Activation tab:

  1. Then, you can see that there are some parameters for ABP in the “ACTIVATION” item:
  • Device address
  • Network Session Key
  • Application Session Key
Figure 8425: Chirpstack ABP Activation Parameters Needed
  • The parameters can be generated as random numbers by the platform or can be set with user values. Once these parameters are filled in properly, the process is completed by clicking on the “ACTIVATE DEVICE” button.
Configure the ABP mode on the RAK811

In the following steps, you will configure the RAK811 module to work in the ABP mode. To set up the RAK811 module to join ChirpStack using ABP, start by connecting the RAK811 module to the Computer (see Figure 1) and open the RAK Serial Port Tool. Wait for the communication to start. It is recommended to test the serial communication by sending either of these two AT commands:

at+set_config=device:restart
at+version
Figure 8426: at+version command response

As an example, these are the list of the parameters you need to configure in RAK811:

  • LoRa join mode: ABP
  • LoRa class: Class A
  • LoRa region: EU868
  • Device address: 26011af9
  • Network Session Key: c280cb8d1df688bc18601a97025c5488
  • Application Session Key: 4d42ec5caf97f03d833cdaf5003f69e1
  1. Set LoRa join mode to ABP.
at+set_config=lora:join_mode:1
  1. Set LoRa class to Class A.
at+set_config=lora:class:0
  1. Set the frequency/region to EU868.
at+set_config=lora:region:EU868
  1. Set the Device Address.
at+set_config=lora:dev_addr:26011af9
  1. Set the Network Session Key.
at+set_config=lora:nwks_key:c280cb8d1df688bc18601a97025c5488
  1. Set the Application Session Key.
at+set_config=lora:apps_key:4d42ec5caf97f03d833cdaf5003f69e1
Figure 8427: Chirpstack ABP Parameters Configuration via RAK Serial Port Tool
NOTE

After configuring all parameters, you need to reset the RAK811 Module to save the parameters.

  1. After resetting RAK811 Module, join in ABP mode.
at+join
NOTE

By using the ABP mode in the LoRaWAN protocol, it doesn’t require to join a network before sending the LoRaWAN package. But, to keep the consistency of internal states of the firmware of the RAK811 module, it is still required to send the at+join command in the ABP mode. This time, the firmware should reply almost immediately with an “OK”.

  1. Try to send data from RAK811 Module to ChirpStack.
at+send=lora:2:1234567890
Figure 8428: Chirpstack Sample Data Sent via RAK Serial Port Tool

LoRa P2P Mode

This section will show you how to set up and connect two RAK811 units to work in the LoRa P2P mode. You will be using EU868 as your frequency, although it is applicable also to other standard bands.

  1. Two RAK811 units shall be set to operate on EU868 frequency.

  2. The setup of the RAK811 units is done by connecting them with a general-purpose computer through the UART port. The setup of each RAK811 can be done separately, but testing the LoRa P2P mode will require having both units connected simultaneously to their respective UART port. This could be one computer with two USB ports or two computers with one USB port each.

  3. Set the RAK811 to work in LoRa P2P mode. Open the RAK Serial Port Tool and send the following command:

at+set_config=lora:work_mode:1
Figure 8429: P2P Initialization
  1. Then, configure LoRa P2P parameters for both of them.
at+set_config=lorap2p:XXX:Y:Z:A:B:C

For this example, the LoRa parameters are the following:

  • Link frequency: 869525000 Hz
  • Spreading factor: 7
  • Bandwidth: 125 kHz
  • Coding Rate: 4/5
  • Preamble Length: 5
  • Power: 5 dBm
NOTE

Refer to the Configuring Using AT Commands section to learn more about the definition of the parameters used.

Hence, it is translated into the following RAK811 AT command and sent to both units.

at+set_config=lorap2p:869525000:7:0:1:5:5
Figure 8430: Configuring P2P in both RAK811 Module
  1. Set the transmission mode of the module. Unit 1 is configured as the sender, and Unit 2 is set to the receiver by AT command.
at+set_config=lorap2p:transfer_mode:2

at+set_config=lorap2p:transfer_mode:1
Figure 8431: Setting Modes in both RAK811 Module
  1. Try sending a message from Unit 1 to Unit 2.
at+send=lorap2p:1234567890
Figure 8432: Message sent and received status in the two modules

Miscellaneous

Upgrading the Firmware

If you want to upgrade to the latest version firmware of the module, you can follow this section. The latest firmware can be found in the software section of RAK811 Datasheet.

NOTE

For RAK811 modules with firmware version V3.0.0.12 and below, you need to use the STM32CubeProgrammer to upgrade your firmware and upload the .hex file (not the .bin file) of the latest RAK811 firmware. The lower versions of the firmware have a different bootloader code and will not work on the RAK DFU Tool.

In the following sections, two (2) options for flashing new firmware in a RAK811 module are shown: Upgrade through DAPLink and Upgrade through UART1.

Firmware Upgrade Through DAPLink

Refer to the RAKDAP1 Flash and Debug Tool guide in the Accessories Category.

Firmware Upgrade Through UART1

Minimum Hardware and Software Requirements

Refer to the table for the minimum hardware and software required to perform the firmware upgrade using J-Link.

Hardware/SoftwareRequirement
ComputerA Windows/Ubuntu/Mac computer
Firmware FileBin firmware file downloaded from the website
OthersA USB to TTL module
Firmware Upgrade Procedure

Execute the following procedure to upgrade the firmware in Device Firmware Upgrade (DFU) mode through the UART1 interface:

  1. Download the latest application firmware of the RAK811 that can be found on the RAK811 Datasheet.

  2. Download the RAK Device Firmware Upgrade (DFU) Tool.

  3. Connect the RAK811 module with a computer through a USB to TTL. Refer to Figure 1.

  4. Open the Device Firmware Upgrade tool. Select the serial port and baud rate of the module and click the "Select Port" button.

Figure 8433: Device Firmware Upgrade Tool
  1. Select the application firmware file of the module with the suffix ".bin".
Figure 8434: Select Firmware
  1. Click the "Upgrade" button to upgrade the device. After the upgrade is complete, the RAK811 module will be ready to work with the new firmware.
Figure 8435: Firmware Upgrading
Figure 8436: Upgrade Successful