cli · newcreate a starting project

dewfpga new

What does its help text say?

dewfpga new <dir>               blink example: blink.sv + blink_tb.sv + blink.xdc + VS Code task (⌘⇧B = flash)

From dewfpga --help, as bin/dewfpga prints it.

What does the README say?

Use a flat folder of .sv/.v modules (an .xdc only for ports without a board name), or run inside a Vivado project: its .xpr selects the enabled design, constraint and simulation files. Commands from a nested .srcs folder use the project root; outputs go there too. dewfpga tops lists top candidates without writing files. The project's selected top wins unless you name one: dewfpga bit <top>. In a flat folder, hierarchy and a unique matching .xdc select the top; ambiguous candidates require a choice. A filename alone does not select it. A testbench has no ports and instantiates the design; $finish/$stop in a design module is an error. A file that holds only a package, an interface or typedefs is read too, each after the files that declare a name it uses: a package before its users, a typedef file before the interface that uses the type (one that another file includes is read through the include, not twice). Example: dewfpga new blink.

dewfpga new <dir>                   blink example with a VS Code task (⌘⇧B = flash)

From the README.

What does the guide say?

all good.

Total: 217 s. Log: /Users/you/fpga/install.log
Next:  dewfpga new blink && cd blink && dewfpga flash

dewfpga new blink    # prints: blink/ ready:  cd blink && dewfpga flash    (VS Code: ⌘⇧B)
cd blink
dewfpga sim          # simulation
dewfpga bit          # .sv -> .bit
dewfpga flash        # .bit -> the board; runs bit first when the .bit is missing or older than the .sv

dewfpga new <dir>                   blink example with a VS Code task (Cmd Shift B = flash)

From section 2, How do you install it in one line?.

dewfpga new blink gives the same blink.sv, blink_tb.sv and blink.xdc without the Makefile, and its tasks.json says dewfpga flash instead.

From section 4, What is in the project folder?.

Open the Command Palette and use dewfpga: choose the top module. The chooser reads dewfpga tops, remembers the selection per project, and offers it again on the next build. The tasks use absolute file locations so compiler diagnostics can appear in Problems when the project lives under Vivado's .srcs tree. dewfpga new also includes project tasks; the Makefile-only download retains its make tasks.

From section 6, How do you set up VS Code?.

How does a coding agent call it?

From the agent interface: the machine-readable CLI and the MCP server.

Which errors can it stop with?

1 codes in the error catalog.

• folder-exists: The folder dewfpga new was told to create is already there; it never overwrites a design.

Which patch notes name it?

• #6 The CLI's untested paths get checks, one number for the count, a test that reads the bitstream, the board test ready for the board
• #16 Project instructions and a measured repair experiment

previous: dewfpga tops
next: dewfpga uninstall
Every command: dewfpga install · dewfpga check · dewfpga run · dewfpga sim · dewfpga bit · dewfpga flash · dewfpga clean · dewfpga tops · dewfpga new · dewfpga uninstall · dewfpga vscode · dewfpga … --json · dewfpga mcp