60 replies to this topic

[nakchak]

Revised: It worked if I moved to another USB port (??!?!).


After SAM-BA has detected the USB driver and I've selected at91sam7x512-ek and then click "Connect", SAM-BA pops up "Error in startup script" "Error h_handle returned zero" etc.

I'm using Windows 7 64, .NET 4.2 and SDK 4.2.

Any idea what could cause this to happen?

Cheers,
Anders

Hi Anders

Are you using SAM-BA 2.12 fixes some issues with x64 os's...
Also are you using the driver in "drv" folder where you installed sam-ba too or the generic GPS camera driver that windows update discovers, try uninstalling the driver in device manager and manually installing the Atmel driver?
Finally have you erased your ND (3.3v to the gold erase pad) before you try and connect with sam-ba?

Nak.

[andersborg]

Hi Anders,

That's very odd. So it did work alright after moving the Netduino to another USB port?

Also, are you using SAM-BA v2.12+? The earlier versions had some issues with Win7 x64.

Chris

Yup. In both cases the ports were detected (COM8 and COM10), so it was nothing wrong with that. My PC supposedly has two different USB controllers, so that might be the reason.

I used 2.12+ (just installed).

[andersborg]

Hi Anders

Are you using SAM-BA 2.12 fixes some issues with x64 os's...
Also are you using the driver in "drv" folder where you installed sam-ba too or the generic GPS camera driver that windows update discovers, try uninstalling the driver in device manager and manually installing the Atmel driver?
Finally have you erased your ND (3.3v to the gold erase pad) before you try and connect with sam-ba?

Nak.

Yes it's 2.12+.

I used the generic driver (actually I didn't do anything with that). I erased as per the instructions.

I'll try the advice. Thanks.

[Henning Krapoth]

After updating to 4.2 I can't deploy to my Netduino. MFDeploy says after ping that it is in TinyBooter Mode, regardless of pressing the button while plugging in or not. Any hints what's wrong?

[andersborg]

I have it going now, so maybe I can help. Did you perform all these steps? http://wiki.netduino...ep-by-step.ashx Cheers, Anders

[Henning Krapoth]

After updating to 4.2 I can't deploy to my Netduino. MFDeploy says after ping that it is in TinyBooter Mode, regardless of pressing the button while plugging in or not. Any hints what's wrong?

I repeated the whole process and now it works.
I had to make a new project though, to get deployment from VS2010 working.

[Chris Walker]

Hi Henning,

I repeated the whole process and now it works.
I had to make a new project though, to get deployment from VS2010 working.

If this happens in the future, open up the project properties and go to the .NET MF tab. Then change transport from USB to Serial and then back to USB.

This is usually because of a mismatch between the device name stored in your project settings and the device name of the target Netduino. Especially if you change the USB device name...that setting gets reset when the board is erased and reflashed.

Chris

[rodoken]

I can't set the network settings or see device capabilities in either tinybooter or tinyclr modes...?

[Chris Walker]

Hi rodoken,

I can't set the network settings or see device capabilities in either tinybooter or tinyclr modes...?

When you're in TinyBooter mode, what response do you get when you press PING?

What happens exactly when you try to change the network settings?

Chris

[rodoken]

I get... Pinging... TinyBooter Bootloader build info: Netduino (v4.2.0.0) by Secret Labs LLC When I try to change network settings I get a pop-up window that says... Network Configuration '! Unable to write configuration'

[rodoken]

If I select target/device capabilities, I get... 'Not Supported' in the response pane in MF Deployment Tool...

[Chris Walker]

If I select target/device capabilities, I get...

'Not Supported' in the response pane in MF Deployment Tool...

Is that with TinyBooter or TinyCLR? You need to be in TinyCLR for device capabilities...

Chris

[kediman]

I had exact same problem. Device was stuck in TinyBooter, and restarting with pressed/depressed button did not change to TinyCLR. Reflashing and following every restart step successfully resolved the issue. Works like a charm now.

[rodoken]

ok reflashed and now I can see device configuration thanks but if I try to set network info, netduino gets stuck in tinybootloader mode...

[TalbotEv]

Love the new firmware but still missing the special build with One Wire, when does that goes live ?

[H07R0D]

ok
reflashed and now I can see device configuration
thanks
but if I try to set network info, netduino gets stuck in tinybootloader mode...

I'm seeing the same thing. Flash works fine, but if I try to set the network configuration, it drops back to TinyBooter mode, then I have to reflash to get into TinyCLR, which of course loses device capabilities.

[habakuk]

Hi, Update from RC5 to 4.2.0 RTM doesn't work for me. After uploading the TinyBooterDecompressor the USB port (or the virtual serial port) is not recognized. I tried to use the bootloader from RC5, but after uploading the firmware the usb port is gone again. Only if I erase my Netduino plus (with the "golden erase pin") the usb port comes back again. If I reflash it with RC5 everything works. I downloaded the zip-file with the RTM firmware twice... Any idea? Ciao! Stefan

[Chris Walker]

Hi Stefan,

If I reflash it with RC5 everything works.

Could you please try upgrading to the .NET MF 4.2 QFE2 SDK and the Netduino 4.2.0.1 SDK on the downloads page?

You'll need the new WinUSB drivers for the device to work once TinyBooter is flashed.

Chris

[Igor Kondrasovas]

Hi Chris, Do you know what is the default precision for the new AnalogInput class? Could not find anywhere and would like to make sure I can only specify the channel if using Netduino. Thanks!

[Chris Walker]

Hi Igor,

Do you know what is the default precision for the new AnalogInput class? Could not find anywhere and would like to make sure I can only specify the channel if using Netduino.

The ADC precision is 10-bits. There is just the one option.

Chris