Rak 3272S-Board RUI3 Arduino programming board

LPWAN Modules / EVBs RAK3172
1

Hello,

i am using a Rak 3272S-Board with latest firmware (RAK3172-E_latest.bin) from downloadpage.

I started the first steps with Arduino 1.8.9 and RAKwireless WisBlock Core modules.

I chose the WisDuo RAK3172 Evaluation Bord and use the LoRaWAN OTTA-example.

When i want to flasch the board with a FTDI-Board and Programmer: AVRISP mkll i got the message:

Device is not in boot mode
Detecting bausrate…
Detect baudratefail, can not get the baudrate

With STM32Cube-Programmer i can flash the RAK3272S-board.

So how can i programm the board?

Greetins E_T

2

Hi @Schulz ,

Is the AT commands of RUI3 working? AT, AT+VER=?, etc. shows good reply?

Also, this part is not relevant to RUI3 Programmer: AVRISP mkll. I think this should not show if you select the WisDuo RAK3172 Evaluation Board in your Arduino IDE.

image
image834×209 11.9 KB

3

Thank you for the quick response.

Is the AT commands of RUI3 working? AT , AT+VER=? , etc. shows good reply? NO!

No reply!

Greetings E_T

4

I am not sure what happened. If the baudrate is set at 11200, UART2-COM port ok and jumpers wires 100% solid but still got no replies, let’s proceed on uploading the HEX firmware file to get a fresh module working.

Please upload this firmware (.hex) using STCubeProgrammer then you can try again sending AT commands to UART2.

5

Now it is working with flashing the hex-file

Arduino-IDE

OK
AT+VER=3.4.2-rui3_22q1_update.112
OK
Programming:
…
[S] TRANSMISSION: block 175 (seq=176) sent
[S] TRANSMISSION: block 176 (seq=177) sent
[S] TRANSMISSION: Reached EOF
[S] TRANSMISSION: EOT sent and awaiting ACK
[S] TRANSMISSION: Finished (ACK received)
[S] TRANSMISSION: SEND NULL

Entering boot mode
Device is in boot mode
Upgrade Complete

Thank you for the support.

For my understanding, what is the difference between firmware.bin and firmware.hex?

I flashed both files with STM32cubeprogrammer!?

Greetings

E_T

1 Like
6

Good to hear is it working now :+1:

The .bin only contains the application code. The .hex contains both bootloader + application code.

Based on your previous message, it looks like things got messy since you upload a .bin file using STM32CubeProgrammer. I don’t want to go deep on the processes you’ve been to so I just suggested to make the device fresh (as if new) by uploading the .hex.

Btw, how’s your experience with RUI3 so far? Any upside and downside?

7

I do my first steps, but i can say rapid implementation is possible.

The connection of the external sensors will still be exciting.

Greetings

E_T