Some unsorted idea
- monitoring an 'unconnected' device is difficult. Write messages to UART and use a tty to USB adapter to monitor what your device is doing. Or grab a pi debug probe (which can work as a UART to USB device) https://www.raspberrypi.com/documentati ... probe.html
- or write messages to a file and read the file when connected
- write a log-method and use it to collect all sort of messages (which then goes either UART or file)
- check if there is a boot.py . Current requirement is "boot.py should always exit and not run indefinitely."
- use a try except block around the main code. Write exceptions to a log file.
- check power supply. I had problems with a lora module which needed capacitors for the power supply, added some 100uF close to the module.
- monitoring an 'unconnected' device is difficult. Write messages to UART and use a tty to USB adapter to monitor what your device is doing. Or grab a pi debug probe (which can work as a UART to USB device) https://www.raspberrypi.com/documentati ... probe.html
- or write messages to a file and read the file when connected
- write a log-method and use it to collect all sort of messages (which then goes either UART or file)
- check if there is a boot.py . Current requirement is "boot.py should always exit and not run indefinitely."
- use a try except block around the main code. Write exceptions to a log file.
- check power supply. I had problems with a lora module which needed capacitors for the power supply, added some 100uF close to the module.
Statistics: Posted by ghp — Sat Jan 31, 2026 8:10 pm