Unable to do FOTA since nRF cloud migrated to memfault

[RossJ]

I am unable to perform a fota on an nrf9160 based device in the field since my nrfcloud account was updated to require the use of the new memfault based version. There was no issue with this on the old platform.

Observing the log on the target device I see...

[00:00:15.172,180] <inf> download_client: Setting up TLS credentials, tag 16842753
[00:00:15.172,302] <inf> download_client: Connecting to fw.nrfcloud.com
[00:00:17.140,869] <inf> download_client: Downloading: firmwares/10624/ota-payloads/35689285308?expire=1790177456&token=OiiHgU5j7O4vTg [0]
[00:00:17.140,899] <inf> nrf_cloud_fota: Downloading update
[00:00:17.909,393] <err> download_client: Error in recv(), errno 122
[00:00:17.909,393] <wrn> fota_download: Download socket error. 2 retries left...
[00:00:17.909,423] <inf> download_client: Reconnecting..

nRFcloud related config...

# nRF Cloud
CONFIG_NRF_CLOUD_MQTT=y
CONFIG_NRF_CLOUD_FOTA=y
CONFIG_NRF_CLOUD_AGPS=y
CONFIG_NRF_CLOUD_ALERTS=y
CONFIG_NRF_CLOUD_CLIENT_ID_SRC_IMEI=y
CONFIG_NRF_CLOUD_CLIENT_ID_PREFIX="cxe-"
CONFIG_NRF_CLOUD_LOG_LEVEL_INF=y

# MQTT
CONFIG_MQTT_KEEPALIVE=120

# Download Client
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_HTTP_FRAG_SIZE_1024=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_DOWNLOAD_CLIENT_BUF_SIZE=2300
CONFIG_DOWNLOAD_CLIENT_MAX_HOSTNAME_SIZE=128

This behavior is consistent. Error 122 (EMSGSIZE) appears to be related to insufficient buffer size. That's a problem for the hundreds of devices we have in the field if the FOTA can't be run without first changing the firmware!
Our devices were built with SDK 2.3.0 (mfw 1.3.5). nRF cloud comm is via MQTT.

[Carl Richard]

Hello Ross!

Thanks for reaching out. I'm just notifying you to say that we're looking into this.

Best regards,
Carl Richard

[Chris Coleman]

Hi Ross, thanks for the report. We identified a TLS interoperability issue with the older version of NCS you are using and have deployed an improvement to handle this. Could you retry on your side now and confirm you now see the update succeed?

Thanks,

-Chris

[RossJ]

Thanks Chris, the fix seems to have done the trick. I've successfully applied a FOTA.

One other question about the transition of our account to memfault... When the devices were copied over, only a small number (5%) of the names were converted to nicknames. I gather the bulk update doesn't allow the nickname to be applied? Is a custom script using the REST api the best way to get these back or is there another option? I assume mine is not the only account where this has happened...