7 replies to this topic

[eddiebrock]

Hi. I'm writing from Italy, I've used Netduino Plus ( from the beginning, but now I've got a problem with my N.Plus after the resetting procedure 3v3-golden pin. After joining these two pins, the three leds, white, blue and ACT led, are always on (no mistakes, no errors, no shorts circuits during joining). When I push the onboard button, the ACT led "follows" the clicks. My Pc (Win 7 64 bit, but I've tried on Win XP too) doesn't recognise the board when attached via USB (doesn't matter the specific USB port I've used). I've tried to use the last release of Sam-ba, and the other older versions too, but I can't proceed any more. I've captured and uploaded the window with the message that samba sends to me: I hope this could be useful for a solution. I've also tried to use drivers of other parts just like suggested in other topics, but the goal is always the same: three leds on forever and NP is not recognised at all, or is recognised like a GPS Camera o like a A91 etc. when I use the drivers inside the folder drv of sam-ba prg. What can I do ? Thanks for all. Cristiano

Attached Files

•  screen.JPG   38.06KB   32 downloads

[nakchak]

When you erase the nd+ you wipe the boot loader so when you reconnect it it will get detected as a gps camera when it is detected as such you should be able to connect to it with sam-ba. It will be detected as a serial port in samba then follow the instructions in the wiki for flashing the boot loader once the boot loader is flashed if you dis connect and reconnect your nd it should then be detected as a netduino It looks like you are choosing the wrong serial port to connect to when you try and connect with samba Nak.

[eddiebrock]

Thanks for your words. I solved the trick. After cleaning my desktop PC from every NP SDK and .NET uFramework, NP has been recognised again, even if just like a GPS Camera, at the beginning. A new flashing processing and an update to the last beta release of the Secret Labs firmware has been possible (bootloader included). Now, the board is fully operative once more. Thank you for saving again. Cristiano

[eddiebrock]

Just another problem. After updating to the last version of beta firmware, the board is fully functioning. Although I deployed some programs and everything was ok, when I unplug and re-plug the board, at the same usb port (but the behaviour is the same with other usb ports) netduino plus can't be reacheable any more. If I test it by MFDeploy I receive "...Error no response from device". I don't understand. This happens when I use my Desktop PC or my notebook. Naturally, netduino is healthy, in fact the last program I deployed is still running ok. Can you help me ? Thank you. Cristiano

[Chris Walker]

Hi Cristiano,

After updating to the last version of beta firmware, the board is fully functioning. Although I deployed some programs and everything was ok, when I unplug and re-plug the board, at the same usb port (but the behaviour is the same with other usb ports) netduino plus can't be reacheable any more. If I test it by MFDeploy I receive "...Error no response from device". I don't understand. This happens when I use my Desktop PC or my notebook. Naturally, netduino is healthy, in fact the last program I deployed is still running ok. Can you help me ? Thank you. Cristiano

Are you still "debugging" the app from Visual Studio? You can connect via MFDeploy or Visual Studio...but using both at the same time will make one of them unhappy.

Also, one more diagnostic: if you reboot your PC...can you see it again fine?

Chris

[eddiebrock]

This is exactly what happens. The board has been correctly update to the last version of firmware (4.2.0.0 RC5) with its Tinybootloader. A little program to test the board is loaded inside and it is running fine. The board is correctly listed as "Netduino" in my PC (W7 64 bit or XP-32) when it's plugged into a usb port. But, and this is the strange problem, the same with every PC I tried, Netduino Plus, after few minutes, doesn't communicate any more with MFDeploy or SAM-BA (I use 2.11 ver.), and obviously with Visual c# too. Every query from MFDeploy ends with the message: "Error, no response for device". Remember: only two or three queries you can send succesfully to the NP, then the communication stops... forever. If I un-plug and re-plug the board, nothing change; neither if I reboot the PC. Sometimes, after deleting the drivers and replaced them again, it starts to run fine one more time, but after few minutes.... I think (but this could be wrong) that the problem is due to the drivers. The drivers I use are 4.2.0.0 ver. from SDK but I also tried the 4.2 drivers you posted without success. Thank you for your patience, but I'm an Electronic Engineer and I'd like understand how can I solve this problem. Thanks again for helping me. Cristiano A note: when I run SA-MBA, after five or six seconds, appears the small window with: "COM1" and "no_board" at the bottom. If I choose the correct board model "at91sam9xe512-ek" an error of communications always appears in a popup window.

[Chris Walker]

Hi eddiebrock, A bit of clarification... SAM-BA and MFDeploy use different drivers and only work with Netduino when it is in a specific state. SAM-BA only works with Netduino when it has been erased (by jumping the 3V3 power header to the gold ERASE pad which is next to pin D0). When you erase your Netduino, it will appear as a serial port on your computer. MFDeploy and Visual Studio only work with your Netduino when it has been flashed with .NET Micro Framework (either the bootloader or the bootloader and runtime both). Chris

[eddiebrock]

Hi Chris. I re-flashed the board to the previous version of firmware 4.1.0.6 and now everything works fine. No stuck, no problems. I think that the problems are inside firmware 4.2.0.5 RC5 or inside the new drivers. So, I'll wait for a new stable version of package. Thanks a lot for your help. I stay tuned. Cristiano