Raspberry Pi

Transfer Options

Netcat

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

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.