You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While working with this example on an ST Discovery Kit I run into a problem where the device fails to retrieve the Account ID and Endpoint name. This persists through erasing the credentials and reflashing the board.
The output can be seen here:
To Reproduce
Steps to reproduce the behavior:
Program a previously used board that contains different credentials / applications
Additional context
I have seen this issue on multiple different Disco Boards. I have only had success clearing this example by programming deprecated examples and clearing the credentials using them.
As an additional comment I am able to resolve this issue by loading a deprecated example: https://os.mbed.com/teams/ST/code/pelion-example-disco-iot01/ and clearing the credentials using it. Then if I reload this example I am able to connect to the platform.
HI @PatrickMillar thanks for the report. We need to check this later.
As a simple workaround there are ways to erase the board without flashing old applications.
use pyocd
pyocd erase --mass-erase
truncate the binary (linux example)
truncate --size 1024K mbed-os-example-pelion.bin
Although normal Drag & Drop flashing of .bin image should also erase any pre-existing KVstore data as that is located in the first bank of the board, between bootloader and application image.
Are you perhaps using some other method for flashing that might preserve those sections that are empty in the image?
Describe the bug
While working with this example on an ST Discovery Kit I run into a problem where the device fails to retrieve the Account ID and Endpoint name. This persists through erasing the credentials and reflashing the board.
The output can be seen here:
To Reproduce
Steps to reproduce the behavior:
Logs
Disco Failure Log Pelion Example.txt
Additional context
I have seen this issue on multiple different Disco Boards. I have only had success clearing this example by programming deprecated examples and clearing the credentials using them.
@cvasilak
The text was updated successfully, but these errors were encountered: