This looks promising!
Are there going to be updates to the BSP User Guide and Native Application Guide? It would be nice to have links to those on the download page, since they tell us what to do with some of those files.
It looks like the documents page got updated overnight. However, section 2 of the BSP User Guide is effectively broken by changes to the directory structure. Step 4 will error, because poky/ is not where it used to be.
Section 3 looks like it should work. I'm just a little curious about the approach. Wrapping a build system inside a different build system smells like "not invented here."
I was looking through the files in the source archive, and found a README for the (new) meta-intel-edison layer that references a git repository (git://git.yoctoproject.org/meta-intel-edison) that doesn't exist. Can we assume that the contents of edison-src-ww18-15.tgz are identical to what should be at that URL?
For Intel Edison devices, the host CPU is an Intel Atom processor running Linux, and the MCU is a Minute Intel® architecture CPU running Viper*, a Wind River real-time operating system (RTOS) that provides basic OS function support, including thread scheduling, memory management, interrupt dispatch, and more.
The MCU application runs as an application above the Viper kernel and independently controls the peripherals that connect to the MCU.
Will Viper OS give access to a part of the API of VxWorks? I was expecting to see these kind of functions :
taskSpawn( ) Spawns (creates and activates) a new task.
taskCreate( ) Creates, but not activates a new task.
taskOpen( ) Open a task (or optionally create one, if it does not exist).
taskActivate( ) Activates an initialized task.
msgQCreate( ) Allocates and initializes a message queue.
msgQDelete( ) Terminates and frees a message queue.
msgQSend( ) Sends a message to a message queue.
msgQReceive( ) Receives a message from a message queue.
semBCreate( ) Allocates and initializes a binary semaphore.
semMCreate( ) Allocates and initializes a mutual-exclusion semaphore.
semCCreate( ) Allocates and initializes a counting semaphore.
semDelete( ) Terminates and frees a semaphore.
semTake( ) Takes a semaphore.
semGive( ) Gives a semaphore.
semFlush( ) Unblocks all tasks that are waiting for a semaphore.
This is great. So what kind of "real-time" stuff can you do with the MCU? What is it connected to?
You have access to all IO, i2c and UART. The advantage of this is that you can do stuff that require a specific timing without being disrupted by Linux overhead. An example of something that was not possible before is to control WS2812 LEDs (see NeoPixels : Adafruit Industries, Unique & fun DIY electronics and kits).
am I being excessively dim?
for Ubuntu 12.04:
sudo gdebi <name_of_flash_tool_lite.deb>
(replace with correct name of the installation deb file)
but where is this file and what is its name