Thingy91: LTE BLE Gateway with Modem Info

[Cody]

I have been closely following this thread (https://devzone.nordicsemi.com/f/nordic-q-a/52689/nrf9160-lte-sensor-gateway-on-thingy-91/217018) to provide support for the LTE BLE Gateway sample on the Thingy91. The patch provided in the thread is working and I am able to scan and receive nearby BLE devices.

My question is, now that I have the BLE gateway working on the Thingy91, I am looking to enable modem info via the modem_info library - is this a supported configuration?

When I attempt to enable the modem info library I get the following error message:

[00:00:00.233,947] <err> at_host: Cannot bind UART_0
[00:00:00.334,045] <err> at_host: UART could not be initialized: -22

I am assuming it has something to do with the UART configuration needed for the HCI bluetooth interface, any assistant would be helpful.

[Simon]

I was able to enable the modem info library in the lte_ble_gateway example on the Thingy:91. Could you test the example I provided and see if it works for you?

merged.hex

lte_ble_gateway.zip

Best regards,

Simon

[Dheeraj]

Hi Simon, 

I have flashed the above image "merged.hex", to get the BLE values on thingy91 (nrf9160_pca20035ns). 

Before this, I have flashed respective hci_uart on nrf52840 (PCA20035)

I followed the " https://devzone.nordicsemi.com/f/nordic-q-a/52689/nrf9160-lte-sensor-gateway-on-thingy-91/217018 "

But unfortunately, the kernel is panicked, Please find the below RTT viewer logs.

/******************************  LOGS  ************************************/

# SEGGER J-Link RTT Viewer V6.54c Terminal Log File
# Compiled: 17:04:11 on Nov 7 2019
# Logging started @ 12 Dec 2019 20:54:08

00> Application started
00>
00> Initializing Bluetooth..
00>
00> Establishing LTE link (this may take some time) ...
00>
00> ASSERTION FAIL [err == 0] @ C:/Nordic/nRFConnectSDK/whatever/ncs/zephyr/subsys/bluetooth/host/hci_core.c:340
00>
00> k_sem_take failed with err -11
00>
00> [00:00:10.473,144] <err> os: r0/a1: 0x00000004 r1/a2: 0x00000154 r2/a3: 0x00000002
00> [00:00:10.473,1400> [00:00:10.473,144] <err> os: r3/a4: 0x20020cb8 r12/ip: 0x00000000 r14/lr: 0x000174f7
00> [00:00:10.473,144] <err> os: xpsr: 0x4100> [00:00:10.473,144] <err> os: xpsr: 0x41000000
00> [00:00:10.473,175] <err> os: s[0]: 0x00000000 s[1]: 0x00000000 s[2]: 0x00000000 s[3]: 0x00000000
00>
00> [00:00:10.473,175] <err> 00> [00:00:10.473,175] <err> os: s[4]: 0x00000000 s[5]: 0x00000000 s[6]: 0x00000000 s[7]: 0x00000000
00>
00> [00:00:10.473,205] <err> os: s[8]: 0x00000000 s[9]: 0x00000000 s[10]:00> [00:00:10.473,205] <err> os: s[8]: 0x00000000 s[9]: 0x00000000 s[10]: 0x00000000 s[11]: 0x00000000
00>
00> [00:00:10.473,205] <err> os: s[12]: 0x00000000 s[13]: 0x00000000 s[14]: 0x00000000 00> [00:00:10.473,205] <err> os: s[12]: 0x00000000 s[13]: 0x00000000 s[14]: 0x00000000 s[15]: 0x00000000
00>
00> [00:00:10.473,236] <err> os: fpscr: 0x00018b15
00>
00> [00:00:10.473,266] <err> os: Faulting instruction address (r15/pc): 0x00000> [00:00:10.473,266] <err> os: Faulting instruction address (r15/pc): 0x00039ad6
00> [00:00:10.473,266] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic
00> [00:00:10.473,266] <err> os: Current thre00> [00:00:10.473,266] <err> os: Current thread: 0x200283a4 (unknown)
00> [00:00:10.876,190] <err> os: Halting system
# Logging stopped @ 12 Dec 2019 20:55:14

 /*****************************      End of Logs       **********************************/

Please let me know if I am missing anything, to the BLE values on Thingy91 (PCA20035), as its blocking the production. 

Thank you for your help.