Debugging MQTT on nrf9160dk

RE: Debugging MQTT on nrf9160dk

LordLucan — Tue, 23 Feb 2021 09:14:41 GMT

Thank you for this. That is helpful information. I'll roll back to previous SDK version and see if I can determine what the original problem was.

Regards,

Paul

RE: Debugging MQTT on nrf9160dk

Simon — Mon, 22 Feb 2021 17:20:02 GMT

You could try setting these in the prj.conf:

CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_LOG=y

Then the system won't reset when an error happens, and if you open Termite and connect it to your board, you'll be provided with information about the fault that happened.

You could also test out SEGGER Ozone for debugging: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/tools/nordic_segger.html#segger-ozone

Best regards,

Simon

RE: Debugging MQTT on nrf9160dk

LordLucan — Mon, 22 Feb 2021 12:44:01 GMT

I tried upgrading to SDK 1.5.0-RC1 and it all seems to work now!

I think there must be a subtle bug somewhere in Zephyr RTOS that has been fixed. But my questions above still stand. It is very frustrating when Zephyr constantly reboots not being able to get any idea why.

RE: Debugging MQTT on nrf9160dk

LordLucan — Sat, 20 Feb 2021 10:06:20 GMT

I should add this is with SDK 1.4.2