lte_ble_gateway does not run for more than 30 minutes

[Marshed]

Hi, 

I am have programmed my Thingy 91 device with lte_ble_gateway program to collect data from 5 bluetooth devices and send them to the cloud. This program runs fine, however it does not appear to continue to run for more than half an hour, after that the program just goes silent. No output, no error message no nothing. 

Can someone point me in the right direction please?

[Kenneth]

I can't find similar reports, have you pulled down the v1.3 release (or master)?
http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.0/nrf/samples/nrf9160/lte_ble_gateway/README.html

Any difference if the thingy:91 is powered through USB (or not)?

Kenneth

[Marshed]

I am using this version lte_gateway_thingy91_v1.1.0_R2.zip posted on this https://devzone.nordicsemi.com/f/nordic-q-a/52689/nrf9160-lte-sensor-gateway-on-thingy-91/217018 I am powering it using USB and it displays this error in the beginning 

<wrn> bt_hci_core: opcode 0x0000 pool id 5 pool 0x200312bc != &hci_cmd_pool 0x20031298

and when it crushes I get this error code 

<wrn> bt_driver: Discarding event 0x3e

[Sigurd]

Hi,

If you have a debugger/nRF9160-DK and a 10-pin cable available, could you try to connect it to the Thingy:91, and enable logging over Segger RTT ? If you are using the nRF52840 USB-UART bridge for logging, and the nRF52840 crashed, then you might get some more information in the RTT logs about why the device crashed.

It might not be directly related to this issue, but if you are still on NCS v1.1.0, you might want to consider updating to a newer version. E.g. NCS v1.2.0 or v1.3.0.

For NCS v1.2.0, I created this updated patch for the Thingy:91 LTE Gateway a couple of months ago:

Thingy91_gateway_ble_NCS-v1.2.zip

[Marshed]

how do you enable logging over Segger RTT? (I have the nRF9160-DK and I use it to program the Thingy:91)

[Sigurd]

See this link: http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/tools/nordic_segger.html#rtt-console

[Marshed]

this is what I see in the logger 

<wrn> bt_ctlr_hci: type: 0x14

and this is what I see in the putty 

<wrn> bt_driver: Discarding event 0x3e

this time it did last 16 hours, but eventually it did crush with the same errors 

[Sigurd]

Marshed said:

this time it did last 16 hours

 1) Are you sure that the device is not e.g. running out of battery power ?

Warning should not make the device crash.

2) I assume this log is from the nRF9160 ?

How does the RTT log from the nRF52840 looks like when this happens?

3) What NCS version are you on?

4) Do you have CONFIG_BT_DATA_LEN_UPDATE set to y or n ?

5) Are you able to pause the debugger when this happens, and see where the program counter is / what the CPU is doing ?

[Marshed]

1) the device is not running out fo battery as it is powered on through usb

2) the log is from nRF9160, and the RTT log is from nRF52840, I haven't seen anything on the nRF52840 side

3) I have tried this on v1.1.0 and 1.2.0 they both give me the same problem

4) I have #define CONFIG_BT_DATA_LEN_UPDATE 1 in autoconf.h file of the program, however I do not see this anywhere else, where should this be set?

[Marshed]

Dear Sigurd, 

I am still stuck on the same errors, 

can you assist please?

[Sigurd]

I have not been able to reproduce the issue.

Do you see anything else in the log, if you enable this ?

CONFIG_BT_DEBUG_HCI_CORE=y
CONFIG_BT_DEBUG_HCI_DRIVER=y

[Marshed]

Hi Sigurd

where should i enable this, in the NRF52840 or NRF9160?

as for the error

 

<wrn> bt_driver: Discarding event 0x3e

I have managed to remove it by switching off scanning for Bluetooth devices after connecting to the intended 5 devices. However now the program runs fine for a while (a day or two),  after that the program just goes silent. No output, no error message no nothing.