Zynq DMA Scatter Gather still included when disabled...?

[Boscoe]

Hi all,

I have this strange problem that I haven't seen on the net.

I'm configuring a DMA in a block design for the Zynq and disabling SG mode as it's simple not needed for this part of the design. Please see the screenshot of the configuration below.

However even after reseting the block design outputs, reseting the synth, generating the bitstream and exporting the HW I still get SG mode enabled in the xparameters header file!? So when I try to use the simple mode it errors out saying it's incompatible with SG.

In Vitis I reimport the hardware, clean and build. A loop I've been running for a weeks now without an issue like this.

Any thoughts would be amazing!

Thanks

[asmi]

In Vitis I reimport the hardware, clean and build. A loop I've been running for a weeks now without an issue like this.

I've noticed that re-importing xsa file into Vitis sometimes is bugged - either it doesn't update the drivers, or leaves out old bitstream. However it always works perfectly when you create a new platform. So I would recommend trying to do just that and see if right settings show up as a result.

[Boscoe]

Thanks for the quick reply.

Will I not have to remake my software project if I do that?

[asmi]

Will I not have to remake my software project if I do that?

You can retarget your project to a new platform if you add it to the same Vitis workspace.

[Boscoe]

So I tried this but SG is still included...  Currently investigating.

I have to say I'm shocked at how unstable Vivado and Vitis is. Perhaps Vitis more so due to the many components it has, I have to have task manager constantly open to kill processes preventing me from debugging etc. Typically I'll have 2-3 crashes from Vivado and Vitis per day.

[asmi]

I have to say I'm shocked at how unstable Vivado and Vitis is. Perhaps Vitis more so due to the many components it has, I have to have task manager constantly open to kill processes preventing me from debugging etc. Typically I'll have 2-3 crashes from Vivado and Vitis per day.

You probably are well advised to get to the bottom of those issues before doing anything productive (maybe hardware issues with your PC?). As both Vivado and Vitis have been rock-stable for me and the last time I've experienced a crash of either one of those has been years ago.

[Daixiwen]

I have about 3-4 Vivado crashes per week and just learned to live with it. I use tcl scripts for my workflow and edit them in VS Code so that I don't loose them when Vivado crashes.

[Boscoe]

I haven't looked into it much but is it possible use the command line with tcl scripts for the majority of the work? Block designs sure need doing in the GUI but I feel like the rest would be great for CLI, especially on Linux.

I despise Eclipse, Cmake or even make would be sooo much nicer than Eclipse.

It's the heaviness and clumsiness of the GUIs that get me.

[Boscoe]

What do you know? I managed to manifest what I wanted 

https://docs.xilinx.com/r/en-US/ug1553-vitis-ide/Components-and-System-Projects

[asmi]

I don't know how you manage to crash Vivado so often, I haven't had a single crash in years, both under Windows 10 Pro nor under Ubuntu 20.04 LTS. I do use VS code for code editing and only use Vivado for simulations, and of course synthesis and P&R.