You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ERRATA.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,8 +41,6 @@ Shell errata is [documented here](./hdk/docs/AWS_Shell_ERRATA.md)
41
41
9. Vivado 2025.1 introduces a `set_property DONT_TOUCH` to the HBM model that makes meeting
42
42
timing difficult in the implementation stage. AMD has responded to this issue on their AR, stating that it will be fixed in a future version of Vivado. [See here for more details](https://adaptivesupport.amd.com/s/article/000038502?language=en_US&t=1754923887312). All HDK CL examples have been updated to address this issue. Customers should follow this AR when creating their own designs.
43
43
44
-
10. Due to a XSIM bug in Vivado 2025.2, simulation library compilation with VCS and Questa requires a double compilation workaround, already added to `Makefile.common.inc`, until AMD releases a fix. This results in slightly longer compilation time and generation of a `cxl_error.log` file with an expected error caused by the `sc_ultralite_v1_0_rfs.vhd` file (which can be safely ignored).
45
-
46
44
## HLx
47
45
48
46
1. When executing the `aws::make_ipi`commandin Vivado to set up the HLx IPI environment, the AWS IP instance may default to the name `f1_inst`. This is a known Vivado behavior and can be safely ignored. Users can rename this instance according to their preference.
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,13 @@
1
1
# F2 Developer Kit Release Notes
2
2
3
+
## v2.3.1
4
+
5
+
* Released FPGA Developer AMIs - 1.19.1: Ubuntu and Rocky Linux with AMD patch [AR000039913](https://adaptivesupport.amd.com/s/article/000039913) pre-installed. This fixes the XSIM compilation bug in Vivado 2025.2, and the double compilation workaround has been removed from `Makefile.common.inc`
6
+
* Updated verbiage in [Amazon DCV Setup Guide](./developer_resources/Amazon_DCV_Setup_Guide.md) to improve clarity
7
+
* Updated all NPM packages in [package-lock.json](./developer_resources/runtime_ami_builder/package-lock.json) to address security advisories
8
+
* Added information about EC2 instance placement groups to maximize throughput and minimize latency when networking between instances in the [Virtual Ethernet Application Guide](./sdk/apps/virtual-ethernet/doc/Virtual_Ethernet_Application_Guide.md)
9
+
* Formatted all Python files for style, consistency, and compliance with PEP 8
Given the large size of the FPGA used for F2, AMD tools work best with at least 4 vCPU’s and 32GiB Memory. We recommend [Compute Optimized and Memory Optimized instance types](https://aws.amazon.com/ec2/instance-types/) to successfully run the synthesis of acceleration code. Developers may start coding and run simulations on low-cost `General Purpose`[instances types](https://aws.amazon.com/ec2/instance-types/).
Copy file name to clipboardExpand all lines: developer_resources/Amazon_DCV_Setup_Guide.md
+95-17Lines changed: 95 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ graphical user interface (GUI) to visualize FPGA development in the cloud.
40
40
### Amazon DCV Server Installation
41
41
42
42
In the [install procedure described here](https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-installing-linux-server.html#linux-server-install), follow steps 1 through 5, 7, and 8.
43
-
When you get to step 9, do the following:
43
+
When step 9 is reached, do the following:
44
44
45
45
```bash
46
46
sudo apt --fix-broken install
@@ -52,9 +52,80 @@ When you get to step 9, do the following:
52
52
53
53
[This section of the post-installation check](https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-installing-linux-checks.html#checks-xserver) should be run to ensure that all aspects of the setup are working as expected.
54
54
55
+
> **Note:** After running `sudo dcvgldiag`, errors like the ones below may appear. If the instance type in use does not have an Nvidia or AMD GPU attached to it, messages like "No NVIDIA card found" can be safely disregarded. This will not affect the ability to view or access the graphical desktop via remote session.
56
+
57
+
```text
58
+
Amazon DCV 2025.0 (r20103) - Diagnostic Script
59
+
============================================
60
+
61
+
Date: Tue, 24 Mar 2026 21:43:25 +0000
62
+
63
+
Host: ip-012-34-56-789
64
+
Architecture: x86_64
65
+
Operating System: Ubuntu 24.04.1 LTS
66
+
Kernel Version: 6.8.0-1021-aws
67
+
Nvidia GPU: unknown
68
+
Nvidia Driver: unknown
69
+
Runlevel: 5
70
+
71
+
X configuration file: /etc/X11/xorg.conf
72
+
73
+
DCV GL (GLVND) is enabled for 64 bit applications.
74
+
75
+
Running tests: ............ DONE
76
+
77
+
ERROR (1/4)
78
+
79
+
There are no devices in '/etc/X11/xorg.conf' configured to use the NVIDIA driver.
80
+
81
+
Please, check the X Server configuration.
82
+
83
+
84
+
ERROR (2/4)
85
+
86
+
DCV cannot access the 3D X Server [:0.0].
87
+
88
+
Please, stop the 3D X Server and disable DCV with 'dcvgladmin disable'.
89
+
Then enable DCV with 'dcvgladmin enable' and restart the 3D X Server.
90
+
91
+
92
+
ERROR (3/4)
93
+
94
+
The 3D X Server [:0.0] does not support the GLX extension
95
+
96
+
Please, check your X server configuration and restart it.
97
+
98
+
99
+
ERROR (4/4)
100
+
101
+
The 3D X Server [:0.0] does not run with depth 24
102
+
103
+
Please, check your X server configuration and restart it.
104
+
105
+
106
+
WARNING (1/2)
107
+
108
+
The X server configuration does not contain the "UseDisplayDevice" "none" option. Ignore this warning if a monitor is connected to the video card adapter.
109
+
110
+
In case there is no monitor connected to the video card adapter associated to DISPLAY=:0.0, you may need to add the "UseDisplayDevice" "none" option to the appropriate "Device" section (of the '/etc/X11/xorg.conf' file.
111
+
112
+
113
+
WARNING (2/2)
114
+
115
+
No NVIDIA card found
116
+
117
+
Please, check a NVIDIA card is installed.
118
+
119
+
120
+
121
+
There are 4 errors and 2 warnings.
122
+
123
+
A detailed report about the tests is available in '/home/ubuntu/nice-dcv-2025.0-20103-ubuntu2404-x86_64/nice-dcv-2025.0-20103-ubuntu2404-x86_64/dcvgldiag-19NNNr'
124
+
```
125
+
55
126
### Setting a Password for Your Sessions
56
127
57
-
In order to connect to an Amazon DCV session, you must have a password set for your user on the EC2 instance.
128
+
In order to connect to an Amazon DCV session, a password must be set for the user on the EC2 instance.
58
129
This can be done with this command:
59
130
60
131
```bash
@@ -63,24 +134,19 @@ sudo passwd $USER
63
134
64
135
### Setting Security Rules to Allow Traffic on Port 8443
65
136
66
-
In order for Amazon DCV to communicate with your EC2 instance, TCP and UDP traffic must be allowed on port 8443.
67
-
This can be accomplished by updating the security group you used to launch your instance.
68
-
69
-
## Amazon DCV Client Installation
137
+
In order for Amazon DCV to communicate with the EC2 instance, TCP and UDP traffic must be allowed on port 8443.
138
+
This can be accomplished by updating the security group used to launch the instance.
70
139
71
-
The [Amazon DCV client](https://www.amazondcv.com/) should be installed on your local machine and is used to view your virtual desktop on your EC2 instance.
140
+
## Basic Session Management on EC2 (Server Side)
72
141
73
-
## Basic Session Management
74
-
75
-
To begin, run the following two commands:
142
+
To begin, run the following commands on the EC2 instance:
Next, refer to the [session management user guide here](https://docs.aws.amazon.com/dcv/latest/adminguide/managing-sessions.html). This guide will provide you with all of the information you need to customize and manage your Amazon DCV sessions.
149
+
Next, refer to the [session management user guide here](https://docs.aws.amazon.com/dcv/latest/adminguide/managing-sessions.html). This guide will provide all of the information needed to customize and manage Amazon DCV sessions.
84
150
85
151
### Quick Session Startup
86
152
@@ -92,20 +158,32 @@ dcv list-sessions
92
158
Session: '1' (owner:ubuntu type:virtual)
93
159
```
94
160
95
-
You may give your session any number you like, but no two sessions may have the same number.
161
+
Sessions may be given any number, but no two sessions may have the same number.
From this point, you can access your session using the Amazon DCV client on your local machine or via the [DCV console in your web browser](https://docs.aws.amazon.com/dcv/latest/userguide/using-connecting-browser-connect.html).
165
+
The [Amazon DCV client](https://www.amazondcv.com/) should be installed on the local machine and is used to view the virtual desktop on the EC2 instance.
166
+
167
+
## Connecting to the Session (Client Side)
168
+
169
+
In the DCV Client Viewer application, enter the connection details:
170
+
-**Hostname or IP Address**: Can be the public IP of the EC2 instance or the full URL format `https://user@ec2_instance_ip_address:8443`
171
+
172
+
- Click `Connect`, then click "Trust and Connect"
173
+
174
+
Sessions can be accessed using the Amazon DCV client on the local machine or via the [DCV console in your web browser](https://docs.aws.amazon.com/dcv/latest/userguide/using-connecting-browser-connect.html).
98
175
99
176
Enter `https://user@ec2_instance_ip_address:8443` into the `Hostname or IP Address` box and click `Connect`. Next, click "Trust and Connect".
100
177
101
-
Enter the password you set in [Post-Installation Checks](#post-installation-checks) in the `Password` box and click `Login`.
178
+
Enter the password set in [Post-Installation Checks](#post-installation-checks) in the `Password` box and click `Login`.
102
179
103
-
At this point, you should see your session begin and a virtual desktop displayed after a brief delay.
180
+
At this point, the session should begin and a virtual desktop will be displayed after a brief delay.
104
181
105
-
Now, open a terminal and run the following command: `source /etc/profile.d/default_module.sh`. You're now ready to use your GUI-enabled EC2 Instance.
182
+
Now, open a terminal and run the following command: `source /etc/profile.d/default_module.sh`. The GUI-enabled EC2 Instance is now ready to use.
0 commit comments