lte_ble_gateway fails with NCS 2.2 and thingy:91 rev 1.6.0

[Jonathan E]

Hi!

I am building an application that is based on the lte_ble_gateway which works perfectly on the nrf9160dk. However, it does not work on the thingy:91.
The error is also present in the unmodified lte_ble_gateway sample, so it should be easy to reproduce.

I am trying to run lte_ble_gateway to a thingy:91 rev 1.6.0, but get the following error message when running the application:
** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.487,274] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.487,426] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.504,943] <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:329
k_sem_take failed with err -11
[00:00:10.497,924] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00000002
[00:00:10.497,955] <err> os: r3/a4: 0x2000e168 r12/ip: 0x20016e78 r14/lr: 0x000223b3
[00:00:10.497,955] <err> os: xpsr: 0x41000000
[00:00:10.497,985] <err> os: Faulting instruction address (r15/pc): 0x000223be
[00:00:10.498,016] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.498,046] <err> os: Current thread: 0x2000eea0 (unknown)
[00:00:10.720,733] <err> fatal_error: Resetting system

Output from nrf52840:
*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.000,671] <inf> sdc_hci_driver: SoftDevice Controller build revision:
6d 90 41 2a 38 e8 ad 17 29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
1f 85 d8 e1 |....
[00:00:00.001,312] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
[00:00:01.001,373] <wrn> lpuart: Tx timeout
[00:00:02.002,166] <wrn> lpuart: Tx timeout
[00:00:03.002,990] <wrn> lpuart: Tx timeout
[00:00:04.003,814] <wrn> lpuart: Tx timeout
[00:00:05.004,638] <wrn> lpuart: Tx timeout
[00:00:06.005,462] <wrn> lpuart: Tx timeout
*** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:00.000,671] <inf> sdc_hci_driver: SoftDevice Controller build revision:
6d 90 41 2a 38 e8 ad 17 29 a5 03 38 39 27 d7 85 |m.A*8... )..89'..
1f 85 d8 e1 |....
[00:00:00.001,312] <inf> bt_hci_raw: Bluetooth enabled in RAW mode

I build lte_ble_gateway with the command:
west build --board [email protected]

and hci_lpuart:
west build --board [email protected]

I have managed to get the sample working for the nrf9160DK earlier (Where I had to build with west build --board [email protected] for hci_lpuart and [email protected] for lte_ble_gateway)

I have looked at this post, but it is not an option to downgrade to NCS 1.9.X: devzone.nordicsemi.com/.../382953

Additionally, it is really tidious to debug as the flashing process fails 70% of the time and the nrf9160dk disappears from discovered devices, which means that I must reboot my computer. Any tips on this would also be greatly appreciated.

Thanks in advance for your help.

[dejans]

Hi,

You could try to disable UART for MCUboot. To do this you could add an overlay file mcuboot.overlay in the child image folder for both hci_lpuart and lte_ble_gateway.

&uart1 {
	/delete-property/ rts-pin;
	/delete-property/ cts-pin;	
	/delete-property/ hw-flow-control;
	status = "disabled";
};

Best regards,
Dejan

[Jonathan E]

Unfortunately, that doesn't seem to solve the issue. I also get these warnings when compiling if it is relevant:

HCI_LPUART:
warning: BT_CTLR_DTM_HCI (defined at subsys/bluetooth\controller\Kconfig.dtm:14) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: BT_CTLR_DTM_HCI_SUPPORT (=n).
See docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_DTM_HCI in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

warning: BOOTLOADER_MCUBOOT (defined at C:/Users/jonat/ncs/v2.2.0/nrf/modules/trusted-firmware-m/Kconfig:178, Kconfig.zephyr:745) was assigned the value 'y' but got the value 'n'. Check
these unsatisfied dependencies: (BUILD_WITH_TFM || !MCUBOOT) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BOOTLOADER_MCUBOOT in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

LTE_BLE_GATEWAY:
CMake Warning at C:/Users/jonat/ncs/v2.2.0/zephyr/cmake/modules/boards.cmake:127 (message):
Board revision 1.6.0 specified for thingy91_nrf9160, but board has no
revision so revision will be ignored.
Call Stack (most recent call first):
C:/Users/jonat/ncs/v2.2.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
C:/Users/jonat/ncs/v2.2.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/Users/jonat/ncs/v2.2.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:44 (find_package)

[dejans]

Hi,

A colleague who could look into this issue is currently on vacation hence the reply might be delayed.

I will get back to you when I get more information related to your problem.

Thank you for your patience.

Best regards,
Dejan 

[Jonathan E]

Hi.

Any progress?

On another note, I also found out that the sample doesn't seem to work on the nrf9160dk when using NCS 2.4.1 with similar issues. Not a problem for me, but it might be worth investigating.

[dejans]

Hi,

Jonathan E said:

Any progress?

I am sorry for delayed reply. I was out of the office. I have contacted the developers again. I will get back to you as soon as I get relevant information. Thank you for your patience.

Jonathan E said:

On another note, I also found out that the sample doesn't seem to work on the nrf9160dk when using NCS 2.4.1 with similar issues. Not a problem for me, but it might be worth investigating.

Thank you for providing additional information.

Best regards,
Dejan

[dejans]

Hi,

I have made more tests on my end, but the issue is still present. I am still trying to get more information about this issue from developers.  Although theoretically this combination of samples could work on Thingy91, I got general recommendation that it should be used on nrf9160-DK, not on Thingy91. In your case, please continue using nrf9160-dk instead of Thingy91.

Best regards,
Dejan

[Jonathan E]

Using the nrf9160-dk is not suitable for my use case. I have to make the Thingy:91 function properly as this is what I am going to use as a bridge for a while with customers until we make our own gateway. It would be highly appreciated if you can help me make the sample work.

Best regards,

Jonathan Eide

[dejans]

Hi,

Could you provide information about your use case?

Best regards,
Dejan

[Jonathan E]

Several BLE devices will transmit data to the internet via a thingy:91 using BLE-connections and LTE-M. I have adapted the lte_ble_gateway for my specific needs which works perfectly on the nrf9160-dk, but not on the thingy:91 (because of the error we have discussed here). The thingy:91 is a perfect bridge for my project, because of its small packaging, battery, and price, and I have already acquired 20 devices.

[dejans]

Hi,

Thank you for providing this information.

I have reached out to developers again. 

Best regards,
Dejan

[dejans]

Hi,

Could you try to change status of uart1 in Thingy91 dts files to "disabled" as shown in this pull request?

Best regards,
Dejan

[Jonathan E]

Hi!

It seems like it worked! Thank you very much.

When can we expect this update to be in the SDK?

-Jonathan