-
Notifications
You must be signed in to change notification settings - Fork 42
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
efuseppkbits - Unknown option on command line #12
Comments
Um reading the code a bit it seems the right way to generate the efuse.txt is to do it at the time of the bin creation only
The command above does generate the efuse file but I'd like to have some guarantees it will work (I dont want to risk bricking this board). please could you confirm? |
@ldts hi, any hints how to write the fuses without breaking some devices ? |
Could you please refer app note for writing eFuses on Zynq Ultra Scale Plus devices
|
@RamyaDarapuneni thanks but the document doesn't illustrate bytes order of the PPKs and I would like to avoid break some devices. can you please provide an example ? Is it also possible to write them from Linux through the nvmem API ? |
Hi @ldts and @embetrix please reference XAPP1357 found in the Xilinx Design Security lounge. https://account.amd.com/en/member/design_security.html#tabs-b08b1a322e-item-5dbfbe7377-tab This will have more details on how to use Bootgen to create the hashes of the PPKs. |
@nathan-menhorn this just redirect to a registration form which I filled weeks ago and no one from AMD is daring to answer... |
Hi @embetrix do you have an active NDA with AMD? This will be required before access is granted. |
Hi,
I am trying to generate the SHA to write to the eFuse so I can properly activate the secure boot authentication
However using the documented bif file, I am having the following issue:
It is not straightforward to debug the parser (lex/bixon stuff).
Could you help me understand the error in the command line please - verbatim from the documentation?
This actually relates to #10
The text was updated successfully, but these errors were encountered: