Rockchip RK3288 Android 4.4.2 SDK and Schematics Released for Firefly Board

Firefly-RK3288 development board was first announced in July. I still don’t have news about availability nor pricing, but the T-Firefly website launched yesterday. They seem do have a nice Wiki, but unfortunately everything is currently in Chinese, except when you go to the download page. You’ll find firmware upgrade_tool for Linux and Windows, the USB drivers for rooting and firmware update, firmware images (Android 4.4.2, Ubuntu 14.04, and dual boot), the board schematics (PDF), and Android KitKat 4.4.2 SDK with U-Boot, Linux, and Android source code, some documentation, XBMC apk (no source) with H.265 hardware decode support for MP4, MOV and MKV container formats.

The SDK is available on Bitbucket. I planned to test it, but unfortunately my network connection is very slow (and unstable) to this server, and I failed to retrieve it with git clone. The company also posted the build instructions in Chinese in their website, but I’ll reproduce them here for Ubuntu 14.04.

  1. Install required packages:
  2. Checkout the SDK:
  3. Build the Linux kernel:
  4. Build Android:

And after some patience, Android should be fully build. Instructions to create a Ubuntu image are also available in the Wiki, but only in Chinese.

Share this:

Support CNX Software! Donate via PayPal or cryptocurrencies, become a Patron on Patreon, or buy review samples

20 Replies to “Rockchip RK3288 Android 4.4.2 SDK and Schematics Released for Firefly Board”

  1. There’s no TS container for 265 here…. is this an hint that review of UyeSee G1H was not complete? There container was almost only TS while here are listed only mp4, mkv and mov….
    Should I cross my fingers?

  2. skelton :
    Not bad, though I don’t see a place to buy it. Not sure if buying this or wait for a Radxa Rock 2

    I would await … from Radxa there will be some surprises with Rock 2 … 😉

  3. @cnxsoft
    Yes, but TS container is not so common for anything more than mpeg2, so let’s hope mp4, mkv and mov container H.265 “compatibility” is different for the whole rk3288.
    (I have an A10 box and as today still haven’t found a decent way to play H.264, tried many)

  4. My $.02 on this is that it was a brave move on the engineer’s part to release this product as open source at all. Personally, I welcome any open source hardware, no matter its degree of openness. Let’s compare this board to a new samsung phone…. Yeah, Firefly’s a whole lot better!

  5. Jacob Gadikian :
    My $.02 on this is that it was a brave move on the engineer’s part to release this product as open source at all. Personally, I welcome any open source hardware, no matter its degree of openness. Let’s compare this board to a new samsung phone…. Yeah, Firefly’s a whole lot better!

    Samsung Phones has 4xCortex-A15+4xCortex-A7 (big.LITTLE configuration)
    but rockchip has 4xCortex-A17
    And rockchips software is really bad optimized at least RK3122 was bad.
    Lots of memory copy => bad for video playback

    http://www.anandtech.com/show/7739/arm-cortex-a17

  6. @Jacob Gadikian
    Open Source Hardware normally refers to http://www.oshwa.org/definition/
    If they don’t release the files necessary to modify the hardware, it’s not really open source hardware. It’s true very few companies release open source hardware. The only ones I can think of are CircuitCo (BeagleBone Black, Minnowboard), Olimex (all their Olinuxino boards), and Arduino. Many system-on-module companies also release their baseboard under an open source hardware license.

    But Raspberry Pi, Cubieboard X, Radxa Rock, Wandboard.. etc.. are not open source hardware, but for most people that’s good enough.

    @m][sko
    I think he was referring to the openness of the platform.

  7. I was, but you’re right. Better terminology is needed here as this isn’t the first time that I’ve seen this confusion come up. Or, just for another example of it, have a look at all of the licenses on upverter– is there a dominant “open platform” open hardware license? That is– one that does not certify that one can download the totality of the plans for the CPU & GPU but instead guarantees that

    A) The board could be built by the user if they had the parts & equipment needed
    B) The board’s essential software is open source.

    Thanks in advance for your thoughts 🙂

Leave a Reply

Your email address will not be published.

Advertisement
Advertisement