Paolo's blog entries

Channel9 : NFC library for all Windows Embedded platforms on Coding4Fun


This time Creg Duncan had to give more than usual explanations to justify the very first constant presence on the Coding4Fun blog!

“Today's Hardware Friday post is another project from our Friend of the Blog, Paolo Patierno (yeah, yeah, I know, it seems like I'm posting his stuff all the time, but hey, it's cool stuff) !”

I'm glad that my "small" open source projects had quite successful and this is the time of uNFC library that implements support for the NXP PN532 NFC chip for all Windows Embedded platforms (from. NET Micro Framework to Windows Embedded 8 passing Windows Embedded Compact).

About this library ... tomorrow it will be featured at the Microsoft Embedded Conference in Naples in a demo on Smart Home & Smart Factory System!

As always .... it is a pleasure to be there!

A bocca aperta

Microsoft Embedded Conference and Netduino Home Automation with Packt Publishing

This year at the second edition of Microsoft Embedded Conference in Naples (on 15 February), the Netduino board will be present in a demo on Smart Home and Smart Factory systems based on MQTT protocol as an example of Internet of Things project. The same board is also protagonist of the book “Netduino Home Automation Projects” written by Matt Cavanagh and published by Packt Publishing. This editor will be “Contributor” sponsor and it gave us two printed copies of the book for two lucky attendees !

I hope that you will be there !!!



.Net Micro Framework 4.3 QFE1 is finally here !!

After waiting for months to watch this post on the blog of .Net Micro Framework team …. finally 4.3 QFE1 version is officially released ! It's been over a year since the last release of the 4.3 RTM version, but I hope that with the advent of the Internet of Things, Microsoft will support better this product that has huge growth potential. Compared to RTM, these are the bug fixes: Work Item: 1874 - Interop compilation fail for project name with dot ('.') Work Item: 509 - Add BitConverter Work Item: 1951 - StringBuilder.Replace Exception Work Item: 2012 - StringBuilder.Replace previous bug resurfaced again Work Item: 1784 - Array.BinarySearch() not accepting null comparer Work Item: 1855 - SDK Installer for 4.3 shows incorrect error message Work Item: 1400 - URI parsing fails when :XX sequence appears and no explicit port is used Work Item: 1738 - var uri = new Uri( ...

Read the rest of entry »

VS2012 and Platform Builder : “fatal error ! Microsoft.NET Framework v4.x must be installed on your machine”

Today, preparing a Windows Embedded Compact 2013 image for an eBox 3310A and for the demo at Microsoft Embedded Conference in February 2014, the Windows 7 operating system (a virtual machine) decides to upgrade the version of .Net Framework from 4.5 to 4.5.1. Reboot the system and resume the job ... but the build system for Visual Studio 2012 has gone mad and the next attempt to build fails! A warning indicates that the .Net Framework 4.5 is not installed on the system and an obvious fatal error indicates that the compilation can not be done! I have found no official news from Microsoft to fix this problem but I have circumvented the problem in the following way .... First I open the file indicated by the fatal error, ie sources.ce in the path C: \ WINCE800 \ public \ common \ oak \ misc, which reports the error in case the environment variable _DOTNET40ROOT  is empty. !IF "$(_DOTNET40ROOT)" == "" !   ERROR Error: Microsoft.NET Framework v4.x must be installed on your machine. ...

Read the rest of entry »

.Net Micro Framework 4.3 QFE1 : news on the future release

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!

A bocca aperta

Channel9 : SPI bus and .Net Micro Framework on Coding4Fun


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 !

A bocca aperta

uNFC library : NFC with the Windows Embedded platforms

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 »

.Net Micro Framework : let’s use I2C bus !

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 ...

Read the rest of entry »

Channel9: the experimental SDKs for .NET Micro Framework, Netduino and AGENT smartwatch for Visual Studio 2013


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!

A bocca aperta

.Net Micro Framework : SPI, the high speed serial bus !

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 ...

Read the rest of entry »

Paolo Patierno's blog

View this page in another language:

Search blog


Turkish porno izle video site in rokettubeporno izle