New main branch and testing DAPLink

[mathias-arm]

New main branch

As previously announced, the master branch has been renamed main. The pull requests have automatically been updated. If you want to update an existing checkout GitHub suggests running the following commands:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

Testing DAPLink

Currently this requires changes from the mbrossard:fix/run-tests branch. This will eventually be merged to develop.

This is how you would run the tests for lpc4322_lpc55s69xpresso_if:

(venv) $ python tools/progen_compile.py lpc4322_lpc55s69xpresso_if
[...]
(venv) $ python test/run_test.py --project-tool make_gcc_arm --firmware lpc4322_lpc55s69expresso_if \
  --targetdir $DAPLINK_VALIDATION --verbose All --quick --logdir logs
[...]
            0: APP=lpc4322_lpc55s69expresso_if BL=lpc4322_bl Board=LPCXpresso55S69 Target=LPCXpresso55S69
[...]
All boards passed

This assumes that the board is connected, and that $DAPLINK_VALIDATION is set to (or replaced with) the path to the dist directory of daplink-validation after running the build instructions, or the uncompressed directory of a release.

The LPCXpresso55S69 value comes from the 5th column of the SUPPORTED_CONFIGURATIONS entry in test/info.py that corresponds to the board. The test script is expecting to find LPCXpresso55S69.bin and LPCXpresso55S69.hex in the binaries from daplink-validation. If you need to add a validation binary, in many cases it should be as simple as adding one entry in the targets variable of gen.py. The entry for our example the entry is "LPCXpresso55S69": "LPC55S69_NS",, where we recognize the first name, and the second is the Mbed OS (latest 5.x) target name. To see a list of the supported targets: mbed target -S (check that GCC_ARM is supported). Pull request to add targets are welcomed.