7 replies to this topic

[svish]

I've gotten myself a Netduino. Wanted to upgrade its firmware to 4.2 and figured that shouldn't be too difficult. Boy was I wrong...

 

The guide here in the forums told me I first had to update the bootloader. So I started with that.

 

- Installed SAM-BA 2.12

- Fully erased the Netduino by connecting the golden square to the 3.3V pin while it was connected to my computer

- Disconnected the Netduino

- Connected the Netduino

 

And here the problems started. When I connected the Netduino again Windows tells me a new device is connected and searches for drivers. It completes and apparently found a device called GPS Camera Detect (COM3)?

 

Anyways, I figured that shouldn't be a problem so I opened my Device Manager, found the device (had to make it display hidden devices to find it) and updated the driver. This time I selected the driver found in C:Program Files (x86)Atmelsam-ba_2.12drv, as told in the guide. This failed because of missing driver signatures. Did some googling and found you could disable signature checks through an advanced boot. So I did that. Now I managed to install the driver and got a device called AT91 USB to Serial Converter, which looked right according to the guides.

 

Then I rebooted. My computer decided to shut down instead. Was completely dead for several minutes. Finally booted, but crashed during the Windows 8 boot process. It collected some error stuff and I rebooted again. This time it managed to get to the login screen (although my graphics settings was messed up with wrong resolution etc). I logged in, and it crashed again.

 

So I booted up into Safe Mode, managed to uninstall the AT91 USB to Serial Converter device and driver, rebooted and now I'm back with a working operating system, but also a GPS Camera Detect (COM3) device which I have no idea what is.

 

When I open the MFDeploy tool and select USB, I get nothing.

 

...what can I do here?

[svish]

Not sure what happened here, but think I managed to fix it by just ignoring that custom driver. Blogged about it here: http://geekality.net/?p=2135

[Chris Walker]

Hi svish,

 

Thanks for the updating on this, sorry for the trouble getting started with reflashing. 

 

The newer versions of SAM-BA seem to be a lot better about detecting the default Windows drivers.  I don't ever tweak the Atmel SAM-BA drivers on my Win8 x64 PC.

 

Welcome to the Netduino community,

 

Chris

[svish]

Thanks!

 

Does that mean maybe those guides should be updated quite a bit? Tried to look at newer versions of SAM-BA, but didn't really get their website. Couldn't find any downloads except through the direct link in your guide, so that's what I used

 

Also, what's the reason for suggesting the .NET MF 4.1 and 4.2 SDK on http://netduino.com/downloads, when the latest 4.3 is able to multi target both and also supports the latest visual studio version?

[dionito]

This is not workfing for me with a Netduino Plus 2. I see, even after erasing completely, the device as Netduino in the Windows 8 device manager, but cannot connect to it with SAM-BA 2.12. At this point the board is totally bricked and do not seem to be able to do much with it. Any ideas on how to proceed?

 

Cheers,

Dioni

[Chris Walker]

Hi Dioni,  

This is not workfing for me with a Netduino Plus 2. I see, even after erasing completely, the device as Netduino in the Windows 8 device manager, but cannot connect to it with SAM-BA 2.12. At this point the board is totally bricked and do not seem to be able to do much with it. Any ideas on how to proceed?

SAM-BA is an Atmel tool, which works with the Atmel SAM7X microcontrollers in the older generation 1 Netduinos. For generation 2 hardware--which use ST microcontrollers--you'll want to use the new "Netduino Update" application instead: http://forums.netdui...te-application/ Welcome to the Netduino community, Chris

[dionito]

Cool!! That did the trick. Thanks a lot!!

 

Cheers,

Dioni

[lifanek]

I couldn't flash my N1+ on win8 x46 (some driver issue) so I did in on 7 x86