We are pleased to present below all posts archived in 'January 2014'. If you still can't find what you are looking for, try using the search box.
I follow constantly the post on the official .Net Micro Framework blog to read the news about the release of version 4.3 QFE1 (currently on RTM).
A few days ago there was an update of Philip Lo (which is part of the team along with the author of the post ShiZhe Jiang), which speaks of a "legal team" that is blocking the release on CodePlex since December 2013 .... I wonder why !
Following what Philip Lo said ...
For the .NET MF 4.3 QFE 1 release, I'm wrestling with our legal team to get this update approved for publishing on Codeplex since early December. Seems legal is shuffling people around, and new faces with no history of past .NET MF releases is causing hiccups. Needless to say I'm trying other avenues to jog legal's memory of past releases to get this update approved.
Also this time we just have to wait, hoping that it won’t be a new update on the blog but the official release on CodePlex!
Quoting the words of Greg Duncan, I’m a "friend of the blog"!
The weekly Friday post on Coding4Fun blog on Channel9 refers to my article on the SPI bus and its use with the .NET Micro Framework (on Netduino board).
It 'a pleasure to be there !
After the previous two articles describing the SPI and I2C buses and their use with the .Net Micro Framework, it is now finally time to see a practical application with my latest project available on CodePlex : uNFC – NFC library for .Net platforms ! Introduction : software and hardware support This library allows to use NFC integrated circuit connected to your PC (via serial) or to embedded system based on Windows Embedded Compact or .Net Micro Framework. It supports all three types of .Net Framework : .Net Framework 4.0 for PC based on Windows 7 / 8 or embedded systems based on Windows Embedded Standard 7 and Windows Embedded 8 Standard; .Net Compact Framework 3.5 / 3.9 for embedded systems based on Windows Embedded Compact 7 and Windows Embedded Compact 2013; .Net Micro Framework 4.2 and 4.3 for embedded systems like Netduino boards and .Net Gadgeteed boards; The library supports NXP PN532 chip but it also defines a little framework so that y ...
Read the rest of entry »
At the same as SPI, analyzed in a previous article, the I2C (Inter-Integrated Circuit) is a synchronous communication bus used to connect and exchange data between a microprocessor and external devices; it was developed by Philips, now NXP, today it is "de facto" standard. Bus description The I2C bus is also known as two-wire as it is characterized in all the effects of only two "wires": SDA (Serial Data Line) : line for the data transfer; SCL (Serial CLock) : clock for data exchange; The lines abovelines are always characterized by a pull-up resistor that has the task of maintaining the signal "high" (logic 1) in conditions of idle while the interconnected components (master and slave) have the task of lowering the level to transfer a logic 0 and release it to bring it back to idle and transfer a logic 1, this behavior is typical of the open-drain lines. Similarly to SPI, you can have multiple slaves connected to the bus and a single master to communicate wit ...
Again, one of my posts on .NET Micro Framework is leading to Coding4Fun on Channel9 in the periodic Friday post on the projects based on the hardware.
This time it refers to experimental SDKs released by Secret Labs for support .Net Micro Framework, the Netduino board and the AGENT smartwatch in Visual Studio 2013.
As always it makes me happy!
The SPI (Serial Peripheral Interface) bus is a synchronous communication bus typically used to transfer data between a microcontroller and an external device (eg sensor, actuator, memory, SD card, ...). Being synchronous, unlike the typical asynchronous serial communication (UART), it uses a clock signal to ensure the perfect synchronism in the transmission and reception between the two counterparts known as master and slave. Bus description Overall, the SPI bus is characterized by the following signals : SCLK (Serial CLocK) : clock for synchronization in the data exchange; SS (Slave Select) : signal for enabling the slave (receiver); MOSI (MasterOut / SlaveIn) : data line used for the transmission from master to slave; MISO (MasterIn / SlaveOut) : data line used for the transmission from slave to master; Excluding the SS signal, which can be handled separately, the bus should be considered a 3-wires bus. The master is responsible f ...
View this page in another language: