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 »
With no version of SQL Server and SQL Compact available for Windows 10 IoT and Windows 10 Phone, the suggested alternative is SQLite. Whilst early evaluations indicate it isn’t available for Win10 IoT Background and Console apps, it’s not too hard to use SQLite with a Windows 10 UWP (Universal) app. The app can be rebuilt without modification and using the exact same project content for the desktop, phone and IoT Windows 10 targets.
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.
A detailed description of the CEJSON JSON Parser.
On March 2 the pending merger of NXP Semiconductors N.V. and Freescale Semiconductor, Ltd was announced.
When an HTML POST/GET/PATCH/DELETE message is posted to an Azure Mobile Service Table, the message can be intercepted and modified. Also the response can also be intercepted and modified. This blog outlines how to do this.
C:\GIT\CEJSON\JSONParser.Desktop\Debug>JSONParser DELETE 24
Delete and Update are now available for CEJSON. This means that the 4 CRUD primitives are now available.
In the previous blog in this series, using Flash for non-volatile program data was covered. One aspect of this was the F( ) macro that enables Serial.print/println strings to be accessed from Flash where the program is stored. That is, they do not consume RAM space allowing for more volatile programming space. This blog compares using and not using the F( ) macro. In the Telemetry sketch this allows for nearly double the number of name-value pairs
This blog covers the Stream Parser - State Machine code in detail...