Hackaday reports:
After a years-long wait, an ARM powered Arduino is finally due. The Arduino Due will finally be released this coming Monday.
On board the Arduino Due is an Atmel-sourced ARM Cortex M3 microcontroller running at 84 MHz. The Due has an impressive list of features including a USB 2.0 host, compatibility with the Android ADK (lest you still need an IOIO), 12 analog inputs with 12-bit resolution, 2 analog outputs running at 12 bits, a CAN interface, and more input pins than you can shake a stick at.
For a full list of features, you can grab this PDF we picked up when we saw the Due at Maker Faire NYC
This hardware update to the Arduino platform makes a lot of very cool builds very possible for even the beginner hardware hacker. Of course the Due will be used for controlling drones and UAVs, laser cutters and 3D printers, and playing WAV files from the analog outputs. The much improved hardware opens up a lot of other possible builds including making your own guitar pedals – DSP is a wonderful thing – and reading the telemetry from your car in real-time via the CAN bus.
Although it’s not available right now, you will be able to buy an Arduino Due for $49 USD this coming Monday at your favorite electronics retailers.
The ArduCopter/ArduPlane team is currently focused on porting the code to our PX4 board, which is based on a much faster and more capable ARM chip than the DUE and has other cool stuff like a RTOS already up and running. But one of the cool things about the Arduino DUE release is that includes some improvements to the Arduino IDE to support a wider range of hardware. So our near-term priority will be to see if the Arduino IDE can be modified to support PX4, which will allow us to retain the accessibility of Arduino without having to support two different ARM-based hardware platforms.
Comments
@wayne garris, I just spend some time looking through the SAM3A datasheet that the DUE uses. There appears to be no 5V tolerant inputs. The chipKIT PIC32's however have almost all pins 5V tolerent.
@Dan Overholt, it appears that the new DUE IDE actually is the chipKIT MPIDE (minus chipKIT), not by an upstream push by the chipKIT team, but rather a pull by the DUE team to take advantage of the awesome functionally created by Mark Sproul and Rick Anderson at Fubarlabs for chipKIT.
Jacob
I have had no problems running servos off a 3.3v signal. A 5v input signal to a 3.3v pin can be a problem however some 3.3v pins are 5v tolerant just check the data sheet.
Well, whatever we do, we better hurry up, we're running out of RAM on the Atmega 2560 again with Arducopter!
Making PX4 work with Arduino-IDE is a good idea. But instead of forking the Arduino-IDE yet again, why not incorporate the PX4 support into the Multi-Platform IDE created by the ChipKIT guys? While they tend to focus on the PIC32 series of processors, MPIDE itself was not created with this spirit in mind, but rather as a true way of "opening up" the Arduino IDE to more processors and platforms. You can read more about it here: http://themakersworkbench.com/node/422
The DUE is nice, but still not as powerful as the Arduino compatible chipKIT Max32 or the PONTECH UAV100 which is also based on the Ardunio compatible chipKIT platform.
Jacob
not sure what all the hoopla is about . I have been using a 32 bit arm with "arduino" environment for years. It's called the maple. and ya it already has a RTOS running on it and already i have some "ardupilot' code running on it. From what i understand this "arduino" arm even uses much of the work put forth by the guys at leaflabs. Seems like this is more about branding then a real "ground breaking" product.
http://leaflabs.com/
and one more thing, Its is not pirating to make a ardupilot after all Chris licensed it so anyone can. DERP!
Yes, I meant MegaPirate. Sorry.
@ramboky: there is actually very little where we draw anything from other projects. Since I've been on the devteam (a little less than a year now) I've never seen anything on Arduplane, and very little on Arducopter. I know we have looked at the acro controller of Multiwii, but did not do a straight port. It was just to get some inspiration of what is wrong with ours, and what direction to head. Meanwhile, Multiwii has said they used our automatic mode code quite heavily in creating their own. And that's fine.
Open Source is supposed to be a two-way street and for the most part it is. But there seems to be a one-way street heading to China.
-
1
-
2
of 2 Next