Seems to be stuck in "tinybooter" mode

I just flashed an N+ to the rtm firmware (framework and SDK correctly updated). I have done this before, so I am somewhat familiar with the procedure. After I completed the flashing process, I rebooted the N+ into "tinybooter" mode to set the MAC address and IP. Now, I can't get it back into "tinyCLR" mode. cycling power does not seem to have any effect. Ideas?

I just flashed an N+ to the rtm firmware (framework and SDK correctly updated). I have done this before, so I am somewhat familiar with the procedure. After I completed the flashing process, I rebooted the N+ into "tinybooter" mode to set the MAC address and IP. Now, I can't get it back into "tinyCLR" mode. cycling power does not seem to have any effect. Ideas?

I had the same problem. After repeating the whole process of flashing it just worked.

I had the same problem. After repeating the whole process of flashing it just worked.

Yeah, I just reflashed and everything's OK. Interesting.

I have had this happen if I have tried to set nework settings in tinyclr mode, as stated reflashing seems to fix everything Nak.

I have had this happen if I have tried to set nework settings in tinyclr mode, as stated reflashing seems to fix everything



Nak.

Yes, that seems to be the issue. I did that the first time. I have now flashed two more N+'s and have no issues.

In theory, if you have trouble then just repower the Netduino by detaching and reattaching its USB cable. If there's a scenario where the 4.2 firmware is causing a Netduino to get into an invalid state, we would love a repro case. The new WinUSB drivers require changes to a few "old ways of doing things" but they shouldn't get Netduino into an invalid state. Thank you for posting about this. I'm glad it's working for you now. If you have any other troubles, please let us know! Chris

In theory, if you have trouble then just repower the Netduino by detaching and reattaching its USB cable.

If there's a scenario where the 4.2 firmware is causing a Netduino to get into an invalid state, we would love a repro case. The new WinUSB drivers require changes to a few "old ways of doing things" but they shouldn't get Netduino into an invalid state.

Thank you for posting about this. I'm glad it's working for you now. If you have any other troubles, please let us know!

Chris

Chris, as Nak said, what appears to happen is that if, after you have flashed to the new firmware, you attempt to edit the network settings while you are in "tinyCLR" mode (of course, you won't be successful), then you repower the N+ while holding down the button to get to "tinybooter"mode, It will now stay in that mode until you reflash the firmware. Cycling power has no effect. As long as you don't try to change those network settings while in the "tinyCLR" mode, everything works correctly.

I got ahead of myself the first time and forgot that I had to go through the "hold the button" step to reset the network stuff, or I wouldn't have seen the issue.

Bryan

Bump. This got me because I went to http://forums.netdui...-firmware-v420/ which refers to http://wiki.netduino...ep-by-step.ashx which then has a link to an old page http://wiki.netduino...ep-by-step.ashx That last old page advises updating network settings, but doesn't advise cycling the N+ with the button pressed first (causes the above trouble). Chris, would you update that page suitable for the new boot arrangements please? (might save some reflash toubles for folks. Thanks, cheers, W

Bump. This got me because I went to
http://forums.netdui...-firmware-v420/
which refers to
http://wiki.netduino...ep-by-step.ashx
which then has a link to an old page
http://wiki.netduino...ep-by-step.ashx

That last old page advises updating network settings, but doesn't advise cycling the N+ with the button pressed first (causes the above trouble).

Chris, would you update that page suitable for the new boot arrangements please? (might save some reflash toubles for folks.

Thanks, cheers, W

Updated the Wiki entry

Nak.