Network requirements
Chipforge needs HTTPS access from each engineer’s computer to the Chipforge service. The companion, which runs your EDA tools, doesn’t connect to anything outside the machine it runs on.
From each engineer’s computer
Section titled “From each engineer’s computer”Allow outbound HTTPS (TCP port 443) to these hosts:
| Host | Contacted by | Used for |
|---|---|---|
api.chipforge.studio |
The desktop app, and your web browser when you download Chipforge | Signing in, the assistant, checking for updates, and downloading Chipforge |
chipforge-production.auth.ap-southeast-1.amazoncognito.com |
Your web browser | The Chipforge sign-in page |
*.s3.amazonaws.com |
The desktop app, and your web browser when you download Chipforge | Downloading Chipforge and its updates. api.chipforge.studio redirects each download to a link here that expires after a short time. |
The assistant sends its replies over a long-lived HTTPS response from api.chipforge.studio. A proxy that buffers responses, or closes them when they seem idle, can delay replies or cut them off.
On Windows, if the Microsoft Edge WebView2 Runtime isn’t installed, the Chipforge installer downloads it from Microsoft.
Between engineers’ computers and a remote EDA server
Section titled “Between engineers’ computers and a remote EDA server”If you run your designs on a remote EDA server, each engineer’s computer needs SSH access to the server: TCP port 22, or the port your server uses. Everything Chipforge sends to the server goes through SSH.
The companion on the server listens on a Unix socket that only its own user account can open, not on a network port. If AMD’s programming tools are installed there, it also starts AMD’s hw_server; see below.
On each machine
Section titled “On each machine”- The desktop app and the companion it starts talk to each other over this computer’s loopback interface (
127.0.0.1), on ports chosen each time the app starts. Security software must allow these local connections. - When AMD’s programming tools are installed, the companion starts AMD’s
hw_serverto reach Xilinx boards. It listens on TCP port 3121 on all of the machine’s network interfaces, not only the loopback interface.
What the companion connects to
Section titled “What the companion connects to”Nothing outside its own machine. It sends no usage data or crash reports. Your EDA tools still contact your licence servers as they normally do.