Here's a "hello world" test application for Intel® Edison Compute Module. As what the title says, it's just a simple LED blinker task executed by a fast processor.
Below is the tiny module powered by Intel Atom dual-core processor at 500 MHz, with 1 GB DDR3 RAM, 4 GB eMMC Flash, Bluetooth 4.0 and Wi-Fi. It runs Yocto Linux (Linux 3.10.17-poky i686).
Some Intel Edison breakout boards that are shield-like (can be stacked on each other) are also already available on SparkFun. Most useful one is the base block which is used for connecting the Edison module to the host PC via USB. This block has two mini USB ports. The first port is an OTG type and is primarily used for flashing firmware/image of the Edison. The other one is an FTDI-based USB-to-Serial which is used for connecting to a host's serial terminal/console.
Initial configuration requires the Edison module to be connected to a serial terminal, like putty (sample boot log). After configuring the WiFi and the root's password, it is now possible to access the module remotely using ssh connection, just like in the demo video above.
The code below is a simple C++ code for blinking an LED connected at GP14. The code depends on mraa low level library to access the GPIO hardware.
/* intel edison led blink - yus 20150109 */#include <mraa.hpp>#include <iostream>intmain()
{
mraa::Gpio *gpio =new mraa::Gpio( 36/*=GP14!*/ );
if (gpio && gpio->dir(mraa::DIR_OUT)==mraa::SUCCESS)
{
std::cout<<"Blinking GP14. Press [CTRL+C] to stop...\n";
while (1) {
gpio->write(1);
sleep(1);
gpio->write(0);
sleep(1);
}
}
return-1;
}
The provided Yocto Linux installed in the Edison already includes a GNU toolchain (GCC 4.9). So the demo code can be compiled/build inside the Edison itself.
Alternatively, a BASH script can be also used to do a LED blink task.
#!/bin/bash# select led pinpin=14
gpio=/sys/class/gpio/gpio$pinif[ ! -d "$gpio"]; thenecho$pin > /sys/class/gpio/export
fiecho out > $gpio/direction
echo Blinking GP$pin. Press [CTRL+C] to stop...
while :
doecho 1 > $gpio/value
sleep 1
echo 0 > $gpio/value
sleep 1
done
Also, for those who are comfortable developing with Arduino IDE, the Arduino IDE also supports Intel Edison. However, you need to check the correct pin mappings if you're going to use boards other than Arduino's Edison kit or Edison breakout board.
#---------------------------------
edit 10/15/12
version 2: BTJoystick.v2.apk 45.8 KB
modifications: * preference menu (e.g. "Menu->Connect" & "Menu->Options" ) * add four customizable buttons (send either an ascii char or a string) * immediately send joystick data when a joystick returns to center position * selectable data format, intervals and timeout * prevent accidental closing
Using ATmega328P, operated at 3.3V supply and 8MHz crystal. At this speed, reading sensors' measurements and computing "AHRSupdate" take about 31ms to complete. Default compiler setting is used on WinAVR. With 25Hz sampling rate, this leaves mega328p extra 9ms to do other tasks. Bluetooth SPP (serial) communication is buffered and interrupt driven, so no processing time is wasted in reading and sending data to the android phone.
*This application is tested only with Samsung Galaxy GT-i5700 Spica (rooted Android 2.1 OS, i570EXXJD1 Baseband version).
The transmitter circuit uses Microchip's dsPIC33FJ16GS504 for the analog-to-digital conversion of the input signals on two channels.
The processed data on the dsPIC are then transmitted to the phone (for waveform display) via the LMX9838 bluetooth SPP module.
specs/ranges:
time per division: {5us, 10us, 20us, 50us, 100us, 200us, 500us, 1ms, 2ms, 5ms, 10ms, 20ms, 50ms }
volt per division: {10mV, 20mV, 50mV, 100mV, 200mV, 500mV, 1V, 2V, GND}
analog input (depends on external pre-amplifier configuration): {-8V to +8V }
The source codes for the bluetooth communication is based on Bluetooth Chat example from http://developer.android.com.
That example contains three java source files. And, I've completely copied the "DeviceListActivity.java", which is used for searching remote bluetooth devices.
Then I've modified the "BluetoothChatService.java" to use only the RFCOMM Client functions,
and used the well-known UUID "00001101-0000-1000-8000-00805F9B34FB" for the Bluetooth RFCOMM/SPP.
For the plotting of waveforms, I'm using SurfaceView object to draw on its canvas.
This tutorial found on www.helloandroid.com helps me a lot for this task:
"How to use canvas in your android".
The rest of the job mainly involves porting of my previous Python S60 script to JAVA language.
It was too painful on my side, because I had to convert a single script file to multiple java + xml source files!
Nonetheless, it was a good experience for me on learning the Android SDK (JAVA programming).
Special thanks to: Samdroid Forum for the customized/rooted firmwares for our Spica. Tipidcp Spica users for sharing their tips and experiences with this android phone.
---------------------------------------------------------------------- #edit (10-15-2010)
Here's now my circuit. Nothing special on it, all are based on existing circuits.
*The dsPIC I have used is most probably NOT the best choice for this project because of the many left unused peripherals (extra pins). But, this is the only part readily available in my bin and it has the fastest ADC (2 x 2MSps) among the chips I have. *If you prefer to change the input range via the op-amp preamp, the computation is located on the "adc.xmcd" file. *You can use other SPP bluetooth modules aside from LMX. (accdg to manufacturer, it's already obsolete)
It's almost a year now, and yet some people are still interested in this project (considered to be obsolete). So I've decided to place the source repository also onGoogle Codesite. You can eitherBrowse or use git to have your own local copy:
See also theChanges, if you want also to learn on how to modify the code. I've started the first 'commit' with a simple "hello world" from the SDK project template. And then changes were made until the desired final oscilloscope application is achieved.
Bluetooth Controlled Mobot using Z8F0823 and LMX9838.
It's supposed to be my entry for a friendly competitions of "sumobots". But, I wasn't able to make it "autonomous" on time for the event. It only have four sensors on each corner to detect "black" lines, but no sensor for detecting an opponent. And so that I can still test the hardware, I just made it manually controllable by using my phone's bluetooth. The bluetooth module is the same circuit I used in my BT minibot . I also used the same python S60 script for my N6120c (Symbian phone) controller.
Bluetooth remotely controlled mini mobot (version 2) using Zilog's Z8F082A and National Semiconductor's LMX9838 (Bluetooth® Serial Port Module) with Nokia 6120 classic as remote controller (using Python S60)