Proview on the Udoo Quad

• UDOObuntu_beta 12.04
• Proview version 5.1.0-4

Thinking about making a new educational kit, surfed the web and found the UDOO.

• Freescale i.MX 6 ARM Cortex-A9 CPU Dual/Quad core @ 1 GHz
• Integrated graphics, each processor provides three separate accelerators for 2D, OpenGL® ES2.0 3D and OpenVG™
• Atmel SAM3X8E ARM Cortex-M3 CPU (same as Arduino Due)
• RAM DDR3 1GB
• 76 fully available GPIO
• 12 analog inputs 12 bits
• 12 8-bit PWM output
• Arduino-compatible R3 1.0 pinout
• HDMI and LVDS + Touch (I2C signals)
• Ethernet RJ45 (10/100/1000 MBit)
• WiFi module
• Mini USB and Mini USB OTG (micro with the final release)
• USB type A (x2) and USB connector (requires a specific wire)
• Analog audio and microphone
• Camera connection
• Micro SD (boot device)
• 12V power supply and external battery connector

Nice board, cheap and the specs. looks good. Tried different kind of distros and chose UDOObuntu 12.04 (beta) LTS armHF. Arduino IDE was installed. Tried to upload the standard pin 13 blink sketch and saw something strange. An error while uploading.....

No problem. Setting the right permissions and tested the standard blink sketch with on pin 13 a LED. Switched to Oracles JDK, build Proview, uploaded the Proview-Arduino sketch, and started Proview with all the standard classes. Not really impressed of the speed, but ok, my 8GB was 90% filled up. Created a small Proview project and Proview couldn't initialize /dev/ttymxc3. I started to read about the communication between the 2 CPU's and thought I was in big troubles. Tried to sent messages with a tool to the sketch and got no response.

The problem was in the stty settings.

Proview..... , the beast is running!

Closed my eyes, dragged a couple of blocks in the PLC and......

Testing!

PLC eats 2% of the CPU

Baudrate 115200

PLC scan time 100 ms

Update: 1 week running

Stopped the test and ordered a shield for the UDOO.