You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @loverdeg-ep. The easiest way to do this, and the only way right now, is connect the board to a PC, run pyocd-gdbserver on that PC with the --persist and --allow-remote options, then connect to it from your development machine. You could even use a Raspberry Pi as the "PC" server running pyOCD.
Serving the CMSIS-DAP protocol over a TCP port would be an interesting addition to DAPLink, but won't happen in the short term. I have added it to the todo list, though! 😀
I want to debug and monitor a board running mbedOS remotely over a local IP based network.
Any comments on the feasibility of adding gdbserver protocol support or a "pyOCDserver" interface to daplink?
I'm envisioning using a modified FRDM-K64 or an evolved version of the CI board to act as a network debug server and test runner.
The text was updated successfully, but these errors were encountered: