Hi, I'm sure this has been discussed (and debated) many times before, but I wasn't able to find any recent discussion via a forum search.
I am wondering if PJRC can revisit their decision to not provide Eagle/KiCad/(other CAD package) design files for the Teensy.
These design files are highly valuable for hobbyists who wish to get tighter integration between their custom projects and the Teensy microcontroller, or implement tweaks to the Teensy PCB design (as just one example, one may want to access a third SPI interface, which is not exposed on the Teensy as a thru-hole connection).
There is a growing movement of open hardware, and I would suggest that PJRC embrace this change by making their designs open and specify a license for use of the CAD files. PJRC sells the proprietary bootloader chip with the apparent intent of enabling custom designs, so why not go all the way and release the full design files?
Artwork for Teensy clones are already available via SparkFun MicroMod or user jenschr on GitHub. Why force hobbyists to rely on these?
TIA for reading.
I am wondering if PJRC can revisit their decision to not provide Eagle/KiCad/(other CAD package) design files for the Teensy.
These design files are highly valuable for hobbyists who wish to get tighter integration between their custom projects and the Teensy microcontroller, or implement tweaks to the Teensy PCB design (as just one example, one may want to access a third SPI interface, which is not exposed on the Teensy as a thru-hole connection).
There is a growing movement of open hardware, and I would suggest that PJRC embrace this change by making their designs open and specify a license for use of the CAD files. PJRC sells the proprietary bootloader chip with the apparent intent of enabling custom designs, so why not go all the way and release the full design files?
Artwork for Teensy clones are already available via SparkFun MicroMod or user jenschr on GitHub. Why force hobbyists to rely on these?
TIA for reading.