Attachments (2) Download All
Nordic Case Info
  • Case ID: 294029
Options

nRF9160: LTE Sensor Gateway ASSERTION FAIL on Thingy:91 (nRF Connect SDK v2.0.2)

Per

I have been trying for hours to get the LTE Sensor Gateway sample to work on my Thingy:91 (PCA20035) without success. According to the v2.0.2 README and the HCI low power UART board definitions it should be supported.

However, compiling out-of-the box, Segger RTT always shows the same assertion error:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
*** Booting Zephyr OS build v3.0.99-ncs1-1 ***
[00:00:00.538,543] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.538,696] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.558,776] <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:309
k_sem_take failed with err -11
[00:00:10.549,194] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000002 r2/a3: 0x00000001
[00:00:10.549,194] <err> os: r3/a4: 0x2000da00 r12/ip: 0x200161d0 r14/lr: 0x000220c10m
[00:00:10.549,224] <err> os: xpsr: 0x41000000
[00:00:10.549,224] <err> os: Faulting instruction address (r15/pc): 0x000220cc
[00:00:10.549,255] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.549,285] <err> os: Current thread: 0x2000ef50 (unknown)
[00:00:10.774,536] <err> fatal_error: Resetting system
*** Booting Zephyr OS build v3.0.99-ncs1-1 ***
[00:00:00.535,980] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.536,132] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.553,863] <inf> lte_ble_gw: Establishing LTE link (this may take some time) ...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


I know this has been encountered by other users,e.g. in this older post, but that was on an unsupported version of the SDK, and the workarounds do not work for me.


To reproduce:

1. Ensure that the modem driver is up to date, according to Getting started with Thingy:91. In fact, I started of with a working Asset Tracker V2 before trying out the LTE Sensor Gateway
2. Refresh v2.0.2:

Fullscreen
1
2
3
git fetch origin
git checkout v2.0.2
west update
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

3. Connect the SEGGER to the 10 pins SWD.
4. Turn off Thingy:91 and set the SW2 switch to nRF52. Turn ON Thingy:91
5. In nrf/samples/bluetooth/hci_lpuart:

Fullscreen
1
2
west build -p -b thingy91_nrf52840
nrfjprog --program ./build/zephyr/merged.hex --chiperase --reset
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Build output: 
Fullscreen 6014.build.txt Download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
-- west build: making build dir /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart
-- Found Python3: /usr/bin/python3.8 (found suitable exact version "3.8.10") found components: Interpreter
-- Cache files will be written to: /home/per/.cache/zephyr
-- Zephyr version: 3.0.99 (/home/per/sandboxes/ncs/zephyr)
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
-- Board: thingy91_nrf52840
-- Found dtc: /usr/bin/dtc (found suitable version "1.5.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/home/per/gnuarmemb)
-- Found BOARD.dts: /home/per/sandboxes/ncs/nrf/boards/arm/thingy91_nrf52840/thingy91_nrf52840.dts
-- Found devicetree overlay: /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/boards/thingy91_nrf52840.overlay
-- Generated zephyr.dts: /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: /home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build/zephyr/dts.cmake
/home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build/zephyr/zephyr.dts:53.25-59.5: Warning (unique_unit_address_if_enabled): /soc/clock@40000000: duplicate unit-address (also used in node /soc/power@40000000)
/home/per/sandboxes/ncs/nrf/samples/bluetooth/hci_lpuart/build/zephyr/zephyr.dts:313.21-317.5: Warning (unique_unit_address_if_enabled): /soc/acl@4001e000: duplicate unit-address (also used in node /soc/flash-controller@4001e000)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

6. Turn off Thingy:91, set to SW2 switch to nRF91 and turn on again:
7. In nrf/samples/nrf9160/lte_ble_gateway:
Fullscreen
1
2
west build -p -b thingy91_nrf9160_ns
nrfjprog --program ./build/zephyr/merged.hex --chiperase --reset
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Build output: build2.txt
8. Turn off and on, start JLink RTT Viewer and observe the faulty ouput shown above. Always constant reboot with the same assertion error


I have tried the sample with and without the external USB, same results. I also tried the latest commit in main for the example, got a different error message, but still no success:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
[00:00:00.522,338] <err> lpuart: err:0bad0002
[00:00:00.522,369] <err> lpuart: rdy pin init failed:-22
*** Booting Zephyr OS build v3.0.99-ncs1-2483-g482dcc7865f7 ***
[00:00:00.522,552] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.522,674] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.522,705] <err> bt_hci_core: No HCI driver registered
[00:00:00.522,735] <err> lte_ble_gw: Bluetooth init failed (err -19)
[00:00:00.529,968] <inf> lte_ble_gw: Establishing LTE link (this may take some time) ...
[00:00:08.984,741] <err> nrf_cloud_transport: Failed to save session state: -2
[00:00:08.985,656] <inf> lte_ble_gw: Initializing GNSS
[00:00:08.991,760] <inf> lte_ble_gw: GNSS initialized
[00:00:08.994,720] <inf> lte_ble_gw: Requesting AGPS Data
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



I hope the Thingy:91 is a supported platform for the sample and look forward to hear from you on this matter.
Regards,
Per

Terms of service