Mbed forum

Manifest rejected, certificate not found

mbed_client

(Greg __) #1

Hello, I am trying to run the FW update following the demo example (pelion-example-disco-iot01) on the ST Disco IoT L475 but the update always fails. The log I get from Pelion is:

January 10, 2019 11:43:10 AM FAIL Device failed to reach desired state Campaign: Update campaign 2019-01-10 11:42
January 10, 2019 11:43:10 AM INFO Idle
January 10, 2019 11:43:10 AM FAIL Manifest rejected, certificate not found Campaign: Update campaign 2019-01-10 11:42

I don’t think I am doing anything weird but, despite trying several time, I always get the same result.
Am I missing something?


(shai feldman) #2

A few things to check:

  1. Can you let us know the versions of all items involved – mbed OS, cloud-client, python, etc. I believe, the manifest tool is very particular about the python version being used.
  2. Are you using a developer certificate or one of your own certificates?
  3. Mbed commands have verbose, very-verbose options to get diagnostic output.
    4.Did you follow - https://cloud.mbed.com/docs/v1.2/updating-firmware/updating-end-to-end.html

Hope this helps.

Thanks, Shai

ARM Mbed cloud Support


(Janne Kiiskilä) #3

The default validity period for the update certificates can also be an issue. Please check the certificates are still valid from validity timeframe point of view. Default was apparently 90 days, which is not that long a time.