Netduino Firmware v4.2.0

Hi Stefan.

I know the procedure but, this is not the problem, my program is configured in .NET MF 4.2, this is what is confusing me.

I have found that changing the target to 4.1 (or below) saving and closing the properties, then changing the target back to 4.2 has fixed that issue for me in the past.
I suspect that it forces a regeneration of the relevant sections in the *.csproj file so that correct references are loaded etc.

You can determine if the issue is with your project file by creating a new project targeting 4.2 and deploying blinky or something equally trivial, if it works then its your project file is at fault and the procedure above should fix it, if not then it would probably be the SDK's, so a full uninstall and reinstall should tidy everything up.

Nak.

No way. I have done everything that nakchack told, but nothing. A detail that I see after upgrading the Netduino is that when I power up, the blue Led lights on only a very short time(much more shorter than when it use to have 4.2.0.RC3). And then, when I deploy my program to it, the blue led doesn´t light on at any time........... Could be a clue of what is happening?????

No way. I have done everything that nakchack told, but nothing. A detail that I see after upgrading the Netduino is that when I power up, the blue Led lights on only a very short time(much more shorter than when it use to have 4.2.0.RC3). And then, when I deploy my program to it, the blue led doesn´t light on at any time...........

Could be a clue of what is happening?????

Hi Gomore

So no dice when trying to deploy a new project?

Have you tried reflashing the firmware?
Also could you post a screen shot of your installed Netmf SDK and Netduino SDK in Control Panel -> Programs and Features ?

Nak.

Yes nakchack, i tried it several times but nothing, here goes a screen shot:

Hi gomore11, Thank you for the screenshot. We're gathering bits of information here to help figure out the details of the situation. To confirm, you have done the following correct? 1. Updated your Netduino to 4.2.0.1 2. Updated the Netduino SDK to 4.2.0.1 (August 2012 refresh) On the deployment issue (waiting for reboot): if you detach and reattach the MicroUSB cable from your board, can Visual Studio then connect successfully? If all else fails, let's try forcing Windows to use the traditional MFUSB drivers instead of the newer WinUSB drivers. http://forums.netdui...-mfusb-drivers/ Chris

Hi Chris. I updated Netduino and the SDK with the links you put in the first post of this Topic. Now it deploys correctly(it seems to find the Netduino well), but now the problem is that is telling me that there were deployment errors: " Error: a3000000 Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)" And more like this, but the problem is that in my proyect properties I have well configured as a 4.2 .Net Micro Framework proyect. After this, I De-attach and re-attach the Netduino and the blue led lights on and stays on.........so something goes wrong.....

Hmmmm, any chance you can could post the csproj file for this project, it sounds like the references are going haywire somehow... Also does deploying a simple app like blinky now work from a fresh project? Nak.

When I start Visual Studio and I want to open a NEW proyect(in the startup options) It only gives me as latest option .NET Framework 4. Is this ok??

I tried this simple code but gives me exactly the same errors as the previous trys:

using System;
using System.Threading;
using Microsoft.SPOT;
using Microsoft.SPOT.Hardware;
using SecretLabs.NETMF.Hardware;
using SecretLabs.NETMF.Hardware.Netduino;

namespace Prueba_txorra
{
    public class Program
    {
        public static void Main()
        {
            OutputPort LED = new OutputPort(SecretLabs.NETMF.Hardware.Netduino.Pins.ONBOARD_LED, false);

            while (true)
            {
                LED.Write(true);
                Thread.Sleep(2000);
                LED.Write(true);
                Thread.Sleep(2000);
            }


        }

    }
}

And the errors:

Link failure: some assembly references cannot be resolved!!


Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)

Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)

Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)

Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)

Error: a3000000

Waiting for debug commands...

The program '[0x2] Micro Framework application: Managed' has exited with code 0 (0x0).

Any suggestion???

Hi gomore11, This may seem like an odd question...but do you current have any beta SDKs for non-Netduino NETMF boards installed on your machine? Also, could you please open up the .csproj file for your project in notepad...and copy and paste the full " <TargetFrameworkVersion>" tag here so we can see what Visual Studio is seeing? We may be able to help provide a workaround here while we dig deeper. Chris

One more thing... If all else fails, please try removing the SecretLabs.### assemblies from your project references and re-adding them from the following location: C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2 Chris

Hi Chris! Finally I´ve got a Netduino working. What I´ve done is: - First, to come back to .NET Micro Frameworc 4.2.0.0 RC3 in Netduino´s firmware. - Second, change assemblies to 4.2 ones, as you suggested me in the previous post. Later I will try to update Netduino´s firmawre to 4.2 RTM and see what happens, and if it is an assemblie problem. If this is the problem, why does the Visual Studio take the incorrect assemblies if I define correctly the project like a 4.2 one???? Thank you so much!!!!

Hello. I´m trying to update the Netduino´s firmware again to the last version(the one of the first post of this topic). With Samba everything goes wright, but when I deatach and reatach the Netduino and I run the MFDeploy tool, the system doesn´t find the Netduino in the USB port.But the problem is that if I find it with the Device Manager of the PC, it apears like Netduino, as it has to be.... witch could be the problem???? I have installed the last sdk of Netduino and .NET Micro Framework 4.2(RTM) .

Hello gomore11,

I´m trying to update the Netduino´s firmware again to the last version(the one of the first post of this topic). With Samba everything goes wright, but when I deatach and reatach the Netduino and I run the MFDeploy tool, the system doesn´t find the Netduino in the USB port.But the problem is that if I find it with the Device Manager of the PC, it apears like Netduino, as it has to be.... witch could be the problem???? I have installed the last sdk of Netduino and .NET Micro Framework 4.2(RTM) .

Be sure to install the 4.2 QFE2 version of the .NET Micro Framework SDK (linked on the downloads page) and not the RTM version. Then install the latest Netduino 4.2 SDK.

The MFDeploy support for the new WinUSB drivers is brand new in QFE2, so the older versions won't be able to detect your Netduino.

Chris