Application Acceleration With FPGAs
Programmable Acceleration Cards (PACs), DCP, FPGA AI Suite, Software Stack, and Reference Designs
477 Discussions

Remote SigntalTap setup issue on Intel PAC Arria10

User1582192733150209
513 Views

Dear Sir/madam,

 

I am running the example nlb_mode_0_stp on Intel PAC arria10 card.

the purpose is try remote signaltap debug function based on vendor provided example and Accelerator Function Unit Developers Guide for Intel FPGA Programmable Acceleration Card.

 

the operation on the debug target host with the PAC installed worked good as I excpected

 

[root@fig01 samples]# ls

dma_afu   hello_afu   nlb_mode_0   README

eth_e2e_e10 hello_intr_afu nlb_mode_0_stp streaming_dma_afu

eth_e2e_e40 hello_mem_afu nlb_mode_3

[root@fig01 samples]# sudo fpgaconf nlb_mode_0_stp/bin/nlb_mode_0_stp.gbs 

[root@fig01 samples]# sudo mmlink -P -B 

 ------- Command line Input START ---- 

 

 Bus         : -1

 Device        : -1

 Function       : -1

 Socket-id      : -1

 Port         : 0

 IP address      : 0.0.0.0

 ------- Command line Input END ---- 

 

PORT Resource found.

Remote STP : Assert Reset

Remote STP : De-Assert Reset

Read signature value 53797343 to hw

Read version value 1 to hw

Read write fifo capacity value 32 to hw

m_listen: 4

listening on ip: 0.0.0.0; port: 0

^Z

[1]+ Stopped        sudo mmlink -P -B

 

-----------------------------the end of target host----------------

below is operation on remote debug host, where the system_consule is not recognized as below for some reason.

 

I did check the PATH environment variable setting ,it looks setting correctly, Any suggestion for this issue?

 

thanks

 

Jim 

 

0 Kudos
4 Replies
User1582192733150209
349 Views

the information from the remote debug host

 

Microsoft Windows [Version 10.0.15063]

(c) 2017 Microsoft Corporation. All rights reserved.

 

C:\Users\a1228079>cd D:\Jimlin\FPGA\dev kits\PAC_Arria10GX\example\nlb_mode_0_stp

 

C:\Users\a1228079>d:

 

D:\Jimlin\FPGA\dev kits\PAC_Arria10GX\example\nlb_mode_0_stp>system_console --rc_script=mmlink_setup_profiled.tcl remote_debug.sof 192.168.111.204 3333

'system_console' is not recognized as an internal or external command,

operable program or batch file.

 

D:\Jimlin\FPGA\dev kits\PAC_Arria10GX\example\nlb_mode_0_stp>

0 Kudos
User1582192733150209
349 Views

I found a wrong spelling for system_console, but after I changed it to correct one system-console ,,issue is still there as below

 

D:\Jimlin\FPGA\dev kits\PAC_Arria10GX\example\nlb_mode_0_stp>system-console --rc_script=mmlink_setup_profiled.tcl remote_debug.sof 192.168.111.204 3333

'system-console' is not recognized as an internal or external command,

operable program or batch file.

 

D:\Jimlin\FPGA\dev kits\PAC_Arria10GX\example\nlb_mode_0_stp>

0 Kudos
User1582192733150209
349 Views

I have found that command not being recognized issue was caused by PATH environment variable.

On the 37 of the AFU Developer’s Guide for Intel FPGA Programmable Acceleration Card , it says your PATH environment variable on the remote

debug host is setup to point to the following location in the Intel Quartus Prime Pro Edition installation:

<installation-path>/<q-edition>/sopc_builder/bin

 

Actually, the PATH should be <installation-path>/<q-edition>/quartus/sopc_builder/bin

there is a middle directory quartus between /<q-edition> and /sopc_builder.

 

hope user manual can be more accurate and save customer time

 

thanks

 

Jim

0 Kudos
MEIYAN_L_Intel
Employee
349 Views

Hi,

Thank you for your information.

I will report this to the developer.

Thanks

0 Kudos
Reply