OK, because I had older firmware, I had to go the STM32CubeProgrammer route as documented in your manual.
This appears successful, although I’m unsure whether the device is now booting up correctly. On connecting the serial port, here’s what I’m presented with:
However, it will not accept any commands at all… i.e. no input. Please help!
My understanding of this latest situation is that the firmware is complaining of there being no LoRaWAN configuration. This doesn’t surprise me given the manual’s recommendation to erase the flash entirely.
Is it possible to flash the configuration via STM32CubeProgrammer?
I read for other devices that holding down the “1” key puts it into configuration mode. I’m having no such luck here. I suspect the RUI SDK based firmware that I now have behaves differently.
You are using the updated FW so you are good on that aspect.
Hmm…
Did you update the FW in STM32CubeProg via STlink or via USB connection (USB-UART chip)?
Did you perform an erase in the STM32CubeProg when you updated your firmware? That can refresh the flash if something internally messes up.
Also, the RAK5205/RAK7205 will sleep most of the so when you input AT commands, you should expect a wake-up reply first before you can input any AT command.
On each AT command, you should also send a termination \r\n.
Did you update the FW in STM32CubeProg via STlink or via USB connection (USB-UART chip)?
USB-UART
Did you perform an erase in the STM32CubeProg when you updated your firmware? That can refresh the flash if something internally messes up.
Yes.
Also, the RAK5205/RAK7205 will sleep most of the so when you input AT commands, you should expect a wake-up reply first before you can input any AT command.
I see the wake up reply, just nothing output if I attempt to enter any AT command. Prior to the firmware upgrade, I did see output in relation to AT commands being entered (even though my input characters weren’t echoed back).
On each AT command, you should also send a termination \r\n.
I’m presuming that the screen command is doing that. Again, prior to this firmware upgrade, the AT commands were being received and acted on.
Your FW is functional because of the replies that you got when you restart the device and the wake up when you send a certain command.
When you use STM32CubeProg to update, did you upload the .hex or .bin?
What’s happening now is that your AT commands on the UART RX are not recognized properly.
Few things in my mind:
no proper termination on command.
baud rate is wrong.
FW issues - bug?
HW issue - USB-UART related, jumpers not set properly, etc.
If I am in your situation, I will try again to upload the FW but this time using the RAK DFU Tool. With the updated FW, you must now be able to use the RAK DFU Tool.
Btw, the wake up is triggered just by any rising edge on RX pin.
When you use STM32CubeProg to update, did you upload the .hex or .bin?
Hex - nothing would have worked with the bin!
no proper termination on command.
It wasn’t a problem before. How can I verify?
baud rate is wrong.
Then nothing would be output from the firmware, right?
FW issues - bug?
Can you point me to other versions of the firmware in hex file form? I can then try that.
HW issue - USB-UART related, jumpers not set properly, etc.
Nothing has changed from before.
If I am in your situation, I will try again to upload the FW but this time using the RAK DFU Tool. With the updated FW, you must now be able to use the RAK DFU Tool.
I was able to use the DFU tool. No difference.
Btw, the wake up is triggered just by any rising edge on RX pin.
Thanks. Any further ideas? I appreciate the dialogue.
Thanks - do you have the hex file just as a zip and not a rar… I can’t decode rar on macOS without installing extra stuff. I appreciate the help, but it baffles me why you’re sending me Windows-based utilities when clearly this issue is about macOS.
I’m reasonably confident that this not a macOS issue. I used screen for many types of device and all is well. I’ve now even tried a separate serial port program with no luck. There were no problems programming via AT commands with the older version of the firmware.
Shouldn’t I be able to flash RUI_RAK5205_V3.0.0.12.H.T1_Release.bin directly via STM32CubeProgrammer? This looks to me as though it’ll contain the bootloader given that it is about 128KiB in size… I’m trying this, but without success so far.
For macOS, I am using coolterm. I like it because of the auto-record with .txt output.
Sadly, v3.0.0.12 is only the application code. You need upload first the bootloader hex file then use the LoRa button tool to upload the application fw.