"Congratulations! Great to see this cooperation across different NETMF manufacturers, and your leadership. I’m particularly grateful since you’ve paved the way for a halving of the cost of Gadgeteer mainboards!"James Scott, Microsoft Research, Cambridge
Project DescriptionThis repository contains the
sources of
NETMF for STM32 (F4 Edition) as a
delta to the .NET Micro Framework Porting Kit 4.2.
This repository also contains some corrections to
NETMF for STM32 (F1 Edition), as a
delta to the .NET Micro Framework Porting Kit 4.2.
BranchesThe project is currently set up with three Mercurial branches: the
default branch into which members of the Mountaineer group commit their updates, the
MFUpdate branch where project member
markmun has added his example solution for the MFUpdate/Microbooter feature, and the
Bugfixes branch where project members can suggest bug fixes. These are considered provisional, and will later be reviewed and merged into the default branch, probably together with the NETMF 4.3 changes.
CompilersThe software can be compiled with the
Keil MDK-Standard tools. Alternatively, you could use the
ARM RVDS Professional tools. There is no support for other compilers.
Binary Images for ST Evaluation BoardsFor your convenience we also provide a number of
binary images of specific solutions (i.e., for specific devices). They have been last updated on
August 16, 2012, for the NETMF update to
QFE2:
stm32f4discovery.zip contains a solution for the
STM32F4Discovery board of STMicroelectronics.
stm3220geval.zip contains a solution for the
STM3220G-EVAL board of STMicroelectronics.
stm3240geval.zip contains a solution for the
STM3240G-EVAL board of STMicroelectronics.
To flash a board, you can use the
ST-LINK utility.
For the Mountaineer firmware binaries, see our
Mountaineer Web site.
USB Drivers for Windows PCsSTM32_WinUSB_drivers_(for_evaluation_purposes_only).zip contains USB drivers that can be used with any of the above boards. They may only be used for evaluation purposes.
If you use an
x64 system: plug in the device, then a dialog box appears saying that no driver could be found. Now you can browse for the driver manually.