<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Raspberry Pi</title><link>https://community.element14.com/products/raspberry-pi/</link><description>Join the Raspberry Pi Community, learn about the Pi 5 and the family of the single board computer</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=93678777-e7ef-4768-b6d9-0ab2f86d5ad5</link><pubDate>Sat, 04 Jul 2026 15:58:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:93678777-e7ef-4768-b6d9-0ab2f86d5ad5</guid><dc:creator>geralds</dc:creator><description>Hi shabaz Wow! Thank you so much! I&amp;#39;ve read your GitHub repository. Great! KiCad keeps crashing: In my opinion, the problem might be partly due to Windows 11, specifically the combination of hard drive type (nowadays it&amp;#39;s flash storage). This operating system has a lot of background processes running, so programs often freeze briefly. I&amp;#39;m also using Windows 11 Pro. KiCad seems &amp;quot;kind of cobbled together,&amp;quot; that&amp;#39;s my impression. I&amp;#39;m monitoring this now because it can&amp;#39;t be that I have a modern, up-to-date system that&amp;#39;s malfunctioning somewhere. I frequently check the Event Viewer in the system settings.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=9de6446f-863e-49a9-9c58-8b9c739a96a1</link><pubDate>Sat, 04 Jul 2026 13:10:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9de6446f-863e-49a9-9c58-8b9c739a96a1</guid><dc:creator>shabaz</dc:creator><description>Hi Gerald, This is great! I have added it to the GitHub repo . Thank you for this! Regarding KiCad crashing with DRC checks, sadly this is quite common, I don&amp;#39;t know the reason, but every version of KiCad I have ever used (6 through 10, I use the Windows version, not tried Linux) has done that. I am just used to saving before running DRC (even without saving, usually KiCad is good with recovery and also has automated backups, so I&amp;#39;ve never actually lost any work (maybe a few minutes of work very rarely). But it&amp;#39;s really bizarre how every KiCad version tends to crash with DRC.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=95cbba3e-f8ac-443d-adc2-0f2f8111ac35</link><pubDate>Fri, 03 Jul 2026 20:07:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:95cbba3e-f8ac-443d-adc2-0f2f8111ac35</guid><dc:creator>geralds</dc:creator><description>Hi shabaz Awesome! I&amp;#39;ve just finished my version. So, starting with your Rev2, I made my Rev3 with the new USB connector and changes to the PCB, including component relocations and trace optimizations. I also adjusted the USB traces, hopefully optimizing them, and surrounded them with a ground shield. I also repositioned the voltage regulator, rotating it to accommodate the USB connector. I placed the passive components on the 603 footprints, and the capacitors according to their capacitances. I optimized the clock&amp;#39;s placement. The project folder with all files. Hopefully that is right for your project. community.element14.com/.../RP2040_5F00_minimal_2D00_edit_5F00_V3.zip Schematic: community.element14.com/.../0081.RP2040_2D00_minimal_2D00_Rev3_5F00_sch.pdf Sorry.... I&amp;#39;m not a KiCad user, normally I work with Fusion360, so, since last few weeks I learned a lot about KiCad. And, yes, this KiCad project was very easy importing into Fusion, there were some wrongs, but they are not fatal. And phew...: I had to adjust the components because there was a mistake in their design. The USB receptacle had a line on the &amp;quot;Edge Cuts&amp;quot; layer of the footprint, right under the component outline. The DRC check kept throwing errors until I discovered this fine, short, hidden line. The KiCad&amp;#39;s library also contains the footprint for the RP2040, which had also been created incorrectly. It has fatal errors (DRC). There was a polygon on the BOT layer. Finding this error in the DRC check was a nightmare, ugh... Therefore, I also modified this footprint and added several pin holes to it, Pin 57. And, last but not least, the KiCad PCB app kept crashing mostly during the DRC check and after saving in between; also, the schematics editor crashed sometimes if I wanted to edit some properties of the symbols. Furthermore, I wanted the entire project in one project folder on the D drive, where there are many different projects in electronics, mechanics, and physics. That was an ordeal! I wasted several hours trying to consolidate the project databases into one project folder. KiCad has databases in the C:..user folder, in the C:..program folder (where the complete KiCad database is), and when you create new components, they are saved everywhere, including in the project folder. And you have to pay close attention to where each part is stored in order to copy it over. Wow, I managed to combine all the components. Well then, this board is now finished. No errors in the DRC check! If you&amp;#39;d like, and if it works for you, you can incorporate my impressions into your version and save it to Git. That&amp;#39;s where I found your files, too. Best regards, Gerald ---</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=43cd5087-0396-4890-abb8-0df804b7dfec</link><pubDate>Fri, 03 Jul 2026 00:30:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:43cd5087-0396-4890-abb8-0df804b7dfec</guid><dc:creator>shabaz</dc:creator><description>That was super fast. It&amp;#39;s done!</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=9d8211db-b1b3-48ed-a708-46a54131e1fb</link><pubDate>Wed, 01 Jul 2026 10:59:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9d8211db-b1b3-48ed-a708-46a54131e1fb</guid><dc:creator>shabaz</dc:creator><description>It is too late for me to do anything (I&amp;#39;ve already placed the order), but I just noticed that the few through-hole parts (which were going to be manual-assembled) are not actually manually-soldered, they will be wave soldered. Unfortunately, that raises two issues: (1) I didn&amp;#39;t make any considerations for that, and I&amp;#39;m not aware of the direction of the wave, so I couldn&amp;#39;t orient parts in any particular way (or orient through-hole pad shapes) and (2) I have unpopulated header pin holes, they may end up plugged with solder : ( I don&amp;#39;t know if they will cover those areas up beforehand. Both of these issues are repairable if they occur of course. Maybe the best solution for small volume is to avoid through-hole assembly, and do that after the boards arrive if needed.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=fd0f39c7-a1c1-4349-920a-121a55e5921a</link><pubDate>Wed, 01 Jul 2026 06:19:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:fd0f39c7-a1c1-4349-920a-121a55e5921a</guid><dc:creator>embeddedguy</dc:creator><description>Oh, I realized that there some FEM for the same device mentioned in the datasheet. That supports 20dbm</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=848aa375-5a20-4222-ad51-7145f3debae3</link><pubDate>Wed, 01 Jul 2026 01:46:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:848aa375-5a20-4222-ad51-7145f3debae3</guid><dc:creator>shabaz</dc:creator><description>I gave it a try! This is the minimal board with the additions I wanted. I uploaded the PCB files, and then at the bottom of the website clicked on PCB Assembly. The website prompted me for the BoM and Component Positions files (which were auto-generated by KiCad by clicking on the icon that got installed with the Fabrication Toolkit plugin). Then, I had to visually go over this rendering that the site created, to check all component positions and orientations were correct. This was the costing for a quantity of 10 (which is excessive, really I should only try a few boards first, but worst case I&amp;#39;ll manually do some rework on these boards if needed). With tax and DHL shipping all included, it worked out to $214 total, which is &amp;#163;169, i.e. &amp;#163;16.90 per board.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=82eb20e9-b894-4c34-8e1f-7d4a7bc3b6c1</link><pubDate>Tue, 30 Jun 2026 23:20:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:82eb20e9-b894-4c34-8e1f-7d4a7bc3b6c1</guid><dc:creator>shabaz</dc:creator><description>That wasn&amp;#39;t too difficult.. I decided to extend the 10-pin GPIO header to become 14-pin, and insert in those four connections (shown in yellow):</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=e9c9fa23-21f6-45fe-a18a-3f1badb0b370</link><pubDate>Tue, 30 Jun 2026 21:51:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:e9c9fa23-21f6-45fe-a18a-3f1badb0b370</guid><dc:creator>shabaz</dc:creator><description>Using the schematic mentioned by veluv01 just four GPIO connections are needed to the RP2040, and I was curious roughly were the module could fit on a minimal RP2040 design (e.g. (+) Making a Custom RP2040 Project with KiCad, Part 1! - element14 Community ). The illustration here shows the four required connections in yellow, and approximately where the module could be placed so traces could be routed easily (I&amp;#39;m not planning to do this with the particular circuit I&amp;#39;m working on, but will consider it for future, or maybe place a SIL header there, for wiring up later. Aside from those four connections, GND and 3.3V is needed of course (The Pimoroni Pico 2 W uses a ferrite bead on the supply), and the module has three GPIO, one of which is used for an LED, and another is wired to a potential divider attached to the USB 5V supply, but seems unnecessary (I don&amp;#39;t think the firmware does anything with that, it is just for developer use if they want to see if the USB supply is present, so I think that could be omitted if it simplifies PCB routing).</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=8c63a1ed-1be1-40ce-ad20-a37f859d6631</link><pubDate>Tue, 30 Jun 2026 19:49:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:8c63a1ed-1be1-40ce-ad20-a37f859d6631</guid><dc:creator>embeddedguy</dc:creator><description>haha, nice tiny little device, but the TX power is bit low it is 12dbm max. I have seen some modules with +20dbm and that will increase the comm. range for sure. Another thing that I would look is how to make P2P link secure and hackproof. That way I am good to go.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=428a0673-4d0d-4c0f-9814-dbb4c3216847</link><pubDate>Tue, 30 Jun 2026 17:46:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:428a0673-4d0d-4c0f-9814-dbb4c3216847</guid><dc:creator>wolfgangfriedrich</dc:creator><description>When I saw this, my first thought was: put it on some sort of m.2 carrier for a more universal wireless card. But the interface does not seem to be fully compatible with whatever m.2 has to offer.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=3c71e7ec-c789-4eba-b49b-97804f6bd912</link><pubDate>Tue, 30 Jun 2026 17:35:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:3c71e7ec-c789-4eba-b49b-97804f6bd912</guid><dc:creator>shabaz</dc:creator><description>Or connect both! For example LoRaWAN with Pi Pico: community.element14.com/.../test-lorawan-thing-code-ported-for-raspberry-pico&amp;#160; . Since Winter I&amp;#39;ve been running the home heating (not right now since it&amp;#39;s extremely hot!) using a low-cost TI CC1101 module connected to a Pi Pico W. (I used that TI part because it is quite flexible radio-protocol-wise, and chances are high to interwork that to existing systems if they are not using LoRa). The WiFi was used to obtain a weather report, and then the CC1101 issued on/off instructions to the boiler.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=09ac890d-6dcd-4651-ac22-2f0091321ab1</link><pubDate>Tue, 30 Jun 2026 17:26:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:09ac890d-6dcd-4651-ac22-2f0091321ab1</guid><dc:creator>shabaz</dc:creator><description>Ah, great, that will be very helpful to confirm the connections! Funnily enough I ordered a Pimoroni Pico Plus 2 but missed that there was a W variant of that.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=958e7727-a5c9-4f0d-bc34-822be59be898</link><pubDate>Tue, 30 Jun 2026 17:16:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:958e7727-a5c9-4f0d-bc34-822be59be898</guid><dc:creator>veluv01</dc:creator><description>The pimoroni pico plus 2W has it.The schematic is available for it. Apparently, it can only be used with the rp2040 and rp2350&amp;#39;s.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it?CommentId=a30a19de-826b-449a-be83-f22a98c92747</link><pubDate>Tue, 30 Jun 2026 17:12:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:a30a19de-826b-449a-be83-f22a98c92747</guid><dc:creator>embeddedguy</dc:creator><description>Would be nice to add some sub-ghz module. You can have better range with that.!</description></item><item><title>Blog Post: Adding Wireless Capability to Custom RP2040/RP2350 Projects: Pi Radio Module 2 - Anyone tried it?</title><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/adding-wireless-capability-to-custom-rp2040-rp2350-projects-pi-radio-module-2---anyone-tried-it</link><pubDate>Tue, 30 Jun 2026 16:29:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:d93937ff-6138-456b-99e8-0609a81acecd</guid><dc:creator>shabaz</dc:creator><description>I just noticed the other day that this thing existed; it supports 2.4 GHz wireless (not 5 GHz), and Bluetooth LE (BLE); the manufacturer part code is RMC20452T , also known as RM2 and it costs about $4. Underside; the board is 16.5 x 14.5 mm in size (but you&amp;#39;ll need some space for a ground plane): The RM2 is useful for custom RP2040 or RP2350 projects where WLAN (again, annoyingly just 2.4 GHz)/BLE is needed; not useful for anything else as far as I&amp;#39;m aware. From a software perspective, coding should be no different to using a Pi Pico W. The RM2 should be very easy to drop into KiCad projects, since the footprint/symbol/3D model is available . The RM2 datasheet (PDF) seems easy enough to follow, but is extremely basic; and I found it a bit confusing regarding a &amp;#39;reset&amp;#39; line it mentions, but the text is silent on that later. It is not clear what line that refers to. There are no suggested layouts, the PDF just states a good ground plane is needed, and shows the copper fill keepout area. Note that there isn&amp;#39;t a version with antenna connector, however, one workaround would be to place the module on a PCB (large enough to have a ground plane, or perhaps use parts of an enclosure for that) and run the interface wires a short distance to the microcontroller, if you needed the antenna positioned somewhere not feasible on the main circuit board. Personally, if it were me, I would try to use the module in that way, i.e. on a separate PCB with short wires, before integrating onto a larger PCB; I&amp;#39;d much rather have it separately and position it for the best signal. Anyone see a use for this module? Or if anyone has seen it in use, any photos showing how it was deployed in the design would be great to see. At some point I&amp;#39;d like to experiment with creating a PCB for it, but I was wondering if anyone else had given it a shot, or were planning to, or would like to! Thanks for reading.</description><category domain="https://community.element14.com/products/raspberry-pi/tags/RP2350">RP2350</category><category domain="https://community.element14.com/products/raspberry-pi/tags/Pi%2bPico%2bW">Pi Pico W</category><category domain="https://community.element14.com/products/raspberry-pi/tags/RM2">RM2</category><category domain="https://community.element14.com/products/raspberry-pi/tags/wlan">wlan</category><category domain="https://community.element14.com/products/raspberry-pi/tags/2-4ghz">2.4ghz</category><category domain="https://community.element14.com/products/raspberry-pi/tags/wireless%2blan">wireless lan</category><category domain="https://community.element14.com/products/raspberry-pi/tags/rpiexpert">rpiexpert</category><category domain="https://community.element14.com/products/raspberry-pi/tags/rp2040">rp2040</category><category domain="https://community.element14.com/products/raspberry-pi/tags/2-4%2bghz">2.4 ghz</category><category domain="https://community.element14.com/products/raspberry-pi/tags/wireless">wireless</category><category domain="https://community.element14.com/products/raspberry-pi/tags/Pi%2bRadio%2bModule%2b2">Pi Radio Module 2</category><category domain="https://community.element14.com/products/raspberry-pi/tags/RMC20452T">RMC20452T</category><category domain="https://community.element14.com/products/raspberry-pi/tags/pi%2bpico">pi pico</category></item><item><title>Forum Post: RE: Pi 5 Custom Active Fan setup</title><link>https://community.element14.com/products/raspberry-pi/f/forum/57076/pi-5-custom-active-fan-setup/236276</link><pubDate>Tue, 30 Jun 2026 05:23:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:03ddae25-5454-468e-a914-47e7c803a9a7</guid><dc:creator>ralphjy</dc:creator><description>You might try looking at this link how-to-customize-raspberry-pi-5-fan-speeds . Here is the relevant info from that discussion: &amp;quot;You are correct that the device-tree is where this is configured, but the dtb file is the compiled device-tree which isn’t (directly) editable. However, in this case we don’t even need to edit the device-tree itself because the values you want to tweak are parameterized and can be customized simply by adding some lines to /boot/firmware/config.txt. Firstly, the reference file you want to have a look at is /boot/firmware/overlays/README. This text file documents all the available device-tree overlays, and their parameters. It also documents the parameters for the base device tree, which is what we’re interested in here. Search for fan_temp0 in that README file and you should find yourself at the start of the various fan-related parameters in the base device-tree. I’ll quote them here, but you should double-check in that file in case they’ve changed across kernel versions:&amp;quot; *********** fan_temp0 Temperature threshold (in millicelcius) for 1st cooling level (default 50000). Pi5 only. fan_temp0_hyst Temperature hysteresis (in millicelcius) for 1st cooling level (default 5000). Pi5 only. fan_temp0_speed Fan PWM setting for 1st cooling level (0-255, default 75). Pi5 only. fan_temp1 Temperature threshold (in millicelcius) for 2nd cooling level (default 60000). Pi5 only. fan_temp1_hyst Temperature hysteresis (in millicelcius) for 2nd cooling level (default 5000). Pi5 only. fan_temp1_speed Fan PWM setting for 2nd cooling level (0-255, default 125). Pi5 only. fan_temp2 Temperature threshold (in millicelcius) for 3rd cooling level (default 67500). Pi5 only. fan_temp2_hyst Temperature hysteresis (in millicelcius) for 3rd cooling level (default 5000). Pi5 only. fan_temp2_speed Fan PWM setting for 3rd cooling level (0-255, default 175). Pi5 only. fan_temp3 Temperature threshold (in millicelcius) for 4th cooling level (default 75000). Pi5 only. fan_temp3_hyst Temperature hysteresis (in millicelcius) for 4th cooling level (default 5000). Pi5 only. fan_temp3_speed Fan PWM setting for 4th cooling level (0-255, default 250). Pi5 only. The syntax for customizing these is a little strange, but not too difficult. In /boot/firmware/config.txt you need to add lines with the format dtparam=PARAM=VALUE. For example, if you want to change the base temperature at which the fan turns on from 50&amp;#176;C to 55&amp;#176;C you might append the following (bearing in mind the value is in millicelcius): dtparam=fan_temp0=55000 You can list multiple parameters in a single dtparam= line like so: dtparam=fan_temp0=55000,fan_temp0_speed=90 Alternatively, you can use multiple dtparam= lines, if you prefer: dtparam=fan_temp0=55000 dtparam=fan_temp0_speed=90 ***********</description></item><item><title>Forum Post: Pi 5 Custom Active Fan setup</title><link>https://community.element14.com/products/raspberry-pi/f/forum/57076/pi-5-custom-active-fan-setup</link><pubDate>Mon, 29 Jun 2026 20:33:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:d405b423-84da-4b56-98f4-84239878c00f</guid><dc:creator>brex2048</dc:creator><description>I am trying to setup a custom fan setting so that it will come on sooner, just to help keep it cooler. I have found the config.txt, how do I actually set a custom fan profile. The file is blank right now.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/getting-custom-rp2040-boards-produced-and-assembled-with-kicad-part-2?CommentId=a6f2abdd-0282-44cd-bc59-70d8fe5c8249</link><pubDate>Mon, 29 Jun 2026 17:21:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:a6f2abdd-0282-44cd-bc59-70d8fe5c8249</guid><dc:creator>shabaz</dc:creator><description>I&amp;#39;ve updated the PCB at the RP2040 custom minimal board repository , so that is uses a surface-mount connector suggested by geralds and it&amp;#39;s simplified the USB data lines routing too. I tried uploading the design to a usual PCB manufacturer, and it looks good. Here&amp;#39;s the costing for ten boards (add your shipping costs and tax on top of that). Of course, this is just for informational purposes, I&amp;#39;m not going to order this specific board as-is, since it&amp;#39;s a minimal design with no GPIO connected (apart from an LED!). It is up to the user to append their own circuitry, e.g. header pins if nothing else). A couple of points regarding the online assembly service experience so far: (1) It can happen that the PCB assembly manufacturer is unable to render some of the components in the 3D view. They were displayed with a checkerbox pattern. I believe that means the manufacturer will ckeck the layout manually, so instead I decided to change the component to one that was recognized. This was an annoying iterative process admittedly. (2) Some components can appear with an offset or incorrect rotation. Rotations can be solved immediately by clicking an icon in the 3D view on the website (this is the simplest way but like me, some might prefer to go back and modify in their files), but if there is an offset, that&amp;#39;s more long-winded. I had to move the component in the footprint editor (i.e. select all, then right-click and from the pop-up menu in KiCad go to Position-&amp;gt;Move Exactly), which is really annoying since of course that means that the PCB needs to be modified because the component will move. For example, the USB connector was off the PCB by precisely 5 mm (I don&amp;#39;t know why!). My original (0,0) position, i.e. origin of the component, was at the location shown with the red arrow. That position made sense to me, because it was the most important reference mechanically, it is where the connector ends. However, I had to move the component such that the origin was at the green arrow location, 5 mm inward. In practise, while this is feasible with the very simple board that I had, with a more complex board you definitely won&amp;#39;t want to be doing this. You could edit the positions in the CSV file generated by the Fabrication Toolkit in KiCad, but then you&amp;#39;d need to remember to re-edit that, if you ever re-ran that toolkit. Probably best to make a checklist and add notes for such things for the specific board, so you don&amp;#39;t forget. One other observation, is that all this might seem like a lot of work to set up, and it really is. But then when I thought about it, manufacturing an entire board should rightly be expected to be a lot of work. Normally that&amp;#39;s a whole team-worth of work (design engineers, PCB engineers, mechanical engineers, parts procurement and parts library management, and so on), so it&amp;#39;s impressive a lot of that can be collapsed into an online ordering process, but you do still need to do an amount of work to get through it.</description></item><item><title /><link>https://community.element14.com/products/raspberry-pi/raspberrypi_projects/b/blog/posts/making-a-custom-rp2040-project-with-kicad-part-1?CommentId=51aec4be-02db-401d-852f-a91bc5739bc5</link><pubDate>Mon, 29 Jun 2026 15:40:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:51aec4be-02db-401d-852f-a91bc5739bc5</guid><dc:creator>shabaz</dc:creator><description>Done, it&amp;#39;s now updated at the GitHub repo . I ended up changing a few of the USB connector pads slightly to work around the connector peg holes, it was easier to get rid of DRC errors this way, than to tighten the design rule settings for the entire board. I think it should still be reliable, since it&amp;#39;s only a fraction of a millimetre, and those pads are larger than the others anyway.</description></item></channel></rss>