Digikey also sells the board ($84, quantity available: 0) https://www.digikey.com/product-detail/en/nxp-usa-inc/MIMXRT1050-EVK/568-13517-ND/7646293
and presumably MBED will have software support "real soon". I did lots of experimenting with MBED K64 before the T3.5/3.6 beta release.
Solderless breadboard compatibility is essential, but not for every signal. Like Teensy 3.2, 3.5, 3.6 only about 20-40 signals will come to breadboard friendly pins. I'm considering a variety of ideas for how to make the rest available, but honestly, not very concerned about that part at this extremely early stage.
Like every other conversation about future Teensy, I'm sure there will be plenty of talk about form factors, connectors, pin spacing, and so on. Feel free to discuss. I am listening. But don't for one second imagine I'm going to abandon breadboard compatibility for a high density connector like Intel did with Edison.
Many questions. Here's some quick answers...
Only NXP can say for sure about their memory design choices, but it's easy to imagine the likely answer: cost.
I need to be careful about the NDA, so I'm not going to comment about questions involving the chip's details or anything I might know about their plans for future chips in this product line.
External SDRAM is one of the very difficult choices for a new Teensy. The situation is similar to Teensy 3.6, where FlexBus consumes many of the I/O pins and makes several important features unavailable. So I'm leaning against SDRAM (or keeping those pins unused). It simply costs too much, in terms of lost functionality.
My hope is to move towards integrating conditionally compiled semaphone or mutux support into the core library and many of the most commonly used Arduino libs. I do not intend to make any RTOS mandatory, but quite a lot could be done in the many libraries so they work much better when used with an RTOS. This is the sort of thing best discussed on its own thread. But I will say right now, the 2 limiting factors are dev time to do this, and having RTOS users willing to help test unstable/alpha/beta code. Both of these always seem so elusive...
Release of bootloader chips and a reference board will almost certainly look similar to prior times. Never before have I managed to get these done right at the Teensy board's release. There's always a ton of stuff to do leading up to the release, and then usually a few months of highly urgent software work following. I'm pretty sure a first Cortex M7 board will be similar.
Ok, maybe it's time to drop a hint about future Teensy.... (hope everyone is sitting down)
This chip is very likely to become the core of Teensy 4.0 sometime in 2018.
http://www.nxp.com/products/microco...x-rt-series-crossover-processor:IMX-RT-SERIES
Yes, you're reading that right, a 600 MHz Cortex-M7 is coming!
uhm, post #3 replicated by a 2 post user, why?
.
Any news about the future Teensy 4?
Next month, at the beginning of March, the new NXP i.MX RT1020 microcontroller, Cortex M7, 500 Mhz will be available. In March available to request samples, in June in production, seem with very cheap price, cheaper than current MK64 or MK66.
I want to order some samples, and make a small evaluation board. Now I have the RT1050 in test, with the NXP evaluation board, and it works very well, an extraordinarily powerful microcontroller. Both RT1020 and RT1050 may be a very good option for new Teensy 4.
.
Any news
once I saw they have no DSP, my interest became limited
...
Was perhaps a typo or auto correction error. These new thingies seem to have no DAC which is a big no-no for me.
It was not a typo
looking at
https://www.nxp.com/products/proces...processor-with-arm-cortex-m7-core:i.MX-RT1050
I see only FPU but no DSP
I see a 2d graphics acceleration, which could be useful for signal processing and is probably better documented than the RPI one, but I doubt that a supporting library will be available soon (see Ethernet on T3.6).
OK, someone interested can always develop a library.
These essential capabilities with enablers like graphics and display support and seamless connectivity increase system-level costs and extend time-to-market.
But does the Pi Zero has deterministic low-level I/O usable without an OS and additional peripherals like external RAM? As far as I can see the i.MX RT is still a microcontroller while the RasPi is a microcomputer.