NRF52840_DK does not work by default

[c1728p9]

This example builds for the NRF52840 without errors but gets stuck in a loop removing files when run.
Example version: mbed-os-5.11.0-rc2 - 1bdc298
OS: Windows 10
Compiler: armcc
Board: NRF52840_DK

Test output:

> mbed compile -t ARM -m NRF52840_DK -f
...
> mbed sterm -b 115200 -r
[mbed] Detecting connected targets/boards to your system...
[mbed] Opening serial terminal to "NRF52840_DK"
--- Terminal on COM326 - 115200,8,N,1 ---
���j
9625) Re�--- Mbed OS KVStore static API example ---
kv_reset
kv_reset -> 265
kv_set first dummy key
kv_set -> 265
kv_get_info of first key
kv_get_info -> 265
kv_get_info key: /kv/dummy_key1
kv_get_info info - size: 0, flags: 139895
kv_get first key
kv_get -> 265
kv_get key: /kv/dummy_key1
kv_get value:
kv_set second dummy key
kv_set -> 265
kv_set third key with Confidentiality, Integrity and Replay Protection flags
kv_set -> 265
kv_set Set 'Real' Key 1
kv_set -> 265
kv_set Set 'Real' Key 2 with flag write-once
kv_set -> 265
Removing 'Dummy' Keys
1) Removing
2) Removing
3) Removing
4) Removing
5) Removing
6) Removing
7) Removing
8) Removing
9) Removing
...

[dannybenor]

@c1728p9 Please see the readme:
Note: The example is by default set to be used on K64F target with internal memory (see: mbed_app.json). If running in another target, make sure the target.json for the target includes the "components": ["FLASHIAP"] and device_has": ["FLASH"] or add this section to the example mbed_app.json.

[MarceloSalazar]

It looks a limitation of the NRF52840_DK platform.

[adbridge]

@MarceloSalazar is this still an issue then ? Or can it be closed?

[sarahmarshy]

@MarceloSalazar @adbridge @c1728p9 does this mean kvstore is not supported on NRF52840_DK?

[ciarmcom]

@c1728p9 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]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[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-3105