3 replies to this topic

[dyadica]

I have now tried installing update Version: 4.1.0 Update 6 (version 4.1.0.6) on two minis each time via TTL using the TTL version on each occasion MFDeploy seemed to complete ok however I now cannot access ping deploy or even re-flash either. If i ping the board I get Error no response from device. I have tried to re-flash (Via RS232) but each I try to connect to samba I get no board detected. If I manually set the 7x512 board type as detailed on the chip I receive a No processor valid ID fatal error. I have repeated this process with both v2.9 and v2.10 but to no avail. I’m not happy at the moment. I have 1 more mini but am scared to update however I need the serial fix to verify a few things I have been working on. I had come across a posing with the same error for another board which detailed the issue to be a security bit - any chance this is a similar issue? Any Ideas?

[Chris Walker]

Hi dyadica, Is it possible that your program on the Mini is opening the serial port when it boots, locking out the computer? Two things to try: 1. Try applying 5V (from pin 21) to the DTR pin (pin 3) during powerup. This will force the Netduino Mini into TinyBooter mode. Try pinging it from MFDeploy...and then ERASE your current app. 2. You can also reflash the Mini via RS232. To do this, you'll need to erase it first. Very carefully: apply 5V power (from pin 21) to the ERASE pad (small gold square in the bottom left corner). Then remove power. When you power it back up, SAM-BA should see it. Chris

[Fred]

I have always found that it can take quote a few attempt to flash both my Minis. Here's what I do:

• I erase using the gold pad, then power off for a few seconds.
• I use SAM-BA 2.09 on Win7 64. It often takes quite a few goes to see the device. I see "no valid processor ID" a lot. SAM-BA seems flaky at the best of times.
• I flash TinyBooter using SAM-BA. I usually write protect sections 0-2 when prompted to. Sometime I enable boot from flash to see if that helps.
• MFDeploy often fails to connect.
• I power cycle the Mini a few times and erase/reflash using SAM-BA a few times.
• MFDeploy eventually sees the Mini.
• Once I'm here then flashing the firmware and programming is fine.

I did think I'd got to the bottom of things when I discover a loose power connection to the mini, but that wasn't it. It may have been my post with the security bit, but that probably wasn't the issue either.

[dyadica]

Hi Guys, Thanks for the replies; sadly my computer has also bit the dust (not having a good week)so I’m not going to be able to try for a couple of days but fingers crossed For ref one of the mini’s was fresh, first thing I did was try the install. However the other one had some serial bits going off. Can I clarify if the update install wipes your existing program? If not then this may be the case for that one?? I’ll give the erase a go and try a few hundred times (hope not lol) and get back to you if that’s ok Once again thanks to you both for the help, hopefully it won’t take that long to get going. Any ideas if there is better software out there for flashing than samba? Also on the off chance is there another version of the update that fixes the serial issues so I can give that one a go on my third chip. Cheers, d