PCIe-385N board factory flash load 13.1

--- Quote Start ---

Hi hangyuxuan19910802,

If your board was functioning before you updated the flash with a design you compiled yourself, I would think that maybe the flash update was not successful or the aocx file was somehow invalid.

Depending on the board you have (A7 or D5), I would reprogram the flash with the factory design for 13.1 I previously posted using the "aocl flash <design>.aocx" command. Once you have done that, power down your system fully (not only reboot) and power it back up. Then check if you can do "aocl diagnostic" again.

Thanks,

G

--- Quote End ---

Thank you, gigi!!

I burnt factory image pcie385n_a7_factory.aocx from this post. It worked and I saw my a7 board can communicate with host machine through pcie, when I ran $ aocl diagnostic. Then I burnt hello_world.aocx again. After cold reboot the host machine, it crashed and showed the same information as before when I ran $ aocl diagnostic.

aocl diagnostic: running diagnostic from /home/jisuansuogcb/altera/13.1/hld/board/pcie385n/linux64/bin

running diagnostic for : acl0

fpga is in user mode. enabling bridges

using platform: altera sdk for opencl

failed clgetdeviceids.

error code: -1

aocl diagnostic: failed.

Something I am not sure is that when I ran $lspci | grep alter, there was no output, probably meaning board driver installation failure, according to get_started documents. As for the board driver installation, since I am using pcie 385n a7 board, I just ran $aocl install, the result was

aocl install: running install from /home/jisuansuogcb/altera/13.1/hld/board/pcie385n/linux64/bin

using kernel source files from /usr/src/kernels/2.6.18-274.el5xen-x86_64

make: entering directory `/usr/src/kernels/2.6.18-274.el5-xen-x86_64'

building modules, stage 2.

modpost

make: leaving directory `/usr/src/kernels/2.6.18-274.el5-xen-x86_64'

That means, as I understand, the driver was compiled successfully. And do I have to run any other commands for the driver installation? Or am I missing some processes before I run ./hello_world on host side? Another question is what does the factory hardware image .aocx do? If I burnt hello_world instead, and the default one should be erased, as I understand, the program of the default image which makes communication between board and host successful will be erased too,right?

Thanks!!

Yuxuan