Update

[Hotwright]

There has been no update for 2 years. The latest AMD/Xilinx is 2023.2 I think you support 2021.2.

Are there any plans to update this?

[AWSjoeluc]

Hello!

Yes, we're actively working on a customer release to enable Vivado 2023.2.

Does Vivado 2023.2 (or any version since 2021.2) add any new features that you're hoping to use on F1?

Thanks,
-Joe

[Hotwright]

Yes. 2023.2 Vitis has a whole new GUI and I find that each release fixes bugs and makes useability fixes. As a user I keep my AMD/Xilinx tools up to date and those releases are so big I can only have the latest release on my server. I’m willing to be a tester if that helps me get access to the latest release. I’m trying to port my latest work at Hotwright.com which is in 2023.1 Cheers Steve PS Something about me. https://bit.ly/WhoIsSteveCasselman From: Joe Luciano ***@***.***> Sent: Monday, November 20, 2023 9:28 AM To: aws/aws-fpga ***@***.***> Cc: Hotwright ***@***.***>; Author ***@***.***> Subject: Re: [aws/aws-fpga] Update (Issue #630) Hello! Yes, we're actively working on a customer release to enable Vivado 2023.2. Does Vivado 2023.2 (or any version since 2021.2) add any new features that you're hoping to use on F1? Thanks, -Joe — Reply to this email directly, view it on GitHub <#630 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4TFRPFBRXQ5UCPGGOG2CZDYFOHLTAVCNFSM6AAAAAA7RD2LYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJZGUYDQNJSGQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A4TFRPFKLPY4LVLBAUUGMLLYFOHLTA5CNFSM6AAAAAA7RD2LYCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTMON7SY.gif> Message ID: ***@***.*** ***@***.***> >

[ioeddk]

I'm also expecting support for the Vitis 2023 release. Specifically, there are bugs fixed for the Task library if we want to implement Task-Channel kernels. I believe the potential benefits are there to updating this repository to keep up with the newer version of Xilinx's development tools.

[Hotwright]

Are task channels a way to have to concurrent process talk to each other? Altera had this kind of extension in their OpenCL compiler. FYI I’m giving a talk on Tuesday the 5th at 6 pm PST. The state machine is runtime loadable so you can change the behavior of your hardware at runtime. I have a demo with 2 threads running on the SoC and a tokenizer that is loadable at runtime. The two threads feed data and retrieve tokens respectively. https://www.svec.org/event/the-hotstate-machinea-runtime-loadable-microcoded-algorithmic-statemachine/ Cheers Steve From: Yingqi Cao ***@***.***> Sent: Friday, December 1, 2023 1:51 AM To: aws/aws-fpga ***@***.***> Cc: Hotwright ***@***.***>; Author ***@***.***> Subject: Re: [aws/aws-fpga] Update (Issue #630) I'm also expecting support for the Vitis 2023 release. Specifically, there are bugs fixed for the Task library if we want to implement Task-Channel kernels. I believe the potential benefits are there to updating this repository to keep up with the newer version of Xilinx's development tools. — Reply to this email directly, <#630 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/A4TFRPE26YDP2UKT5MKGPSLYHGR7BAVCNFSM6AAAAAA7RD2LYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVG44TAOJWGU> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A4TFRPDY4DSKEZL5DI4VRZLYHGR7BA5CNFSM6AAAAAA7RD2LYCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTNNPZHK.gif> Message ID: < ***@***.***> ***@***.***>

[augierg]

@AWSjoeluc : I am also looking forward to support for 2023.2. We are having issues getting our RTL to complete with a simple synth_design -lint in 2021.2 because of crash with Abnormal program termination (11). We face no such issue with 2023.2, and now we are at the stage we want to integrate our CL with the F1 FPGA shell. Having a support for 2023.2 would greatly help us save time in debugging the reason of a crash on a 2 year old version

[jjones-github]

It would be great to get 2023.2 supported!

[ioeddk]

Really need a newer version of Vitis AMI since there are a lot of bugs in the 2021.2 version. For example, using "pragma dependence off" to specify the false dependency, the synthesis tool would run into infinite loop printing "identified false dependence". This is a crucial feature of our project. Also, some times the use of the vector library would get "conflict pragma of array partition and aggregate", which is a behavior not documented anywhere.

[AWSjoeluc]

Hi everyone, thanks for the data points and known issues with 2021.2. Learning about these issues really helps improve the devkit going forward.

We've been prioritizing the 2023.2 AMI release and will update you all as soon as it's ready!

[augierg]

Hi everyone, thanks for the data points and known issues with 2021.2. Learning about these issues really helps improve the devkit going forward.

We've been prioritizing the 2023.2 AMI release and will update you all as soon as it's ready!

@AWSjoeluc : is there an expected availability estimate for the 2023.2 AMI release ? We are still facing issues with Vivado 2021.2 not fully supporting some of systemverilog constructs, and crashing randomly when running synthesis on our RTL, and all these issues appear to be resolved in 2023.2

[ioeddk]

As @augierg mentioned, is there an estimated expected availability for the new AMI release? The current AMI is CentOS7 based and it just went EOL at the end of June.

[AWSjoeluc]

Hello, we're currently working on a new FPGA Developer AMI release. In the mean time Centos 7 has EOL, yum repos have been moved to vault.centos.org
If you need access to repo, you can do the following

sudo sed -i "s/^mirrorlist=/#mirrorlist=/g" /etc/yum.repos.d/CentOS*.repo
sudo sed -i "s/^#baseurl=http:\/\/mirror.centos.org\/centos\/\$releasever/baseurl=https:\/\/vault.centos.org\/7.9.2009/g" /etc/yum.repos.d/CentOS*.repo

We appreciate everyone's patience with the long awaited release!

[augierg]

We appreciate everyone's patience with the long awaited release!

@AWSjoeluc : thanks for the update. Would you be able to give some timeframe for this long awaited release (3mo, 6mo, 1y, more ?)