RAK3401 + RAK19007 + RAK13302: no TX after software reset, only physical button recovers

WisBlock
1

Hi everyone,

I’m running into an issue where RAK13302 stops transmitting after any software-triggered reset of the nRF52. Only pressing the physical reset button on the baseboard recovers it.

Info

  • Product: RAK3401 + RAK19007 + RAK13302
  • Firmware: Arduino BSP (PlatformIO), WisBlock-API-V2 +
    SX126x-Arduino
  • Version: AT+VER=? → WisBlock API 2.0.21
  • OS: macOS
  • OS version: 26.4.1 (build 25E253)
  • Frequency: 100% reproducible
  • Repro: provision OTAA creds, issue ATZ. Gateway sees nothing for about 2 minutes 30 seconds, firmware reboots itself, loops forever. Press physical reset and device joins in 5 seconds.
  • Source: private; can build a minimal repro from WisBlock-API-V2’s stock OTAA example if needed.

Tried, no change

  • Direct NVIC_SystemReset
  • Watchdog reset
  • Radio.Sleep before reset
  • 100 ms NRESET pulse on Arduino pin 4
  • WB_IO2 cycle
  • Drive P0.18 low
  • Clear GPREGRET

Questions

  1. Is the RAK13302’s NRESET tied to the nRF52’s hardware reset line on the RAK19007?
  2. If yes, any way to assert that line from firmware?
  3. Any other way to reset just the RAK13302 from firmware?

Thank you for all of your help!

2

Turns out, the root cause is faulty hardware.

My newly arrived second WisMesh 1W Booster Starter Kit worked fine with the firmware.