DaveKR

Hi,

I´m a german teacher preparing myself right now for working with netduino plus 2 in class. (I already ordered 15 of them ;-)
I figured out that the device will become unusable in class(no ping response, no connection in MFDeploy, reflash of Firmware is the only solution) when using the following lines of Code:

private static OutputPort StatusLED = new OutputPort(Cpu.Pin.GPIO_Pin11, false);
private static OutputPort AccessGrantedLED = new OutputPort(Cpu.Pin.GPIO_Pin12, false);
private static OutputPort AccessProhibitedLED = new OutputPort(Cpu.Pin.GPIO_Pin13, false);

The deployment process in VS will take very long and will fail. If I press the reset button on netduino my mashine goes completely down (bluescreen). I have to boot in DFU mode and erase/reflash the latest Firmware to get it to work again.
If I Change the code like this:

private static OutputPort StatusLED = new OutputPort(Pins.GPIO_PIN_D11, false);
private static OutputPort AccessGrantedLED = new OutputPort(Pins.GPIO_PIN_D12, false);
private static OutputPort AccessProhibitedLED = new OutputPort(Pins.GPIO_PIN_D13, false);

everything works as expected.

The problem here is somewhat IntelliSense related. When students start to work with netduino and use IntelliSense with OutputPort(..., they will get the suggestion to use the Cpu.Pin enumeration :-(

Are you guys at secret labs are aware of this problem ?

My Environment:
- Windows 8 Prof., 64 bit
- VS 2010
- Micro Framework 4.2
- SL SDK 4.2
- Netduino FW is Netduino Plus 2 (v4.2.1.2) by Secret Labs LLC

P.S: When you try different CPU.Pin enumeration members you will not always crash the device completely, sometimes all you get is an unhandled exception in SPOT.Hardware.

Greetings from Germany,

David