OpenOCDDriver: disable default server ports - #1958
Conversation
|
This currently breaks tests and there is a DCO complaint. |
c2254f0 to
3adbae2
Compare
Thanks, that is a good point! However, that would be a broader architectural change. Since OpenOCDDriver currently invokes OpenOCD directly and does not use those server interfaces, I would prefer to keep this PR focused and consider exporter-managed OpenOCD invocation in a separate one. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1958 +/- ##
========================================
- Coverage 60.8% 60.8% -0.1%
========================================
Files 184 184
Lines 15189 15190 +1
========================================
- Hits 9241 9240 -1
- Misses 5948 5950 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
3adbae2 to
540bd3a
Compare
OpenOCD starts GDB, telnet, and TCL servers on fixed default ports. When multiple boards on the same exporter bootstrap concurrently, the second OpenOCD instance fails to bind these ports. Disable the server ports before loading OpenOCD configuration files. OpenOCDDriver does not provide a lifecycle for using or stopping these servers, while disabling them allows parallel bootstrap operations. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
540bd3a to
a70ed34
Compare
Description
OpenOCD starts GDB, telnet, and TCL servers on fixed default ports. When
multiple boards on the same exporter bootstrap concurrently, the second
OpenOCD instance fails to bind these ports.
Disable the server ports before loading OpenOCD configuration files.
OpenOCDDriver does not provide a lifecycle for using or stopping these
servers, while disabling them allows parallel bootstrap operations.
Configurations that intentionally require a server interface can re-enable
the required port before
init.Checklist
Tested with: