BLE: check flags to make sure the IRK has been stored before retrieving it

[paul-szczepanek-arm]

Description

Fix for IRK and BDADDR being read in without checking the storage is valid. Found through a new clitest SM_whitelist_generation_test_01.

Pull request type

[x] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 2318
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7123/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 1941
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7123/

[mbed-ci]

Test : FAILURE

Build number : 2097
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7123/2097

[0xc0170]

@studavekar Can you review the test results? One target fails, but from logs - all is success, so why failed? Only one target, target issue?

Update: console shows it

greentea/mbed_greentea/mbed_report_api.py", line 557, in get_result_overlay_testcase_dropdown
23:24:50     datetime.datetime.fromtimestamp(testcase_result['time_start']).strftime('%d-%m-%Y %H:%M:%S.%f'),

A bug in greentea?

[pan-]

@0xc0170 The change in this PR do not impact the failing target; failure must be caused by something else.

[cmonr]

We're looking into some CI issues at the moment. The test will be restarted when the dust has settled.

[cmonr]

/morph test

[mbed-ci]

Test : SUCCESS

Build number : 2118
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7123/2118