There is no output to UART console when I set CONFIG_BT=y in prj.conf
peripheral_lbs sample project in ncs V2.0.2 can't printk anything.
There is no output to UART console when I set CONFIG_BT=y in prj.conf
peripheral_lbs sample project in ncs V2.0.2 can't printk anything.
Hi,
Unfortunately I cannot reproduce your issue.
I just now tried a brand new application based on the NCS v2.0.2 peripheral_lbs example on both the nRF52DK and the nRF5340DK, and for both printk() worked and I got data on a Serial Port.
I really don't think CONFIG_BT=y would break UART console, that would really not make sense.
Are you developing on a Development Kit or on your custom board?
By the way, as you requested, the prj.conf used to test:
# # Copyright (c) 2018 Nordic Semiconductor # # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause # CONFIG_NCS_SAMPLES_DEFAULTS=y CONFIG_BT=y CONFIG_BT_PERIPHERAL=y CONFIG_BT_DEVICE_NAME="Nordic_LBS" # Enable the LBS service CONFIG_BT_LBS=y CONFIG_BT_LBS_POLL_BUTTON=y CONFIG_DK_LIBRARY=y CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
Best regards,
Hieu
Hello Hieu,
Thanks for your quick response. I have one more request. Would you use the nrf5340dk_nrf5340_cpuapp.overlay file to disable to UART console and see if you can still receive output.? My problem seems to be complicated. The UART on nRF5340DK always work even if I intentionally disable the UART or assign different TX and RX pins. I am trying to make sure the overlay file can change the behavior first, then I will make correct adjustment on my own custom board.
I have more problem on my custom board, but one thing at a time. I want to get the UART working in different configuration/overlay first.
Thanks again.
My own. nrf5340dk_nrf5340_cpuapp.overlay. for a different custom board, but nRF5340DK is unexpectly working fine with it, so something is wrong
I may have mistakes in the overlay file
&uart0 {
//status = "okay";
status = "disabled";
label = "UART_0";
current-speed = <115200>; // 115200
pinctrl-0 = <&uart0_default_alt>;
pinctrl-1 = <&uart0_sleep_alt>;
pinctrl-names = "default", "sleep";
};
&pinctrl {
uart0_default_alt: uart0_default_alt {
group1 {
psels = <NRF_PSEL(UART_TX, 1, 1)>; // P1.1 is TX
};
group2 {
psels = <NRF_PSEL(UART_RX, 0, 29)>; // P0.29 is RX
bias-pull-up;
};
};
uart0_sleep_alt: uart0_sleep_alt {
group1 {
psels = <NRF_PSEL(UART_TX, 1, 1)>, // P1.1 is TX
<NRF_PSEL(UART_RX, 0, 29)>; // P0.29 is RX
low-power-enable;
};
};
};
There are some UART0 registers is the data sheet. Going thru functions call stack to find out which function call is making some changes ??
19 0x41013000 UARTE UARTE0 NS NA Universal asynchronous receiver/transmitter
0x50008000 0x40008000 UARTE UARTE0 : S UARTE0 : NS US SA Universal asynchronous receiver/tra
Hi JC,
I am not sure we are on the same page at the moment. Here is my current understanding about your current situation:
If there is anything wrong above, please correct me.
Assuming my understanding above is correct, below I will give some facts that might help
I hope the above information is sufficient for you to understand what is going on. If you are interested, be low I will also expand on some extra things you can do.
Notes (more advanced "ways to discover" the problem):
gpio_fwd: nrf-gpio-forwarder { compatible = "nordic,nrf-gpio-forwarder"; status = "okay"; uart { gpios = <&gpio1 1 0>, <&gpio1 0 0>, <&gpio0 11 0>, <&gpio0 10 0>; }; };
Best regards,
Hieu
Hello Hieu,
I am a bit confused too, so I step back to check on my build tool and test setup first.
There are three virtual com from nRF5340DK
When I run peripheral_lbs onnRF5340DK. One com port shows the the output from the AppCore
*** Booting Zephyr OS build v3.1.99-ncs1 ***
Starting Bluetooth Peripheral LBS example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fc8
I: data wra: 0, 2c
I: No ID address. App must call settings_load()
Bluetooth initialized
Advertising successfully started
and another com port shows
*** Booting Zephyr OS build v3.1.99-ncs1 ***
and I think this may be from the NetCore
I am back to square 0 to restart the whole debugging process slowly now.
You read my mind and I was exactly in that situation. Thanks for your info which helps directing my thought on the debugging process. Let me regroup with your suggestions first before moving forward
The message *** Booting Zephyr OS build v3.1.99-ncs1 *** coming out at
may be from the NetCore and I am looking for the output from AppCore. Let me try your suggestion to disable the UART at NetCore first.
The message *** Booting Zephyr OS build v3.1.99-ncs1 *** coming out at
may be from the NetCore and I am looking for the output from AppCore. Let me try your suggestion to disable the UART at NetCore first.