Intel® DevCloud
Help for those needing help starting or connecting to the Intel® DevCloud
1047 Discussions

arria 10 won't work [ devcloud implementation fails]

AVolo2
Novice
550 Views

Hi Guys

How is it going?

I am trying to get through https://github.com/intel/FPGA-Devcloud/tree/master/main/QuickStartGuides/OpenCL_Program_PAC_Quicksta...

 

But first it fails to locate the setup tools, then after sourcing the environment manually still  third execution fails

 

aoc device/hello_world.cl -o bin/hello_world_fpga.aocx -board=pac_a10
aoc: Running OpenCL parser....
aoc: OpenCL parser completed 
aoc: Linking Object files....
aoc: Optimizing and doing static analysis of code...
aoc: First stage compilation completed successfully.
aoc: Compiling for FPGA. This process may take several hours to complete.  Prior to performing this compile, be sure to check the reports to ensure the design will meet your performance targets.  If the reports indicate performance targets are not being met, code edits may be required.  Please refer to the Intel FPGA SDK for OpenCL Best Practices Guide for information on performance tuning applications for FPGAs.
Error (23035): Tcl error: 
Error (23031): Evaluation of Tcl script build/entry.tcl unsuccessful
Error: Quartus Prime Shell was unsuccessful. 2 errors, 0 warnings
Error: Compiler Error, not able to generate hardware

we also got a local arria 10gx  PAC which was not possible to get running up to a point where hello world example works. But at the devcloud it neither works up to the hello world example. So far only up to the point below which passes

aocl diagnose

 

0 Kudos
17 Replies
BoonBengT_Intel
Moderator
522 Views

Hi @AVolo2,

 

Thank you for posting in Intel community forum and hope all is well.

To clarify, are you saying that when you run the tools_setup command it is failing?

On which node are you connected to in the devcloud?

 

Suspecting that they might be some node anomaly which is causing error.

U have managed to try the mention steps to perform a tools_setup and aocl diagnose and diagnostic passed.

Hence would recommended maybe to try another node or node s005-003.

Hope to hear from you

BoonBengT_Intel_0-1655777077775.png

 

Best Wishes

BB

 

AVolo2
Novice
512 Views

Hi, 

Thank you for following up!

Q.1 : "To clarify, are you saying that when you run the tools_setup command it is failing?"

A.1:There is no setup_tools alias in bach terminal unfortunately

I have to source environment manually

Q2. "On which node are you connected to in the devcloud?"

) Enter Specific Node Number

Number: 1
Which Arria 10 PAC Development Stack release would you like to source?
0) 1.2
1) 1.2.1

Number: 1

running: qsub -q batch@v-qsvr-fpga -I -l nodes=s005-n003:ppn=2
qsub: waiting for job 33988.v-qsvr-fpga.aidevcloud to start
qsub: job 33988.v-qsvr-fpga.aidevcloud ready


########################################################################
-------
# Resources:           neednodes=s005-n003:ppn=2,nodes=s005-n003:ppn=2,walltime=06:00:00
########################################################################

 

 

 

How do I switch to try another node or node s005-003? what are nodes available how to try them?

AVolo2
Novice
492 Views

any ideas

now it got to another issue

can it be because fpga compilation [ that takes long got ssh to devcloud abruption]? else?

BSP Diagnostics                                                     
--------------------------------------------------------------------
--------------------------------------------------------------------
Device Name:
acl0

BSP Install Location:
/opt/a10/inteldevstack/a10_gx_pac_ias_1_2_1_pv/opencl/opencl_bsp

Vendor: Intel Corp

Physical Dev Name   Status            Information

pac_ee00000         Uninitialized     OpenCL BSP not loaded. Must load BSP using command: 
                                      'aocl program <device_name> <aocx_file>'
                                      before running OpenCL programs using this device

DIAGNOSTIC_PASSED
--------------------------------------------------------------------

