Nordic thingy 91 Azure Iot Sample gives UART FRAMING error

[JSMdev]

I am trying to add a Nordic Thingy 91 to my azure Iot hub. 

i've configured the device according to the guide 

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/networking/azure_iot_hub.html#prerequisites-for-connecting-to-azure-iot-hub

I've provisioned the ceritificates,  and I have the sample code working on a 9160 DK. I am now trying to do the same with a  Thingy 91. Im om course using another set of device name, certificates and sercurity tags. 

I am using the DK to flash the NordicThingy91, which works fine. I'm then using the LTE link Monitor tool for the terimnal to look at the results. 

I have enabled 

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_AT_CMD_LOG_LEVEL_DBG=y

CONFIG_LTE_LINK_CONTROL_LOG_LEVEL_DBG=y

Im using VScode with the NRF connect extension. Im doing an "erase and flash".

I am not sure if the UART error even.  When running the code withouth any debug i get the following result:

Any help is appreciated!

it runs twice and produvces this error on the first run:

The next run it gives teh same, withouth the UART error

--------------------------- New first error ----------

[Charlie]

Hi Johannes,

Do you have any problem without changing the prj.conf file? I tested with the latest nRF9160: Azure IoT Hub — nRF Connect SDK 1.9.0 documentation (nordicsemi.com) and did not able to repeat your issue. Could you test with this version(NCS 1.9.0)?

For the changes you made:

CONFIG_BOOTLOADER_MCUBOOT=y # this is set by default, not necessary.

CONFIG_AT_CMD_LOG_LEVEL_DBG=y # this should replace by CONFIG_AT_MONITOR_LOG_LEVEL_DBG=y.

CONFIG_LTE_LINK_CONTROL_LOG_LEVEL_DBG=y # this is OK.

You can check the final configuration used by the building process build\zephyr\.config

Best regards,

Charlie

[JSMdev]

Will get back to you when done. Thanks.