Hello @ChrisGammell, I make a new Topic because the problem is different.
Updating ncs to 2.4.0 solved topic https://forum.golioth.io/t/error-in-poll-95. I think there was some issue with the socket absed on error 95 that mean operation not supported on socket.
Now while typing this reply I had this, previously nothing happens.
I’ve upload artifact and turn on rollout. I’m pretty sure that part is correct.
it connects 'cause the console says:
After adding some logging to zcbor_utils I found the issue was cause by num_decoded < num_entries in zcbor_utils.c. It never enter the while cycle.
What I have to do? Thanks in advance.
From the console logs you shared, it looks like the returned manifest is empty (a0 is the CBOR empty map), suggesting there is not a rollout that meets the criteria for the device. Maybe check the device tags and/or blueprints against the release configuration to see if the device is supposed to get it.
I tried with your sample and I’ve the same output, I think I made a mistake in the artifact settings, could you provide an exhaustive example on how blueprints, tags, artifacts and releases have to set. Is a problem if I build the binary for the artifact with the provided vscode nrf extension instead of with the west command in cli?
If you create a release that does NOT specify a blueprint and does not have any device tags, the device should get the release. I’ve taken a screenshot of creating such a release.
I’ve tried right now your suggestion and all works fine, I think the problem was in the settings of blueprint or tag, could you provide me a working example of both? Thank you very much @tim, finally after months I can do ota dfu.