hey gang! let me just first say that i'm very eager to get my board in and start playing around with it. however, as i wait for it to come in, i was hoping someone could shed light onto something for me... First, my application though… I'm building a motion control camera system which essentially consists of 3-5 stepper motors which are driven through a train of HIGH/LOW pulses on output pins at intervals anywhere between 200 to 800 uSec (different pins will have different frequencies). Obviously Arduino boards (using the Due currently) are perfectly suited for this task. However, its difficult to create any type of complex motion profiles without some external software (e.g. Blender/Maya) that runs a nice GUI and that allows you to visualize the camera moves in a virtual environment (through Bezier curves and what not). Then, you attach your Arduino to your computer, the computer creates the complex motion profiles and then runs through them telling the Arduino when to step (pin HIGH/LOW). So, when I came across UDOO, I thought it be perfectly suited for me: the Linux side would handle the complex motion path planning along with GUI and it would talk to the Arduino side which would step the pins with proper timing. But then I read something that confused me -- from the UDOO block diagram: "Each pin can be individually configured to be driven by one or by the other processor. Configuration is done via software" I guess what I'm wondering then, is why we need the ATMEL processor at all; I mean, if we can just throw a bunch of pins HIGH/LOW with the Freescale processor, then why add the ATSAM3x8E as well as the complexity and potential latency of communication between the two? Is it faster to control pins through the Atmel than the Freescale? I'm also concerned about speed bottlenecks between the processors when communicating the timing of the pins; serial might be too slow to send timing for 5 (or even more motors), so that again makes me think that I should do everything from the Freescale processor. I see the processors could also communicate through USB OTG; but again, if I can set any pin to be controlled by Freescale, why not just forget about the Arduino? I'm not too concerned about doing any kind of parallel processing; really the only thing that is critical in my application is the ability to through multiply pins HIGH/LOW at high frequencies. From tests, running 3 pins HIGH/LOW at 200uSec is on the limit of being attainable for the Due; so certainly being able to do that from the Freescale side (with the 1Ghz ) seems like I'd have plenty of resources. But then again, I feel like I'm missing some sort of technical insight that comes with controlling GPIO from the Freescale side. Can someone detail? Thanks for all your thoughts and insights everyone and keep up the good work!