Figure 1: An early revision of the dev kit’s schematics from May 2nd (Git commit hash 023915d5)Īfter the schematic drawing was completed, we then exported our netlist file, getting us that much closer to the physical implementation of the dev kit. The entirety of the design was done using Git as our revision control system. The process of defining the specific components to be used on the dev kits was done concurrently while drawing the schematics. Once the specific SOM we were going to use was nailed down we were able to really begin cranking through the design. We determined that EmCraft’s SOM and their general resources were exactly what we needed. At around mid-April we established a natural relationship with EmCraft who were just getting into their first big SOM production run and were close to releasing its Hardware Architecture spec sheet. However, even in the early stages of the development when we began drawing the schematics, there were SOMs we were interested in that still didn’t get to their first production run. In order to get a head-start in the development, add some extra modularity and future-proofness, we decided to go with a System-On-Module (SOM), which includes the SoC, SDRAM, eMMC, and PMIC. Initially, when the research phase was effectively over and we had to begin bringing our ideas into life, the i.MX 8M Quad had just recently become available on the market.
![qucs checker error no actions defined qucs checker error no actions defined](https://b2i.sg/help/topic/com.b2international.snowowl.help/eclipsehelp/Description_Logic_and_OWL/EquivalencyQuickFix.png)
We eventually nailed it down to the mPCIe SIMCom SIM7100A/E baseband modem module and the M.2 RedPine RS9116 Wi-Fi+BT module. Early on, Nicole had the brilliant idea of using mPCIe and M.2 modules so as to make the dev kits modular and future-proof. We included an SMD 2×5 JTAG footprint on the board and verified its functionality during the prototype phase if this is something you’re interested in playing around with then have a look for the part-number GRPB052VWQS-RC.įor the WWAN/baseband modem and the Wi-Fi + BT we knew we needed to go with some sort of modules, surface-mount or otherwise.
![qucs checker error no actions defined qucs checker error no actions defined](https://kct.ittuning24.pl/templates/01558c024928d45cf320f6f75eede787/img/e1f083c81187b02c3410a87da8436a1e.png)
Hint: If you are not comfortable with a soldering iron then you may be able to use a press-fit header on these through-holes, search for the part-number Autosplice 23-1063. We also added the to-be-expected through-holes for a UART debug header which is unpopulated by default (serial over USB works on the default image shipped with your dev kit).
![qucs checker error no actions defined qucs checker error no actions defined](http://passahongkong.weebly.com/uploads/1/3/3/5/133594912/596682543_orig.jpg)
#Qucs checker error no actions defined license
Luckily, I had prior experience designing electronics using the EDA tool KiCad, so Purism had the opportunity to create a dev kit design which used 100% Free Software. KiCad was also an obvious choice not only due to its freedom-respecting license (GNU GPLv3+), but also because it is a very capable electronics design suite that even outperforms several pricey proprietary tools out there. Initially, the idea was to modify FEDEVEL’s i.MX 6QP OpenRex board, which would have satisfied the dev kit’s basic requirements, but we quickly met two major issues: it used the archaic i.MX 6QP, and even worse was that it was designed in the proprietary EDA suite Altium.
![qucs checker error no actions defined qucs checker error no actions defined](https://images-na.ssl-images-amazon.com/images/I/51n1wzAbECL._SX218_BO1,204,203,200_QL40_.jpg)
The dev kit’s design is released under the terms of the GNU GPLv3+, its hardware Git repository can be found here: Ī backup mirror repo can be found here: KiCad as The Obvious EDA of Choiceīefore the development of the dev kit began, it was not completely clear which path we would take to produce the design, specifically, which Electronic Design Automation (EDA) tool would be used.
#Qucs checker error no actions defined software
Today we’re going to cover the journey of designing the Librem 5 Developer Kit and how 100% Free Software was used in its development. Librem 5 Dev Kit’s PCB layout viewed on the Dev Kit itself