Skip to content

Maxim targets are not currently enabled #11233

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

Closed
MarceloSalazar opened this issue Aug 15, 2019 · 4 comments
Closed

Maxim targets are not currently enabled #11233

MarceloSalazar opened this issue Aug 15, 2019 · 4 comments

Comments

@MarceloSalazar
Copy link

Description

The Maxim targets are not currently enabled in Mbed OS 5.13.2+

We're getting the message "Target does not support mbed OS 5" when using Mbed CLI

Need to check that the target can be compiled with Arm Compiler 6, GCC, and IAR 8 (#9206) and then re-enable target in Mbed OS once tests pass ok.

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug
@adbridge
Copy link
Contributor

@ARMmbed/team-maximintegrated please investigate

@ciarmcom
Copy link
Member

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1619

@maclobdell
Copy link
Contributor

I see that in targets.json, those two boards have no release version listed. The MAXWSNENV is listed as end-of-life, so that might be intentional.

        "release_versions": []

@jessexm - Can you confirm - are both the MAXWSNENV & MAX32620HSP at end-of-life?
If so, I propose 1) adding a warning on the platform page indicating end-of-life & which versions of Mbed OS are supported, 2) making the platform page unlisted (I can help with that), 3) keeping support for those targets for ~6 months after EOL notification, then stripping out support.

@MarceloSalazar
Copy link
Author

Closed as targets removed - #12984

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants