Just a heads-up that Teensy my favorite small form factor Arduino compatible board, just got a solid upgrade with the 32bit ARM Cortex-M4 48mhz based Teensy 3.0. The Teensy 2.0 has pretty much been my bread and butter board for homegrown experiments (and some work related ones also). Looking forward to playing with the capabilities of the new one. The creator also aims to keep Arduino compatibility with the new ARM chip, if you don't want to talk directly to the hardware.
More information about the Teensy 3.0 should become available once the Kickstarter pre-order is completed and the Teensy 3.0 becomes official in the PJRC.com store.
But a quick highlight of the specification are:
- 32 bit ARM Cortex-M4 48 MHz CPU (M4 = DSP extensions)
- 128K Flash Memory, 16K RAM, 2K EEPROM
- 14* High Resolution Analog Inputs (13 bits usable, 16 bit hardware)
- 34* Digital I/O Pins (10 shared with analog)
- 10 PWM outputs
- 8 Timers for intervals/delays, separate from PWM
- USB with dedicated DMA memory transfers
- 3 UARTs (serial ports)
- SPI, I2C, I2S, IR modulator
- I2S (for high quality audio interface)
- Real Time Clock (with user-added 32.768 crystal and battery)
- 4 general purpose DMA channels (separate from USB)
- Touch Sensor Inputs
Comments
Hi
Since this system works with 3.3 V , do you connect it directly to your RX receivers?
Regards
Todd, if you want to move away from Arduino and into a more "mature" ARM environment using RTOS/Linux etc. you have LOTS of options. Popular ones are Rasperry Pi, Beagleboard, Pandaboard, Hawkboard, Gumstix and the list goes on. The important thing especially when you are starting out, in is to make sure there is an active community for the hardware you select.
What would you guys suggest for a newbie wanting to move from the Atmel/arduino environment to a dev board that is more capable?
Nice - Always a Teensy fan; never an Ardweeny.
(why - because com ports are bad, but virtual comm ports are worse - they cannot be labelled, predicted, or scanned - the user has to choose the comm port with no knowledge - aka guess. It's BS.)
I agree that 48mhz is somewhat slow for a 32bit device. But according to PJRC the die is the same as the 100mhz version, so at your own discretion there is a overclock option for 100mhz.
the clocking speed of the teensy is a way beyond of what i would expect.
i would opt for the fez device.
I don't know what happened to Michael Zaffuto's comment, I thought it was very useful: spec-wise the FEZ Cerb40 does look like a good alternative (especially with the STM32F4) to this board..
That is no problem, even on the atmega hardware if you just talk directly to the hardware. Arduino severely limits much of the available functionality trying to be user friendly.
For example if you have a timer with no prescaler on a 16mhz system, you theoretically get a timer resolution of 62.5 nanoseconds. But of course you have to spend some time requiring and processing the timer counter, so the practical resolution is worse depending on what you want to do. But beating micros() is no problem outside Arduino.
Ok cool. Basically, I'm interested in having more than micros() timing resolution. But I guess if I used the Arduino IDE, that's all I'd get. Do you know what the timing resolution is if using basic C++ programming?
R, that is correct.
-
1
-
2
of 2 Next