Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 7 of 7

Thread: Use of the bootloader chip question

  1. #1

    Use of the bootloader chip question

    Hi everyone!

    I'm very happy with my prototype based on the 3.6. So I think it's time to move to the next phase. I am wondering how the bootloader (from PJRC) chip can be used. Would it be OK to have the bootloader on a ICSP programmer and only use it to program the main MCU chip but omit it from the final design? Or is the bootloader chip needed every time the main MCU chip is powered and so present permanently on every board?

    Thanks for your advice (and sorry if my terminology is wrong).

  2. #2
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    6,784
    Saw this recently - and found it :: Doing-business

    Quote Originally Posted by PaulStoffregen View Post
    Yes, you can embed Teensy inside your product and sell it. There's no extra license fee, beyond the price paid for the Teensy board. Likewise, you can buy the bootloader chip and its price is effectively the license to make your board fully Teensy compatible.

    You can also make your own board without anything from PJRC, and still use the open source code we've published. Of course, you'll need to do *something* to get your program onto the MK20 chip. Programmers from P&E Micro, chip programming service offered by some distributors, or buying just 1 bootloader chip and making your own "programmer" which unplugs after you test your board are the popular approaches.

    Almost all the open source code is MIT license, which gives you the most flexibility. But some Arduino libraries are GPL, so if you use libraries (as almost all projects do), check their license info. Usually that means having to read the headers in the source code.

    The name "Teensy" is a registered trademark. You can't call your product "Teensy" or anything that would be confusingly similar. If you use an actual Teensy board as a component, it's ok to say you have Teensy inside or powered by Teensy or similar language. You'll probably want to give your product a distinctive name anyway.

  3. #3
    Thanks very much for the info. This seems EXTREMELY generous of PJRC. So thank-you Paul and the gang!

  4. #4
    Quote Originally Posted by alialiali View Post
    Thanks very much for the info. This seems EXTREMELY generous of PJRC. So thank-you Paul and the gang!
    And... I just ordered a few more Teensy 3.6. I am going to keep the board in the design for a while instead of jumping to create a standalone version for a saving of around 10 USD. Looking more at the schematic and board it really is a masterpiece. I'm not going to be able to create anything that small and perfect in a hurry.

  5. #5
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    6,784
    Indeed - a 6 layer board to match the size of the T_3.2 MCU on the new MCU with ball pins was no small work. There is a reference board I just link on another thread in the past few posts.

  6. #6
    Yes, the reference board would be my starting point. But I guess I can spend more time on software, case design, etc for now. I'll certainly be back for my own custom Teensy, but ... since I am mostly hiding the Teensy on the back of a board behind a screen -
    priorities \_(ツ)_/

    Thanks again for all your help.

  7. #7
    p.s. Here's a sneak preview of the 3rd iteration if anyone cares:

    https://photos.app.goo.gl/FwwQLErUFPiSKv4I2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •