when teensy 5.0 will comming?

The newer, faster chips have in general worse performing analog sections. External DAC and ADC are becoming more necessary. I don't see those being fitted on a Teensy form factor (for space reasons, and to avoid tying up SPI buses, and to give more flexibility). Of course this is just my opinion.

I believe Paul already said that any new design would use USB-C.
 
jerryk said:
I dearly hope that the Teensy 5 will have support for hardware debug.
Click to expand...
Agreed.
We've used teensy for a number of small odds and ends - perfect fit to speed up development.
We used it for one moderately complex project what needed lots of raw speed - generally went as well given the scope of the project.
And we used it for one complex project with lots of features - The phrase never again has been used a number of times. It did speed up the initial development but any time saving and benefits were more than lost in the debugging and integration stages. Future plans are to possibly use the same family of processors but not the teensy bootloader/ecosystem.
 
I have gone to the RPI Pico for little utility things. Because it has hardware debug. SO much faster than debug printf()s. But it
doesn't have the raw speed of the Teensy.
 
Just a thought, how about debugging on the Pico, then compile for Teensy.
I know I/O etc is likely to be different but I would have thought the core software would have been the same.
You could use something like:
Code: 
#define pico
//#define teensyCode

#ifdef teensyCode
//  code for teensy implementation
#else
// code for other implementation ie pico etc
#endif
I often use Visual Studio to design/bug check, having dummy or otherwise code for Teensy functions.
When sorted I use Visual Micro with Visual Studio for the "real thing".
 
I wonder how hard it would be to use a bare processor ( with JTAG debug ) and still use the PJRC libraries? I saw a forum post
somewhere in PJRC were somebody made a little flexible circuit board. They lifted the boot processor and soldered it on top of this flexible board, and exposed the JTAG signals.
 
One way to do it might be to revise the bootloader code so pulling an unused pin (looks like there are a couple) low forces it to an inactive state, which should then allow use of JTAG. Routing JTAG to some header pins or pads would be tricky, as Teensy 4.x are very dense boards; and you’d have to have some way of loading code to Flash for applications too big for RAM.
 
You must log in or register to reply here.
Back
Top