Loading, please wait.
From the monthly archives: August 2014
We are pleased to present below all posts archived in 'August 2014'. If you still can't find what you are looking for, try using the search box.
The issues get partly resolved.. Please read on. There were some issues with the August update. I posted this: The August update stated that : The Aug 2014 (11.0.50728 & 12.0.30527) release resolves the following issues: · The Debug.Start Debugging option will delete the deployment directory contents. · You cannot deploy a class library to the device if the solution does not contain an executable project. · You cannot specify an external program to execute when run is clicked. ====== · I tested the first point and that hasn’t been fixed · In an existing solution (One console app project and a DLL project on which it depends) if you right click on the DLL project in Solution Explorer, there’s no option to deploy it. Also if there is only a DLL in the solution same applies, so point 2 hasn’t been resolved. The issue in my previous post wrt being able to deploy and debug in other than \Temp hasn’t been resolved. So I suggest that nothing has been resolved. PS 12.0.30527 is the new installe ...
Read the rest of entry »
I recently made several improvements to the community Beaglebone BSP available on Codeplex.
The BSP now support all three serial communication ports. These ports are 2-wire (Rx and TX only) and available on the expansion P9 connector. Also added support for the third instance of the SDHC controller. These, along with the I2C and SPI bus are also available on the expansion connectors. I have included managed (C#) test programs to exorcise these buses.
Added a define file for the TPS65217 PMIC (Power Management IC). This PMIC has some nice features, like built in LCD backlight support and a Li battery charger. I have battery support working and will release additional code soon. Support for WEC7 and WEC2013.
DV
Ever get: "Warning MSB3061: Unable to delete file " message towrds the end of a build, eg: BUILDREL: BUILDMSG: Cleaning up "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release" C:\WINCE800\public\common\oak\misc\buildrel.proj(495,5): warning MSB3061: Unable to delete file "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release\proxydriver.dll". The process cannot access the file 'C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release\proxydriver.dll' because it is being used by another process. {log="C:\WINCE800\build.log(40826)"} C:\WINCE800\public\common\oak\misc\buildrel.proj(501,5): error : Error cleaning up flat release directory "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release". Unable to delete the following file(s) "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release\proxydriver.dll". ...
Read the rest of entry »
I was about to board a Southwest flight last night, when the Scanner and Camera Wizard error dialog suddenly popped up on top of the boarding group display (see picture). I know people who like to take pictures of things like this, and to be honest I have been doing it myself lately, but I really didn’t know what to do with them. Then I thought about this being a teachable moment, how can we prevent this from occurring on systems that we manage?
I am not sure exactly how to get to this point. But I can guess, I think that one of the Southwest employees probably plugged their smartphone into the computer that controls this display (probably to charge it. Reminds me of the time that one of the judges on Americas Got Talent unplugged the shows judging buttons to charge her phone.)
There are actually a few things wrong in the picture:
The Explorer shell and start bar a running. That means that someone can always figure out a way to jump on the sys ...
Read the rest of entry »
Lorenzo Maiorfi, a Windows Embedded MVP from Italy, recently released a Bluetooth 4.0 Low Energy (BLE) class library for .NET Micro Framework, under an Apache License.
Read the rest of entry »
Windows Embedded Compact 2013 (WEC2013) has great graphics and the XMAL /Silverlight support makes it great for User Interface (UI) development. With WEC 2013 many of the traditional user shell components, like the control panel, have been removed. This shifts most of the UI burden back on the OS developer. Not to worry though, there are some great samples included with WEC2013 and the development tools are now top notch. Here is an example of a home screen and the control panel included in WEC7 but removed in WEC2013: And here is an example of a home screen included as sample code in WEC 2013: You can clearly see the improvements. One additional nice feature of the new graphics framework is its ability to support “hardware acceleration”. Most all the new PCs graphic cards do some form of hardware acceleration and now even the lower-end embedded Systems On a Chip (SOC’s) include graphics accelerators or GPUs. The Beagleboard Black, which contains a Texas Instruments AM335X processor, is no excepti ...
Read the rest of entry »
Valter Minute, Windows Embedded MVP, joined Embedded101 board to help guide and expand our community.
Read the rest of entry »
The July 4th and 5th I was in Florence for the event Better Embedded 2014, the first Italian conference dedicated to the embedded world.
I was lucky and honored to be a speaker with a session on the Internet of Things entitled "Internet of Things: protocols war !" The event was attended by many people every year and has kept his expectations and I hope to be able to relive this experience again next year.
Regarding my slides you can find them on SlideShare.
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
example.
To start I wired a prototyp ...
Read the rest of entry »