Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Mohamedou__Ahmed
Beginner
273 Views

Couldn't Program Intel PAC with Provided Bitstreams

I have Intel PAC with the latest FIM version. Running

sudo fpgainfo fme

shows:

FW version 26889
Pr Interface Id: 69528db6-eb31-577a-8c36-68f9faa081f6

I have succefully programmed it with hello world bitstream. When I tried to program it with bitstreams provided with OpenVino as follow:

aocl program acl0 /opt/intel/computer_vision_sdk_fpga_2018.5.445/bitstreams/a10_dcp_bitstreams/5-0_RC_FP16_ResNet_ELU.aocx

This error keeps showing:

aocl program: Running program from /home/centos/inteldevstack/a10_gx_pac_ias_1_2_pv/opencl/opencl_bsp/linux64/libexec
libopae-c bitstream.c:387:validate_bitstream_metadata() **ERROR** : Interface ID check failed
Error writing bitstream to FPGA: invalid parameter
Error programming device
aocl program: Program failed.

 

How to resolve this error?

Thanks

 

 

0 Kudos
7 Replies
Gdeep
Beginner
273 Views

Dear ahmed 

I have also the same Hardware which you are using: 'Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA'

My software configuration is ubuntu 16.04 (LTS) with kernel version 4.14.20-041420-generic

To setup Intel® Programmable Acceleration Card with Intel® Arria® 10 GX FPGA' i am following the steps which they mentioned in this link -> https://software.intel.com/en-us/articles/OpenVINO-Install-Linux-FPGA

I have skipped first two steps mentioned below:

1 Configure the Intel® Arria® 10 GX FPGA Development Kit

2 Program the Intel® Arria® 10 GX FPGA Development Kit

I have begun from step number 3 that is the installation of openvino, the problem is here:- 

When i ran:->  aocl  diagnose

My output for the above command was:-

root@iwave:/home/iwave/Downloads/fpga_support_files# aocl diagnose
--------------------------------------------------------------------
Warning:
No devices attached for package:
/opt/altera/aocl-pro-rte/aclrte-linux64/board/hddlf_1150_sg1
--------------------------------------------------------------------

Call "aocl diagnose <device-names>" to run diagnose for specified devices
Call "aocl diagnose all" to run diagnose for all devices
root@iwave:/home/iwave/Downloads/fpga_support_files#

please guide me to sort out this error, which steps you followed to configured 'Intel® Programmable Acceleration Card with Intel® Arria® 10 GX' ? had you followed same steps or some extra work we have to do? 

Mohamedou__Ahmed
Beginner
273 Views

Dear Gagan,

I am not sure if you are using PAC or DevKit.

In case, you are using DevKit, it seems that your development kit is not initialized yet. You need the firs two steps if your development kit is not programmed yet. You need to program your development kit so that it can understand OpenCL for FPGA. Also, you need to physically install the DDR4 memory (be very careful so that you don't damage your kit when removing fans and watch out for electrostatic discharge). Follow this link steps:

https://www.intel.com/content/www/us/en/programmable/documentation/tgy14.

In case you are using PAC, make sure you have installed the OpenCl driver by running:

sudo -E aocl install

when asked about BSP, answer yes. Check this link:

https://www.intel.com/content/www/us/en/programmable/documentation/fvf15.

Note that my host OS is CentOS 7.4. The support for Debian based OS (i.e. Ubuntu) is introduced recently. The issue may lie there.

Good Luck

mahinlma
New Contributor I
273 Views

Dear ahmed ,

Facing same issue,

libopae-c bitstream.c:387:validate_bitstream_metadata() **ERROR** : Interface ID check failed
Error writing bitstream to FPGA: invalid parameter
Error programming device
aocl program: Program failed.

 Do you find any fix, then please let me know

Thanks

LAB__XPERIENCE
Beginner
273 Views

Same issue here.  Output of aocl diagnose is:

[root@ait-fpga01 a10_dcp_bitstreams]# aocl diagnose acl0
Using platform: Intel(R) FPGA SDK for OpenCL(TM)
Using Device with name: pac_a10 : PAC Arria 10 Platform (pac_a10_ed00000)
Using Device from vendor: Intel Corp
clGetDeviceInfo CL_DEVICE_GLOBAL_MEM_SIZE = 8589934592
clGetDeviceInfo CL_DEVICE_MAX_MEM_ALLOC_SIZE = 8588886016
Memory consumed for internal use = 1048576
Actual maximum buffer size = 8588886016 bytes
Writing 8191 MB to global memory ...
Allocated 1073741824 Bytes host buffer for large transfers
Write speed: 6880.73 MB/s [6856.10 -> 6887.21]
Reading and verifying 8191 MB from global memory ...
Read speed: 5661.89 MB/s [5626.57 -> 5678.22]
Successfully wrote and readback 8191 MB buffer

Transferring 262144 KBs in 512 512 KB blocks ... 3298.82 MB/s
Transferring 262144 KBs in 256 1024 KB blocks ... 3425.35 MB/s
Transferring 262144 KBs in 128 2048 KB blocks ... 4597.71 MB/s
Transferring 262144 KBs in 64 4096 KB blocks ... 5486.36 MB/s
Transferring 262144 KBs in 32 8192 KB blocks ... 6080.87 MB/s
Transferring 262144 KBs in 16 16384 KB blocks ... 6444.40 MB/s
Transferring 262144 KBs in 8 32768 KB blocks ... 6636.86 MB/s
Transferring 262144 KBs in 4 65536 KB blocks ... 6742.40 MB/s
Transferring 262144 KBs in 2 131072 KB blocks ... 6791.45 MB/s
Transferring 262144 KBs in 1 262144 KB blocks ... 6760.12 MB/s

As a reference:
PCIe Gen1 peak speed: 250MB/s/lane
PCIe Gen2 peak speed: 500MB/s/lane
PCIe Gen3 peak speed: 985MB/s/lane

Writing 262144 KBs with block size (in bytes) below:

Block_Size Avg    Max    Min    End-End (MB/s)
  524288 2689.24 3298.82 1578.81 2387.39
 1048576 3317.31 3425.35 3000.64 3147.81
 2097152 4536.61 4597.71 4184.51 4409.96
 4194304 4487.08 5486.36 2309.47 4441.66
 8388608 6014.73 6080.87 5418.39 5973.34
16777216 6402.87 6444.40 6096.55 6377.81
33554432 6461.89 6636.86 6107.19 6441.38
67108864 6634.25 6742.40 6498.42 6623.85
134217728 6733.81 6791.45 6677.14 6730.69
268435456 6760.12 6760.12 6760.12 6760.12

Reading 262144 KBs with block size (in bytes) below:

Block_Size Avg    Max    Min    End-End (MB/s)
  524288 2017.84 3094.90 1638.53 1856.38
 1048576 3279.74 3353.87 3005.55 3121.85
 2097152 3432.32 3474.14 3249.33 3368.62
 4194304 3447.82 3478.34 3338.50 3419.27
 8388608 4408.15 4577.55 4304.01 4377.21
16777216 4863.95 5464.42 4453.67 4844.69
33554432 5341.19 5640.67 5250.91 5330.31
67108864 5584.89 5904.25 5470.91 5579.80
134217728 2825.80 3179.78 2542.73 2824.86
268435456 5686.80 5686.80 5686.80 5686.80

Write top speed = 6791.45 MB/s
Read top speed = 5904.25 MB/s
Throughput = 6347.85 MB/s

DIAGNOSTIC_PASSED

Zihan_C_Intel
Employee
273 Views

Hi guys,

I happen to get the same issue and run into this article, lol. I don't know if you have figured it out. If not I feel the problem is related with the PR Interface Id mismatch with the most recent Id. could you please check the output of " sudo fpgainfo fme | grep "Pr Interface Id" "?

If the output is not "69528db6-eb31-577a-8c36-68f9faa081f6", it means the pac card is not configured properly and hence need to be updated. Please refer to this link to update the Pr Interface Id:

https://www.intel.com/content/www/us/en/programmable/documentation/iyu1522005567196.html#ymd15478770...

Feel free to reach me for more details

Good luck,

Zihan

 

MEghb
Beginner
273 Views

Hi guys,

I installed the Intel PAC recently and I followed the instructions to install the drivers. Now, when I wanted to initialize the bsp with hello_world.aocx I will get the following errors:

aocl program: Running program from /opt/inteldevstack/a10_gx_pac_ias_1_2_1_pv/opencl/opencl_bsp/linux64/libexec
libopae-c bitstream.c:387:validate_bitstream_metadata() **ERROR** : Interface ID check failed
Error writing bitstream to FPGA: invalid parameter
Error programming device
aocl program: Program failed.

 

Also, this is the PR interface id:  69528db6-eb31-577a-8c36-68f9faa081f6

I was wondering if anybody found the solution to this issue?

 

Best,

Mostafa

NSVR
Novice
68 Views

Did you find the solution i Have faced same issue. and my interface id is matching