Call "aocl diagnose <device-names>" to run diagnose for specified devices
Call "aocl diagnose all" to run diagnose for all devices
u155004@s005-n002:~/A10_OPENCL_AFU/hello_world/bin$ aocl program acl0 hello_world_fpga_unsigned.aocx
aocl program: Running program from /opt/a10/inteldevstack/a10_gx_pac_ias_1_2_1_pv/opencl/opencl_bsp/linux64/libexec
Program succeed. 
u155004@s005-n002:~/A10_OPENCL_AFU/hello_world/bin$ ./host
Querying platform for info:
==========================
CL_PLATFORM_NAME                         = Intel(R) FPGA SDK for OpenCL(TM)
CL_PLATFORM_VENDOR                       = Intel(R) Corporation
CL_PLATFORM_VERSION                      = OpenCL 1.0 Intel(R) FPGA SDK for OpenCL(TM), Version 19.4

Querying device for info:
========================
CL_DEVICE_NAME                           = pac_a10 : Intel PAC Platform (pac_ee00000)
CL_DEVICE_VENDOR                         = Intel Corp
CL_DEVICE_VENDOR_ID                      = 4466
CL_DEVICE_VERSION                        = OpenCL 1.0 Intel(R) FPGA SDK for OpenCL(TM), Version 19.4
CL_DRIVER_VERSION                        = 19.4
CL_DEVICE_ADDRESS_BITS                   = 64
CL_DEVICE_AVAILABLE                      = true
CL_DEVICE_ENDIAN_LITTLE                  = true
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE          = 32768
CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE      = 0
CL_DEVICE_GLOBAL_MEM_SIZE                = 8589933568
CL_DEVICE_IMAGE_SUPPORT                  = false
CL_DEVICE_LOCAL_MEM_SIZE                 = 16384
CL_DEVICE_MAX_CLOCK_FREQUENCY            = 1000
CL_DEVICE_MAX_COMPUTE_UNITS              = 1
CL_DEVICE_MAX_CONSTANT_ARGS              = 8
CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE       = 2147483392
CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS       = 3
CL_DEVICE_MEM_BASE_ADDR_ALIGN            = 8192
CL_DEVICE_MIN_DATA_TYPE_ALIGN_SIZE       = 1024
CL_DEVICE_PREFERRED_VECTOR_WIDTH_CHAR    = 4
CL_DEVICE_PREFERRED_VECTOR_WIDTH_SHORT   = 2
CL_DEVICE_PREFERRED_VECTOR_WIDTH_INT     = 1
CL_DEVICE_PREFERRED_VECTOR_WIDTH_LONG    = 1
CL_DEVICE_PREFERRED_VECTOR_WIDTH_FLOAT   = 1
CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE  = 0
Command queue out of order?              = true
Command queue profiling enabled?         = true
Using AOCX: hello_world.aocx
Context callback: Malformed program binary: missing .acl.board section
Context callback: kernel argument info is not available
Context callback: Invalid binary
ERROR: CL_INVALID_BINARY 
Location: ../common/src/AOCLUtils/opencl.cpp:407
Failed to create program with binary

qsub: job 33996.v-qsvr-fpga.aidevcloud completed

 

AVolo2
Novice
506 Views

seems I got through

thanks

but it is faulty at the another issue listed above

 

AVolo2
Novice
489 Views

unfortunately connection seems to interrupt every time I am trying to run this step

so ifthe output is broken or not I am not certain

if it is that may be the cause of the next mentioned ahead step failing 

aoc device/hello_world.cl -o bin/
aoc: Running OpenCL parser....
aoc: OpenCL parser completed 
aoc: Linking Object files....
aoc: Optimizing and doing static analysis of code...
aoc: First stage compilation completed successfully.
aoc: Compiling for FPGA. This process may take several hours to complete.  Prior to performing this compile, be sure to check the reports to ensure the design will meet your performance targets.  If the reports indicate performance targets are not being met, code edits may be required.  Please refer to the Intel FPGA SDK for OpenCL Best Practices Guide for information on performance tuning applications for FPGAs.
client_loop: send disconnect: Broken pipe
client_loop: send disconnect: Broken pipe
AVolo2
Novice
484 Views

then without integrity check I could execute further steps but it fails on the step of executing ./host as you may see from posts above

 source $AOCL_BOARD_PACKAGE_ROOT/linux64/libexec/sign_aocx.sh -H openssl_manager -i hello_world_fpga.aocx -r NULL -k NULL -o hello_world_fpga_unsigned.aocx
The script assumes the PACsign and Intel Acceleration Stack environment is setup. If not run the command : <stack_installation_path>/init_env.sh
hsm_manager=openssl_manager
aocx filename/path=hello_world_fpga.aocx
root_public_key=NULL
csk_public_key=NULL
output filename/path=hello_world_fpga_unsigned.aocx
null=1
openssl hsm_manager_options=openssl_manager 
input path =.
input filename =hello_world_fpga.aocx
output path =.
output filename =hello_world_fpga_unsigned.aocx
Extracted the filename as hello_world_fpga_unsigned 
1. Extracted the bin from the aocx 
2. Extracted the gzip compressed GBS file from the .bin
gzip: temp_hello_world_fpga_unsigned.gbs already exists; do you wish to overwrite (y or n)? y
3. Uncompressed .gz it to get the GBS file
Initiating PACSign tool to sign the GBS. This process will take a couple of minutes...
Creating unsigned aocx file by signing a NULL key 
No root key specified.  Generate unsigned bitstream? Y = yes, N = no: Y
No CSK specified.  Generate unsigned bitstream? Y = yes, N = no: Y
4. Signed the GBS 
gzip: signed_hello_world_fpga_unsigned.gbs.gz already exists; do you wish to overwrite (y or n)? y
5. Compressed the gbs file 
6. Added the signed gzip file to fpga.bin 
7. Added the fpga.bin file back into aocx file
The signed file hello_world_fpga_unsigned.aocx has been generated. Use the command aocl program <device_name> <filename>.aocx to program it on the FPGA card
AVolo2
Novice
480 Views
aoc device/hello_world.cl -o bin/hello_world_fpga.aocx -board=pac_a10

so the question is how to confirm the command resulted in success given during its execution connectivity always gets lost ?

 

AVolo2
Novice
468 Views

seems it worked;

it is the hello-world example, right?

~/A10_OPENCL_AFU/hello_world/bin$ ./host                                                                    Querying platform for info:                                                                                                   ==========================                                                                                                    CL_PLATFORM_NAME                         = Intel(R) FPGA SDK for OpenCL(TM)                                                   CL_PLATFORM_VENDOR                       = Intel(R) Corporation                                                               CL_PLATFORM_VERSION                      = OpenCL 1.0 Intel(R) FPGA SDK for OpenCL(TM), Version 19.4                                                                                                                                                        Querying device for info:                                                                                                     ========================                                                                                                      CL_DEVICE_NAME                           = pac_a10 : Intel PAC Platform (pac_ee00000)                                         CL_DEVICE_VENDOR                         = Intel Corp                                                                         CL_DEVICE_VENDOR_ID                      = 4466                                                                               CL_DEVICE_VERSION                        = OpenCL 1.0 Intel(R) FPGA SDK for OpenCL(TM), Version 19.4                          CL_DRIVER_VERSION                        = 19.4                                                                               CL_DEVICE_ADDRESS_BITS                   = 64                                                                                 CL_DEVICE_AVAILABLE                      = true                                                                               CL_DEVICE_ENDIAN_LITTLE                  = true                                                                               CL_DEVICE_GLOBAL_MEM_CACHE_SIZE          = 32768                                                                              CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE      = 0                                                                                  CL_DEVICE_GLOBAL_MEM_SIZE                = 8589933568                                                                         CL_DEVICE_IMAGE_SUPPORT                  = false                                                                              CL_DEVICE_LOCAL_MEM_SIZE                 = 16384                                                                              CL_DEVICE_MAX_CLOCK_FREQUENCY            = 1000                                                                               CL_DEVICE_MAX_COMPUTE_UNITS              = 1                                                                                  CL_DEVICE_MAX_CONSTANT_ARGS              = 8                                                                                  CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE       = 2147483392                                                                         CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS       = 3                                                                                  CL_DEVICE_MEM_BASE_ADDR_ALIGN            = 8192                                                                               CL_DEVICE_MIN_DATA_TYPE_ALIGN_SIZE       = 1024                                                                               CL_DEVICE_PREFERRED_VECTOR_WIDTH_CHAR    = 4  
BoonBengT_Intel
Moderator
455 Views

