stack overflow

RE: stack overflow

Ben Li — Tue, 23 Aug 2022 04:41:59 GMT

Thank you so much it works!

RE: stack overflow

Simon — Mon, 22 Aug 2022 11:35:18 GMT

Actually I don't think you need to program the Thingy:52. By default it should be shipped with the hex file under https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-52/Download?lang=en#infotabs. Looking at your logs, you're able to connect to the Thingy:52, so it seems like the correct firmware is running (Thingy:52 should advertise with the following UUID).

In my case I had reprogrammed the Thingy:52 and used it for different stuff, so I had to program the correct firmware onto it. I used a 10-pin cable and the programmer on the nRF52 DK (Thingy:52 does not have a programmer itself), but I think it should be possible through OTA-DFU as well.

Try programming the 52840 and 9160 on the nRF91 DK, with the hex files I uploaded, and see if you encounter the issue.

RE: stack overflow

Ben Li — Mon, 22 Aug 2022 04:24:43 GMT

Sorry, I didn't know that I need to flash nrf52 with the thingyv210HW10.hex firmware. It was running on DFU mode the whole time. I've tried to flash the firmware onto thingy52 but it seems like thingy52 doesn't have a programmer. I also tried to use nrfstudio to flash thingy52 but it's using 64bit operating system so I can't get it installed. Is there a recommended way to flash thingy52? The only avaliable baords I have are nrf9160dk and thingy52.

Best,

Ben Li

RE: stack overflow

Simon — Sun, 21 Aug 2022 21:58:52 GMT

I still think it's strange that increasing CONFIG_BT_RX_STACK_SIZE did not resolve the issue. What value did you set it to? Would it be possible to try increasing it more?

RE: stack overflow

Simon — Sun, 21 Aug 2022 21:57:14 GMT

I just tested with a Thingy:52 v1.0.0 and an nRF9160 DK v1.0.0 and was not able to reproduce the issue, I got the following log:

*** Booting Zephyr OS build v3.0.99-ncs1  ***
+CEREG: 90
[00:00:00.493,041] <inf> lte_ble_gw: LTE Sensor Gateway sample started
[00:00:00.493,255] <inf> lte_ble_gw: Initializing Bluetooth..
[00:00:00.510,803] <inf> lte_ble_gw: Establishing LTE link (this may take some time) ...
[00:00:01.204,040] <wrn> bt_hci_core: opcode 0x0000 pool id 3 pool 0x20015304 != &hci_cmd_pool 0x2001536c
[00:00:01.255,310] <inf> lte_ble_gw: Bluetooth ready
[00:00:01.262,390] <inf> lte_ble_gw: Scanning...
[00:00:05.030,029] <inf> lte_ble_gw: Device found: CA:99:4C:95:7E:69 (random)
[00:00:05.416,290] <inf> lte_ble_gw: Connected: CA:99:4C:95:7E:69 (random)
[00:00:12.578,857] <inf> lte_ble_gw: Orientation: 0
[00:00:18.459,045] <inf> lte_ble_gw: Orientation: 1
[00:00:25.359,252] <inf> lte_ble_gw: Orientation: 2
[00:00:32.649,444] <inf> lte_ble_gw: Orientation: 0
[00:00:35.139,526] <inf> lte_ble_gw: Orientation: 3

I'll upload the exact hex files I used. Try to program them to the appropriate chips and see if you are able to reproduce the issue then:

nRF9160DK nRF9160: devzone.nordicsemi.com/.../lte_5F00_ble_5F00_gateway.hex
nRF9160DK nRF52840: devzone.nordicsemi.com/.../7367.hci_5F00_lpuart.hex
Thingy52: devzone.nordicsemi.com/.../thingyv210hw10.hex

Best regards,

Simon

RE: stack overflow

Ben Li — Sun, 21 Aug 2022 08:17:42 GMT

Hi Simon,

Yes I'm using NCS v2.0.0. I'm just trying to test it out with the LTE sensor gateway sample with the exact nrf9160dk and thingy:52. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/lte_ble_gateway/README.html I tried to run it out of the box without making anychanges, but I'm expericing these problems above. Then, I've tried changing the code. The only thing I've changed is the config stack size.

Best,

Ben Li

RE: stack overflow

Simon — Fri, 19 Aug 2022 09:13:45 GMT

Hmm.. I'll try to reproduce this myself. Based of the logs, it seems like you're using NCS v2.0.0, correct? Have you made any changes to the lte_ble_gateway sample, or did you run it out of the box?

Best regards,

Simon

RE: stack overflow

Ben Li — Fri, 19 Aug 2022 07:26:00 GMT

Hey Simon,

Thank you for your input. However, I'm still experiencing the same issue dispite I have increase the CONFIG_BT_RX_STACK_SIZE. Is there any debugging method you would recommend? Or is there anything else I should change here?

Best,

Ben Li

RE: stack overflow

Simon — Thu, 18 Aug 2022 13:54:07 GMT

Solution:

Try increasing CONFIG_BT_RX_STACK_SIZE.

Check the file <sample>/build/zephyr/.config what CONFIG_BT_RX_STACK_SIZE is currently set to and set it to a higher value in the prj.conf file.

Explanation:

I can see from your log that the overflow happened in the thread "bt_rx_thread". After searching for bt_rx_thread in the whole NCS, I figured out that this thread was created in zephyr/drivers/bluetooth/hci/h4.c, and if you look at line 38 in this file you see that the stack size is determined by CONFIG_BT_RX_STACK_SIZE