We are pleased to present below all posts tagged with 'ARM'. If you still can't find what you are looking for, try using the search box.
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( ...
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 !
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 ...
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 ...
Having already written something similar on the official forum of the Netduino, Chris Walker (Secret Labs) has written a comment to a post on the official blog of the .Net Micro Framework team after meet them at MVP Summit of thi year.
He emphasizes that Microsoft seems to be getting more interested in pursuing .NET Micro Framework development (it is now part of the Windows Embedded team), whereas the processors for embedded systems are becoming increasingly powerful and less expensive (eg, the Cortex -Mx) and the C # and VB.Net with Microsoft development tools can start to make difference, especially by leveraging all the developers who have knowledge of. Net Framework.
In short, it seems that 2014 will be a fantastic year for the framework and for the community !
After hearing about it for months, finally Windows Embedded Compact 2013 has arrived! The successor to Windows Embedded Compact 7 promises a number of improvements that I report below: General improvements related to the core; Improved performance of the file system (which in my opinion was one of the weaknesses of previous versions); Otimization of the boot which has a duration of a few seconds, possibly with a UI and a number of drivers that are already active; Built-in support for Wi-Fi, cellular and Bluetooth; Obviously, the operating system supports x86 and ARM architectures and the development environment is fully integrated with Visual Studio 2012, and is guaranteed to coexist side-by-side as an environment previously installed Visual Studio 2008 (WCE7) or Visual Studio 2005 (WCE6). In order to begin to enjoy the new features, you can download it at the following link and can be very useful to follow the two webinars by Douglas Boling on 18 and 25 June: Windows Embedded Comp ...
Interestingarticle, “.NET Development for ARM processors”, by Andrew Pardoe (ProgramManager on the CLR team)…