5 replies to this topic

[IronMarco]

I have tried to update my board from 4.1.0 v6 to 4.2.0 RC5 but something doesn't work. I have read and followed the instruction on wiki page but after flashing the board with the new FW I'm not albe to communicate with it. After the flashing I don't receive the message from the board about checking, please look the screenshot attached below. I'm wondering if could be my mistake or someone have had same problem? Cheers IronMarco

Attached Files

•  FW 4_2_RC5.JPG   68.28KB   56 downloads

[Chris Walker]

Hi IronMarco, I haven't seen that issue before. Can you confirm that you're deploying a matching set of TinyBooter and TinyCLR (ER_CONFIG/ER_FLASH) files? Chris

[IronMarco]

Hi IronMarco,

I haven't seen that issue before. Can you confirm that you're deploying a matching set of TinyBooter and TinyCLR (ER_CONFIG/ER_FLASH) files?

Chris

Yes I have downloaded both from Forum:

Topic
http://forums.netdui...-netduino-plus/

Files for NetDuino plus
http://forums.netdui...&attach_id=1708


http://forums.netdui...?showtopic=2768

Followed the instruction here:
http://wiki.netduino...ep-by-step.ashx
http://wiki.netduino...ep-by-step.ashx

Cheers

[IronMarco]

No news?

Hi IronMarco,

I haven't seen that issue before. Can you confirm that you're deploying a matching set of TinyBooter and TinyCLR (ER_CONFIG/ER_FLASH) files?

Chris

[nakchak]

I have had similar issues in the past.

Try this:

• Erase the netduino (3.3v to the erase pad)
• Unplug the usb then reconnect it
• Use SAM-BA and copy the 4.2 RC5 bootloader over
• Unplug the usb then reconnect it
• Open MFDeploy
• Check you get the bootloader response (click ping)
• Redeploy the firmware.
• Unplug the usb then reconnect it, then ping the board.

Not sure why this happens but i guess a bad flash is possible or something silently fails, but a complete reflash seems to fix it for me.

[Chris Walker]

Hi IronMarco, We're digging into this a bit. There's a potential for a buffer issue in the NETMF drivers which might be able to cause something like this, which should be fixed with the new WinUSB drivers coming in the upcoming RC6 (i.e. NETMF 4.2 QFE2). In the meantime, I'd recommend using the release firmware. Or trying the process that nakchak just mentioned. Chris