Designing boards
Describe a circuit board in plain language and Morbium designs it, checks it for errors, and shows you a live 2D and 3D view you can iterate on.
Morbium's board designer turns a description into a real circuit board. You say what you want, it designs the board, checks it, and fixes its own mistakes, then shows you the result in the PCB viewer.
Design a board
Describe what you want in the composer. Be as specific as you like about the parts, the connectors, and the layout:
Design a board for an ESP32 dev kit with a USB-C port, a reset button,
a user button, and a status LED.
Morbium hands this to the board designer, which writes the board and then validates it. Boards are saved as files in your project under .morbium/pcb, so they are real, versioned artifacts you own.
The design loop
The board designer does not just write a board and hope. It runs a loop:
- Write or change the board.
- Validate it, which renders the board and reports problems: compile errors, unconnected traces, missing footprints, and placement or design-rule errors.
- Fix whatever came back.
- Repeat until the board is clean.
This is why the boards it produces hold together. You can watch it work through the loop.
View the board
When a board is ready, the PCB tab opens in the workspace. You can:
- Switch between a flat 2D layout view and a 3D view of the assembled board.
- Pan and zoom to inspect traces, footprints, and placement.
- Toggle routing to see the copper.
If a design has more than one board, a switcher lets you choose which to view.
Iterate
Ask for changes in plain language and the board updates in place:
Move the USB-C connector to the top edge and add two 3mm mounting holes
in the bottom corners.
The LED should be on GPIO 2 with a 330 ohm resistor.
Each change runs through the same validate-and-fix loop, so the board stays correct as it evolves.
Multiple boards
You can keep several boards in one project, each in its own file with a descriptive name. Ask Morbium to show a specific one to bring it into the viewer.
Tips for good results
- Name the parts you care about. If you want a specific microcontroller, connector, or sensor, say so.
- Describe the interface, not the wiring. "Read a temperature sensor over I2C" is better than trying to specify every net.
- Add constraints up front. Board size, mounting holes, and connector positions are easy to include in the first prompt.
Next steps
- Bill of materials and sourcing: turn the board into a parts list and price it.
- 3D models and enclosures: design a case that fits the board.
- Firmware: write code that matches the board's pinout.