Dead Board Debugging

Please include the following information, in order for us to help you as effectively as possible.

  • What product do you wish to discuss? RAK4631, RAK3372, RAK11200, RAK11310, RAK11722?
    RAK10722
  • What firmware are you using? (RUI3 or Arduino BSP or other IDE (e.g. STM32CubeIDE)?
    Meshtastic
  • What firmware version? Can it be obtained with AT+VER=?
    firmware-rak4631-2.6.11.60ec05e
  • Computer OS? (MacOS, Linux, Windows)
    Linux
  • What Computer OS version?
    Fedora Core 43
  • How often does the problem happen?
    Every plugin
  • How can we replicate the problem?
    Not sure if it is possible

Upon plugin I can see in dmesg, where the board is recognized, but it immediately disconnects, no lights blink at all. There was what appeared to be corrosion near the battery connection point that I cleaned up, I don’t see any further damage. I don’t see any other issues visually.

The board powered up long enough to flash the meshtastic firmware, but shortly after started showing these symptoms. I cannot enter dfu mode.

Welcome to the forum @Famous_Longwing

Did you connect a battery to the device?
If yes, did you check that the polarity of the battery was correct?
See RAK19007 Battery Connector

If you double push the RESET button, while the device is connected over USB, does the green LED start to dim on and off and does the device show up as an external drive.

Did you try a different USB cable and a different computer or different USB port?

I did connect a battery, looks like my battery is reversed polarity if I am reading your link properly.

exactly zero lights show up, tried multiple cables, multiple ports, attempting to enter dfu does nothing. The initial plugin shows that the device is recognized, but it immediately disconnects. Pressing reset shows no additional information in console.

If the voltage was revers, then, if you are lucky, you only need a new Base Board. If you are unlucky, the Core module is damaged as well.

If you have a second Base Board, you can switch the Core module to the other Base Board and check if it is booting up.

I do not happen to have another base board.