Hi @AVolo2,


Good to know that you managed to get it work, for the clarification that you mention previously below are the answer for them:

1) how to confirm the command resulted in success

  A> By doing a batch submission on the steps #4 in the link you have above, that would output the log into 2 seperate files which will help to us understand the compilation even if connection timeout.

2) it is the hello-world example

  A> Yes you are right.


Hope that clarify your doubts.


Best Wishes

BB


BoonBengT_Intel
Moderator
437 Views

Hi @AVolo2,


Greetings, as we do not receive any further clarification on what is provided, and challenges are overcome previously, we will no longer monitor this thread. For new queries, please feel free to open a new thread and we will be right with you. Pleasure having you here.


Best Wishes

BB


AVolo2
Novice
413 Views

@BoonBengT_Intel 

today I noticed that devcloud won't work anymore after the server signature got changed;

It won't let to connect to a node.

How to do it? given the problem is that user got lost group association for access to PAC node

BoonBengT_Intel
Moderator
403 Views

Hi @AVolo2,

Apologies to hear that, however from my end I am still able to connect to devcloud.

Per understanding, there is a recent SSH server changes in the devcloud.

And steps has been mention in the email on what to perform and expect.


However if you are still having issues still persist and you are not able to connect to devcloud, would suggest to drop a note in the thread below, and our team will get back to you as soon as possible.

- https://community.intel.com/t5/Intel-DevCloud/Announcement-Changes-to-SSH-Server-on-DevCloud/m-p/139...

Cheers


Best Wishes

BB


AVolo2
Novice
391 Views

@BoonBengT_Intel 

Thank you for following up

However, the problem is not that I can not connect to the devcloud with the updated signatures,

But that it lost access to the [1) Arria 10 PAC Compilation and Programming - RTL AFU, OpenCL]
after the update due to the fact the user doesn't seem to have group association for 10 GX RTL AFU access.

 

Can you access the node s005-n007

ssh -L 4002:s005-n007:22 devcloud 

--------------------------------------------------------------------------------------

running: qsub -q batch@v-qsvr-fpga -I -l nodes=s005-n007:ppn=2
qsub: submit error (Unauthorized Request  MSG=group ACL is not satisfied: user u155004@login-2.aidevcloud, queue batch)

 

AVolo2
Novice
382 Views

@BoonBengT_Intel 

Could you also extend on the batch submission, please?

Because the step from the link above section 4 won't work

"

1) how to confirm the command resulted in success

  A> By doing a batch submission on the steps #4 in the link you have above, that would output the log into 2 seperate files which will help to us understand the compilation even if connection timeout."
u155004@login-2:~$ devcloud_login -b A10PAC 1.2.1 A10_v1.2.1_opencl_batch.sh
qsub: script file 'A10_v1.2.1_opencl_batch.sh' cannot be loaded - No such file or directory

 

 

AVolo2
Novice
367 Views

@BoonBengT_Intel The issue with node access has been resolved with help of Intel folks who addressed the permission issue

However I wasn't able to figure out how to use the reference example to run the batch submission

 devcloud_login -b A10PAC 1.2.1 A10_v1.2.1_opencl_batch.sh
qsub: script file 'A10_v1.2.1_opencl_batch.sh' cannot be loaded - No such file or directory
AVolo2
Novice
310 Views

@BoonBengT_Intel could you extend on the batch submission exampl, please?

BoonBengT_Intel
Moderator
265 Views

Hi @AVolo2,


Greetings and apologies for the delayed in response.

For the mention on the previous issues where having some challenge running example design seems to be overcome and currently there are another issues on the devcloud account related I am suspecting.


I am seeing a similar thread below on the issues hence lets continue our discussion there.

https://community.intel.com/t5/Intel-DevCloud/arria-10-won-t-work-devcloud-implementation-fails-2-co...

And we would marked this thread as closed, please do let us know if there is any concern there.


Best Wishes

BB


Reply