If you have a question about the Experimenting with Sensor Fusion competition, you can ask it here.

It seems that there are some trial licenses and specifically there is a 120-day trial license for the AXI 1G/2.5G Ethernet Subsystem

With this design it is the only IP core that reports license problems.

Hi scottiebabe ,,it's actually a bit daunting at first to work around xilinx tools (they are SO MANY).

You can have a look at this github repository to help you work around that: https://github.com/Xilinx/Vitis-Tutorials There are whole range of tutorials which should get you started.

That would make sense because the Spartan-7 does not have a hard Ethernet core (unlike Zynq series, for example), and the soft Ethernet cores are not supplied for free by Xilinx. If you're not goint to use Ethernet in your project, then it's not an issues. If you are, then the 120 days trial license could cover the project duration fine. But i DO understand the frustration with limited-time trial licenses . Especially since the (paid) IP core licenses are too expensive for individual/hobbyist use.

I think the issue is that the usual Vitis Acceleration flow requires a linux kernel, which in case of Zynq can run on the hard ARM processors. In case of Spartan theoretically one can have Linux running on the microblaze, but then the microblaze is not based on ARM, so I would think a lot of the libraries used to compile the Xilinx XRT would need to be compiled for microblaze, and so on. If Xilinx is not supporting Vitis Vision Library on the Spartan, then that means it's a lot of work to do all of that . 

On the other hand, IPs compiled using HLS should still work, as those do not require XRT, and plus you also have all the video IPs available from Xilinx for free in Vivado, which enable building fairly complex video designs (from personal experience). I have been very tempted to participate in this contest, since I have done fair bit of work with video processing on the Xilinx FPGAs (mostly on Zynq), however I am already busy with a roadtest, and not sure what other commitments the next 2 months will bring.

I am finding it very difficult to participate in this challenge due to platform issues. I have had to modify the blogs several times because the new version of Verint treats them as SPAM for having too many Links. I can no longer edit the blogs with either Edge or Chrome because the editor crashes with the 'latest versions of Edge and Chrome. I have installed Firefox but it also fails with code widgets.
At the moment I have managed to publish two blogs and I have a third inaccessible marked as SPAM before even publishing it, marked as SPAM when including the tags and saving as draft.
I try to take advantage of free time to work on the project but blogging is proving to be quite a frustrating experience.

For the rest, thank you very much to the whole team of element14, the development kit is fascinating and I hope to continue telling my experiences with it.

It happened to me today, under these circumstances:

I showed code snippet from GITHUB, where a normal practice is to sign your code and commits with an email address.

The flag message referred to that email address as reason for review.

I'm sorry to hear about your experience. I know our development team is working on it. Let me ask about it tomorrow and see what the pathway to resolving them is. I open open to extending this challenge by several weeks to make up for lost time. 

I submitted a suggestion in the feedback area:  suggestion: moderation queue - warn when saving as draft 

It could allow a writer to keep on writing. And to either let them remove the flagged content, or let the review team decide, when it's time to publish.

Jan,

Thanks for doing that. 

Randall

Sanitizing personally identifiable information from content is a good habit to get into