Community
cancel
Showing results for 
Search instead for 
Did you mean: 
maxdd
Beginner
254 Views

N3000 Sample Test: Native Loopback fail

I try to run Sample Test: Native Loopback by using 'sudo ./hello_fpga', but it gives error

 

 

Using OPAE C library version '1.3.7' build '81afe79'
Error no matching accelerator: not found

 

 

 

'lspci | grep acc' gives

 

 

08:00.0 Processing accelerators: Intel Corporation Device 0b30

 

 

 

I also try to use 'sudo ./hello_fpga -B 0x08' but it gives the same error.

 

Any idea on how to solve this? Thanks!

0 Kudos
9 Replies
wchiah
Employee
218 Views

Hi,

 

I might need the below info (PrintScreen will help)

  • rpm -qa | grep opae
    check the OPAE version, also to confirm the step is correct.

The hello_fpga sample host application uses the OPAE library to test the hardware in native loopback mode (NLB).

I would suggest referring back to session 7.2.1 at link below (for detailed setup)

What you have to do is the following

  1. cd sw_sample
  2. gcc -o hello_fpga -std=gnu99 -rdynamic -ljson-c -luuid -lpthread -lopae-c -lm -Wl,-rpath -lopae-c hello_fpga.c
  3. sudo sh -c "echo 20 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages"
  4. sudo ./hello_fpga

[guest@hw-rae-a3-l sw_sample]$ sudo ./hello_fpga

Using OPAE C library version '1.3.3' build 'c6c0d9f'

Running Test

Running on bus 0x07.

dfh = 100000008000001f

id[0] = c000c9660d824272

id[1] = 9aeffe5f84570612

dfh = 2000000080000000

id[0] = a9149a35bace01ea

id[1] = ef82def7f6ec40fc

dfh = 2000000080000000

id[0] = a9149a35bace01ea

id[1] = ef82def7f6ec40fc

dfh = 2000000080000000

id[0] = a9149a35bace01ea

id[1] = ef82def7f6ec40fc

dfh = 2000000080000000

id[0] = a9149a35bace01ea

id[1] = ef82def7f6ec40fc

dfh = 1000010080001070

id[0] = f89e433683f9040b

id[1] = d8424dc4a4a3c413

Found NLB0 at offset 0x28000

Done Running Test

Let me know if this helps.

Regards,

WeiChuan_C_Intel

 

maxdd
Beginner
201 Views

Thanks for the reply.

When following the tutorial, I don't know what is this variable '$OPAE_PLATFORM_ROOT'. After installation, I only have two folders. Here is the folder structures. (I only show 2 levels)

intelrtestack
├── bin
│   ├── init_env.sh
│   ├── sr_vista_rot_2x2x25-v1.3.16.bin
│   └── sr_vista_rot_4x25G-v1.3.16.bin
├── src
│   ├── opae-1.3.7-5
│   ├── opae.admin-1.0.3
│   ├── opae-intel-fpga-driver-2.0.1-10.src.rpm
│   └── opae.pac_sign-1.0.4
└── sw_sample
    └── hello_fpga.c

inteldevstack
├── bin
│   ├── sr_vista_rot_2x2x25-v1.3.16.bin
│   └── sr_vista_rot_4x25G-v1.3.16.bin
├── intelFPGA_pro
│   ├── devdata
│   ├── ip
│   ├── licenses
│   ├── logs
│   ├── nios2eds
│   ├── qsys
│   ├── quartus
│   └── syscon
├── rtl
│   └── n3000_1_3_v1.5.7
└── src
    ├── opae-1.3.7-5
    ├── opae.admin-1.0.3
    ├── opae-intel-fpga-driver-2.0.1-10.src.rpm
    └── opae.pac_sign-1.0.4

 

I am using 'N3000-2', the link you send me is for 'Intel Arria 10 GX FPGA', not for 'N3000-2', is that correct?

 

Here is the output

rpm -qa | grep opae
opae-intel-fpga-driver-2.0.1-10.x86_64
opae-libs-1.3.7-5.el7.x86_64
opae-devel-1.3.7-5.el7.x86_64
opae-tools-1.3.7-5.el7.x86_64
opae-tools-extra-1.3.7-5.el7.x86_64
opae.admin-1.0.3-2.el7.noarch
opae.pac_sign-1.0.4-3.el7.x86_64

 

wchiah
Employee
175 Views

Hi Max,

How about the test result of "fpgainfo fme" and "fpgabist" ?

Apologize for wrong doc, can you please try out doc below

Just want to ensure that the step is correct, please let me know if you are still unable to get it.

Regards,

WeiChuan_C_Intel



maxdd
Beginner
170 Views

I think there is the correct doc for N3000-2?

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

 

I follow the instruction on this doc and I also follow the instructions on the doc you suggest, but none of them work.

Here is the error and the output for "fpgainfo fme" and "fpgabist".

sudo ./hello_fpga -B 0x08
Using OPAE C library version '1.3.7' build '81afe79'
Error no matching accelerator: not found


fpgainfo fme
Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** FME ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
Boot Page                     : user
 
fpgabist -i 0x0b30
==========================================================

Beginning FPGA Built-In Self-Test

==========================================================
Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** FME ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
Boot Page                     : user


Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** PORT ******//
Object Id                     : 0xF000000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
Accelerator Id                : 850adcc2-6ceb-4b22-9722-d43375b61c66


Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** TEMP ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
(12) FPGA Core Temperature        : 44.00 Celsius
(13) Board Temperature            : 30.00 Celsius
(15) QSFP A Temperature           : N/A
(38) QSFP B Temperature           : N/A
(44) Retimer A Core Temperature   : 49.00 Celsius
(45) Retimer A Serdes Temperature : 49.50 Celsius
(46) Retimer B Core Temperature   : 50.00 Celsius
(47) Retimer B Serdes Temperature : 51.00 Celsius


Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** POWER ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
( 1) Board Power              : 46.28 Watts
( 2) 12V Backplane Current    : 2.13 Amps
( 3) 12V Backplane Voltage    : 11.95 Volts
( 4) 1.2V Voltage             : 1.20 Volts
( 6) 1.8V Voltage             : 1.82 Volts
(  3.3V Voltage             : 3.29 Volts
(10) FPGA Core Voltage        : 0.90 Volts
(11) FPGA Core Current        : 5.84 Amps
(14) QSFP A Voltage           : N/A
(24) 12V AUX Current          : 1.74 Amps
(25) 12V AUX Voltage          : 11.96 Volts
(37) QSFP B Voltage           : N/A


Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** FME ERRORS ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
PCIe0 Errors                  : 0x0
PCIe1 Errors                  : 0x0
Catfatal Errors               : 0x0
Seu Emr                       : 0x0
Inject Error                  : 0x0
Nonfatal Errors               : 0x0
Next Error                    : 0x0
First Error                   : 0x0
Errors                        : 0x0
Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** PORT ERRORS ******//
Object Id                     : 0xF000000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
Accelerator Id                : 850adcc2-6ceb-4b22-9722-d43375b61c66
First Malformed Req           : 0x0
First Error                   : 0x0
Errors                        : 0x0


Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** PHY ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
//****** PHY GROUP 0 ******//
Open /dev/char/10:56 failed
//****** PHY GROUP 1 ******//
Open /dev/char/10:55 failed
//****** Intel C827 Retimer ******//
Port0 10G                     : Down
Port1 10G                     : Down
Port2 10G                     : Down
Port3 10G                     : Down
Port4 10G                     : Down
Port5 10G                     : Down
Port6 10G                     : Down
Port7 10G                     : Down
Retimer A Version             : 101c.1064
Retimer B Version             : 101c.1064


Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** MAC ******//
Object Id                     : 0xF100000
PCIe s:b:d.f                  : 0000:08:00.0
Device Id                     : 0x0b30
Numa Node                     : 0
Ports Num                     : 01
Bitstream Id                  : 0x23000010000000
Bitstream Version             : 0.2.3
Pr Interface Id               : 901dd697-ca79-4b05-b843-8138cefa2846
Number of MACs                : 8
MAC address 0                 : 64:4C:36:12:E8:C8
MAC address 1                 : 64:4C:36:12:E8:C9
MAC address 2                 : 64:4C:36:12:E8:CA
MAC address 3                 : 64:4C:36:12:E8:CB
MAC address 4                 : 64:4C:36:12:E8:CC
MAC address 5                 : 64:4C:36:12:E8:CD
MAC address 6                 : 64:4C:36:12:E8:CE
MAC address 7                 : 64:4C:36:12:E8:CF


Running mode: nlb
Running fpgadiag lpbk1 vh0-vh0 test...
AFU NLB not found
Error: configuration failed.
Failed Test: vh0-vh0
Command 'fpgadiag -B 0x8 --mode=lpbk1 --read-vc=vh0 --write-vc=vh0 --multi-cl=4 --begin=1024 --end=1024 --timeout-sec=1 --cont -G 850adcc2-6ceb-4b22-9722-d43375b61c66 -T 200000000' returned non-zero exit status 102.
Running fpgadiag lpbk1 vh0-vh1 test...
AFU NLB not found
Error: configuration failed.
Failed Test: vh0-vh1
Command 'fpgadiag -B 0x8 --mode=lpbk1 --read-vc=vh0 --write-vc=vh1 --multi-cl=4 --begin=1024 --end=1024 --timeout-sec=1 --cont -G 850adcc2-6ceb-4b22-9722-d43375b61c66 -T 200000000' returned non-zero exit status 102.
Running fpgadiag lpbk1 vh1-vh0 test...
AFU NLB not found
Error: configuration failed.
Failed Test: vh1-vh0
Command 'fpgadiag -B 0x8 --mode=lpbk1 --read-vc=vh1 --write-vc=vh0 --multi-cl=4 --begin=1024 --end=1024 --timeout-sec=1 --cont -G 850adcc2-6ceb-4b22-9722-d43375b61c66 -T 200000000' returned non-zero exit status 102.
Running fpgadiag lpbk1 vh1-vh1 test...
AFU NLB not found
Error: configuration failed.
Failed Test: vh1-vh1
Command 'fpgadiag -B 0x8 --mode=lpbk1 --read-vc=vh1 --write-vc=vh1 --multi-cl=4 --begin=1024 --end=1024 --timeout-sec=1 --cont -G 850adcc2-6ceb-4b22-9722-d43375b61c66 -T 200000000' returned non-zero exit status 102.
Finished Executing NLB (FPGA DIAG) Tests

Running mode: dma_afu
Running fpga_dma_test test on DDR4_A...

Running test in HW mode
AFU DMA not found
Error fpgaDmaOpen: not found
Failed Test: fpga_dma_test 0 -B 0x8 -D 0 -S 4294967296 -G 850adcc2-6ceb-4b22-9722-d43375b61c66
Command 'fpga_dma_test 0 -B 0x8 -D 0 -S 4294967296 -G 850adcc2-6ceb-4b22-9722-d43375b61c66' returned non-zero exit status 1.
Running fpga_dma_test test on DDR4_B...

Running test in HW mode
AFU DMA not found
Error fpgaDmaOpen: not found
Failed Test: fpga_dma_test 0 -B 0x8 -D 1 -S 4294967296 -G 850adcc2-6ceb-4b22-9722-d43375b61c66
Command 'fpga_dma_test 0 -B 0x8 -D 1 -S 4294967296 -G 850adcc2-6ceb-4b22-9722-d43375b61c66' returned non-zero exit status 1.
Running fpga_dma_test test on DDR4_C...

Running test in HW mode
AFU DMA not found
Error fpgaDmaOpen: not found
Failed Test: fpga_dma_test 0 -B 0x8 -D 2 -S 1073741824 -G 850adcc2-6ceb-4b22-9722-d43375b61c66
Command 'fpga_dma_test 0 -B 0x8 -D 2 -S 1073741824 -G 850adcc2-6ceb-4b22-9722-d43375b61c66' returned non-zero exit status 1.
Running fpga_dma_test test on QDR...

Running test in HW mode
AFU DMA not found
Error fpgaDmaOpen: not found
Failed Test: fpga_dma_test 0 -B 0x8 -D 3 -S 16777216 -G 850adcc2-6ceb-4b22-9722-d43375b61c66
Command 'fpga_dma_test 0 -B 0x8 -D 3 -S 16777216 -G 850adcc2-6ceb-4b22-9722-d43375b61c66' returned non-zero exit status 1.
Finished Executing DMA Tests


Built-in Self-Test Completed.

 

wchiah
Employee
148 Views

Hi Max,

Thanks for double confirm that. We can confirm that there is no missing step/driver error.
May I know server OS and kernel version that you are using ? Currently PAC N3000 cards support:

  • CentOS Linux version 7.6 kernel 3.10 or kernel 4.19
  • Red Hat* Enterprise Linux* (RHEL) version 7.6 kernel 3.10
  • It is possible to happen if your OS is not in the suggested version or missing file (kernel headers) 

Apart of that, is there any hardware you are running on ?

  • IF you don’t have an FPGA platform in your system.
  • It is expected for the software not to find any accelerators (well, to be fair, there aren't any ).
  • If you want to run your OPAE application without hardware, you can run it against a simulation of your accelerator in the AFU Simulation Environment (ASE).
  • You'll need to link your application against a different implementation of the OPAE library (libopae-c-ase instead of libopae-c) and run your accelerator RTL through a logic simulator.
  • Have a look at the AFU user guide for more details on how to use ASE.
    https://www.intel.com/content/www/us/en/programmable/documentation/rjg1562957780901.html
  • In some case, the error might also occur if the FPGA image doesn’t match the test to do, hence the software can’t connect with the AFU which has the same accelerator ID

Hope this can help you

Regards,

WeiChuan_C_Intel

maxdd
Beginner
140 Views

I have followed the instructions to install kernel headers. Here is my os/kernel version.

$ cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"


$ cat /etc/centos-release
CentOS Linux release 7.6.1810 (Core)


$ uname -r
4.19.106-rt45

 

And I have an N3000-2 inserted to the server. You can find the output of 'lspci | grep acc' in my original question post.

 

There is some error in the output of 'fpgabist -i 0x0b30'. I don't know if that indicate anything wrong. Could you please help me check that?

 

Also, I have another post and I think that problem might be related to this one. Could you please take a look? Thanks!

https://community.intel.com/t5/FPGA-SoC-And-CPLD-Boards-And/how-to-use-N3000-as-a-plain-NIC-to-send-...

wchiah
Employee
119 Views

Hi Max,

Thanks for your reply, as mention, It is expected for the software not to find any accelerators
if you don’t have an FPGA platform in your system.
Maybe you can try run it against a simulation of your accelerator in the AFU Simulation Environment (ASE).

Meanwhile for the case related to "./nvmupdate64e and device not found"
I am working on it, might need sometime expected will reply you within 3 days.

Regards,

WeiChuan_C_Intel

 

 

wchiah
Employee
94 Views

Hi Max,

I think I had answered your question about "why the accelerator not found".
I will set this as close-pending. 
Let me know if you still have any other questions about this issue.
Else, I will close this after 3 days.

Regards,
WeiChuan_C_Intel

wchiah
Employee
61 Views

Hi Max,

I do not receive any reply from you since last week.
In anticipation that your question has been answered. I am setting this case to closed.
Feel free to get back to us if you facing any other problems in the future.

Regards,
WeiChuan_C_Intel

Reply