NCS/9160: do I have to have uart0 as console?

RE: NCS/9160: do I have to have uart0 as console?

bluebeam — Wed, 21 Dec 2022 23:16:45 GMT

I did try to comment out those lines as you mentioned. But I found I have to at least keep the line "CONFIG_CONSOLE=y" to have RTT working. Otherwise the RTT viewer shows nothing.

Strange. There's definitely some complicated relationship between those CONFIGs.

RE: NCS/9160: do I have to have uart0 as console?

DamoL — Wed, 21 Dec 2022 16:43:55 GMT

Ah yes sorry. I am looking at a different project from when I first had this issue.

Looks like you already found it, but you nrf9160dk_nrf9160ns_defconfig can be edited for your board folder.

For reference mine now looks like this. It will probably get rid of the error you have above.

# SPDX-License-Identifier: Apache-2.0

CONFIG_SOC_SERIES_NRF91X=y
CONFIG_SOC_NRF9160_SICA=y
CONFIG_BOARD_NRF9160DK_NRF9160NS=y

# Enable MPU
CONFIG_ARM_MPU=y

# Enable hardware stack protection
CONFIG_HW_STACK_PROTECTION=y

# Enable TrustZone-M
CONFIG_ARM_TRUSTZONE_M=y

# This Board implies building Non-Secure firmware
CONFIG_TRUSTED_EXECUTION_NONSECURE=y

# enable GPIO
CONFIG_GPIO=y

# # Enable uart driver            #COMMENT THIS OUT
# CONFIG_SERIAL=y                 #COMMENT THIS OUT
#                                 #COMMENT THIS OUT
# # enable console                #COMMENT THIS OUT
# CONFIG_CONSOLE=y                #COMMENT THIS OUT
# CONFIG_UART_CONSOLE=y           #COMMENT THIS OUT

RE: NCS/9160: do I have to have uart0 as console?

bluebeam — Wed, 21 Dec 2022 06:03:09 GMT

Now I see some error at the very beginning of app starting. It seems someone still try to use the UART_0 port. But this doesn't seem to affect anything else. My app can continue if I ignore it.

E: Cannot bind UART_0
E: UART could not be initialized: -22

RE: NCS/9160: do I have to have uart0 as console?

bluebeam — Tue, 20 Dec 2022 23:21:04 GMT

I don't think I have a SPM folder. I only have one prj.conf within my source folder.

RE: NCS/9160: do I have to have uart0 as console?

bluebeam — Tue, 20 Dec 2022 23:20:10 GMT

Setting CONFIG_SERIAL=n alone doesn't work either. But I got a warning saying the value has been set in my copy of nrf9160dk_nrf9160_ns_defconfig. So I went there and comment out the line. But that still doesn't work. Finally I comment out the line "CONFIG_SERIAL=y" in nrf9160dk_nrf9160_defconfig (the non NS version) and that works. Now I don't need to have a unused uart0 in my nrf9160dk_nrf9160_common.dts file and I still have RTT working as expected.

It's strange why it has to be the non-NS version but not the NS version of defconfig. I'm building my application as the NS version. I don't see how the defconfig file was referenced by any of the DTS or DTSI files.

Is there any guide explaining the relationship and dependencies among these CONFIG_SERIAL/CONFIG_CONSOLE/CONFIG_LOG/CONFIG_UART...etc. It's very confusing.

RE: NCS/9160: do I have to have uart0 as console?

DamoL — Tue, 20 Dec 2022 10:48:51 GMT

Check your prj.conf in you SPM folder. I had CONFIG_SERIAL=y within that and that was overwriting the CONFIG_SERIAL=n in my project.

I went round the houses creating functions to disable UART0 in runtime before I realised that was there.

RE: NCS/9160: do I have to have uart0 as console?

Kenneth — Mon, 19 Dec 2022 11:52:01 GMT

[quote user=""]Nor can I set the uart0 to "disabled"[/quote]

This should work, but can you also set CONFIG_SERIAL=n?

Kenneth