New Contributor
New ContributorHi Kian,
1) chicken and egg problem: since I cannot deploy any image on the board, I haven't be able to test it with any program (my end goal is to use Intel P4 SDK with this card)
2) the only thing that I flashed on the card is a more recent BMC firmware (using a USB/jtag cable). The initial version was 3.1. I upgraded it to 3.14 but to no avail:
Board Management Controller NIOS FW version: 3.14.0
Board Management Controller Build version: 3.14.0
3) the problem occurs systematically after any number of (cold) reboot
I'm not aware of the SDM firmware. Is it distinct from the BMC firmware ?
Regards
Frederic
Frequent ContributorHi Frederic ,
Thanks for the reply, so basically the fpga board does not have any image in it yet other than the BMC firmware on max10.
I was trying to find which version is associated with Pr Interface Id : 00bc56cf-9e1f-5bf0-8011-48736ec862c9
Anyway, I discuss with my colleague over here on this issue, we should focus on why fpgasupdate fail with missing files. I were thinking because the card is non functional without valid image , it is triggering the SDM (secure device manager) to try reconfigure the fpga and fail. It is a separate firmware from BMC but have some interface with it.
Do you know the OFS version that you installed in your system, I only saw OPAE is 2.1.1 but dfl version unknown except you are running kernel 5.15.92) and also the Quartus version that is installed in your system?
Could you try using Quartus to program/flash the fpga and see whether the fpga is working?
Thanks
Regards
Kian
