New Contributor
Regular ContributorHi Daniel,
Next , are you using gen4 or gen3 design ?
Please be aware that Gen4x4 is not supported in Agilex 5 Modular devkit, this feature will be hidden in Quartus v25.1.1 release
While I am trying gen3x4 design, I able to get the device link successful - attach the design .qar (please have a try on your host)
Regards,
Wincent_Altera
New ContributorHi Wincent,
Thanks for your quick response.
It’s strange that you couldn’t open the QAR file - I was able to open it without any issues. Regardless, I’ve created a new one, which is attached to this message.
Regarding your second question, I used the Gen3x4 configuration for the design.
Did you make any modifications to your design beyond generating the example design?
Also, do you think the issue could be related to the host system I’m using? If so, I’d appreciate any guidance on why that might be the case and how I can check for host compatibility.
My host supports up to Gen5, and the Agilex 5 is powered via an external power supply rather than through the PCIe slot. I assumed that would be sufficient, but is there any other criterion that needs to be met to ensure proper functionality?
Best regards,
danield17
Regular ContributorHi Daniel,
Sorry for taking 4 days to reply this, I miss out your reply in last week and over the weekend..
Did you make any modifications to your design beyond generating the example design?
>> Generate the Design Example by default without changing anything
>> One thing i change is on the design example tab where I select the "target devkit" it help to assign all pin assignment accordingly on the Modular Devkit
>>
Also, do you think the issue could be related to the host system I’m using? If so, I’d appreciate any guidance on why that might be the case and how I can check for host compatibility.
>> Based on my experience of working on PCIe, certain host having problem to direct perform speed degrade if the PCIe Speed on BIOS setting is selected as "AUTO" , perhaps you can try to select "GEN3" same as your design and check if this work or not.
>> this method work for me in most of the previous device (Arria 10, Stratix 10)
I noticed that in your project you selected the device number A5ED065BB32AE4SR0, whereas when selecting the modular dev kit from the board tab in the device selection menu, it defaults to A5ED065BB32AE6SR0. Is your modular dev kit different from the default one, or is it normal that the board’s default device number isn’t always the one we should use?
>> My devkit is the normal one with OPN A5ED065BB32AE6SR0 https://www.intel.com/content/www/us/en/products/details/fpga/development-kits/agilex/a5e065b-modular.html
>> I believe it is default setting if I select the "current development kit" in IP GUI during Design Example Generation
>> Anyway the .sof passing 100 % upon programming
>> the "4s" and "6s" represent the speed grade of PCIe, where the "4s" would be the fastest one (supporting gen4)
>> Did you try my .qar file ? is it work on your side ?
Regards,
Wincent_Altera
Regular ContributorHi Daniel,
I try to check on your design.
The result still the same, why not you try to provide me only the .sof file ?
I try at my host, meanwhile please try out the design I provided to you as well.
New ContributorHi Wincent,
I have tried you design and it seems like it worked for me and was able to identify. However, the issue with device identification by the operating system is now occurring intermittently, even without any changes to the design.
Even when device identification is successful, the user application doesn't function as expected. I'm encountering "queue reset failed" errors, as shown in my first post, or the application appears to initialize correctly but fails to transfer data. I've attached the application log for your review.
Currently, I'm still focusing on resolving the device identification issue. Any insights you can provide on either this or the user application problems would be greatly appreciated.
Additionally, I've attached the .sof file for your reference. Be aware that my design differs from yours in two key ways:
I am using MCDMA + BAM mode with the AVMM interface instead of the AVST interface.
There is 1MB of on-chip memory connected to both the DMA and BAM interfaces, mapped to BAR2 in the BAM interface, offset `0x0080_0000`.
While I acknowledge that the problem could be related to the computer I'm using, I want to be thorough and avoid making assumptions. If possible, I would appreciate it if you could review my .sof file or even try implementing the design yourself and running the software provided with the example — specifically the "perfq_app". I've also attached the software folder in case you don't have it.
If you need guidance on how to build and run the software, you can refer to the MCDMA Example Design User Guide.
The specific command I was trying to run is:
sudo ./perfq_app -b 0000:02:00.0 -u -p 128 -l 5 -d 2 -c 1 -a 2
Best Regards,
danield17
