Your SDK of choice

Your SDK of choice

  • I own Leopardboard 368 and conduct some experiments with it in order to make sure that DM368 works for my needs. I'm struggling to set up an SDK which would be easy to use and extend as needed. All I need is decent kernel version, bootloader capable of booting the device from an SD card, working minimum set of userspace (busybox plus dropbear), gstreamer with hardware-accelerated plugin and an ability to recompile the latter. However there are some problems in setting all that up.

    One of the problems is that there is a big scatter in the SDK land and it's not really clear where to start. There are available:

    1. TI DaVinci PSP SDK. Appears to be just a collection of components. IIUC there is no ability to easily build your own image, only prebuilt ones are included. However it is an authoritative source of sources of DMAI, codecs engine, gstreamer. An SDK is painful to install and use on any host but what they declare as supported (which is quite dated Ubuntu 10.04). Requires old CS toolchain.
    2. RidgeRun SDK. Has quite nice UI, everything ready to build an FS image. However also requires using old CS toolchain, is a bit outdated with respect to upstream packages, is barely configurable when it comes to customization of rootfs. Has utterly stupid installer which after all just does "svn checkout". They new planned release (no idea of when will it be available) will be based on Arago project.
    3. Arago project. Seems interesting, but its status is unclear. Is it really supported now? I've tried to build it but it fails at many points. As far as I understood they are switching to OE-core now. Also I'm not sure if they support leopardboard. There is no dm365/dm368 machine config in their meta-ti layer.
    4. Openembedded "classic". Seems to have passed EOL line. Doesn't build from master for me.
    5. Openembedded core + layers. Is probably the most close to upstream projects, has the widest community. Has a bit steep learning curve, but it is still doable. On the negative side: there is no (or at least I couldn't find) layer that provides support of leopardboard or even dm365-evm. Even in official TI layer repos.

    So far I was only able to create an image that would boot the device using RR SDK. Still I'm not particularly happy with it. I like openness, modularity and customizability of oe-core, but there still some work needs to be done to make it support leopardboard. There should be a machine definition added, kernel and bootloader recipes, as well as recipes for dmai, codec engine, gstreamer-ti and so on.

    Have anyone tried that? Maybe I'm missing something and bsp layer for leopardboard 365/368 is available somewhere? What is your SDK of choice?

  • I have same feeling. Did you find a free SDK with support of all hw avalaible at DM368? I have found a blog for porting of TI DVSDK so maybe I will try it. tw.myblog.yahoo.com/.../article

    I just need to use came port and I am confused :) I dont know how to start

  • I have the same feeling too - we need an IP cam that can do PSIA (which TI claim theirs does) but TI won't even speak to you unless you're going to sell 100k units a year, and Appro don't answer e-mails and aren't clear on what their various Demo-cams/SDK packages actually do or don't do.

    It's like people don't want customers.