-
Notifications
You must be signed in to change notification settings - Fork 3k
[Mbed OS 6.6.0] Flashing SDP-K1 board causes interface firmware to fail. Can no longer program board after flashing with any Mbed OS 6.6.0 project. #14121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. |
What is the previous version that worked - to start bisecting what has changed ? cc @ARMmbed/team-st-mcd |
this should be though @ARMmbed/team-analogdevices |
Please check #14032 |
Last working on Mbed-OS 6.5.0.
Checked this and configured the SDP-K1 so that the change in #13777 is disabled. Can confirm this is the issue, thanks Jerome. Will submit a pull request when #14032 is merged to change this option in master for the SDP-K1 to solve the problem. |
Hi |
Description of defect
Flashing SDP-K1 with any Mbed OS 6.6.0 project appears to break the DAPLink update program preventing any more programming of the SDP-K1. Initial program will work, but any subsequent attempt to flash the board will result in a fail. Fail log is output with the following message:
error: The interface firmware FAILED to reset/halt the target MCU
.Target(s) affected by this defect ?
SDP-K1
Toolchain(s) (name and version) displaying this defect ?
GCC-ARM
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.6.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli and online compiler
How is this defect reproduced ?
Flash SDP-K1 board with any binary/project using the Mbed OS 6.6.0 library (e.g. simple LED blinky project). Program will work initially. Try to program the board with any other bin/hex file after this first flash and interface firmware will start to fail consistently.
The text was updated successfully, but these errors were encountered: