Application Uart Interface
Building
This application uses sysbuild to build for multi-core build targets, such as the nRF5340, that require an image for both the application core and the network core. This application has two options for network core images, depending on the target test of the application. These are:
ant_rpc
hci_ipc_with_writes
Using sysbuild, these images can be added to the build by choosing options ‘’SB_CONFIG_NRF_DEFAULT_ANT_ONLY’’ or ‘’SB_CONFIG_HCI_IPC_WITH_WRITES’’ for ant_rpc or hci_ipc_with_writes, respectively, in sysbuild.conf. This will automatically cause the network core image to be added to the build.
Furthermore, this application requires additional configurations to be applied to both images depending on the target test.
For the application core image this is done through adding the respective .conf file for the test (prj_central_client for the central client DUT, for example) as a Kconfig fragment in the nRFConnect VSCode extension build configuration menu.
For the network core image this is done using sysbuild. All options for these additional configurations are defined in Kconfig.sysbuild and must be set in sysbuild.conf. For example, choosing ‘’SB_CONFIG_CENTRAL_CLIENT’’ would add the configuration found in sysbuild/hci_ipc_with_writes/prj_central_client.conf to the network core image. Note that the options defined in Kconfig.sysbuild need to be prefixed with ‘’SB_CONFIG’’ when being set in sysbuild.conf.
Running
Once the application is flashed, use ANT_BFT_Controller PC tool to connect to the DUT’s VCOM port.
Port Type: COM Port: <PC dependent, check Connected Devices in VS code or Device Manager> Baud Rate: 115200 (see app.overlay and/or serial.c for definition) HCI Frame Type: Standard
See the ‘’scripts/testlog_parser’’ directory for a python script that is helpful to condense and/or combine BFT output.
Debug
Use VS code extenstion to connect to RTT. Debug prints can be enabled via Kconfig. See the root Kconfig, specific source files and prj.conf for debug options.