Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
761 Views

FIM and BMC Firmware not available on Acceleration Board A10

Jump to solution

I was installing OPAE on host machine, my PC, for Intel Programmable Acceleration Card with Intel Arria 10 GX FPGA  and encounted the attached problem when ruuning the following command

$ sudo fpgainfo fme

Screenshot from 2020-07-03 15-26-22.png

Any helpful suggestion ? 

Thanks

0 Kudos

Accepted Solutions
Highlighted
Employee
670 Views

Hi,


Since your PAC card is from 1.0Beta version, you will need to update it to 1.1 version before proceeding to 1.2.


So you will need to update the board to 1.1 PV before updating to 1.2 PV. Sorry for the inconvenience.


Follow the "Identifying and Updating FIM" section of the 1.1PV version of the Intel Acceleration Stack Quick Start Guide for Intel Programmable Acceleration Card with Intel Arria 10 GX FPGA to first update to 1.1PV FIM (dcp_1_1.rpd).

Note: • It is acceptable to leverage the 1.2 OPAE packages when following the FIM update instructions from the 1.1PV version of the Intel Acceleration Stack Quick Start Guide for Intel Programmable Acceleration Card with Intel Arria 10 GX FPGA.

• 1.1PV runtime download package can be located here. For access to the previous version of the Intel Acceleration Stack Quick Start Guide for Intel Programmable Acceleration Card with Intel Arria 10 GX FPGA, refer to the "Intel Acceleration Stack Quick Start Guide for Intel Programmable Acceleration Card with Intel Arria 10 GX FPGA Archives" section.

2. Follow the instructions in the "Updating FPGA Flash and BMC Firmware" section in the current version of this document


View solution in original post

0 Kudos
43 Replies
Highlighted
Employee
411 Views

Hi,


May I know which acceleration stack version are you using for your installation? The board that you are using is from Acceleration Stack 1.1. So if you are using Acceleration Stack 1.2 or 1.2.1 then I would recommend you to update your board to the Acceleration Stack software you are using before moving forward.


0 Kudos
Highlighted
Beginner
409 Views

Right, I guess I used the 1.1 version of acceleration stack but I directly download from here Screenshot from 2020-07-06 12-28-00.png

which I thought it could be installed as 1.2.1 version. Then I found the upgrade page hereScreenshot from 2020-07-06 12-30-33.png

Is it right for updating the FIM and BMC version?

Thanks!

0 Kudos
Highlighted
Beginner
404 Views

Hi, now I have a new issue during updating process:Screenshot from 2020-07-06 18-14-33.png

It always stops here when I run setup.sh even after I install this package dependency. 

0 Kudos
Highlighted
Employee
400 Views

Hi,


I would recommend you to download Acceleration Stack 1.2 from https://www.intel.com/content/www/us/en/programmable/solutions/acceleration-hub/archives.html and update the FIM and BMC.


0 Kudos
Highlighted
Beginner
398 Views

Thanks but that's the one I've downloaded for updating and the problem emerged during the process. There is always a conflict between opae-lib and libjson Screenshot from 2020-07-07 10-35-37.png

0 Kudos
Highlighted
Employee
390 Views

Hi,


May I know if the issue is fixed after you removed the conflict?


0 Kudos
Highlighted
Beginner
389 Views

The problem is still there. Even happens when I reinstall the previous 1.2.1 version, which did not happen before. Now I remove the card and put it on another PC trying to install the 1.2 version.

0 Kudos
Highlighted
Employee
383 Views

Hi,


May I know what is the issue that you are observing? If it is related to the initial screenshot then this is related to system setup issue and not related to PAC card.


0 Kudos
Highlighted
Beginner
380 Views

I know the problem is about system setup as I attached a screenshot describing the conflict between OPAE-lib and libjson. But this issue never happened before when I installed the 1.2.1 acceleration stack at very first time.

To be specific, in the after installation process, when I launch the setup.sh and answer all questions with Yes and set path to the default,  the script will quit with a dependency problem(opae-lib depend on libjson) but I already have the libjson at the newest version, which makes me confused.

Now I put the PAC board on another PC and install the acceleraiton stack 1.2, finding it is the problem of lower version of FIM and BMC firmware on PAC board (1.1).  I'm contacting the Bitware to get the BittWorks II Toolkit Lite software as I see the instruction about how to update FIM and BMC version to 1.2 on the quick start guide. Hope this will solve the problem and bring up the PAC board.

0 Kudos
Highlighted
Employee
377 Views

Hi,


When you install the version 1.2, I think you didn't uninstall the 1.2.1 which causes the conflict. Usually I would recommend user to uninstall the previous library use in order to downgrade the acceleration stack version.


0 Kudos
Highlighted
Beginner
376 Views

That could be the problem but I didn't find any uninstall instruction provided on the guide and I've already removed the OPAE using command line. Is there any other way to uninstall the stack?

Thanks! 

0 Kudos
Highlighted
Employee
367 Views

Hi,


If you look into the quick userguide, you will observed "sudo yum remove opae-*.x86_64" which is to remove all the OPAE library.


0 Kudos
Highlighted
Beginner
360 Views
 
0 Kudos
Highlighted
Beginner
356 Views

Alright, that issue is passed.

Now I'm updating the FIM and BMC from 1.1 to 1.2 but after running setup_fim_and_bmc.sh for a while and flash successfully verified, the following error happens:

Screenshot from 2020-07-09 17-53-16.png

I tried several times to rerun but it always stopped here.

0 Kudos
Highlighted
Employee
344 Views

Hi,


Have you try power cycle your system? Are you able to detect the PAC card?


0 Kudos
Highlighted
Beginner
343 Views

Yes, I did reboot the system and the device was detected as well. The script still stopped there.

0 Kudos
Highlighted
Employee
339 Views

Hi,


When you mention reboot, do you performed soft reboot or hard reboot? I would recommend you to shut down your system and power on again to see if the issue is still observed.


0 Kudos
Highlighted
Beginner
338 Views

I did both but the issue is still there. Is this problem normal?

0 Kudos
Highlighted
Employee
337 Views

Hi.


Could provide me the step you used and where it is stuck?


0 Kudos