nrf5340 audio dk hci_uart sample and VCOM

[chelalv]

I am using nrf5340 audio DK. After plugging it into the computer, 3 VCOMs and RTT will appear. What are these three ports?
docs.nordicsemi.com/.../logging_nrf5340.html Here is the nrf5340 DK

Why can other programs sysbuild compile two hex, one application mcu and one network mcu, but hci uart only has one application mcu?

[Priyanka]

Hi,

For  the nRF5340 DK v1.0.0  there are 3 VCOMs:

First VCOM: Outputs log from the network core (if available).
Second (middle) VCOM: Routed to the P24 connector of the DK (can be used for custom UART connections).
Third VCOM: Outputs log from the application core.

For  nRF5340 DK v2.0.0, only two virtual COM ports are available.

You can refer this documentation for more details. 

In hci_uart, it only targets the application core. The network core is not used in this sample, so only one HEX file is generated. Other programs, you get two HEX files: one for the application MCU (app core) and one for the network MCU (net core).

Regards,

Priyanka

[chelalv]

Hi Priyanka, How do I use the HCI UART example for the NRF5340 DK or the NRF5340 Audio DK?

I just want to use nrf5340 dk or nrf5340 audio dk as a controller

[Priyanka]

Hi,

As mentioned in this ticket, is there any particular reason why you need to split the controller and host between two nRF5340 devices? With its dual core design the nRF5340 is optimized to run the controller on the network core and the host on the application core. Though what you aim for might be possible for the nRF5340DK, I doubt it's possible on the nRF5340 Audio DK.

For the nRF5340DK, you should be able to build the hci_uart sample, just like you build any other sample, i.e. use the hci_uart sample from zephyr/samples/bluetooth/hci_uart.
And then build the sample targeting the network core (nrf5340dk_nrf5340_cpunet).

After that you can flash the DK using:

nrfjprog -f NRF53 --coprocessor CP_NETWORK --program build/zephyr/zephyr.hex --chiperase

-Priyanka