Skip to content
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

Add an optional --chip argument to the flash and write-bin subcommands #475

Closed
jessebraham opened this issue Sep 14, 2023 · 0 comments · Fixed by #514
Closed

Add an optional --chip argument to the flash and write-bin subcommands #475

jessebraham opened this issue Sep 14, 2023 · 0 comments · Fixed by #514
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@jessebraham
Copy link
Member

jessebraham commented Sep 14, 2023

Since we only verify the target device based based on architecture currently, it's possible to eg.) flash a C6 application to the H2, which of course does not work.

We should allow users to optionally specify which chip the target should be, and error out instead of flashing if the detected device does not match. This check does not need to be performed if no chip argument was provided, there's nothing we can do if the application is wrong at this point.

@jessebraham jessebraham added the enhancement New feature or request label Sep 14, 2023
@SergioGasquez SergioGasquez added this to the v3 milestone Nov 2, 2023
@SergioGasquez SergioGasquez linked a pull request Nov 20, 2023 that will close this issue
@SergioGasquez SergioGasquez self-assigned this Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants