Skip to content

Revert "Always build both .hex and .bin files" #13584

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

Merged
merged 1 commit into from
Sep 10, 2020

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Sep 10, 2020

Reverts #13011

The issue : ARMmbed/mbed-cli#980 . We did not realize the PR 13011 has an impact on the tooling. Producing both outputs make it impossible for a tool to select which one to flash without additional logic from a target (does a target support both or just one - which one is it?). Additional work would be needed for the tools to support this.

mbed-cli currently copies what it finds first. This is causing an error for targets supporting only .bin output format (.hex is checked first in the tools). There are lot of targets affected unfortunately. The newer firmware (daplink , stlink and others) support both but not all people are up to date, or the target supports latest updates.

The change itself in 13011 was good one but without tools supporting it, we have to revert it. The new tools should consider this functionality.

cc @alzix

Copy link
Contributor

@Patater Patater left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mbed-ci
Copy link

mbed-ci commented Sep 10, 2020

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs Status
jenkins-ci/mbed-os-ci_unittests ✔️
jenkins-ci/mbed-os-ci_build-ARM ✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM ✔️
jenkins-ci/mbed-os-ci_greentea-test ✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage ✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest ✔️
jenkins-ci/mbed-os-ci_wisun-mesh-test ✔️

Copy link
Collaborator

@andypowers andypowers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

@0xc0170 0xc0170 merged commit 8a22d35 into master Sep 10, 2020
@mergify
Copy link

mergify bot commented Sep 10, 2020

This PR does not contain release version label after merging.

@mergify mergify bot added the release version missing When PR does not contain release version, bot should label it and we fix it afterwards label Sep 10, 2020
@0xc0170
Copy link
Contributor Author

0xc0170 commented Sep 10, 2020

@alzix It would be good to have tracking issue for new tools - mbed-tools to capture this feature there.

@0xc0170 0xc0170 deleted the revert-13011-alzix/both-artifacts branch September 10, 2020 11:25
@0xc0170 0xc0170 added release-type: patch Indentifies a PR as containing just a patch and removed needs: review release version missing When PR does not contain release version, bot should label it and we fix it afterwards labels Sep 10, 2020
@mbedmain mbedmain added release-version: 6.3.0 Release-pending and removed release-type: patch Indentifies a PR as containing just a patch Release-pending labels Sep 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants