Samples hci_lpuart + lte_ble_gateway not working on thingy91 SDKs v2.4.2, v2.3.0, v2.2.0

[0x35c]

Hi, I am programming on a thingy91 (and a nrf9160DK).
I have an app that uses hci_lpuart sample and used to be running with 1.9.1 sdk, the app is very similar to the lte_ble_gateway sample
I am migrating to a newer version (2.4.2) and I managed to make it work on my DK.
However, when I try to flash it on the thingy91, it will not be able to enable bluetooth (using bt_enable) because of what's going on with the 52 chip.
I can make both my app and the lte_ble_gw sample work on my DK (using hci_lpuart sample) but when trying to do the exact same thing on my Thingy91, nothing works and the bluetooth cannot be enable, no matter what I try.
I would like to know if I need to have any specific configuration (maybe a specific .overlay file or smth) as it's most likely that the problem comes from compatibility issues with the configuration build provided when getting the sample since I cannot even make a nordic sample work on my thingy.

Thanks for your answers.

Regards,

0x35c

[Susheel Nuguru]

The SDK you are using is a bit old. I would recommend using latest version for testing and prototyping.

Also check the hardware revision number for your Thingy and check if if the suggestions mentioned by my colleague Simon here helps to fix this issue.

[Susheel Nuguru]

Actually I found one more internal ticket under investigation that this is not working with newer SDK version and newer Thingy91 version as well. So this seems like a known bug (NCSIDB-1073). I will update the dev team that more developers are seeing this issue.

[0x35c]

I'm using sdk 2.4.2 which is the latest before 2.5, how is it old ?

[Susheel Nuguru]

I have an app that uses hci_lpuart sample and used to be running with 1.9.1 sdk,

From this above text you wrote, I thought you were using SDKv1.9.1.

But it seems that it does not matter as this issue seems to be there in the newer SDK as well with newer Thingy91 hardware versions. I requested dev team to bump up the priority to investigate this.

[0x35c]

Yes but I am doing a migration to 2.4.2, the migration is almost complete and the only remaining issue is with nrf52 chip specific to thingy (it works on the DK)