Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #32048
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Wireless UART for debug purposes |
| Date | 2023-11-13 10:00 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <uisojb$j2e7$1@dont-email.me> (permalink) |
| References | <uislkq$i8k7$1@dont-email.me> |
On 13/11/2023 09:10, pozz wrote: > I often have embedded boards with a UART that shows debug logging > messages. Most of the times, only the TX signal is of interest, in a few > cases the debug UART features a full command line console, so both TX > and RX lines are of interest. > > I have many UART/USB adapters and they work well when I have a desktop > or mobile PC, running putty or Realterm or a similar software, near the > device. > > However, in some cases, the device is installed far from a PC and it's > difficult to have USB wired cable connection. So I'm wondering if > there's an off-the-shelf UART/wireless adapter that could help in these > cases. Bluetooth? WiFi? Proprietary wireless protocol (with a > priorietary dongle USB receiver)? > > Do you have the same problem as me? How did you solve? There are plenty of Bluetooth modules with UART connections, but of course you need something at the other end. A couple of Silicon Labs evaluation boards can be configured as linked to each other - then they can act mostly like a UART cable with a wireless cable, with very little effort. If you need to have the Bluetooth module inside the device, and have one master PC talking to lots of devices, then you'll need to do a bit more work. And if it is always installed, then suddenly your device is classified as a radio communications device, with all the standards, certifications, EMC rules, and testing that goes along with that. If it is okay to plug something temporarily into the board that needs debugged, you could set up a Rasberry Pi with a USB battery pack, and plug that into your TTL-level UART debug signals on the board. Then you can have Wifi configured in any way you like. A tty to tcp/ip port converter for remote access should not be difficult to make - with Python Twisted, it's probably no more than a couple of dozen lines.
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Wireless UART for debug purposes pozz <pozzugno@gmail.com> - 2023-11-13 09:10 +0100
Re: Wireless UART for debug purposes David Brown <david.brown@hesbynett.no> - 2023-11-13 10:00 +0100
Re: Wireless UART for debug purposes pozz <pozzugno@gmail.com> - 2023-11-13 10:39 +0100
Re: Wireless UART for debug purposes David Brown <david.brown@hesbynett.no> - 2023-11-13 13:15 +0100
Re: Wireless UART for debug purposes pozz <pozzugno@gmail.com> - 2023-11-13 13:46 +0100
Re: Wireless UART for debug purposes David Brown <david.brown@hesbynett.no> - 2023-11-13 15:33 +0100
Re: Wireless UART for debug purposes Theo <theom+news@chiark.greenend.org.uk> - 2023-11-13 14:35 +0000
Re: Wireless UART for debug purposes Hans-Bernhard Bröker <HBBroeker@gmail.com> - 2023-11-14 19:47 +0100
Re: Wireless UART for debug purposes "Peter Heitzer" <peter.heitzer@rz.uni-regensburg.de> - 2023-11-15 08:16 +0000
Re: Wireless UART for debug purposes pozz <pozzugno@gmail.com> - 2023-11-20 08:29 +0100
Re: Wireless UART for debug purposes pozz <pozzugno@gmail.com> - 2023-11-20 08:29 +0100
Re: Wireless UART for debug purposes Hans-Bernhard Bröker <HBBroeker@gmail.com> - 2023-11-20 17:34 +0100
csiph-web