You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!!!!
The text was updated successfully, but these errors were encountered:
👍 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.
@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
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!!!!
The text was updated successfully, but these errors were encountered: