Forum Discussion
New ContributorRSU: Corrupted decision firmware after loading initial RSU image jic (Stratix 10)
Hi plancheres
The likely issue is that factory.rbf and the application RBFs are signed, but factory_boot.rbf was generated as an unsigned RBF:quartus_pfg -c factory_image.sof factory_boot_unsigned.rbf -o rsu_boot=ON
Please sign the generated BOOT_INFO RBF using the same signing chain and private key used for the factory image:
quartus_sign --family=stratix10 --operation=sign \ --qky=<signing_chain.qky> \ --pem=<signing_private_key.pem> \ factory_boot_unsigned.rbf factory_boot_signed.rbf
Update Bitstream 1 in the PFG to use the signed file:
<bitstream id="Bitstream_1"> <path>factory_boot_signed.rbf</path> </bitstream>
Regular ContributorHi plancheres
The likely issue is that factory.rbf and the application RBFs are signed, but factory_boot.rbf was generated as an unsigned RBF:
quartus_pfg -c factory_image.sof factory_boot_unsigned.rbf -o rsu_boot=ON
Please sign the generated BOOT_INFO RBF using the same signing chain and private key used for the factory image:
quartus_sign --family=stratix10 --operation=sign \ --qky=<signing_chain.qky> \ --pem=<signing_private_key.pem> \ factory_boot_unsigned.rbf factory_boot_signed.rbf
Update Bitstream 1 in the PFG to use the signed file:
<bitstream id="Bitstream_1"> <path>factory_boot_signed.rbf</path> </bitstream>
plancheresThank you for the clear solution tehjingy!
Yes, my factory images and application images are signed and encrypted. Your solution worked, that is, signing the BOOT_INFO RBF with the quartus_sign command that you showed fixed the decision firmware corruption issue. My initial RSU image now boots into the first application image.
Regards,
Phil
