Encryption error during DCP generation

0

Hi,

I am using on-prem setup for generating DCP checkpoints in HDK flow for multiple projects. So far, after updating the encrypt.tcl and other relevant files in build/scripts folder, I was able to generate checkpoints.

But, with a recent project of mine, I am facing error, where AWS is saying there is nothing to encrypt. Below is the output where it throws error.

## encrypt -k $HDK_SHELL_DIR/build/scripts/vivado_keyfile_2017_4.txt -lang verilog  [glob -nocomplain -- $TARGET_DIR/*.{v,sv}] [glob -nocomplain -- $TARGET_DIR/*.vh] [glob -nocomplain -- $TARGET_DIR/*.inc]
ERROR: [Vivado 12-3330] encrypt 1735: Failed to encrypt ''./home/user/.Xilinx/.temp3fabed45-9f07-491c-89e9-867452be593b/vivado_keyfile_2017_4.txt: FileStructure::encrypt1735: Nothing to encrypt.

I have checked the hierarchy of the design, and also created the project from scratch multiple times, but this error stays same.

Any pointers on what could be the issue would be really helpful.

Thanks in advance.

posta 4 anni fa223 visualizzazioni
4 Risposte
0

Hi pradeepsi,

Can you please check if $TARGET_DIR is set?

If it is set, do you have the required files under $TARGET_DIR?

Let us know to assist you further.

Thanks,
Sunil.

AWS
con risposta 4 anni fa
0

Hi Sunil,

Yes, the TARGET_DIR is set to src_post_encryption directory, and the RTL files does get copied to the folder. The vivado_keyfile_2017_4.txt file is also there at its default location.

Thanks.

Edit:
I am able to generate DCP after disabling the encryption by commenting last two commands in encrypt.tcl.

Edited by: pradeepsi on Jul 6, 2020 12:05 PM

con risposta 4 anni fa
0

Hi pradeepsi,

We ran the cl_dram_dma example https://github.com/aws/aws-fpga/tree/master/hdk/cl/examples/cl_dram_dma and the encryption works for us.

As we are unable to reproduce the issue you are facing, to root cause the issue you may run the encrypt command for each file in the $TARGET_DIR and see which file is causing this issue?

Thanks,
Sunil.

AWS
con risposta 4 anni fa
0

Hi Sunil,

I could identify the troubling file by running the command on individual files. Thanks for your help.

Please provide feedback to developers for a more informed prints when this kind of errors occurs, which will really help in debugging for F1 users.

Thanks again!

con risposta 4 anni fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande