The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
Getting back into this after being away from it for a while. Have a Plus2 on order, but in the meantime, want to get the Plus going. Had some issues, decided to flash the firmware and reset everything. Got that going (I think) and now can connect to the device (via the MFDeploy tool). But, can't seem to load any assemblies to the device from VS 2013. This was working yesterday but today, after all the resets and flash, can't seem to make it happen.
when I power up the Plus, I can connect and ping comes back with "Pinging... TinyCLR"
I can get device capabilities
HalSystemInfo.halVersion: 4.2.0.0
...
ClrInfo.clrVersion: 4.2.0.0
...
SoftwareVersion.BuildDate: Sep 19 2012
What am I missing in order to get the assemblies to load in VS? Thanks.
Sorry, should have mentioned that yesterday. Target framework is 4.2 Strange thing, just tried it again, and the simple little LED flasher program works. When I try and load the little web server program I have, using the network interface, it can't seem to deploy the program. I get the following messages in the output window.
Looking for a device on transport 'USB'
Starting device deployment
Iteration 0
...
Iteration 59
So it looks like it try's it 60 times then gives up. I don't see any of this when I try the LED flasher program.
It must be a setting in the project file, new programs I create seem to work fine. When I try and compile/run old programs, I can't seem to deploy them. Will try this with the web server one and see what happens.
Does not appear to be that simple. I don't have a clue why some assemblies won't load. Created a new project, just added two lines to flash the LEDs, and it won't load. Very strange, some projects work sometimes, others not at all.
Try pinging the device from MFDeploy. If that doesn't work, then the app on the board has locked out the debugger somehow. If we can figure out which piece of code is doing that then we can resolve the issue.
Can you post your project which flashes the LEDs--but won't load onto an erased board? We can open it up here, try to deploy it, etc.
Here is a new project, just touching the LED, that will not load. Other projects will load. I just can't seem to find out why some and not others. Can ping from MFDeploy just fine, get device capabilities, etc.
The one thing that changed, after I reloaded the firmware, I set the device name and the MAC address. Previously, I had not done this. The device name changed was automatically updated in Visual Studio. Did not think this could cause a problem, but is really the only thing I've done since flashing the firmware.
Really appreciate the help. Expecting a Plus2 shortly, but would like to get this one working so I can use it.
When you set the device name and mac address, did you do that in TinyBooter mode or TinyCLR mode? With the latest version of the 4.2 firmware, you need to switch to TinyBooter mode before changing these settings (or NETMF can get confused and get you stuck in a permanent TinyBooter state).
Was not able to change anything in TinyCLR, had to go to TinyBooter to make any changes. It was during this that I think I screwed everything up and had to reflash the firmware. It is now booting in TinyCLR mode, at least that is what it says when I use MFDeploy and ping it.
Right now, I can use MFDeploy and ping it, get device capabilities, etc.
Problem is that with some, not all, projects, I can't load the assembly.
Do you know what VS is trying to do when you see the Iteration messages? When it works, this happens really fast and then you can see the pieces loading on the Netduino.
I've seen this before (just this morning in fact) and I usually just pull down the build menu and stop the "build", unplug the USB cable, plug it back in, and try again. If that doesn't work then I bring up the project properties and reset the .NET Micro Framework Device, that usually solves the problem.
Thanks. Tried again this morning, and voila, it is working. I think its something in the project properties as you suggested. I did reset the device, start VS, made a change there, and it just started downloading the code. Hoping that once it works, it will keep working but have been able to get the code moving again which is key. "Feels" like an issue with VS, but only have the sense its related to the project properties.
