Skip to content

IOTBTOOL-407 Fix microbit to use Arm C5 #11609

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
Oct 15, 2019

Conversation

madchutney
Copy link
Contributor

Description

Earlier changes introduced a change to default Arm C6, which does not compile the micro library which is based on Mbed 2. This change fixes the compiler version for NRF51_MICROBIT devices.

https://jira.arm.com/browse/IOTBTOOL-407

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Earlier changes introduced a change to default Arm C6, which does not compile the micro library which is based on Mbed 2. This change fixes the compiler version for NRF51_MICROBIT devices.
@@ -5318,7 +5318,8 @@
"inherits": ["MCU_NRF51_16K_S110"],
"macros_add": ["TARGET_NRF_LFCLK_RC"],
"release_versions": ["2"],
"device_name": "nRF51822_xxAA"
"device_name": "nRF51822_xxAA",
"supported_toolchains": ["ARMC5", "GCC_ARM"]
Copy link
Member

Choose a reason for hiding this comment

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

Why only ARMC and GCC and not IAR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

NRF51_MICROBIT inherits from MCU_NRF51_16K_S110 which inherits from MCU_NRF51_S110 and MCU_NRF51_16K_BASE. MCU_NRF51_S110 is a dead end and does not define a toolchain. So following MCU_NRF51_16K_BASE this inherits from MCU_NRF51, which defines the supported_toolchains as [“ARM", "GCC_ARM”]. This means before my change the supported toolchains were Arm C6 and GCC ARM, but before the change which broke microbit they should have been Arm C5 and GCC ARM. This definition seems to be setup in 2016, which means as best as I can tell this platform has never declared support for IAR.

Copy link
Contributor

Choose a reason for hiding this comment

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

I had to check this one as well as I would have assumed nrf51 was supported also by IAR but has not been.

@ciarmcom ciarmcom requested a review from a team October 1, 2019 17:00
@ciarmcom
Copy link
Member

ciarmcom commented Oct 1, 2019

@madchutney, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

@adbridge
Copy link
Contributor

adbridge commented Oct 7, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Oct 7, 2019

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_exporter

@@ -5318,7 +5318,8 @@
"inherits": ["MCU_NRF51_16K_S110"],
"macros_add": ["TARGET_NRF_LFCLK_RC"],
"release_versions": ["2"],
"device_name": "nRF51822_xxAA"
"device_name": "nRF51822_xxAA",
"supported_toolchains": ["ARMC5", "GCC_ARM"]
Copy link
Contributor

Choose a reason for hiding this comment

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

I had to check this one as well as I would have assumed nrf51 was supported also by IAR but has not been.

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 14, 2019

Exporters restarted

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 14, 2019

I restarted the entire pipeline accidentally 😞

@mbed-ci
Copy link

mbed-ci commented Oct 14, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts

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