BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Thu, 23 Nov 2023 08:14:02 GMT

It's great to hear that you've successfully built the projects now.

[quote user="tjm1"]I was assuming that the first build would be pristine. [/quote]

If there is no existing 'build' folder in the project at the time of the first build, it should be same as performing a pristine build. So, I'm unsure why you encountered these build errors in the first place (I didn't include my build folder in the .zip). Despite multiple attempts, I have not been able to reproduce these errors on my end.

A pristine or clean build is necessary when adding new overlay files to a project, as CMake will not detect the new overlays otherwise.

[quote user="tjm1"]

This usually happens on a line like this:

const struct device *dev = DEVICE_DT_GET(NODE_ID);


does this make any sense to you or help solve the problem?

[/quote]

Yes, the issue in our case was that relevant configurations from the overlay files in central_build/boards/nrf9160dk_nrf9160_ns* were not being applied.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 21:13:44 GMT

Vidor: I found the problem Burt helped in determining that I needed to do a pristine build as soon as I created the build configuration. I was assuming that the first build would be pristine. the pristine build worked on hci_lpuart and I flashed it into the nRF52840. The pristine worked on central_uart that you sent me. I flashed it into the nrf9160 and all is working below is an example of messages seen on the nrf9160. The nrf52DK board is running uart_peripheral. I have a temp/humidity sensor connected that is sending data every 10 seconds. I see this on the nrf9160 console. I can also send commands over to the nRF52 board. All is good. Let me play with this for a few days and see if all problems are eliminated. Thanks for your patience and you help. my rookie mistake not using pristine first.

*** Booting nRF Connect SDK v2.5.0 ***
Starting Bluetooth Central UART example
T: 25.26 H: 51.50
T: 25.27 H: 51.46
T: 25.27 H: 51.48
T: 25.27 H: 51.51
T: 25.27 H: 51.50
T: 25.26 H: 51.54
T: 25.26 H: 51.50
T: 25.26 H: 51.57

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 15:23:33 GMT

I see a definition in overlay file. what is missing? do I need an alias statement or something?

&uart2 {
current-speed = <1000000>;
status = "okay";
/delete-property/ hw-flow-control;

pinctrl-0 = <&uart2_default_alt>;
pinctrl-1 = <&uart2_sleep_alt>;
pinctrl-names = "default", "sleep";
lpuart: nrf-sw-lpuart {
compatible = "nordic,nrf-sw-lpuart";
status = "okay";
req-pin = <21>; /* <&interface_to_nrf52840 3 0>; */
rdy-pin = <19>; /* <&interface_to_nrf52840 2 0>; */
};
};

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 15:18:34 GMT

I also see the following in autoconfig.h. Where does that get defined. I do not

#define CONFIG_DT_HAS_NORDIC_NRF_SW_LPUART_ENABLED 1

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 15:12:10 GMT

C:\Nordic1\test_n160\central_uart\build\zephyr\include\generated\syscalls\uart.h:230: undefined reference to `__device_dts_ord_118'

from devicetree_generated.h

118 /soc/peripheral@40000000/uart@a000/nrf-sw-lpuart

so where does this get set. the note says it is not being set. do I need to add this to an alias file somehow? How come it is set in your build. This is the unzipped central file you sent me with no changes.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 14:57:02 GMT

https://docs.zephyrproject.org/latest/build/dts/troubleshooting.html

undefined reference to `__device_dts_ord_<N>`¶

This usually happens on a line like this:

const struct device *dev = DEVICE_DT_GET(NODE_ID);

does this make any sense to you or help solve the problem?

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 14:45:22 GMT

I repeated the entire process and got the same error. I am stuck here. How do I move forward. I will repeat the process for the central application you sent me.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 14:30:07 GMT

yes I used nrf9160dk_nrf52840 and it's overlays. I think the problem is with the device tree. googling around others have seen a similar error but I do not see how to fix it. I can build other examples for the nRF52 and the nRF9160 (blinky, buttons). I will remove the hci_lpuart and try the entire process again.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Wed, 22 Nov 2023 14:16:18 GMT

Sorry, I'm puzzled as to why it's failing on your end. Initially, I suspected that some files in the SDK might have been corrupted or altered. However, since you were able to successfully build the gateway sample, it doesn't seem likely that this is the issue.

Did you build the hci_lpuart sample for the 'nrf9160dk_nrf52840' board?

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 14:10:39 GMT

The build of hci_lpuart failed similar to all others. What am I missing.? it seems ...dts_ord... is always undefined on my system. is there something I need to set somehwre?

[167/172] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map
cmd.exe /C "cd . && C:\Nordic1\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf && cmd.exe /C "cd /D C:\Nordic1\test\hci_lpuart\build\zephyr && C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.exe -E true""
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj): in function `uart_irq_tx_ready':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:939: undefined reference to `__device_dts_ord_107'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj): in function `z_impl_uart_irq_tx_disable':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:904: undefined reference to `__device_dts_ord_107'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj): in function `uart_fifo_read':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:820: undefined reference to `__device_dts_ord_107'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj): in function `hci_uart_init':
C:\Nordic1\v2.5.0\zephyr\samples\bluetooth\hci_uart\src\main.c:342: undefined reference to `__device_dts_ord_107'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj): in function `rx_isr':
C:\Nordic1\v2.5.0\zephyr\samples\bluetooth\hci_uart\src\main.c:193: undefined reference to `__device_dts_ord_107'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj):C:\Nordic1\v2.5.0\zephyr\samples\bluetooth\hci_uart\src\main.c:403: more undefined references to `__device_dts_ord_107' follow
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\Nordic1\test\hci_lpuart\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Wed, 22 Nov 2023 13:54:33 GMT

No problem. Yes, "C:\Nordic1\v2.5.0\nrf\samples\Bluetooth\hci_lpuart" is the project you want to flash to the nRF52840.

[quote userid="87403" url="~/f/nordic-q-a/105879/ble-communication-between-a-nrf52-dk-board-and-a-nrf9160-dk-board/456945"]what application is flashed into the nRF9160? is that the centarl_uart you sent me that I cannot get to build yet or some other from the list of samples?[/quote]

Correct. The central UART sample I provided should be programmed to the nRF9160. If everything works it should try to connect to your nRF52 DK board programmed with the Peripheral UART example.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 13:50:28 GMT

Vidor thanks for the quick response.

so is C:\Nordic1\v2.5.0\nrf\samples\bluetooth\hci_lpuart the project that gets flashed into the nRF52840 on the nRF9160 DK board? I will flash that into the nRF52840 using the SW10 switch in the nRF52 position.

what application is flashed into the nRF9160? is that the centarl_uart you sent me that I cannot get to build yet or some other from the list of samples?

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Wed, 22 Nov 2023 13:37:52 GMT

The nRF9160 runs the Bluetooth host (i.e., the upper layers of the Bluetooth stack) and the application code, while the nRF52840 chip on the same nRF9160 DK board is supposed to run the Bluetooth controller firmware (Bluetooth: HCI low power UART) to enable the BLE connectivity since the 9160 doesn't have its own BLE RADIO.

The nRF52840 must be programmed separately with the FW build from the Bluetooth: HCI low power UART project.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Wed, 22 Nov 2023 13:30:44 GMT

I think I understand what you are trying to say. The nrf9160 has a programmed flashed in that device. what is that program? the nrf%2840 on the DK board has a separate program flashed in that part. What is that program and how do I program the nRF52840 on the nRF9160 DK board? Thanks for your help.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Wed, 22 Nov 2023 11:09:13 GMT

[quote user="tjm1"]ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:338
command opcode 0x0c03 timeout with err -11[/quote]

The assertion displayed when you programmed the gateway sample indicates that the Bluetooth host on the nRF9160 is failing to communicate with the Bluetooth controller on the nRF52840. Did you remember to program the controller?

[quote user="vibe"]Edit: forgot to add that you need to program the LP HCI UART sample to the nRF52840 on the board for BLE connectivity: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/samples/cellular/lte_ble_gateway/README.html#programming-the-sample [/quote]

Do you know what was done differently this time as you managed to build the LTE_BLE_GATEWAY without the errors mentioned earlier? I can't see any reason why you would be able to build this sample, but not the one I uploaded, given that the BLE configurations should be the same in both cases.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Tue, 21 Nov 2023 21:34:04 GMT

I did get LTE_BLE_GATEWAY allpication to build and run. The output is what is shown below.

*** Booting nRF Connect SDK v2.5.0 ***Resetting system
[00:00:00.251,770] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.251,953] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.499,328] <inf> lte_ble_gw: Establishing LTE link (this may take some time) ...
ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:338
command opcode 0x0c03 timeout with err -11
[00:00:10.262,481] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00000002
[00:00:10.262,512] <err> os: r3/a4: 0x2000d218 r12/ip: 0x00000010 r14/lr: 0x000102b5
[00:00:10.262,512] <err> os: xpsr: 0x41000000
[00:00:10.262,542] <err> os: Faulting instruction address (r15/pc): 0x000102c0
[00:00:10.262,573] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.262,603] <err> os: Current thread: 0x2000f7e0 (unknown)
*** Booting nRF Connect SDK v2.5.0 ***Resetting system

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Tue, 21 Nov 2023 18:02:11 GMT

I started from scratch. I unzipped your file and opened existing application and rebuilt the application. I still get the errors. below is my screen shot similar to yours. what am I doing wrong or missing?

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Tue, 21 Nov 2023 17:09:17 GMT

I get similar messages if I just build the LTE App unchanged.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Tue, 21 Nov 2023 16:34:22 GMT

I'm afraid I don't have an explanation for why it is failing to build now. I had a coworker try the same project I uploaded here, and he couldn't reproduce the issue either.

Here's a screenshot of what I'm seeing after building the project for comparison:

But did you try with the Cellular: LTE Sensor Gateway sample? As mentioned earlier, I took must of my changes from that project, so it would be interesting to know if it results in the same errors or not.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Tue, 21 Nov 2023 16:06:59 GMT

errors now are shown below. A different undefined. I was hoping the sample Bluetooth/central_uart would be the simple way to connect to the Bluetooth/peripheral_uart but that does not seem to work.

what am I missing?

zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj -L"c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/thumb/v8-m.main/nofp" -LC:/Nordic1/test_n160/central_uart_n9160/build/zephyr -lgcc zephyr/arch/common/libisr_tables.a -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfp16-format=ieee -Wl,--gc-sections -Wl,--build-id=none -Wl,--sort-common=descending -Wl,--sort-section=alignment -Wl,-u,_OffsetAbsSyms -Wl,-u,_ConfigAbsSyms -nostdlib -static -Wl,-X -Wl,-N -Wl,--orphan-handling=warn -Wl,-no-pie -DPICOLIBC_INTEGER_PRINTF_SCANF C:/Nordic1/v2.5.0/nrfxlib/crypto/nrf_cc310_platform/lib/cortex-m33/soft-float/no-interrupts/libnrf_cc310_platform_0.9.18.a --specs=picolibc.specs -lc -lgcc && cmd.exe /C "cd /D C:\Nordic1\test_n160\central_uart_n9160\build\zephyr && C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.exe -E true""
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `uart_irq_rx_disable':
C:\Nordic1\test_n160\central_uart_n9160\build\zephyr\include\generated\syscalls\uart.h:278: undefined reference to `__device_dts_ord_123'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `z_impl_uart_irq_rx_enable':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:960: undefined reference to `__device_dts_ord_123'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `uart_irq_tx_disable':
C:\Nordic1\test_n160\central_uart_n9160\build\zephyr\include\generated\syscalls\uart.h:230: undefined reference to `__device_dts_ord_123'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `h4_send':
C:\Nordic1\v2.5.0\zephyr\drivers\bluetooth\hci\h4.c:490: undefined reference to `__device_dts_ord_123'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `uart_fifo_read':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:820: undefined reference to `__device_dts_ord_123'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj):C:\Nordic1\v2.5.0\zephyr\drivers\bluetooth\hci\h4.c:560: more undefined references to `__device_dts_ord_123' follow
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\Nordic1\test_n160\central_uart_n9160\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Tue, 21 Nov 2023 15:40:44 GMT

Not sure what I'm missing, but it should not have been neccessary to add the overlay manually. As I test, can you try to remove the build folder, then set up the build configuration again, but this time with the board revision set to 1.1.0?

Edit: the "\hci\h4.c:560: more undefined references to `__device_dts_ord_118' follow" error likely means the CONFIG_NRF_SW_LPUART symbol did not get enabled in your build. It should habe been enabled by the central_uart/boards/nrf9160dk_nrf9160_ns.conf file.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Tue, 21 Nov 2023 15:30:54 GMT

I had left out the second overlay file. It does build a configuration file now but when I go to build it I get the following errors. I am still missing something. any ideas?

[291/298] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map
cmd.exe /C "cd . && C:\Nordic1\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf && cmd.exe /C "cd /D C:\Nordic1\test_n160\central_uart_n9160\build\zephyr && C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.exe -E true""
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `uart_irq_rx_disable':
C:\Nordic1\test_n160\central_uart_n9160\build\zephyr\include\generated\syscalls\uart.h:278: undefined reference to `__device_dts_ord_118'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `z_impl_uart_irq_rx_enable':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:960: undefined reference to `__device_dts_ord_118'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `uart_irq_tx_disable':
C:\Nordic1\test_n160\central_uart_n9160\build\zephyr\include\generated\syscalls\uart.h:230: undefined reference to `__device_dts_ord_118'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `h4_send':
C:\Nordic1\v2.5.0\zephyr\drivers\bluetooth\hci\h4.c:490: undefined reference to `__device_dts_ord_118'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj): in function `uart_fifo_read':
C:\Nordic1\v2.5.0\zephyr\include\zephyr\drivers\uart.h:820: undefined reference to `__device_dts_ord_118'
c:/nordic1/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/bluetooth/libdrivers__bluetooth.a(h4.c.obj):C:\Nordic1\v2.5.0\zephyr\drivers\bluetooth\hci\h4.c:560: more undefined references to `__device_dts_ord_118' follow
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\Nordic1\test_n160\central_uart_n9160\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Tue, 21 Nov 2023 15:04:13 GMT

Does your build configuration look identical to mine here:

? From the build log you posted, we can see the 9160 overlay is picked up by the build system, but I don't understand the reference to the nrf21540dk here: Bc:\Nordic1\test_n160\central_uart_n9160\build' -GNinja -DBOARD=nrf21540dk_nrf52840 -

It would also be interesting to know if you receive the same error if you build the Cellular: LTE Sensor Gateway sample.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Timothy — Tue, 21 Nov 2023 14:39:07 GMT

Vidar: thank you for your quick response. I tried to build a configuration and it failed with the information shown below. what am I doing wrong? I unzipped the file and tried to configure as I have done with all of the other samples.

-- Found devicetree overlay: boards/nrf9160dk_nrf9160_ns.overlay
In file included from <command-line>:
./boards/nrf9160dk_nrf9160_ns.overlay:1:10: fatal error: nrf9160dk_nrf52840_reset_on_if5.dtsi: No such file or directory
1 | #include <nrf9160dk_nrf52840_reset_on_if5.dtsi>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
CMake Error at C:/Nordic1/v2.5.0/zephyr/cmake/modules/extensions.cmake:3885 (message):
failed to preprocess devicetree files (error code 1):
C:/Nordic1/v2.5.0/zephyr/boards/arm/nrf21540dk_nrf52840/nrf21540dk_nrf52840.dts;boards/nrf9160dk_nrf9160_ns.overlay
Call Stack (most recent call first):
C:/Nordic1/v2.5.0/zephyr/cmake/modules/dts.cmake:226 (zephyr_dt_preprocess)
C:/Nordic1/v2.5.0/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
C:/Nordic1/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/Nordic1/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:8 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\Nordic1\toolchains\c57af46cb7\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/Nordic1/toolchains/c57af46cb7/opt/bin/python.exe '-Bc:\Nordic1\test_n160\central_uart_n9160\build' -GNinja -DBOARD=nrf21540dk_nrf52840 -DNCS_TOOLCHAIN_VERSION:STRING=NONE -DCONF_FILE:STRING=c:/Nordic1/test_n160/central_uart_n9160/prj.conf -DDTC_OVERLAY_FILE:STRING=boards/nrf9160dk_nrf9160_ns.overlay '-DBOARD_ROOT:STRING=c:/nordic1/test/peripheral_uart;c:/nordic1/test/ble_prototype;c:/nordic1/test/i2c_api;c:/nordic1/test_n160/asset_tracker_v2_n9160;c:/nordic1/test_n160/central_uart_n9160;.' '-Sc:\Nordic1\test_n160\central_uart_n9160'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

Vidar Berg — Tue, 21 Nov 2023 14:24:11 GMT

Hello,

Attached is a modified version of the Central UART sample, which you can program to the nRF9160 on the nRF9160 DK (use the 'nrf9160dk_nrf9160_ns' build target). You can see the changes I made in the 'changes.diff' file bundled with the zip. It was mostly just copy-and-paste from the Cellular: LTE Sensor Gateway sample.

Attachment (tested with SDK v.2.5.0)

devzone.nordicsemi.com/.../6431.central_5F00_uart.zip

Best regards,

Vidar

Edit: forgot to add that you need to program the LP HCI UART sample to the nRF52840 on the board for BLE connectivity: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/samples/cellular/lte_ble_gateway/README.html#programming-the-sample

BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

undefined reference to __device_dts_ord_<N>¶

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

RE: BLE communication between a nRF52 DK board and a nRF9160 DK board

undefined reference to `__device_dts_ord_<N>`¶