12 replies to this topic

[viktor]

Hello, I need someone's help on this. I tried updating to the 4.2 rc4 firmware and ran into an issue. I first jumpered the 3.3v to the little copper tab by port 0, then i tried connecting the device and windows said it couldn't connect to it and eventually figured out that it was a gps camera. Well, I was able to use SAM-BA to load the tinybootloader unto it, but now i am trying to get it to show up in mfdeploy and it only shows up under serial connections com3, but of course can't ping/erase/upload to it. What else can i do to get the card back into operation? Thanks, Viktor.

[viktor]

ok, got it figured out, remembered i could just uninstall the device from device manager and do the detection again. This time it was found as the right device.

[viktor]

Ok, i was able to flash it with 4.2 rc4, and i am getting response when i ping it in mfdeploy, and i have just a power LED on until I try and load a project into it, then both led's come on and i'm not getting any feedback from it. Visual Studio is not able to go into debug either. Anyone?

[Stefan]

Hi Victor, Did you only update the TinyBooterDecompressor.bin or also the ER_FLASH file?

[viktor]

Hi Victor,

Did you only update the TinyBooterDecompressor.bin or also the ER_FLASH file?

I was able to update the ER_FLASH and config, the board seems to have good vital signs after this until I try to load a project unto it then I get both lights on.

Here are the procedures I've done a few times:

1. Erase by doing the copper tab + 3.3v
2. use SAM-BA to clear flash (just to be sure), then load tinybootloader
3. disconnect/reconnect it, then go into mfdeploy and load the FLASH and CONFIG
4. disconnect/reconnect, ping returns TinyCLR, then go into network config and do the settings there.
5. power LED on, onboardLED off.
6. Try to start a project after I upgraded it to 4.2 and it gets built and when its trying to reboot the card I get both LEDs to come on and debug never kicks in. Also the card wont respond to a ping then.

Thanks,
Viktor.

[Chris Walker]

Hi viktor, What are you trying to do in your app? Is there an SD card inserted? What happens if you remove it? Chris

[viktor]

Hi viktor,

What are you trying to do in your app? Is there an SD card inserted? What happens if you remove it?

Chris

No sd card. But I just re-installed the Netduino SDK 4.2 and now its taking the projects. Thanks again for chiming in.

[Shy_B]

No sd card. But I just re-installed the Netduino SDK 4.2 and now its taking the projects. Thanks again for chiming in.

same problem here ...

[Shy_B]

same problem here ...

Got it...

Wrong version of the Netduino SDK (4.1 instead of 4.2).

now it all works

[seuabb]

I've installed the right version mf sdk(4.2) and netduino sdk(4.2), but my device failed to give any response now. How can I resolve this problem?

[Chris Walker]

Hi seuabb,

I've installed the right version mf sdk(4.2) and netduino sdk(4.2), but my device failed to give any response now.

How can I resolve this problem?

Can you give us more details on how you updated your Netduino, what it shows up as in Device Manager, etc.?

Chris

[syntroniks]

Hi seuabb,

Can you give us more details on how you updated your Netduino, what it shows up as in Device Manager, etc.?

Chris

Maybe not, but I can try to jump in!
I am able to successfully deploy the tinybooterdecompressor.

Afterwards, the netduino will not enumerate over USB. I have verified that the tinybooterdecompressor is programmed to 0x100000. I must be missing a step because after a power cycle, the device has the tinybooterdecompressor but I can not access it in mfdeploy. (it isn't avail over USB and pinging over serial yields no response)

I am using a usb->serial converter to do the flash erases/programming. I have tried multiple versions of the tinybooterdecompressor.

FWIW sam-ba 2.8 works for me under compat mode. (I am W7 64 bit) I have Micro SDK 4.1 and 4.2


[this is not a + device. -- I need the latest beta firmware for I2C internal addressing. I have an AVR-ISP if that helps.]

Edited by syntroniks, 29 March 2012 - 05:22 PM.

[Firegun]

Maybe not, but I can try to jump in!
I am able to successfully deploy the tinybooterdecompressor.

Afterwards, the netduino will not enumerate over USB. I have verified that the tinybooterdecompressor is programmed to 0x100000. I must be missing a step because after a power cycle, the device has the tinybooterdecompressor but I can not access it in mfdeploy. (it isn't avail over USB and pinging over serial yields no response)

I am using a usb->serial converter to do the flash erases/programming. I have tried multiple versions of the tinybooterdecompressor.

FWIW sam-ba 2.8 works for me under compat mode. (I am W7 64 bit) I have Micro SDK 4.1 and 4.2


[this is not a + device. -- I need the latest beta firmware for I2C internal addressing. I have an AVR-ISP if that helps.]

Didn´t you forgot to set it to boot from flash in SAM-BA (on the scripts combobox), before the power cycle? Idk how it may helps, but there are a new version of SAM-BA (v2.11) too.