The wrestling with my latest toy proves to be difficult.
First, I obtained the RidgeRun SDK for the LeopardBoard DM365. Following the user guide in the wiki, I was able to build the image for the board.
First difficulty: my USB-to-RS232 serial dongle (PL2303) seems to be not working well – I wasn’t able to use the serial console… So I had to work around and get a ssh shell – which took me a while to integrate my ssh key into the root file system correctly and install dropbear correctly. But I made it. Unfortunately, I have a DM368 (higher clock speeds) which are not supported out-of-the-box by the RidgeRun SDK.
Getting to know the whole thing more, I got the Texas Instruments SDK working for the DM368. After a night with playing with GStreamer (the framework TI integrated their hardware assisted codecs), I figured that GStreamer on the TI can’t do decoding and encoding at the same time.
I started to look for alternatives and found ffmpeg-dm365. To compile I had to install the updated codecs from Texas Instruments into the SDK. ffmpeg-dm365 itself links to some components of the dvtb – which are relying on includes of the old codec. In order to build ffmpeg-dm365, I had to adjust the dvtb source to fit the new codecs. Which I finally managed. Bad luck: ffmpeg crashes when I try to use any of the libdm365-codecs.
Kind of a dead end for now.
