So I got my hands on the Mountaineer Ethernet Mainboard. I’m using it as an early prototype board for a project at my school regarding home automation.
Because it’s a school project I want to keep it as much “plain vanilla NETMF” as possible. To initialize I/O ports I downloaded the Mountaineer.Netmf.Hardware namespace from http://www.mountaineer.org/resources/netmf-4-2-qfe2/ but this is obviously “socket-oriented”. In the documentation at the top it says:
“4) For “plain vanilla” NETMF programs, without Gadgeteer libraries
/// but with a microcontroller pin-oriented view on hardware features:
/// You want your application to directly depend on the
/// microcontroller’s pinout only, so that you can most easily
/// migrate to a custom board with the same microcontroller
/// later on.
/// Use the Mountaineer.Stm32.Hardware namespace.
/// With that approach, you don’t need this namespace here.”
The only problem is that I can’t find the Mountaineer.Stm32.Hardware namespace anywhere. Anyone have an idea/download link?
This is still the Mountaineer.Netmf.Hardware namespace which has a socket-oriented view on hardware features and not the Mountaineer.Stm32.Hardware namespace which has a pin-oriented hardware view… Later on I will produce my own PCB and this will not have the Gadgeteer sockets. This is why I don’t want to use the Mountaineer.Netmf.Hardware namespace with all the Socket-classes.
@ tr0lle - Why are you so fixed on Mountaineer.Stm32.Hardware?
You need to take a look at the Mountaineer.Netmf.Hardware I have mentioned earlier. You said it uses Socket, but it is not a Gadgeteer socket it just another “local” class to group the pins according to their layout on the board.
In the Mountaineer SDK 4.3 we have added the namespace to the Mountaineer assembly. So you can now choose between Gadgeteer socket-oriented pin names (Mountaineer.Netmf.Hardware) and CPU-oriented pin names (Mountaineer.Stm32.Hardware).