17 replies to this topic

[backsix]

Hi There, have a new netduino plus trying to get vb working by applying 4.2.0 rc3 no previous versions installed. SAM-BA works fine after MFdeploy the device becomes unresponsive. 'Response: Pinging... Error: No response from device' Have tried on 3 seperate xp systems of different hardware with identical failure. I've found at several users with the same problem & no solution Alladdin http://forums.netdui...dpost__p__19529 Daxi http://forums.netdui...dpost__p__19793 emg http://forums.netdui...dpost__p__21100 couchounou http://forums.netdui...dpost__p__21062 leo http://forums.netdui...dpost__p__22119 What's the status of this issue?

[Chris Walker]

Hi backsix, There are some known issues with the beta .NET MF 4.2 firmware and driver. The first thing to try is to update to the 4.2 beta drivers. If that doesn't work, please stay with the production firmware for now, and vote for the bug report on codeplex. We hope to get the issue sorted out soon. Chris

[emg]

backsix,
Upvote the issue at Codeplex created by Leo:

Device becomes inaccessible after deploying 4.2.0RC3 Firmware

Chris,
I am a bit sketchy on how things work WRT the forums here and the Netduino Codeplex. Should I have reported my issue back in November to Codeplex instead of here in the forums?

Mike

[Chris Walker]

Hi Mike, All bug reports should go to the codeplex site, although we do appreciate it when community member bring up any issues they are experiencing in the forums (in this case, in the beta forum). Please note that there are two codeplex repositories to place bug reports: 1. netmf.codeplex.com <-- for bugs in the core .NET Micro Framework 2. netduino.codeplex.com <-- for bugs that only exist in the Netduino firmware Most bug reports should be filed at netmf.codeplex.com, so that they can be fixed in conjunction with the rest of the core tech team and can be fixed in the NETMF core. This is one of those cases. Is there any chance I can get you to file the bug report over at netmf.codeplex.com (and then all affected parties can vote for it)? Chris

[emg]

Thanks Chris,
I did not realize that there were 2 Codeplex sites. Just to be sure I don't mis-report something, the original problem I reported here:

Post 1

Post 2

This problem is not Netduino specific and should be reported to the NETMF team? (This was the issue where you were looking for example boards that could not be flashed for testing at SL). If so, does this point to the issue being related to the USB/COM drivers?

I can file a report at netmf if it would help!

[Chris Walker]

Correct, this problem exists in the core .NET MF implementation. If you downloaded the .NET MF PK, built the SAM7X_EK solution, and deployed it to your Netduino...you'd experience the exact same issue. There was actually a similar issue with 4.1, and we created a patch which worked around it. With 4.2, we tried that patch--but it no longer works. By filing a bug report (or voting for one) on netmf.codeplex.com, it'll help everyone get the same info regarding the core issues and ways to fix the glitch. Chris

[backsix]

backsix,
Upvote the issue at Codeplex created by Leo:

Device becomes inaccessible after deploying 4.2.0RC3 Firmware

Chris,
I am a bit sketchy on how things work WRT the forums here and the Netduino Codeplex. Should I have reported my issue back in November to Codeplex instead of here in the forums?

Mike

upvoted at codeplex.
thanks for the response.

[backsix]

Hi backsix,

There are some known issues with the beta .NET MF 4.2 firmware and driver.

The first thing to try is to update to the 4.2 beta drivers. If that doesn't work, please stay with the production firmware for now, and vote for the bug report on codeplex.

We hope to get the issue sorted out soon.

Chris

Hi Chris,

Are the 4.2 beta drivers valid for xp?
from the posting it appeared to me to be only relevant to windows 7?
When I try the procedure to update them on xp, they are rejected as not matching the hardware?

[emg]

Are the 4.2 beta drivers valid for xp?
from the posting it appeared to me to be only relevant to windows 7?
When I try the procedure to update them on xp, they are rejected as not matching the hardware?

Same here. I used the driver from the SDK v6.1.7600.16385, I assume that's the latest?

[emg]

Chris, backsix, et al:

I have submitted this issue to the NETMF Codeplex site:

Flashing tinyclr 4.2RTM to Netduino fails

Let me know if you have any further info to add or correct and please upvote to see if we can get this resolved.

Thanks
Mike

[couchounou]

Chris, backsix, et al:

I have submitted this issue to the NETMF Codeplex site:

Flashing tinyclr 4.2RTM to Netduino fails

Let me know if you have any further info to add or correct and please upvote to see if we can get this resolved.

Thanks
Mike

[couchounou]

Upvoted

[backsix]

Have discovered a workaround: Tonight I installed everything on a 32-bit windows 7 machine. flashing and deploying the framework went well (I'm well practiced at this point) as did running my first vb blinky program on the netduino- It's alive! I used: 1) NetDuinoSDK4.2Beta 2) Firmware_NetduinoPlus_4.2.0.0_RC3 I did NOT use the beta driver(think it's win 7 64 bit only) afterwards I plugged the confirmed working netduino back into a xp box and it was still inaccessible.

[emg]

Have discovered a workaround:

Tonight I installed everything on a 32-bit windows 7 machine.

flashing and deploying the framework went well (I'm well practiced at this point) as did running my first vb blinky program on the netduino- It's alive!

I used:
1) NetDuinoSDK4.2Beta
2) Firmware_NetduinoPlus_4.2.0.0_RC3
I did NOT use the beta driver(think it's win 7 64 bit only)

afterwards I plugged the confirmed working netduino back into a xp box and it was still inaccessible.

Yep, after initially failing with XP, I tried with W7 64bit, to verify my board actually worked. I was even able to deploy vb blinky from XP, once. Every subsequent attempt to access from XP fails until it is erased via gold pin. Not really a work around for me as I can't dedicate the W7 machine to dev...

[couchounou]

Hello I've just done the test now and this is the same for me : Finaly work on a 64bit Windows 7 ... and still not on xp.

[lesmondo]

Hi Just to let you know, I've reverted back to RC1 since RC3 was giving me the No response error on XP - same issues as above. L

[emg]

Hi

Just to let you know, I've reverted back to RC1 since RC3 was giving me the No response error on XP - same issues as above.

L

If you have not done so already, could you take a moment and upvote the issue at these sites?

Device becomes inaccessible after deploying 4.2.0RC3 Firmware

Flashing tinyclr 4.2RTM to Netduino fails

Thanks

[lesmondo]

If you have not done so already, could you take a moment and upvote the issue at these sites?

Device becomes inaccessible after deploying 4.2.0RC3 Firmware

Flashing tinyclr 4.2RTM to Netduino fails

Thanks

Done.