diff --git a/Images/Image07.png b/Images/Image07.png new file mode 100644 index 0000000..808fa4f Binary files /dev/null and b/Images/Image07.png differ diff --git a/Images/Image08.png b/Images/Image08.png new file mode 100644 index 0000000..053d2c7 Binary files /dev/null and b/Images/Image08.png differ diff --git a/Images/Image09.png b/Images/Image09.png new file mode 100644 index 0000000..0745b05 Binary files /dev/null and b/Images/Image09.png differ diff --git a/Images/Image10.png b/Images/Image10.png new file mode 100644 index 0000000..2cc1e49 Binary files /dev/null and b/Images/Image10.png differ diff --git a/Images/Image11.png b/Images/Image11.png new file mode 100644 index 0000000..6df182a Binary files /dev/null and b/Images/Image11.png differ diff --git a/Images/Image12.png b/Images/Image12.png new file mode 100644 index 0000000..15a26a6 Binary files /dev/null and b/Images/Image12.png differ diff --git a/Images/Image13.png b/Images/Image13.png new file mode 100644 index 0000000..9bd640d Binary files /dev/null and b/Images/Image13.png differ diff --git a/Images/Image14.png b/Images/Image14.png new file mode 100644 index 0000000..7dcafb2 Binary files /dev/null and b/Images/Image14.png differ diff --git a/Images/Image15.png b/Images/Image15.png new file mode 100644 index 0000000..9527352 Binary files /dev/null and b/Images/Image15.png differ diff --git a/Images/Image16.png b/Images/Image16.png new file mode 100644 index 0000000..5d65b83 Binary files /dev/null and b/Images/Image16.png differ diff --git a/Images/Image17.png b/Images/Image17.png new file mode 100644 index 0000000..fa105ec Binary files /dev/null and b/Images/Image17.png differ diff --git a/Images/Image18.png b/Images/Image18.png new file mode 100644 index 0000000..8843a51 Binary files /dev/null and b/Images/Image18.png differ diff --git a/Images/Image19.png b/Images/Image19.png new file mode 100644 index 0000000..dcb4144 Binary files /dev/null and b/Images/Image19.png differ diff --git a/Images/Image20.png b/Images/Image20.png new file mode 100644 index 0000000..4717daa Binary files /dev/null and b/Images/Image20.png differ diff --git a/Install instructions.md b/Install instructions.md index 5857818..4e2bd7a 100644 --- a/Install instructions.md +++ b/Install instructions.md @@ -1 +1,87 @@ -# Install instructions \ No newline at end of file +# Install instructions + +## 1. Copy the files locally + +Copy the `RP-Pico Libraries` folder wherever you like on your computer. + +## 2. Install the Raspberry Pi Pico board schema symbol + +Use the `KiCad | Preferences | Manage Symbol Libraries...` command to manage the symbol library: + +![symbol library manager](Images/Image07.png) + +then select the global tab and click on the folder button: + +![symbol library manager](Images/Image08.png) + +navigate to the `RP-Pico Libraries` folder, select the `MCU_RaspberryPi_and_Boards.lib` file and open it: + +![symbol library manager](Images/Image09.png) + +et voilà, the first step is completed: + +![symbol library manager](Images/Image10.png) + +You can now close the symbol libraries manager window. + +## 3. Install the Raspberry Pi Pico board footprint + +You can use a similar approach to add the footprint to the footprint libraries manager, but I've found some issues that I've solved using the footprint editor, so here are the steps I suggest you to follow: + +Open the footprint editor + +![symbol library manager](Images/Image11.png) + +wait for the footprints to load... then use the `File | Add Library` command: + +![symbol library manager](Images/Image12.png) + +select the `MCU_RaspberriPi_and_Boards.pretty` folder (yes, the folder represent a footprint library on KiCad): + +![symbol library manager](Images/Image13.png) + +and confirm the `Global` choice: + +![symbol library manager](Images/Image14.png) + +Now the library is installed on KiCad with the Raspberry Pi Pico footprint (double click on it to see it on the editor pane): + +![symbol library manager](Images/Image15.png) + +Don't close the windows as the next step start from here. + +## 4. Install the Raspberry Pi Pico board footprint 3D visual + +If not already open, open the the footprint editor + +![symbol library manager](Images/Image11.png) + +double click on the `RPi_Pico_SMD_TH` footprint from the `MCU_RaspberriPi_and_Boards` library and then click on the `Footprint properties` icon: + +![symbol library manager](Images/Image16.png) + +In the footprint properties window, first select the `3D Settings` tab. Please note that the preview shows only the PCB board with the footprint added on step 3, without any 3D representation of the Raspberry Pi Pico board. Now click on the folder icon to add the 3D model: + +![symbol library manager](Images/Image17.png) + +Navigate to the `RP-Pico Libraries` folder, select the `Pico.wrl` file and wait until the model is shown in the right panel, then confirm with OK: + +![symbol library manager](Images/Image18.png) + +Due to different origin setup and unit of measure, I found that the imported model doesn't fit with the footprint: + +![symbol library manager](Images/Image19.png) + +but we can easily fix it changing the scale and the offset: + +![symbol library manager](Images/Image20.png) + +now close the `Footprint Properties` window, and the `Footprint Editor`, obviously saving the changes. + +## Conclusion + +Now that you've installed the schema and footprint and added the 3D model to the footprint, you can use the Raspberry Pi Pico board on your KiCad projects. + +I've also added a test KiCad Project on the `Test` folder, that you can use to see an example of it. + +Have fun! \ No newline at end of file