RAK3172 - STM32 RUI flash, still tries to join?

Hi everyone
We’ve had about 20 boards ordered with RAK3172 - And until now we’ve deployed 12 with no problems.

We have two boards now where we flash via STM32cube programmer the RUI3 firmware - It says done, all good.

Once we go into serial and look at the device, its just doing this:

18:29:57.629 →

18:29:57.833 → RAKwireless RAK3172-E

18:29:57.833 → ------------------------------------------------------

18:29:57.833 → Version: RUI_4.2.0_RAK3172-E

18:29:57.833 → Current Work Mode: LoRaWAN.

18:30:05.333 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:30:21.083 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:30:36.791 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:30:52.501 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:31:08.262 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:31:23.959 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:31:39.692 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:31:55.449 → +EVT:JOIN_FAILED_RX_TIMEOUT

18:32:11.151 → +EVT:JOIN_FAILED_RX_TIMEOUT

Its nothing we’ve asked from it to do… So why would it do it? Especially when completly newly flashed.

If you enabled automatic join once with AT+JOIN=1:1 or with an API call from your application, it is stored as setting in flash. Flashing a new firmware does not reset these settings.