errors running hello world kernel, need help with debugging info?

Question

I posted this in another thread, but I'm at a loss. I am not sure if this is a Bittware problem or not, and I would like to understand how to troubleshoot errors like this.

Building the kernel works fine. When running the hello world host program, the first sign of a problem comes with,

"MMD INFO : [acl0] New FPGA design has different periphery from programmed design.

MMD INFO : AOCX base and CvP periphery hashes differ. Programming will fail in hardware, so aborting."

I'm afraid this doesn't make sense to me, what is it telling me?

Full output of running hello world demo below:

--- Quote Start ---

Querying platform for info:==========================

CL_PLATFORM_NAME = Altera SDK for OpenCL

CL_PLATFORM_VENDOR = Altera Corporation

CL_PLATFORM_VERSION = OpenCL 1.0 Altera SDK for OpenCL, Version 14.0

Querying device for info:

========================

CL_DEVICE_NAME = s5phq_d8 : S5PHQ

CL_DEVICE_VENDOR = Bittware Inc

CL_DEVICE_VENDOR_ID = 4466

CL_DEVICE_VERSION = OpenCL 1.0 Altera SDK for OpenCL, Version 14.0

CL_DRIVER_VERSION = 14.0

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 = 0

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 = 2147483648

CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS = 3

CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS = 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? = false

Command queue profiling enabled? = true

Using AOCX: hello_world.aocx

MMD INFO : [acl0] New FPGA design has different periphery from programmed design.

MMD INFO : AOCX base and CvP periphery hashes differ. Programming will fail in hardware, so aborting.

MMD INFO : executing "quartus_pgm -c 1 -m jtag -o "P;reprogram_temp.sof@1""

Error (213013): Programming hardware cable not detected

MMD INFO : Link currently operating at 5 GT/s.

MMD INFO : Link operating at Gen 2 with 8 lanes.

MMD INFO : Expected peak bandwidth = 4000 MB/s

mmd program_device: Board reprogram failed

--- Quote End ---

altera_forum · Answer

Hi unterhausen,

That looks like a BittWare board support package problem to me. A quick way to confirm this would be to change your target device to the s5_ref using emulation. You would need to modify some of your environment variables, such as AOCL_BOARD_PACKAGE_ROOT=$ALTERAOCLSDKROOT/board/s5_ref and CL_CONTEXT_EMULATOR_DEVICE_ALTERA=s5_ref and then run your host executable. You would also need to recompile your kernel using "aoc --board s5_ref -march=emulation foo.cl -o foo.aocx" for example. You can find a complete walk through of these steps in the Altera getting started guide, but this is a good quick way to root cause what you're experiencing.

altera_forum · Answer

Btw, what operating system are you running this under?

altera_forum · Answer

--- Quote Start ---

Btw, what operating system are you running this under?

--- Quote End ---

running under windows 7, Visual Studio 2010.

Bittware compiled hello world kernel works, so everything else is set up properly, I just can't build a kernel. I was wondering if there is some v13 stuff left over in the board support package

altera_forum · Answer

As long as you correctly updated your environment variables to point to 14.0 stuff, you won't have any issue with 13.x versions remaining on your system. Keep in mind though if you were to switch back and forth between Quartus versions, you should flash the FPGA (with an rbf and the BittWare Tool Kit in this case) from the version you are targeting in addition to updating your environment variables. My personal recommendation is to not jump between Quartus versions and just use the most recent.

Using emulation is a good troubleshooting practice, plus it will allow you to keep developing while concurrently working with BittWare to resolve the issue so that you can run in hardware :) Generally, you can develop faster if you first prove out functional correctness using the emulator because those compile times are significantly faster, and then compile to hardware when you want to benchmark performance.

altera_forum · Answer

It is a new system and new board.  I didn't have a license for the 13.1 version of OCL, so although I had quartus installed and also the board support package installed, I never tested the OCL kernel build process.  It's possible I have some remnant of 13.1 on there, but I don't see it.  Of course, msft makes it difficult to see things in the environment variables

Forum Discussion

errors running hello world kernel, need help with debugging info?

7 Replies

Recent Discussions

Quartus did not start

Self service license server doesn't work

Timing analysis - long combinational path

Docker image for Quartus Pro 26.1 missing ?

Error (292014): Can't find valid feature line for core SLL_CA_HBC_T001_Hyperbus_Memory_Controller_10