What should I call my boards?If you're making your own board, come up with your own name! This will allow people identify you with your products and help you to build a brand. Be creative: try to suggest what people might use the board for, or emphasize the form factor, or just pick a random word that sounds cool. "Arduino" is a trademark of Arduino team and should not be used for unofficial variants. If you're interested in having your design included in the official Arduino product line, please see the So you want to make an Arduino document and contact the Arduino team. Note that while we don't attempt to restrict uses of the "duino" suffix, its use causes the Italians on the team to cringe (apparently it sounds terrible); you might want to avoid it.
This is one area where the Teensy could open up a bit -- it would be nice to see the communication protocol published so that others can create compatible bootloaders and host-side software
I've since found AVROpendous and ordered a board to play with
Can you find the bootloader source?
Last time I checked, the DFU bootloader and GUI-based FLIP loader program were both closed source!Sure, the website says "Open Hardware and Open Software Development Platform", but what does that really mean? Can you find the bootloader source?
If you need larger quantities you can always manufacture your own. AVRopendous is an Open Hardware design so all files are available for Open Source KiCAD (schematic/layout/gerbers/BOM/solder paste stencil). For the adventurous, there is a simplified Quasi-Single-Layer version which can be built without needing to drill any holes and etching only one copper layer.
By contrast, the AVROpendous uses either the stock Atmel bootloader, or the LUFA (formerly MyUSB) DFU/CDC class bootloaders. The LUFA bootloaders are much bigger - 4KB a piece - however may be jumped to from the user application (with the processor in any state) and use the LUFA library as a backend, rather than a smaller set of custom USB code.
Paul, I know this probably seems like frustrating and bizarre behaviour to you,
I'm seeing what look like a lot of apologizing for avropendous having a closed source bootloader
"Embrace, extend and extinguish," also known as "Embrace, extend, and exterminate," is a phrase that the U.S. Department of Justice found was used internally by Microsoft to describe their strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences to disadvantage its competitors.
But I do hear your overall message, that you want me to make all aspects of Teensy open source. I haven't actually answered this yet, so I will do so now.Teensy is more than bits and bytes. Teensy has a business model which has been carefully considered. That model involves a mostly open source approach, but also some closed source tools. PJRC has made very substantial capital investment into this business model. More developments are on the way, which I won't discuss at this time.Yes, factored into the business model are potential lost sales opportunities for "zealots" who will only buy a completely open platform.... or perhaps one with crafty marketing that seems like it has openness but in fact ships with a closed source bootloader and recommends closed source tools. You won't see PJRC doing that!But if the business model is successful, you should in time see more and more compelling advantages to using a Teensy.