In an increasingly digitally connected world, it can be easy to forget sometimes how much work still relies on specific pieces of hardware, especially in the field of hardware happened to have that one development board right there on their desk, yet they didn’t exactly live around the corner? Here it would be perfect if said pal could hook up a testing harness and give you access to this board
While remote access to server systems is fairly common, things get a lot more interesting when it comes to the wider area of development boards, and their plethora of physical features and fascinating world of errata and silicon-specific bugs. So how does one get easy access to such a remote board?
What’s Available
This concept of remotely using development boards is hardly a new idea, of course. Back in 2019, for example, Erich Styger gdbserver that provides a remote server for clients. GDB is the GNU Debugger that comes as part of the GCC toolchain, with the remote server component doing what it says on the tin: being able to run GDB on a different system than on which the application that is being debugged is running.
With that one simple trick you can already turn any development board that is connected to a system running gdbserver into a remotely accessible board. Even if you balk at the idea of having an entire PC dedicated to that server task, you got projects like the
<p>This requires a bit of digging into how exactly your typical programming method can be adapted to this <code>gdbserver</code> link. Fortunately tools like OpenOCD would seem to
This option is only available for J-Link customers, of course, but it provides one example of how to safely provide such remote access, featuring password protection and point-to-point connections.
Although you can technically still do a general port-forwarding on a router as well, this has become increasingly less convenient in an era of carrier-grade NAT (CG-NAT) nuking IPv4 from orbit, not to mention the potential security concerns of having <a >

