hardware CS not working when using BLE with nRF5340DK

Hi,

The actual issue here is that P1.1 (33) is used by the network core. So the fix is to use another pin. I have tested with P1.3, and with that it works as expected with both secure and non-secure, using both west on the command line and SES.

Thank you, instead I have reconfigured the P1.1 to be used by the application core.
When using the HCI RPMsg, for what function is this UART used ? Is there a documentation about it ?
I saw that pins are configure to be used by the network core in the function remoteproc_mgr_config(). Why isn't there a way to desactivate this function with prj.conf ?

Hi,

Nicolas Brunner said:

HCI RPMsg, for what function is this UART used ? Is there a documentation about it ?

It is used for logging. It is not explicitly documented in that example, but logging is enabled by default. You can disable it by setting CONFIG_LOG=n in hci_rpmsg's prj.conf.

Nicolas Brunner said:

I saw that pins are configure to be used by the network core in the function remoteproc_mgr_config(). Why isn't there a way to desactivate this function with prj.conf ?

Calling of remoteproc_mgr_config() among other things is configured via CONFIG_TRUSTED_EXECUTION_NONSECURE, but there is no way to disable configuration of just the UART pins via prj.conf out of the box. I agree that would make sense though, if you do not want UART logging from the network core.

Thanks for the information, I use the RTT instead of UART for the logging.
I measured with a ohmmeter and saw the pins P0.10, P0.11, P1.0 and P1.1 were connected to the Signal switches that further connect them to the virtual COM port.
It would be helpful to add to the Virtual COM port page the information about the port for the network core.
In the Solder bridge configuration page, information about S27 to SB30 is also missing.

Hi,

Thank you for pointing out the lacking documentation. I have forwarded it to the team so that it can be fixed.