Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Difference between revisions of "Userspace Arduino"

From eLinux.org
Jump to: navigation, search
(Beaglebone Black to Arduino Pin Map)
Line 28: Line 28:
 
* Get https://github.com/anujdeshpande/send_exec
 
* Get https://github.com/anujdeshpande/send_exec
 
* Follow the readme. The stuff is pretty self explanatory
 
* Follow the readme. The stuff is pretty self explanatory
= Beaglebone Black to Arduino Pin Map =
+
 
 +
= Boards Support =
 +
 
 +
== Beaglebone Black ==
 +
 
 +
Initial development is being done with the Beaglebone Black and the [[Bacon_Cape]]
  
 
{| border="1" cellspacing="0" cellpadding="5"
 
{| border="1" cellspacing="0" cellpadding="5"
Line 162: Line 167:
 
|
 
|
 
|}
 
|}
 +
 +
== MinnowBoard ==
 +
 +
* Initial support started
 +
* Need Lure accessory board for testing
 +
 +
== Raspberry Pi ==
 +
 +
* support planned
 +
* will use [[RPi_Gertboard]] for initial development
  
 
= Transfer Options =
 
= Transfer Options =

Revision as of 17:02, 15 July 2013

Development Blogs for the Userspace Arduino project:


this page is to document some research on creating a userspace executable using the wiring and processing language used with Arduino.

Getting Started

Cloning

git clone https://github.com/prpplague/Userspace-Arduino.git

Running a demo

cd Userspace-Arduino/arduino-makefile/examples/HelloWorldUserspace
  • To make, while in the above directory:
make
  • A binary HelloWorldUserspace.elf should be created in a directory build-userspace
  • Copy the binary to the Beaglebone Black and execute!

Using send - exec

Boards Support

Beaglebone Black

Initial development is being done with the Beaglebone Black and the Bacon_Cape

Arduino Pin BBB Header Pin Function Alternate Function
0 P9_11 UART (RXD)
1 P9_13 UART (TXD)
2 P9_15 GPIO
3 P9_14 PWM
4 P9_12 GPIO
5 P9_16 PWM
6 P9_42 PWM
7 P8_19 GPIO PWM
8 P9_19 I2C (SCL)
9 P9_20 I2C (SDA)
10 P9_17 GPIO SPI_CS0
11 P9_18 GPIO SPI_MOSI
12 P9_21 SPI_MISO
13 P9_22 GPIO SCK
14 USR LED 0 LED
15 USR LED 1 LED
16 USR LED 2 LED
17 USR LED 3 LED
18 P9_33 AIN4
19 P9_35 AIN6
20 P9_36 AIN5
21 P9_37 AIN2
22 P9_38 AIN3
23 P9_39 AIN0
24 P9_40 AIN1

MinnowBoard

  • Initial support started
  • Need Lure accessory board for testing

Raspberry Pi

Transfer Options

Netcat

  • GNU Netcat networking tool http://netcat.sourceforge.net/
  • Can create a connection using nc -w 1 192.168.7.2 1114 < new.zip on the server (in this case the machine running the Energia IDE), and nc -lp 1114 > n.zip on the Beaglebone. 1114 is a random port number which has to be the same on client as well as server side.
  • Some issue with sending .bin files directly. Mostly it was with how the file ends, not sure. So need to zip the file.
  • Requires no authentication
  • A script will be needed to listen on a particular port on the BBB for any incoming connections which will receive, unzip and execute the code.

ssh/sftp

  • Needs ssh and sftp installed
  • Need to configure keys initially. Works without user authentication after that
  • Code to upload and execute binary here : https://github.com/anujdeshpande/send_exec
  • To do :
    • Create Sketchbook folder
    • Fetch output if any, display it in the serial monitor

Emulating the Arduino bootloader

  • The Arduino Bootloader uses a protocol similar to STK500v1 (over UART, though)
  • One way to program (copy) the binaries would be to emulate the protocol on the bone over USB gadget and use AVRDude on the IDE side
  • However this would be cumbersome, since the protocol was designed to write bytes to flash memory, not copy files.
  • Energia uses mspdebug to flash the MSP430 using a serialized version of JTAG called Spy-Bi-Wire (SBW).
  • File transfer protocols over serial like XMODEM and ZMODEM could be explored for an easier and more compatible option to Upload the binaries.
  • Install the lrzsz package on both the host (PC) and the client (Beaglebone):
apt-get install lrzsz
  • Connect the Beaglebone via USB and determine the port (for e.g. /dev/ttyUSB1). Once the OS is booted up, start the transfer:
sz -vv -b filename.bin < /dev/ttyUSB1 > /dev/ttyUSB1

HTTP post

  • Send executable over port 80
  • On BBB, listen for any uploads and execute them

Action List and Issues

  • The Arduino 1.5 IDE has better support for arbitrary architectures than the Energia fork of Arduino. This could help since the architecture specific stuff has been moved to config files. Further investigation is needed. Should the Userspace implementation forked directly out of the Arduino IDE or should the current implementation continue?
  • For development beyond the GSOC period, an option to get this upstream needs to be considered.
  • The BBB needs a separate FTDI cable for serial ports. However, a /dev/ttyACM port is available over USB. It can be used for uploading via the normal bootloader way. After the upload, it can be used for serial read/write to the host (PC).
  • A single protocol to tackle uploading via USB and ethernet and may not be feasible. Networking over USB is pretty unreliable and tough for newbies to get working. For ethernet upload, several of the above options can be considered. For USB, a simple bootloader emulator will do.