I'm a free software junky. Have been since the late 1990's. I run Linux on all my machines. I wouldn't have it any other way.
Which can pose a problem in the embedded space. Nearly all tools are highly Windows centric.
With the RDK, things are even worse, in that they are pushing a proprietary RTOS, Toolchain, and Debug environment. I think as also is typical, most are restricted in some way. A drug dealer approach to getting you to cough up some cash. Just a taste.
As as Engineer and tinkerer, I like to understand how things work, to have a chance to be able to fix bugs.
"If you can't change it, you don't own it." - DJ Delorie
What I find incredible that so many hackers types, who like to dismantle, re-purpose and build things, are happy to be closed off to this whole world by using highly restricted OSes and tools. It seems like a contradiction.
Anyway, there is no coincidence with the above quote, luckily for the RDK, free software hero DJ Delorie has done a lot of the heavy lifting for us Linux users.
I started here: http://www.renesasrulz.com/thread/3137
To shortcut bring up a little, I went and got the precompiled GCC binaries from kpitgnutools
The blinky example worked first go, yay!
For my application, I was initially planning on skipping using an OS entirely (due to the proprietary nature of the one that comes with the kit) and just coding to the hardware directly.
First step would be to get an on board timer running and generating interrupts... the heart beat of the application.
Plus blinking LEDs are pretty boring when you have an LCD sitting there.
So I set about modifying the blinky example from DJ to be timer and interrupt driven and also use the LCD.
The result is here: https://github.com/Zizzle/blinky2
Since getting that running I discovered that FreeRTOS looks good and is easy to build under Linux and run thanks again DJ.
So I may end up using FreeRTOS for my brewbot. Subject of another post I guess.