Hi everyone, we have started on a version of Teensy 3.2 which will use this longer footprint:
https://oshpark.com/shared_projects/HGzzmZbK - a DIP48 that accepts the Teensy 3.2 module side pins and optional SMT pads. Soldering this up with a T 3.2 requires a jig and hand work and ends up making the controller quite expensive.
But we need access to those optional signals, and need 5V tolerant I/O and a hardware reset input. We can't get those with Teensy 4.X. We have enought T 3.2 to meet our customer's need for the rest of this year and our selling our excess with a
message elsewhere on this forum. Those sales are being used to fund this new module.
It might seem silly to be designing a new Teensy 3.2-like module when the rest of the world is moving on, but we have a large investment in our larger system and it works very well. We have shipped some low thousands of that system using this adapter board approach. Since we can't get Teensy 3.2 any more but apparently
now the components to make them are available (not the case a year ago), we have started on a single board with the DIP48 footprint, plus castellations for direct solder (similar idea to the
RP2040 Raspberry Pi Pico module). It will use the PJRC bootloader and have a micro-B USB so it will look and act like a Teensy 3.2 but with more pins and access to the hardware reset (because our system relies on that). We won't call it Teensy 3.2 since we are not PJRC. Again,
it will not be a perfect drop-in for the Teensy 3.2 since it has more pins and is a longer board. But since the DIP 28 pins of the Teensy 3.2 are there as part of the DIP 48 larger board, you could just solder in header pins to those only and use it like a 3.2, with extra PCB hanging off the ends. Maybe that would work for some folks whose design has extra space in the right place around the Teensy. This module will of course use the existing superb Teensy 3.2 infrastructure and libraries.
Maybe some other folks would also find such a module useful? We have
no delivery schedule yet, no price, and no public documentation (so please don't ask since I don't yet have any answers).
We're just getting going and are in no rush (that could change of course). I was here on the forum looking for other information and saw this thread so thought I would jump in with news of what is at the moment admittedly 'vaporware'. I'm curious what interest there might be in this module, since that may advise our initial production plans. I'll try to monitor this thread as my time permits.
