RAK5205 shows only ERROR: 3 messages in Serial Port Tool

Hi,

the world of IoT is interesting but pretty much unfamiliar to me, so I decided to get the RAK Lora Starter Kit to study the subject. I got the included gateway up and running in no time, but the included RAK 5205 node is causing me gray hairs. As I know nothing about circuit boards, I’m completely at a loss as what the problem is.

I’ve got the node connected to my PC by USB, but every command I send via the RAK Serial Port Tool only returns ERROR: 3. I also tried to flash the board as per instructions here, but the STM Cube Programmer can’t connect to the board either. Is the board busted or am I doing something wrong?

Sorry about the slightly unclear picture of the errors, as a forum newbie I was only allowed to attach one picture in post. :slight_smile:

Is this burning firmware? Do not press the restart button when you read the module information!
You try to burn the latest RAK5205 firmware for operation.

Thanks for the quick reply. :slight_smile: I don’t quite follow though, so could you please elaborate? :slight_smile:

First of all, what does the ERROR 3 mean, which I get when using the serial tool? It comes after connecting the node to the PC, starting the serial tool, opening the connection and sending any message to the board. Is there something I should do before sending messages to the board (install drivers, burn the firmware on it or something else), or is this due to some fault on the board itself? I didn’t find a clear cut startup guide for newbies. :slight_smile:

Secondly, I tried the firmware route after I didn’t find any information of the ERROR 3 message. The error shown in the STM Cube Programmer comes right after I press the Connect button on the program, so it’s not even at the burning stage yet. I haven’t been pressing the reset button on the node while STM Cube Program has been running.

Did you put the BOOT jumper on the board? Close all other serial tools that may have use the port?
But before flashing firmware or bootloader:
Can you please remove the boot jumper(if any) connect to PC, start RAK Serial Tool, Open the corresponding port, press reset button of the board and give us print screen of output in RAK Serial Tool?

Here you go:

And yes, I did put the BOOT jumper on the board, and there was no other tools using the same port.

Error: 3 occurred because the AT command you currently use is not applicable, you need to upgrade the version and then proceed with the operation. You can refer to the document:https://doc.rakwireless.com/rak5205-rak7205-wistrio-lora-tracker/installing-the-firmware

I did try this again to the letter, but unfortunately still no dice. The STM CubeProgrammer fails with the same error as before at step 8, even after closing the program and resetting the board.

The RAK Serial Tool isn’t running at the same time, and afaik I have no other software running that would be using the same port.

I’ll try this later on another computer. Thank you for troubleshooting this. :slight_smile:

Well, I tried this on a Mac, but unfortunately the end result is the same, the STM CubeProgrammer fails at step 8. No other USB devices were connected at the same time, and resetting the board doesn’t help. Any ideas what to do, or is this a lost case?

Full log from the STM CubeProgrammer:

