Can no longer deploy
#1
Posted 10 August 2010 - 11:08 PM
#2
Posted 11 August 2010 - 02:22 AM
Anything I can do or am I the proud new owner of a brick?
If Visual Studio gets stuck while deploying, press the reset button on your Netduino.
If that doesn't work, then your current Netduino app may have "locked out" Visual Studio's debugger. We have you covered You just need to erase your Netduino app manually. Here goes...
Step 1:
* Start up the MFDeploy tools (Start button > Programs > Microsoft .NET Micro Framework 4.1 > Tools > MFDeploy.exe
* Select "USB" as the transport in MFDeploy. And then select your Netduino if it's not already selected
Step 2:
* Disconnect your Netduino from its USB connection (and external power if any is provided).
* Hold down the button on your Netduino while plugging it into your PC; this will put it into "pre-boot".
* When your Netduino reappears in the MFDeploy device dropdown, press the PING button. Your Netduino should respond with "TinyBooter".
Step 3:
* Within 20 seconds, press the ERASE button; this will clear the current Netduino app off your Netduino.
* Disconnect and reconnect your Netduino to get out of pre-boot mode. You should be good to go!
If this doesn't work for you, PM me and I'd be happy to get you up and running offline.
Chris
#3
Posted 11 August 2010 - 03:02 AM
#4
Posted 11 August 2010 - 03:12 AM
Brilliant! It looks like you've got a well-thought-out infrastructure.
Any ideas on how to not lock out the debugger in the future?
You shouldn't get "locked out" of the debugger easily, so I'm not quite sure. If you can reproduce it, we can try to hunt down why it happened and fix it in future releases
Chris
#5
Posted 11 August 2010 - 03:22 AM
You shouldn't get "locked out" of the debugger easily, so I'm not quite sure. If you can reproduce it, we can try to hunt down why it happened and fix it in future releases
Chris
Easy to reproduce unfortunately...just bricked it again.
The attached program works fine with "#if false" but bricks the board with "#if true" near the bottom. Looks like it might be PWM or analog reads giving it headaches.
Attached Files
#6
Posted 11 August 2010 - 04:57 AM
Easy to reproduce unfortunately...just bricked it again.
The attached program works fine with "#if false" but bricks the board with "#if true" near the bottom. Looks like it might be PWM or analog reads giving it headaches.
Hmm, it appears that having one AnalogInput in use is not a problem...but having the second one open at the same time doesn't work (probably causing a safety assertion). That's our bad. We'll put this back to engineering and get an update for you that will let you use multiple ADC channels at the same time. It may take a few days (but it's good timing as we were wanting a few small changes in the ADC code anyway).
In the meantime, can you try using just one of the AnalogInputs at a time and see if that works?
Chris
#7
Posted 11 August 2010 - 04:00 PM
Hmm, it appears that having one AnalogInput in use is not a problem...but having the second one open at the same time doesn't work (probably causing a safety assertion). That's our bad. We'll put this back to engineering and get an update for you that will let you use multiple ADC channels at the same time. It may take a few days (but it's good timing as we were wanting a few small changes in the ADC code anyway).
In the meantime, can you try using just one of the AnalogInputs at a time and see if that works?
Chris
Using a single AnalogInput seems to work! Looking forward to using all 5 of my analog inputs real soon
What's the best way to follow the announcement of new firmware? Can this forum be set up for RSS feeds?
Thanks.
#8
Posted 11 August 2010 - 04:42 PM
What's the best way to follow the announcement of new firmware? Can this forum be set up for RSS feeds?
We'll post the new firmware as a sticky post in this forum.
I know that IP.Board is supposed to do RSS feeds (it's in our control panel), but I'm not sure how to download them. Hmm, something to research...
In the meantime, check back in the forum or just bookmark the "view new content" page (link at top-right under search box) and visit regularly
We should have the AnalogInput firmware update posted by Monday at the latest, since there's an AnalogInput tutorial scheduled for Monday. With a little luck, sooner.
Chris
#9
Posted 16 August 2010 - 07:41 AM
#10
Posted 25 September 2010 - 08:28 PM
Although this thread is long and mentions bugs that had since been fixed, I wonder if we should pin this thread because it contains the solution to a very common (1, 2, 3) and perplexing problem: VS Deploy stuck at "Preparing to deploy assemblies to device".
I thought I killed my Netduino because even MFDeploy was freezing on me. Even a reboot (the magic fix to everything ) doesn't fix it.
The steps you outlined on second post of this thread is what finally fixed it. I was able to erase my app (not firmware) that was on the Netduino, and now I can deploy again. Phew...
Or maybe you can start an FAQ section. After a question is asked more than three times, you would move/copy the post there.
#11
Posted 26 September 2010 - 01:30 AM
#12
Posted 26 September 2010 - 03:45 AM
Hari, that's a really good idea. We should make a "troubleshooting" guide which is a few pages long--and put it on the downloads page under documentation. That way everyone will see it...
Does that sound like a good way to handle it?
Chris
I agree, download page is more visible than forum. Good thinking!
#13
Posted 26 September 2010 - 10:49 PM
I agree, download page is more visible than forum. Good thinking!
Add this to the download page! Item number 4 in the upper left.
#14
Posted 30 September 2010 - 09:05 PM
Chris,Add this to the download page! Item number 4 in the upper left.
Good to know how to erase, but if you were lazy like I am, mine got stuck nemerous times, simply unplug the USB cable while it is stuck and replug back in, wait for all driver loaded up then try again, that will alway work for me too.
This is not just NetDuino issue but FEZ also has this dissease, I guess microsoft vs and hardwares team are still having some small problem understanding each other...
Thanks!
#15
Posted 26 October 2011 - 09:43 PM
#16
Posted 23 January 2013 - 03:24 AM
I am having this issue but when i plug the device in to windows holding down the button i get a different device that is loaded in to windows it is called "STM 32 Bootloader"
Please let me know what i must do to fix my device.
Thank you
#17
Posted 23 January 2013 - 12:27 PM
I am having this issue but when i plug the device in to windows holding down the button i get a different device that is loaded in to windows it is called "STM 32 Bootloader"Please let me know what i must do to fix my device.
Thank you
This is exactly what you should see if you are holding down the button when you plug the device into the USB cable.
Can you be a little more clear as to what your problem is and what you are trying to achieve?
#18
Posted 12 June 2014 - 10:22 PM
Hi,
My Netduino One is frozen following a program upload that appears to never complete. The reset procedure with the 3.3V does not seem to work. MSDeploy when USB is selected does not show Netduino.
What are my options now?
Thanks!
#19
Posted 15 June 2014 - 02:21 AM
shimoda -- on your gen1 Netduino, try pressing and holding the pushbutton while powering it up. Does it show up in MFDeploy (in TinyBooter mode, so you can erase your current app)? If not then let's try erasing the board (using the 3.3V to ERASE pad process) and reflash the board using Atmel SAM-BA.
Chris
#20
Posted 16 June 2014 - 03:54 AM
Hi Chris,
I was documenting my situation here with pictures and snap shops until I get to picture the error with sam-ba... but it worked instead. Unfortunately I do not know why Sam-ba was not working before. Anyway, going through sam-ba allowed Windows to recognize a new component. I was able to update Netduino driver. I delete the other Netduino component that was not working (see situation below). From there MFDeploy recognized Netduino on as a USB component and I was able to follow the upgrade procedure successfully.
Thanks for you time Chris!
Below the description of my previous state... if it can help other.
************************************************************************************************
I have uploaded pictures of my situation to better explain what is going on.
https://plus.google....337114075498465
- When connecting Netduino using the USB cable it is recognized by Windows as a Camera on COM4. See picture
- But the Netduino driver seems in error. Windows cannot update the driver. See picture.
- When I pluged Netduino to the PC (after having it unpowered) holding and keeping pressed the reset button. MFDeploy does not see Netduino.
- MFDeploy sees COM4 as a serial component not USB. See picture.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users