@jackyruth
I see in your log RUI Bootloader Version:3.2.6
So your device doesn’t have the default AT command firmware installed.
Here is the log I get when I use default AT command firmware and start the upgrade procedure.
Hi,
That is indeed what I get the first time I did it. However, after the YModem transfer failed, only then did it start sending the “AT not supported”.
I am pretty sure the AT command section is fine, because I believe that “Start firmware upgrade…” is a direct response to my “at+upgrade” command
The V3.3.5 is part of the RAK4270 FW versions starting V3.3.0.14. Right now the updated version is V3.3.0.17 which I sent the link on my previous post above. So when you update to the latest FW, the bootloader version should be updated as well. There is no separate bootloader hex starting RAK4270 FW V3.3.0.14.
You can upload the updated FW using STM32CubeProgrammer via UART or ST-LINK. Also use the .hex file and not the .bin file.
@carlrowan Do you think its possible to compile the binary from RUI online compiler, then flash it through SWD w the STM32CubeProgrammer. We can bypass the YModem protocol this way.
I have to confirm with the SW team but I am afraid that is not possible. When you compiled via RUI, the bootloader will be included already in the .hex file that will be generated. May I know why you want to bypass the YModem protocol?
Just to remove a step from the process. The goal is to automate RAK module programming in the assembly line.
I can successfully upload new firmware using the RAKWireless DFU tool. I am simply attempting to figure out how to automate that process. Could you give more info as to how the DFU tool was implemented? That would be a great help!
(BTW, I updated the firmware with STM32CubeProgrammer as per your suggestion, the issue persists as seen below)