12:58:57:641 : Serial Port cu.usbserial-0001 is successfully opened.
12:58:57:641 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off
12:58:57:641 : No Init bits value is : 0
12:58:57:641 : Sending init command:
12:58:57:642 : byte 0x7F sent successfully to target
12:58:57:643 : Wait ends after 1 loop, dataready = 1, delay = 0
12:58:57:644 : Received response from target: 0x1f
12:58:57:654 : Activating device: OK
12:58:57:654 : Sending GetID command and its XOR:
12:58:57:655 : byte 0x02 sent successfully to target
12:58:57:655 : byte 0xFD sent successfully to target
12:58:57:657 : Wait ends after 1 loop, dataready = 1, delay = 1
12:58:57:658 : Received response from target: 0x79
12:58:57:658 : Received response from target: 0x01042979
12:58:57:659 : Chip ID: 0x429
12:58:57:659 : Sending Get command and its XOR:
12:58:57:661 : byte 0x00 sent successfully to target
12:58:57:661 : byte 0xFF sent successfully to target
12:58:57:663 : Wait ends after 1 loop, dataready = 1, delay = 3
12:58:57:663 : Received response from target: 0x79
12:58:57:664 : Received response from target: 0x0b
12:58:57:664 : size of bytes in the response: 11
12:58:57:664 : Received response from target: 0x31000102112131446373829279
12:58:57:664 : Full received response: 0b31000102112131446373829279
12:58:57:664 : BootLoader protocol version: 3.1
12:58:57:665 : byte 0x11 sent successfully to target
12:58:57:666 : byte 0xEE sent successfully to target
12:58:57:668 : data sent successfully to target: 0x0800000008
12:58:57:670 : byte 0x00 sent successfully to target
12:58:57:671 : byte 0xFF sent successfully to target
12:58:57:671 : Sending GetID command and its XOR:
12:58:57:671 : byte 0x02 sent successfully to target
12:58:57:672 : byte 0xFD sent successfully to target
12:58:57:673 : Wait ends after 1 loop, dataready = 1, delay = 1
12:58:57:673 : Received response from target: 0x79
12:58:57:673 : Received response from target: 0x01042979
12:58:57:786 : byte 0x11 sent successfully to target
12:58:57:786 : byte 0xEE sent successfully to target
12:58:57:790 : data sent successfully to target: 0x0800000008
12:58:57:790 : byte 0x00 sent successfully to target
12:58:57:790 : byte 0xFF sent successfully to target
12:58:57:790 : Sending Read command and its XOR:
12:58:57:791 : byte 0x11 sent successfully to target
12:58:57:791 : byte 0xEE sent successfully to target
12:58:57:791 : Wait ends after 1 loop, dataready = 1, delay = 0
12:58:57:791 : Received response from target: 0x79
12:58:57:791 : Sending Read address and its checksum:
12:58:57:792 : data sent successfully to target: 0x1ff80000e7
12:58:57:796 : Wait ends after 1 loop, dataready = 1, delay = 1
12:58:57:796 : Received response from target: 0x79
12:58:57:796 : Sending number of bytes to be read - 1 and its checksum:
12:58:57:797 : data sent successfully to target: 0x03fc
12:58:57:805 : Wait ends after 1 loop, dataready = 1, delay = 1
12:58:57:805 : Received response from target: 0x79
12:58:57:806 : Received response from target: 0xaa0055ff
12:58:57:807 : Database: Config 0 is active.
12:58:57:807 : byte 0x11 sent successfully to target
12:58:57:807 : byte 0xEE sent successfully to target
12:58:57:807 : data sent successfully to target: 0x0800000008
12:58:57:807 : byte 0x00 sent successfully to target
12:58:57:807 : byte 0xFF sent successfully to target
12:58:57:807 : Sending Read command and its XOR:
12:58:57:807 : byte 0x11 sent successfully to target
12:58:57:807 : byte 0xEE sent successfully to target
12:58:57:808 : Wait ends after 1 loop, dataready = 1, delay = 0
12:58:57:808 : Received response from target: 0x79
12:58:57:808 : Sending Read address and its checksum:
12:58:57:808 : data sent successfully to target: 0x1ff8004cab
12:58:57:812 : Wait ends after 1 loop, dataready = 1, delay = 1
12:58:57:812 : Received response from target: 0x79
12:58:57:812 : Sending number of bytes to be read - 1 and its checksum:
12:58:57:814 : data sent successfully to target: 0x03fc
12:58:57:814 : Received response from target: 0x1f
12:58:57:814 : Response received from device: NACK
12:58:57:815 : Error: Number of bytes to be be read at address: 0x1FF8004C not acknowledged!
12:58:57:815 : failed to read the requested memory content
12:58:57:815 : Could not read flash size at address 0x1ff8004c
12:58:57:947 : Sending Read command and its XOR:
12:58:57:947 : byte 0x11 sent successfully to target
12:58:57:948 : byte 0xEE sent successfully to target
12:58:57:948 : Received response from target: 0x1f
12:58:57:948 : Response received from device: NACK
12:58:57:948 : Error: READ command not acknowledged at address: 0x1FF8004C
12:58:57:989 : failed to read the requested memory content
12:58:57:989 : Could not read flash size at address 0x1ff8004c
12:58:57:990 : byte 0x11 sent successfully to target
12:58:57:991 : byte 0xEE sent successfully to target
12:58:57:991 : data sent successfully to target: 0x0800000008
12:58:57:991 : Error: RDP level is set to 1 (0xBB), try using Read UnProtect (-rdu) command in order to remove the Read Out Protection.
12:58:58:034 : UPLOADING OPTION BYTES DATA …
12:58:58:034 : Bank : 0x00
12:58:58:035 : Address : 0x1ff80000
12:58:58:035 : Size : 24 Bytes
12:58:58:035 : Sending Read command and its XOR:
12:58:58:036 : byte 0x11 sent successfully to target
12:58:58:036 : byte 0xEE sent successfully to target
12:58:58:036 : Received response from target: 0x1f
12:58:58:036 : Response received from device: NACK
12:58:58:037 : Error: READ command not acknowledged at address: 0x1FF80000
12:58:58:066 : Error: Uploading Option Bytes bank: 0 failed
12:58:58:097 : Error: Initializing the Option Bytes failed
12:58:58:126 : Disconnected from device.