If you just want the PCB outline and connector layout, it’s fairly quick and you have enough to design a PCB that can mate with the nucleo board. If you want to turn the whole board into a KiCad project, it’s quite a lot of work. (I still have to cleanup that FAQ article) I assume the only information available is a schematic in some readable, (but not EDA form, such as a. The goal of this reverse-engineering tutorial is to re-create a complete KiCad project from partial information. Some help with proofreading and finding missing or unclear parts is appreciated. Reverse engineering KiCad project from Gerber files FAQ What is such resource called? Where do I find the existing dimensions? Should I use the measurements given in the user manual for the board? Or is there some more fool-proof way of obtaining the correct dimensions? Are those symbols and footprints meant to be used on a carrier board for placing an existing module? And not for actually designing the module itself?įind a resource that describes the size and placements of the board outline and connectors. So far I’ve only used symbols that has corresponded to one component and footprints that has corresponded to one component. But that footprint is for the entire board, with all connectors and mounting holes. I found symbols for Nucleo-144 in the MCU_Module folder and footprints in the Module folder. I found this template for 5.1 but couldn’t use it from 5.99. Try importing those schematics into KiCad 5.99įind an existing template for KiCad 5.99. I’m thinking of having just 100 pin Morpho headers but keep the Zio (Arduino) header.

Andh ere’s the schematic pack for the Nucleo-144. The nucleo-114 user manual MB1137 has a lot of information. Now, how do I go about creating such board? The board exists in three variants Nucleo-32, Nucleo-64 and Nucleo-144.

Now I want to create a STM32 Nucleo board for the 100-pin stm32f105vc MCU of which we have plenty at work from old boards. I’ve followed the Getting Started tutorial, then created my own small dev board just for experimenting.

Software developer and Beginner KiCad user here.

Schdoc kicad