Many of you know I am the author of a Windows Embedded Compact Board Support Package (BSP) for the Beaglebone development board. This is an open source project hosted on Codeplex at http://beaglebonebsp.codeplex.com/. I also have a sister project targeting the Gumstix COM modules. I have made a recent change to its BSP to support 1GB Flash memory which is now included on newly purchased Gumstix OVERO modules. I have several video posted. See https://gumstixbsp.codeplex.com/
In my last blog post I showed how to
transfer IoT data over the network using the M2MQTT library. But how, you may
ask, do you acquire the data in the first place? Well, chances are you have some
kind of sensor, be it temperature, pressure, accelerometer or what have you.
These sensors, more than likely, interface to the IoT node processor via some
kind of bus. It could be I2C, SPI, CAN, LIN or any number of others in the
alphabet soup. By far the two most popular low level sensor buses are I2C and
SPI. I2C stands for Inter-Integrated Circuit and was invented by Philips
Semiconductor (now NXP Semiconductor), SPI stand for Serial Peripheral Interface
invented by Motorola.
In this example I will show how we can interface to these buses using managed
code (C#) in Visual Studio 2013. I will use the BeagleBone Black as the platform
running Windows Embedded Compact 2013. A prebuilt demo image is available at my
Codeplex site along with all the source code for the
To start I wired a prototyp ...
Read the rest of entry »
Many of the Board Support Packages (BSPs) for Windows Embedded that I have seen over the years tend to have several drawbacks. Some lack the full complement of drivers, others only come with binary code. Some show little, if any signs, of ever being tested. I can understand the underlying reason for some of these issues but one that is rather irritating is the lack of a consistent coding style. You would think that at least within an individual BSP a single, consistent coding style could be followed. Most times this is not the case. Over the years different developers work on different pieces, each imposing their own coding style (instead of taking the time and effort to learn the existing style and following the existing norm). Also, as more platforms based on the same SOC come on line, we tend to just “add on” adding deeper levels of abstraction, adding more compile time and macro directives. While it can be argued this is what makes modern day programming so powerful, it also adds “code bloat”, slows down ...
Re: Windows Embedded Compact 2013 on Beaglebone gets IoT sample
Please contact me regarding a full installation of this BSP for WINCE2013, and what is necessary for...
-- Aaron Peterson
Re: BeagleBone BSP code clean up
Hi David, Interest in the fully version of the image. Please let me know the commercials. I need clarification...
Re: BeagleBone BSP gets several improvements
Hi David, How can I get a full version (without reboot) of your image available for demonstration?
-- Marco Aurélio Braun
Re: Low power operation on the community IoT Beaglebone BSP (Part 1)
Hello , dvescovi . Because of Job , I use your Beaglebone black BSP which is helpful for me . I want...
Re: Yet Another Gotcha: Compact 7 Update
Hi David, Would you please contact me regarding the wince7 BSP for the BBB? I have a few LCD Capes...
Seems MS may have posed a new updated ISO on MSDN. For those without a subscription, you are still out...
Re: Power management on the Beaglebone part 2–Battery
Hi David, First of all thanks for this, blog it's been very useful. Before I go ahead and solder anything...
Re: More improvements for Beaglebone BSP
Thank you for the fixes. The latest version builds under WEC7! Yay! Next .. have to try deploying it...
Of course, I meant the WEC2013 SDK ... see what happens when you work with too many bits at the same...
Hi David. First, thank you for what must have been a huge amount of work. I have been trying to install...