wooohaaa .... running ... don't ask me why ... probably when I power down the pc the next time it won't work .... this was an adventure ... I even managed to give the device a new usb name ... of course after that I had a breaking issue so I went back to the st-link utility and set the name bytes to hex 00 and the original usb name came up again. Back to VS, started deploying only to figure out you can not mixed netmf versions, so had to uninstall 4.3.1.0 and install 4.3.0.0 since the ST is on that and voila there we go it deployed and ran almost faster then I could blink but instead the LEDs did so we have a nice running a little blinky led and empty screen program on a not so stable disco board:

@piwi

 

Are you running the STM port?

 

Cheers,

-Matt

if you mean the one from the ST web site .... Yes !!! 

1:1 Unchanged and still on NetMF 4.3.0.0 ... 

@Juzzer, are you using the STM32F429I Discovery board as well ?

this is going not so well ...

using the st-link to open the hex files and program to flash ... 

1. Tinybooter.hex

2. er_flash.hex

3. er_congfig.hex

but stil no recognition and deploy in VS2012. 

doing only point 1 & 2 I get the following result in mfdeploy when doing device caps:

Pinging... HalSystemInfo.halVersion:               4.3.0.0
HalSystemInfo.halVendorInfo:            Copyright Oberon microsystems, Inc.
HalSystemInfo.oemCode:                  255
HalSystemInfo.modelCode:                0
HalSystemInfo.skuCode:                  65535
HalSystemInfo.moduleSerialNumber:       FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
HalSystemInfo.systemSerialNumber:       FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ClrInfo.clrVersion:                     4.3.0.0
ClrInfo.clrVendorInfo:                  Copyright Oberon microsystems, Inc.
ClrInfo.targetFrameworkVersion:         4.3.0.0
SolutionReleaseInfo.solutionVersion:    4.3.0.0
SolutionReleaseInfo.solutionVendorInfo: STMicroelectronics
SoftwareVersion.BuildDate:              Sep 25 2013
SoftwareVersion.CompilerVersion:        410713
FloatingPoint:                          True
SourceLevelDebugging:                   True
ThreadCreateEx:                         True
LCD.Width:                              240
LCD.Height:                             320
LCD.BitsPerPixel:                       16
AppDomains:                             True
ExceptionFilters:                       True
IncrementalDeployment:                  True
SoftReboot:                             True
Profiling:                              False
ProfilingAllocations:                   False
ProfilingCalls:                         False
IsUnknown:                              False

this behavior is the same when I turn off/disconnect the device from USB and reconnect. It is recognized by USB but won't do any in neither mfdeploy nor vs. 

thx 2 juzzer's tip got to switch off the digital signing ... the driver installed now and even recognized the device ...

but blooming vs2012 does not see it for deploying ... no usb recognized device as .netmf deployable devices at all ...

any ideas left ??? 

well thinking about it ... I'd might check if mfdeploy has somthing to say ... maybe just the bootloader is on not the rest ... give me a minute ... or so ...

I have one laying around ... see how it works with .net ... should be not that difficult ... I'll share my experiences here as well ...

well so far so good ....

there is another way of doing this, with a marklin modell train. You can use one of the .net microfamework harware boards to use the CAN bus signal, followed by some minor electronics for buffering (isolator and optocoupler). Have to dig up the schematics, pretty simple stuff. I did it on a breadboard. Then connect it to the second train controller box coming pretty much with every digital started pack and can be bought seperately as well.

Use some software in .net to write the CAN bus messages. And off you go, I succeeded in doing this even with an LCD touch connected to the NetMF HW and control the trains speed, extras, the train's track switches, pretty much anything connected and using the rails as means of communication. The CAN protocoll from Marklin can be found on the Marklin web site. 

One can even think of connecting a BLE or Wifi receiver unit to the .net board and be able to control your train from your mobile device. If you extend the controlling software with some nice UDP stuff UPNP is even in the game .... so your trainset will even be noticable on the network ....