External TDB Requires Device ROT

[ghost]

Description of defect

Initially posted here: ARMmbed/mbed-os#13327

After testing, it seems that it is necessary to call DeviceKey::get_instance().device_inject_root_of_trust() before using kv store in external TBD mode (either with RBP or without). It would be helpful to update this example to include that.

Target(s) affected by this defect ?

N/A

Toolchain(s) (name and version) displaying this defect ?

N/A

What version of Mbed-os are you using (tag or sha) ?

N/A

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

N/A

How is this defect reproduced ?

Using kv store in external TBD mode

[0xc0170]

@ARMmbed/mbed-os-core

[ciarmcom]

@DMCEngineering thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[ciarmcom]

@DMCEngineering it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@DMCEngineering it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@DMCEngineering it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@DMCEngineering it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@DMCEngineering it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@DMCEngineering it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[evedon]

@DMCEngineering Thank you for reporting the issue. Since you were testing this use case, could you consider providing a fix? We appreciate your help to keep this example up to date.

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2832

[LDong-Arm]

Hi @DMCEngineering, I've created #66 to fix this, thanks.

[LDong-Arm]

Hi @evedon, would you please close this as it wasn't automatically closed by the PR?