b22c961e5e
The gdb-port defines the GDB port and the openocd runner passes this value to openocd as well as gdb. However, the TI AM62x board provides multiple ports for each subsystem. For example, systick appears at 3333, A53 as 3334-3337, R5F as 3338 and M4F as 3339. If we want to connect to the M4F, we need to add another port which is different to the to the gdb-port value. This patch adds an additional argument --gdb-client-port to define the port which GDB should connect to. It defaults to 3333, identical to gdb-port. Signed-off-by: Daniel Schultz <d.schultz@phytec.de> |
||
|---|---|---|
| .. | ||
| completion | ||
| fetchers | ||
| runners | ||
| tests | ||
| zspdx | ||
| bindesc.py | ||
| blobs.py | ||
| boards.py | ||
| build_helpers.py | ||
| build.py | ||
| completion.py | ||
| debug.py | ||
| export.py | ||
| flash.py | ||
| mypy.ini | ||
| README.txt | ||
| robot.py | ||
| run_common.py | ||
| run_tests.py | ||
| shields.py | ||
| sign.py | ||
| simulate.py | ||
| spdx.py | ||
| twister_cmd.py | ||
| zcmake.py | ||
| zephyr_ext_common.py | ||
This directory contains implementations for west commands which are tightly coupled to the zephyr tree. This includes the build, flash, and debug commands. Before adding more here, consider whether you might want to put new extensions in upstream west. For example, any commands which operate on the multi-repo need to be in upstream west, not here. Try to limit what goes in here to Zephyr-specific features. When extending this code, please keep the unit tests (in tests/) up to date. The mypy static type checker is also run on the runners package. To run these tests locally on Windows, run: py -3 run_tests.py On macOS and Linux: ./run_tests.py Note that these tests are run as part of Zephyr's CI when submitting an upstream pull request, and pull requests which break the tests cannot be merged. Thanks!