The BeagleBone Black could use a VPU (video processing unit)

Top side of a BeagleBone Black

I've been working a bit with the BeagleBone Black (BBB), a $45USD single board computer, for the last couple of months. It's capabilities, relative to its cost, are impressive. Several sites have compared the specs of the BBB and the popular Raspberry Pi (RPi), another powerful and low cost single board computer. You can check out some analysis of the two here.

One important difference between the BBB and the RPi is that the BBB lacks a video processing unit (VPU) to accelerate video playback. A video processing unit helps improve video decoding and/or encoding rates by performing some or all of the specialized operations involved in video processing. Without a VPU or other specialized hardware, a system would have to perform the video processing using the system's core processor, likely a general purpose processor, and at a far slower rate. This RPi and BBB comparison picks up on the video decoding capabilities as a key difference between the two otherwise similar platforms. A lack of vpu means that the BBB will struggle when playing back 720p video, using a large portion of the processor to do so. 1080p decode is out of the question with the BBB. The RPi on the other hand has a VPU called VideoCore that performs hardware video decoding. Many people have reported being able to playback 1080p video on RPi's used for media center systems.

It would be neat if the next version of the BBB had a processor that could either perform 1080p video decode in its general purpose ARM processor, maybe by having multiple processor cores or a higher clock rate, or if it had some hardware to perform the specialized video operations. This hardware might not have to perform as many of the video decoding steps as the VideoCore or other VPU's do, just enough to enable 1080p playback with some comfortable margin of available CPU.

I hope to post some concrete results of video decode performance on the BBB in the near future, along with links to the sample videos so the tests can be easily repeated. If anyone has some good numbers related to BBB video performance I'd appreciate if you could drop me an email or post a comment below.

Comments

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was

Memory efficient queuing of variable length elements

In embedded environments memory can be a critical driver of the design of data structures and containers. Computing resources have been expanding steadily each year but there are still a wide range of systems with far less than a megabyte of memory. On systems with tens of kilobytes of memory, structures are often designed to be compact to maximize data density. Rather than splurging on memory aligned elements that would be faster for the processor to access, a developer will typically use types with minimal sizes based on the known range of values that the element is intending to hold. Fixed sized buffers At my day job a fixed size pool of messages was implemented to hold message data. While this achieved one design goal of using statically allocated buffers, avoiding dynamic allocations that might fail at runtime, it isn't efficient if there is a wide range of message sizes. It isn't efficient because each message uses a message buffer. With small message sizes the buff

Chris M.

Search This Blog