Tom Fifield

Duplicate of https://github.com/meshtastic/firmware/issues/3883

Hi @janveeh , thanks for following the trademark guidelines. Please go ahead and make a PR for the board and variant :) We're here to help

Fatal error 3 means no radio was detected. A log file would be very helpful to work out why. Connect to USB, go to Open Serial Monitor on HTTPS://flasher.meshtastic.org

Thanks, very useful. That error is `RADIOLIB_ERR_SPI_CMD_FAILED (-707) [SX126x](https://jgromes.github.io/RadioLib/class_s_x126x.html) failed to execute SPI command. Often this means that the module is trying to use TCXO while XTAL is connected (or...

@NomDeTom - you're an XTAL vs TCXO expert - any ideas on what happening with this t-echo?

@geeksville 加油！

Thanks @cracky22 . Do you have the ability to build your own firmware? If so logs from one with #define GPS_DEBUG 1 in variant.h . Otherwise let me know and...

OK, interesting. I wonder if our GPS configuration is being lost while asleep. Then it starts back up with every NMEA sequence enabled. Something like #5088

Thanks for the logs @cracky22 . So, the NMEA sequences are correct: GGA and RMC Though, there are a few lines in there like the GPS just started up again...

OK,so I read the logs from 10:00 to 10:10 and it all looks good. Then out of the blue, we get our buffer error. There aren't too many messages going...