- jimbojones
- Posts: 38
- Joined: Sun Apr 15, 2018 2:33 pm
Advice on best way to remotely debug Pi 5 via UART
As title suggests, does anyone know the best way to remotely debug my pi5? There's been the odd occasion where I've managed to bork my pi5 whilst remotely tinkering, to the point it won't boot, and so I would like to be able to read the pre-boot logs to get an idea of what I've done and what I'll need to do to fix once I get "on site" back home (Even when I am home, it's a real pain to try to connect to it via hdmi given the Pi5's location and connected peripherals).
My current thinking is to buy the https://www.raspberrypi.com/documentati ... probe.html to plug into the Pi5's dedicated 3-pin UART port, and then plug the Probe into an old Pi 3B I have lying around currently doing nothing. I would have the 3B headless, connected to my router via WiFi, and an SSH server running on it, and then when needed I could VPN into my LAN and then SSH into the 3B to then use screen or something similar to view the Pi5's UART output (layers upon layers of connections!).
So it would be [Remote Laptop] -> [VPN to LAN] -> [Rpi3B to USB] -> [Debug Probe to 3-pin UART] -> [Rpi5]
This does seem a little bit overly complicated to me, but it also seems like my best (and most economical) bet, given I already have a 3B lying around.
Obviously if the 3B also borks then I'm in the exact same situation I'm currently in, but I'm thinking that I would literally have nothing but an ssh server running on it and won't be actively tinkering like I do with my pi5, so chances of that going down are waaay smaller.
Would love some advice on whether my current idea would work / is any good, or suggestions for potentially better ways to achieve the same result. Cheers in advance!
My current thinking is to buy the https://www.raspberrypi.com/documentati ... probe.html to plug into the Pi5's dedicated 3-pin UART port, and then plug the Probe into an old Pi 3B I have lying around currently doing nothing. I would have the 3B headless, connected to my router via WiFi, and an SSH server running on it, and then when needed I could VPN into my LAN and then SSH into the 3B to then use screen or something similar to view the Pi5's UART output (layers upon layers of connections!).
So it would be [Remote Laptop] -> [VPN to LAN] -> [Rpi3B to USB] -> [Debug Probe to 3-pin UART] -> [Rpi5]
This does seem a little bit overly complicated to me, but it also seems like my best (and most economical) bet, given I already have a 3B lying around.
Obviously if the 3B also borks then I'm in the exact same situation I'm currently in, but I'm thinking that I would literally have nothing but an ssh server running on it and won't be actively tinkering like I do with my pi5, so chances of that going down are waaay smaller.
Would love some advice on whether my current idea would work / is any good, or suggestions for potentially better ways to achieve the same result. Cheers in advance!
Re: Advice on best way to remotely debug Pi 5 via UART
How remote is remote?
You don't need a debug probe if you're using a 3B. Just a cable with female dupont connectors on one end and the matching connector for the debug socket on the other. You will need to make sure that the UART on the 3B is enabled, that a login on it is not enabled, and that your user is in the dialout group.
A further advantage of using the 3B is that with minimal electronics you could also control the Pi5's power button - the Pi5 has a two pin header in parallel with the button.
You don't need a debug probe if you're using a 3B. Just a cable with female dupont connectors on one end and the matching connector for the debug socket on the other. You will need to make sure that the UART on the 3B is enabled, that a login on it is not enabled, and that your user is in the dialout group.
A further advantage of using the 3B is that with minimal electronics you could also control the Pi5's power button - the Pi5 has a two pin header in parallel with the button.
Knowledge, skills, & experience have value. If you expect to profit from someone's you should expect to pay for them.
All advice given is based on my experience. it worked for me, it may not work for you.
Need help? https://github.com/thagrol/Guides
All advice given is based on my experience. it worked for me, it may not work for you.
Need help? https://github.com/thagrol/Guides
Jump to
- Community
- General discussion
- Announcements
- Other languages
- Deutsch
- Español
- Français
- Italiano
- Nederlands
- 日本語
- Polski
- Português
- Русский
- Türkçe
- User groups and events
- Raspberry Pi Official Magazine
- Using the Raspberry Pi
- Beginners
- Troubleshooting
- Advanced users
- Assistive technology and accessibility
- Education
- Picademy
- Teaching and learning resources
- Staffroom, classroom and projects
- Astro Pi
- Mathematica
- High Altitude Balloon
- Weather station
- Programming
- C/C++
- Java
- Python
- Scratch
- Other programming languages
- Windows 10 for IoT
- Wolfram Language
- Bare metal, Assembly language
- Graphics programming
- OpenGLES
- OpenVG
- OpenMAX
- General programming discussion
- Projects
- Networking and servers
- Automation, sensing and robotics
- Graphics, sound and multimedia
- Other projects
- Media centres
- Gaming
- AIY Projects
- Hardware and peripherals
- Camera board
- Compute Module
- Official Display
- HATs and other add-ons
- Device Tree
- Interfacing (DSI, CSI, I2C, etc.)
- Keyboard computers (400, 500, 500+)
- Raspberry Pi Pico
- General
- SDK
- MicroPython
- Other RP2040 boards
- Zephyr
- Rust
- AI Accelerator
- AI Camera - IMX500
- Hailo
- Software
- Raspberry Pi OS
- Raspberry Pi Connect
- Raspberry Pi Desktop for PC and Mac
- Beta testing
- Other
- Android
- Debian
- FreeBSD
- Gentoo
- Linux Kernel
- NetBSD
- openSUSE
- Plan 9
- Puppy
- Arch
- Pidora / Fedora
- RISCOS
- Ubuntu
- Ye Olde Pi Shoppe
- For sale
- Wanted
- Off topic
- Off topic discussion