This blog is a Tutorial on how to implement Win 10 IoT Universal Apps that make use of Raspberry PI 2 (RPI2) General Purpose Input Output (GPIO) pins. This covers:
The interrupt (event driven) version addresses the InvokeRequired pattern in the XAML context. (Controls can't be updated directly from another thread).
The complete solutions are available (in source) on Codeplex at:
"Windows 10 IoT Samples": https://IoTSampler.Codeplex.com
Read the rest of entry »
An old gem that has stood the test of time. This implements the key functionality of s stream driver project (as OS subprojects with test apps) for Windows Embedded Compact and CE. Time for an major update:
Versions 3.0 and 3.5 were Standard Editions. When a driver project was generated, there were a lot of place holders as comments (what is needed to be done) in the code that implement things such as shared memory, registry access, counting driver instances, as well as driver context and open context buffers etc. This Professional Version fully implements all of those features.
Build Tour Los Angeles on June 15 at Universal Studios is part of the series of worldwide events to bring the Build experience to cities around the globe.
I was an early adopter of Win 10 IoT with Raspberry PI 2 (RPI2) as well as Windows Remote Arduino. Whilst I was able to use my Windows 8.1 phone to control an Arduino device as per the latter technology, I did have some problems with some fine detail with the RPI2 technology. I have now had a second stab at Win 10 IoT with RPI2 with success. This blog discusses these issues.
In this blog, the eBoot menu is modified to to allow user selection of Clearing of the Hive or not. This is implemeneted by adding a further parameter to the BOOT_CG and BSP_ARGS structures to handle the boolean selection. The eBoot code is then extended to pass the selection up to the OS args driver. The OS args driver then is modified to get the value when requested by getting it from the structure passed to it through shared memory. This replaces the use of the dummy variable s_bClearHive as used in args.c in the previous blog.
Broadcom is best known for its wireless and connectivity chips used by the likes of Apple and Samsung in their smart phones.
It also makes the ARM processor used in the highly popular Raspberry Pi platforms. As I mentioned in a previous blog posting, Microsoft is targeting this platform as one of the Windows 10 IoT core platforms. It will be interesting to see how things shakeout.
The previous blog in this series demonstrated how to add a custom OAL IOCTL to the BSP. In particular it implemented the IOCTL_HAL_GET_HIVE_CLEAN_FLAG IOCTL so that it returns a fixed value to the OS when called. In this blog, that code is extended to call the BSP boot args using a custom boot arg. A fixed value is returned by boot args in this case. A later blog will pass that arg from eboot.
OAL IOCTLs are callable from OAL code to perform specific functions within the OS Kernel. The OS requires the OEM to specifically implement certain IOTLCs that it calls, and some other standard IOTCLs if implemented are automatically called by the OS. One such optional IOCTL, IOCTL_HAL_GET_HIVE_CLEAN_FLAG, will cause the OS to clear the hive registry if it passes back a TRUE when called at OS startup. These IOCTLs are normally called in kernel mode as they are called directly by the the kernel. Some IOCTLs can be called by a user mode thread as well. In our book, Professional Windows Embedded Compact 7, I covered implementing a custom OAL IOCTL for the VCEPC BSP. This blog looks at adding an OAL IOCTL with the ARM TI AM335X BSP
Booting a Windows Embedded Compact image is a three step sequence.. A raw binary of binary file or a record based binary file is used for each phase of the OS boot. Includes use of CELoader to image a target.
Last month I developed a lot and I had the pleasure of being speaker to three national events and an international one in California (but from remote).I was greatly involved to write code and content that I decided to summarize hoping that you could enjoy them.
With the slides I tried to describe the most important features of the Azure Service Bus focusing on the Event Hubs and its use within the telemetry pattern in IoT :Event Hubs : million events per second to the Cloud (MEC Internet of Things Conference 2015 in Naples)Event Hubs : million events per second to the Cloud (Global Azure Bootcamp, OC community California) of which it is also available the video here on YouTubeMicrosoft e l’IoT (M2M Forum in Milan, session with Roberto Andreoli and Erica Barone from Microsoft Italia)Azure Service Bus : under the hood (IoT Day in Venice)These slides have related demos where I used my last Azure SB Lite library, thanks to which you can access to the Microsoft Azure Service Bus using the same API of the "o ...