Does anyone have any experience with resurrecting these p1 solar nodes. I accidentally uploaded the wrong Meshtastic firmware to it (the Rak 4631 firmware was in the same folder and I accidentally moved it to the solar p1 drive after I double clicked reset). Shame on me. Now the solar P1 will just constantly reboots after about 10 seconds. When i have the solar P1 plugged into my computer i can hear the windows ding for a device connecting and disconnecting. I can still double click reset and get into the (DFU? Bootloader?) mode, and still see the drive “XIAO-BOOT”. While in this (DFU? bootloader?) mode, the rebooting every 10 seconds issue goes away. But when I drag a new Meshtastic firmware to it, I get the same issue of it rebooting every 10 seconds. I did some chat GPT research and it looks like I may have overwritten some important stuff by uploading the wrong firmware. After some trouble shooting i downloaded NRf Connect Programmer, and after messing with that for a bit and doing some research realized the issue probably cannot be resolved over USB. It is looking like i might I need to flash (via SWD with a Segger Jlink EDU mini) one or all of the following: the soft device, bootloader, and Meshtastic firmware. I have been pulling my hair out the past few hours trying to recover this and then i found these forums. I saw a forum thread here where a gentleman recommended deleting the current.uf2 and resetting, this did not work for me. Any advice would be helpful, i would assume since this device uses the NRF52840, someone may have had a similiar issue or the knowhow to help me. -Thank you Kindly.
I turned Putty on with serial connection at the com port my device is on, with a baud of 115200, and I see the output of putty looks the same every time i captured it before it reset:
//\ E S H T /\ S T / C
DEBUG | ??:??:?? 2 Filesystem files:
DEBUG | ??:??:?? 2 prefs (directory)
DEBUG | ??:??:?? 2 config.proto (168 Bytes)
DEBUG | ??:??:?? 2 module.proto (88 Bytes)
DEBUG | ??:??:?? 2 channels.proto (57 Bytes)
DEBUG | ??:??:?? 2 device.proto (126 Bytes)
DEBUG | ??:??:?? 2 nodes.proto (281 Bytes)
DEBUG | ??:??:?? 2 adafruit (directory)
DEBUG | ??:??:?? 2 bond_prph (directory)
DEBUG | ??:??:?? 2 bond_cntr (directory)
DEBUG | ??:??:?? 2 Power::lipoInit lipo sensor is not ready yet
DEBUG | ??:??:?? 2 Use analog input 16 for battery level
INFO | ??:??:?? 2 Scan for i2c devices
DEBUG | ??:??:?? 2 Scan for I2C devices on port 1
INFO | ??:??:?? 2 No I2C devices found
DEBUG | ??:??:?? 2 acc_info = 0
.
.
.(I have removed a bunch of stuff for the sake of the post not being huge, but see below lines were it fails on that last line every time)
DEBUG | 07:26:44 6 [GPS] NMEA GPS time set 2025-12-28 07:26:44 age 2
INFO | 07:26:44 6 [PowerFSM] Loss of power in Powered
INFO | 07:26:44 6 [PowerFSM] Loss of power in Powered
DEBUG | 07:26:44 6 [PowerFSM] Init NRF52 Bluetooth
INFO | 07:26:44 6 [PowerFSM] Init the Bluefru
it always fails there, and this kind of lines up with what chat GPT was pointing towards, that something might be wrong with the Bluetooth. Every time it gets to the Bluetooth initialization, it reboots.