Ashish Kashinath

Members
  • Content Count

    5
  • Joined

  • Last visited

About Ashish Kashinath

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi folks, we are facing issues while running acceptance tests on NetFPGA SUME board. We are following steps listed in: https://github.com/NetFPGA/NetFPGA-SUME-public/wiki/Acceptance-Test-Project The steps work fine till "make cores" - Next, when we run "make test", the "Run Auto Test" does not terminate. We have attached screenshots from our tests here. Could you tell us if we are missing something? We just want to make sure that our board is not having any fault. Any help in this regard is highly appreciated. Regards, pic1
  2. Hi folks, We have a NetFPGA SUME and are bringing it up on a Dell T630 server with a Dell 0NT78X motherboard having a PCIe3.0 slot and running the acceptance tests mentioned in https://github.com/NetFPGA/NetFPGA-SUME-public/wiki/Acceptance-Test-Project * The board is detected as a USB-UART target in the acceptance test * In the acceptance test, we run the "Run Auto Test". It says the bitstream is not found and asks to compile the project. (screenshot 1_cannot_find_bitstream.png) * On clicking yes, it says acceptance test xxxx does not exists and throws up a bunch of popups (screenshot 2_compiling_acceptance_tests.png) * When we try to build the aceptance tests by running the commands such as make PROJ=ddr3B project compile, it continues for a while and then gets stuck at a point such as the screenshot 3_progress_halted.png (screenshot 3_progress_halted.png) Could this be a hardware issue with the board? Could you folks help us with this? Note: The board does not get detected as a hardware target from Vivado GUI (screenshot 4_vivado_not_detecting_sume.png). Furthermore commands to flash bitfiles into the FPGA such as fpga -f reference_nic.bit brings up a error that the connection to the host failed, even when the SUME is properly seated in the PCIe3.0 G3 slot. (screenshot 5_bitfile_writing_not_working.png)
  3. Ashish Kashinath

    Issue