I am using:
- nRF Connect SDK 3.4.0
- SDK Tools 3.4.0
- Asset Tracker Template
- Thingy91X / nRF9151
- CoAP cloud connection
The device successfully connects to nRF Cloud and reports:
SW type: app
SW version: 0.0.1
HW version: thingy91x
I created an OTA Release 0.0.3 in the new nRF Cloud OTA Experience (Memfault-based OTA Releases). The release is activated for cohort 3rd_ota, and the cohort view shows:
Current version: 0.0.1 (app) (thingy91x)
Future version: 0.0.3
Device count: 1
The device is the single member of that cohort.
However:
Asset Tracker FOTA path
Running:
att_fota poll
results in:
nrf_cloud_fota_poll: Checking for FOTA job...
nrf_cloud_fota_poll: No pending FOTA job
Memfault OTA path
Running:
mflt get_latest_release
results in:
mflt: FOTA Update Available
mflt: FOTA Update Available. Starting Download with URL: ...
mflt: FOTA start failed, rv=-5
I stepped through the code and confirmed that:
fota_download_any(...) returns: -5
The device therefore sees the OTA Release through the Memfault path, but the Asset Tracker Template FOTA module does not see a pending FOTA job.
Question
For SDK 3.4.0 Asset Tracker Template:
- Is
att_fota pollexpected to work with the new OTA Release / Cohort / Activation workflow? - Is the Asset Tracker Template expected to use the Memfault OTA path instead?
- Is the
rv=-5fromfota_download_any()a known issue or indicative of a missing configuration? - Are there any additional Kconfig settings required when using the new OTA Release system?
