ctadlock

Id probably add a new section right under "Supported Chips" titled "Determination of Teensy Variant" or something that states that the bootloader is responsible for reporting the variant of the Teensy and it does so by an introspection of the...

"you did read that thread, right ?!?!?" - dont be that guy

None of these custom boards "are" a Teensy 4.1 in reality, only in the logic of the bootloader. Hopefully the people designing future custom boards find this post so they don't blindly make a mistake.

So what hardware config makes the bootloader think its a Micromod? It baffles me this information is not on the bootloader page.

Damn! This is exactly what I need as well. need to break out the USB to something that can survive vibration environments. Is it a lockable teensy? BTW I like your machine, I assume it's producing fireballs for super mario :D

Yes we will be creating lockable Teensy for this.

This seems like required reading for anyone developing a custom board. Should be included on this page. https://www.pjrc.com/store/ic_mkl02_t4.html

I'm still unclear where the determination of board type is happening. Is it? 1. In the boot loader and it says "I'm a teensy 4.1" and then the software compiler reacts to that 2. In the compiler logic that introspects the hardware (size of...

That seems like an odd assumption. I have no real knowledge why other people are making custom Teensy's though. For me I needed a compact board. Either way this information should definitely be on the custom bootloader page. I almost used the...

Looking at the core code there is a bunch of logic that is conditional on ARDUINO_TEENSY41. Seems like this should be documented on the bootloader page.

Out of curiosity isn't that an issue? If I used smaller flash would I then not be able to access the higher pins that are only available on 4.1? I haven't looked through the core code for what conditional logic is based on this.

Size of the flash memory indeed. If you use a 16MB flash it will think it's a Teensy Micromod.

I just built a custom Teensy 4.x and its all working great. What I was surprised at is when I ran the first blink sketch I had to compile as Teensy 4.1. What configured this as a 4.1 vs a 4.0? As far as I know its the same bootloader chip for...

The boards work great!

Here is the X-ray of one of the boards. NXP chip in the middle, boot loader at the bottom, ST NFC chip on the right, flash top-left.

Project thread here.. https://forum.pjrc.com/index.php?threads/high-performance-custom-nfc-reader-based-on-teensy-4.76634/

My company GoToTags, makes NFC encoding robotics and software. We got to the point with off the shelf NFC readers that they couldnt meet our performance goals, so we decided to make our own. We worked directly with STMicro engineers on the board...

Best thing we ever did was remove PlatformIO; all it did was act as an annoying middle man. Given we use CLion we made our own cmake for Teensy and it has been great. We use the Arduino IDE and Teensyduino tools from cmake so we get all the...

I went through the process of getting the Teensy 4 bootloader chip (IC_MKL02Z32_T4_QFN16) added to the list of parts at JLCPCB. As always you will need to buy it from PJRC and send it to JLCPCB as a consigned part. Its now JLCPCB part#...

It still unclear to me what is different about the lockable Teensy 4s. Is it that you have configured them differently when they are made? Im making a custom Teensy 4 and need it to be lockable.

Thanks for taking a look Paul. I'm not sure I understand your comment. Are you referring to the 5V-3.3V LDO? If so it seems well able to handle the current as its rated to 1A. The part is NCP692MN33T2G...

Im building a custom board based on a Teensy 4. We heavily use the Teensy 4.0 and 4.1 in our other projects but for this project we need a very small form factor and a limited number of exposed pins to talk with another chip via SPI and a couple...