Whilst the Raspberry Pi 2 has extensibility through GPIO, I2C, SPI and Single wire, the main interface for adding off-the-shelf peripherals is via USB. Unlike the desktop, there is though only a limited set of USB peripherals that can be used on the RPI2 running Windows 10 IoT in the first release. This series of articles looks at what is available and what the overarching issues are. The first Article is “Connected Devices”
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.
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.
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.
A solution is now at hand with respect to interrupts being lost when they are close to a system timer tick interrupt, with TI AM335X CPU. THE LATEST UPDATE NOW HAS THIS SOLUTION.
A new Compact 2013 release is available on MSDN that will bring your build environment up to date as per February 2015.
A new release of Windows Embedded Compact 7 is available on MSDN which is a rollup of all previous updates packaged as a new installation.
Solution: Clean out the build and do a rebuild.
Something in the OS configuration,I don't know what, has got corrupted. Works every time for me!
Another: When building get an error that says not much more than “In” .
Solution: You’re building whilst the OS is running. Shut it down first.
Smartdevice projects opened in a Compact 2013 development context are not automatically upgraded to Compact Framework 3.9. This article discusses techniques for upgrading of Smartdevice (Compact 7) projects to the Compact 2013 context (Compact Framework 3.9). This includes comparison of project files as well as use of the CEESharpWiz wizard.