aws-fpga simulation errors

0

I am trying to integrate HBM into sde engines to allow large amount data stored on my FPGA. But after some simulation, I found that I can not access HBM module with axi4 (all read requests does not receive a valid). I started to run simulations in cl_mem_perf and cl_dram_hbm_dma to get a ground truth axi4 usage.

Error 1: cl is not correct. I found that some simulations in cl_mem_perf and cl_dram_hbm_dma examples are not correctly executed. I dumped the waves by adding "log_wave -r /" in waves.tcl, and I found the cl module is still cl_sde (while it should be cl_mem_perf or cl_dram_hbm_dma). It seems that the simulation is executed on a completely wrong cl.

I run my simulations like this: cd aws-fpga source hdk_setup.sh cd hdk/cl/examples/cl_mem_perf export CL_DIR=$(pwd) cd verif/scripts make TEST=test_hbm_perf32 > perf32.log

Error2: xvlog runs for more than 1 hour Normally, my simulation takes about 2 hours, and the overhead is on xelab (the simulation part). But, when I simulate some test examples in cl_mem_perf, xvlog execution takes more than 1 hour and still does not finish. For example, this xvlog command runs for more than 1 hour: cd /home/ubuntu/aws-fpga/hdk/cl/examples/cl_mem_perf/verif/sim/xsim/test_hbm_perf32_sv && xvlog --sv -m64 --define DMA_TEST --define plusarg_save --define timeout=1ms --define AWS_SIM --define USE_64GB_DDR_DIMM=1 --work xil_defaultlib --incr --relax -f /home/ubuntu/aws-fpga/hdk/cl/examples/cl_mem_perf/verif/scripts/top.xsim.f Sometimes, even test_null's xvlog command also has this error. I have to mannualy ctrl+c to stop them. But ctrl+c does not fix this, the next simulation still has this problem. All I can do is go to ec2 console, stop the m4.2xlarge instance I am using, and restart after waiting for several minutes.

I hope you can help me fix these two errors or identify the causes. That will be extremely helpful because these two problems are really slowing me down.

asked 24 days ago60 views
2 Answers
4

The simulation's incorrect execution on the wrong CL module may stem from misconfigured environment settings or inaccuracies in configuration files. Additionally, the extended execution time of xvlog could be attributed to large or intricate design files, inadequate resources available on the EC2 instance, or underlying issues within the simulation setup itself.

EXPERT
answered 23 days ago
0

When switching from CL example to another CL example with XSIM:

  • Delete the $HDK_COMMON_DIR/verif/ip_simulation_libraries to remove any trace of previous CL
  • Set the CL_DIR to new example directory
  • If further debug is needed, eliminate the chance your changes caused issue, try a fresh git clone

XSIM HBM related tests are slow due to Xilinx model, it can run 3-4 hrs.

AWS
answered 23 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions