cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mark@bish.net
Adventurer
Adventurer
2,901 Views
Registered: ‎09-19-2017

Programming BBRAM (2017.3) error

Capture.PNG

 

I keep getting this error message in Vivado when attempting to program the bbr key.

 

Any ideas?  I've rebooted and restarted a bunch of times.

0 Kudos
12 Replies
balkris
Xilinx Employee
Xilinx Employee
2,886 Views
Registered: ‎08-01-2008

I am looking into this post meanwhile you can refer this discussion
https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2017-3-not-enabling-VU7P-ES1-devices/td-p/799664
Thanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
mark@bish.net
Adventurer
Adventurer
2,880 Views
Registered: ‎09-19-2017

I am using a node locked license for right now.

 

I am creating my bbram.nky key as follows:

 

In file generate_aeskey.bif-

 

generate_aeskey_image:
{
[aeskeyfile] bbram.nky
[bootloader, encryption=aes] zynq_mmp_fsbl.elf
}

 

then bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram -p xc7z045

 

If I can provide any more detail please let me know.  Its put me at a standstill.

 

0 Kudos
mark@bish.net
Adventurer
Adventurer
2,876 Views
Registered: ‎09-19-2017

Also, my part is a xc7z045ffg900-1

 

It is found in 'get_parts' but bootgen fails if you specify the full part:

bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram -p xc7z045ffg900-1
ERROR: syntax error
... bbram -p xc7z045ffg900-1
^^^^^^^^^^^^^^^

[ERROR] : Command line parsing failed with code 1

 

If you create it like this: bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram -p xc7z045ffg900

 

Then Vivado complains:

Capture.PNG

0 Kudos
balkris
Xilinx Employee
Xilinx Employee
2,817 Views
Registered: ‎08-01-2008

Can you please try this commend 

 

bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram

 

Can you refer this XAPP

XAPP1175 -  Secure Boot of Zynq-7000 All Programmable SoC Application Note( ver2.0, 7890 KB ) [PDF]

Describes how to boot the Zynq®-7000 AP SoC device securely using Quad-SPI and SD modes, including optimal use of RSA authentication and AES encryption.
Associated File(s)

 

Refer this wiki page to prepare boot image 

http://www.wiki.xilinx.com/Prepare+boot+image

Thanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
mark@bish.net
Adventurer
Adventurer
2,809 Views
Registered: ‎09-19-2017

Here is the output of that command:

 

mark@stride:~/git_repo/ZMMP_7045_PetaLinux_PL2015_2/SDK_boot$ source /opt/Xilinx/Vivado/2017.3/settings64.sh 
mark@stride:~/git_repo/ZMMP_7045_PetaLinux_PL2015_2/SDK_boot$ bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram
[ERROR]  : Partname must be specified with -p <partname> option in command line for generating a key file

 

 

I've been going through that XAPP over and over.  My issue is loading the key into BBRAM for the boot from SD.  

0 Kudos
balkris
Xilinx Employee
Xilinx Employee
2,800 Views
Registered: ‎08-01-2008


Xilinx BootGen
Build-2017.2, Date-May 18, 2017
Copyright (c) 1995-2017 Xilinx, Inc. All rights reserved.

------------------------------------------------------------------------------+
COMMAND LINE OPTIONS |
-------------------------------+----------------------------------------------+
-arch [options] | Xilinx Architecture |
| options: [zynq, zynqmp, fpga] |
-------------------------------+----------------------------------------------+
-image <filename> | Input Boot Image File (.bif) |
-------------------------------+----------------------------------------------+
-o <filename> | Output filename in MCS/BIN format |
-------------------------------+----------------------------------------------+
-w [options] | Overwrite mode |
| options: [on, off] |
-------------------------------+----------------------------------------------+
-encrypt [options] | AES Key storage in chip (Zynq only) |
| options: [bbram, efuse] |
-------------------------------+----------------------------------------------+
-p <string> | Part name |
-------------------------------+----------------------------------------------+
-efuseppkbits <filename> | Generate PPK hash for e-fuse |
-------------------------------+----------------------------------------------+
-generate_hashes | Generate SHA hashes (PKCS#1v1.5) |
-------------------------------+----------------------------------------------+
-spksignature <filename> | Generate SPK signature file |
-------------------------------+----------------------------------------------+
-fill <hex-byte> | Fill byte for padding |
-------------------------------+----------------------------------------------+
-split [options] | Split partitions to diff files |
| options: [bin, mcs] |
-------------------------------+----------------------------------------------+
-padimageheader [options] | Pad header tables |
| options: [0, 1] |
-------------------------------+----------------------------------------------+
-process_bitstream [options] | Outputs bitstream in bin/mcs format |
| options: [bin, mcs] |
-------------------------------+----------------------------------------------+
-generate_keys auth [options] | Generate Authentication Keys |
| options: [pem, rsa] |
-------------------------------+----------------------------------------------+
-dual_qspi_mode [options] | Generate 2 output files for Dual QSPI |
| options: [parallel, stacked <size>] |
-------------------------------+----------------------------------------------+
-log [options] | Generate log file |
| options: [error, warning, info, debug, trace]|
-------------------------------+----------------------------------------------+
-zynqmpes1 | Generate boot image for (1.0)ES1 |
-------------------------------+----------------------------------------------+
-h | -help | Print the help summary |
-------------------------------+----------------------------------------------+
-bif_help | Print the BIF help summary |
-------------------------------+----------------------------------------------+
Note : For more info on bootgen options, use the command |
bootgen -help <option> |
Example : bootgen -help efuseppkbits |
------------------------------------------------------------------------------+

 

Thanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
mark@bish.net
Adventurer
Adventurer
2,791 Views
Registered: ‎09-19-2017

mark@stride:~/git_repo/ZMMP_7045_PetaLinux_PL2015_2/SDK_boot$ /opt/Xilinx/SDK/2017.2/bin/bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram 
[ERROR]  : Partname must be specified with -p <partname> option in command line for generating a key file

Same error regardless if I use 2017.2 or 2017.3

 

Also, the MD5sum is the same for both bootgen

0 Kudos
mark@bish.net
Adventurer
Adventurer
2,711 Views
Registered: ‎09-19-2017

Are there any other channels to get more formal support from Xilinx for this issue?

0 Kudos
sylvainsgndt
Observer
Observer
2,437 Views
Registered: ‎05-26-2014

I get the same problem. Did you, by any chance, figured out a solution? I read the links the moderator sent you and it looks like he just not read your question or was just trying to send you to the "user manual" without even noticing that Xilinx Software merge your home directory with the part name, which sounds like a bug to me. 

 

Thanks in advance 

pmallad
Xilinx Employee
Xilinx Employee
1,638 Views
Registered: ‎01-15-2014

I was successful in programming the BBRAM key using Vivado

 

This is the bif:

generate_aeskey_image:
{
    [aeskeyfile] bbram.nky
    [bootloader, encryption=aes] zynq_fsbl_0.elf
}

 

This is the command:

bootgen -image generate_aeskey_image.bif -o temp.mcs -encrypt bbram -p xc7z045

0 Kudos
mark@bish.net
Adventurer
Adventurer
1,619 Views
Registered: ‎09-19-2017

@sylvainsgndt  I had to move on.  I'm coming back to it but it is going to be a few months.

0 Kudos
liwenz
Explorer
Explorer
1,500 Views
Registered: ‎10-09-2017

I got the same error.  in 2015.4

I follow the xapp1175, with  bootgen -image generate_aeskey.bif -o temp.mcs -encrypt bbram

it tells me -p partname need.

I add -p xc7z010 

it runs and report the program fall down
 

0 Kudos