Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Flashing a factory image #23

Open
bmesnet opened this issue Dec 5, 2017 · 2 comments
Open

Flashing a factory image #23

bmesnet opened this issue Dec 5, 2017 · 2 comments
Assignees

Comments

@bmesnet
Copy link
Contributor

bmesnet commented Dec 5, 2017

Can we have the option to flash a factory image ?
This would allows to recover now that the new release starts by resetting the FPGA to the factory image. Indeed, if the factory image is not good, then this new capi-utils release prevents from flashing any new image in user domain!!!!

@jsvogt
Copy link
Contributor

jsvogt commented Dec 20, 2017

👍 My proposal: add an option to the binary flashing tools (built from capi_flash_xxx.c) that can be used when calling the flashing tool manually. Just for users who know well what they are doing and what they risk.
However, I wouldn't put an option to update the factory image into the capi-flash-script, as this is the default "safe" way to update an image.

regarding "safe":
not 100%, as it is still possible to provide a .bin file that doesn't match the selected card.

@kenhill kenhill self-assigned this Dec 20, 2017
@kenhill
Copy link
Contributor

kenhill commented Dec 20, 2017

@jsvogt I am planning on doing a major rewrite to the C flashing code. I can include the factory flashing functionality for the SNAP related CAPI adapters. I agree this should not be wrapped into capi-flash-script and included as advance instructions in the README

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

No branches or pull requests

3 participants