cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
dbrinks
Visitor
Visitor
3,706 Views
Registered: ‎10-13-2009

Bootgen errors when using authentication

Jump to solution

When I try to generate an authenticated bootloader, bootgen fails with the error:

 

FATAL: Exception: Sanity check in GetModulesExtension Failed

 

Has anyone seen this before (or successfully generated an authenticated bootloader)?

 

A few more details:

  • I've got Xilinx 14.6 tools installed
  • My command line is: "bootgen -image bootgen_sign.bif -o i BOOT_signed.bin -w on -efuseppkbits efusebits.txt -p xc7z020clg484 -encrypt bbram
  • My .bif files contains:

image : {
    [aeskeyfile]inc_key.nky
    [pskfile]rsa_keys_p_u.pem
    [sskfile]rsa_keys_s_u.pem
    [bootloader,authentication=rsa]fsbl.elf
}

 

The two PEM files are both unencrypted and were generated using ssh-keygen. They look like this:

-----BEGIN RSA PRIVATE KEY-----
<base64 encoded data>
-----END RSA PRIVATE KEY-----

 

I've used the inc_key.nky file before to perform encryption, so that shouldn't be the problem.

 

Thoughts?

 

0 Kudos
1 Solution

Accepted Solutions
htsvn
Xilinx Employee
Xilinx Employee
4,706 Views
Registered: ‎08-02-2007

Hi,

 

This issue is reported for Windows. Can you try this on a different OS?

 

--HS

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
3 Replies
htsvn
Xilinx Employee
Xilinx Employee
4,707 Views
Registered: ‎08-02-2007

Hi,

 

This issue is reported for Windows. Can you try this on a different OS?

 

--HS

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
dbrinks
Visitor
Visitor
3,647 Views
Registered: ‎10-13-2009

That seems to fix it--any chance of this being fixed for Windows at some point?

0 Kudos
orazey
Visitor
Visitor
3,557 Views
Registered: ‎07-15-2013

 

I am having the same problem what operating system did you use? And is your image secure RSA or non secure RSA?  Is  "[aeskeyfile]inc_key.nky" needed in both cases and the attributes will decide whether it is secure or non secure RSA? How did you generate this key in bootgen? 

 

Lastly, how did you go about blowing the PPK eFUSE and generating the PPK hash for it?  Is this done automatically when  booting the RSA image?  I know its alot of questions and any help would be greatly appreciated.

0 Kudos