Netduino home hardware projects downloads community

Jump to content


Photo

Error: No response from device in MFDeploy


  • Please log in to reply
13 replies to this topic

#1 Frode

Frode

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts
  • LocationNorway

Posted 23 April 2014 - 10:57 PM

Hi, 

I've been working with my Mini this evening, and have successfully been able to deploy solutions from VS2010 Express many times.

 

However, at some point the Mini stopped responding to the deployment from VS2010. I'm moving the Mini between my PCB and the breadboard for programming, and even if VS2010 couldn't program it it still worked on the PCB.

 

I've tried erasing the board, and can successfully do all the SAM-BA tasks described in the Wiki. I'm using firmware 4.1, and SAM-BA seems to be OK when I write the TinyBooterDecompressor.bin.

 

However, I cannot get any sort of connection through MFDeploy. I've tried both the 4.1, 4.2 and the old custom one I found on the forum, but none of them are able to get the device capabilities. It just responds "Error: No response from device".

 

I've used a USB->RS232 cable when using SAM-BA. The cable plugs into a DB9 breakoutboard, and from there I've connected RXD->TX, TXD->RX and GND->GND. It shows up as COM8, but there is no reply on that port in MFDeploy.

 

I've also got a USB->TTL cable which I'm using for programming the Mini. It uses COM3.

 

What can I do?

Attached Files



#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 24 April 2014 - 04:12 AM

Hi Frode,

When you deployed TinyBooter via SAM-BA, did you "enable boot from flash"? Did you do a verify after flashing? Did it verify okay?

Also...be sure that you're flashing TinyBooter_RS232 if you're going to deploy TinyCLR via the RS-232 port. Or flash TinyBooter_TTL (not sure if we publish that anymore) if you're going to deploy TinyCLR via the TTL serial port.

BTW, if you ever run into issues deploying to your Mini again...just drive the DTR pin high while powering up your Mini. That will force it into TinyBooter mode (if it's flashed), and you can then erase the misbehaving app.

Chris

#3 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 24 April 2014 - 05:12 AM

Hello!

That whole business sounds horribly familiar to something I collided with early on. I didn't want to reply because I knew Chris or someone else would. As for the different examples of what runs on the Netduino Mini, I believe I have copies of each here. Except for the experimental stuff that you referenced, I confess I never had a reason to pull it down. 

 

If you do need copies of them, PM me and I'll see which ones I have in storage and make arrangements for them to be sent off to you.

 

Of course Chris this would never have happened if you didn't pay that Yeti to run the transition from whatever the site lived on to Windows Azure extreme hazard pay.



Doctor Who
"This signature does not exist!"

#4 Frode

Frode

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts
  • LocationNorway

Posted 24 April 2014 - 05:44 AM

Hi guys, thanks for answering!

 

I followed the guide in the Wiki, (which includes "Boot from flash" and "Enable flash access") and this time I also clicked "Compare sent file with memory". It says they are the same. MFDeploy still won't connect though.

 

I used the .bin file I found in the second post in this thread. Is that the correct one?



#5 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 24 April 2014 - 05:34 PM

Hi guys, thanks for answering!

 

I followed the guide in the Wiki, (which includes "Boot from flash" and "Enable flash access") and this time I also clicked "Compare sent file with memory". It says they are the same. MFDeploy still won't connect though.

 

I used the .bin file I found in the second post in this thread. Is that the correct one?

 

Hello!

On that thread I saw three enclosed. Both were for the Mini to use the RS232 style port on the first pins on it, and then TTL one.

 

Which one did you chose?



Doctor Who
"This signature does not exist!"

#6 Frode

Frode

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts
  • LocationNorway

Posted 24 April 2014 - 06:11 PM

I used the one from the second post. 

 

I also tried the RS232 one from the 4.2 firmware thread, but get the same result. SAM-BA seems to be OK, but MFDeploy cant find the Mini.



#7 Frode

Frode

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts
  • LocationNorway

Posted 24 April 2014 - 07:30 PM

At the end of the Wiki it shows MFDeploy using USB. That should be Serial, right?

 

Does it matter if I use MFDeploy from v4.1, v4.2 or v4.3?

 

Also, I'm using SAM-BA v2.12.



#8 Frode

Frode

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts
  • LocationNorway

Posted 24 April 2014 - 07:43 PM

Ha! For some reason it started working!

 

For future reference;

11.1V battery on pins 23/24.

USB to RS232 cable + DB9 breakoutboard.

Pins 2 (RXD), 3(TXD) and 5(GND) on the DB9 is connected to pins 1(TX), 2(RX) and 4(GND) on Netduino.

In Samba v2.12 I uploaded TinyBooterDecompressor.bin from the 4.1 Update 6 Firmware.

Disconnected and reconnected battery.

Disconnected and reconnected USB.

Started MFDeploy 4.1, choose correct serialport, and Ping. 

 

When I test with MFDeploy 4.2 I get the same error as before, but when switching back to MFDeploy 4.1 it responds to ping.

 

Then uploaded firmware for 4.1.0.6 in MFDeploy.



#9 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 April 2014 - 05:11 AM

Hi Frode,

Glad you are back up and running!

Is it possible that the board just needed power cycling after TinyBooter got flashed? [For reference, SAM-BA leaves the board in a programmed-but-not-booted state, so you do want to power cycle.]

Chris

#10 Frode

Frode

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts
  • LocationNorway

Posted 25 April 2014 - 06:11 AM

Hi Chris, 

I doubt it since I troubleshooted this over such a long time. I know I disconnected the Mini totally several times during the troubleshooting.

 

One of the major changes I made was that I initially powered the mini with 5V->Pin21, but at the end I changed it to a 11.1V LiPo battery on pin 24.

 

But does it make sense that I am able to ping the Mini via MFDeploy v4.1, but not with MFDeploy v4.2?



#11 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 April 2014 - 12:45 PM

Hi Frode,

It's odd that MFDeploy 4.2 has trouble communicating with the bootloader but MFDeploy 4.1 works fine. There are reasons why MFDeploy might not like the newer firmware--but things should be pretty backwards compatible.

For now, I recommend sticking with what works for you (NETMF 4.1). If there's a way to repro this on other computers in the future, we may have the opportunity to revisit this :)

Chris

#12 eschneider

eschneider

    Member

  • Members
  • PipPip
  • 16 posts

Posted 20 April 2015 - 10:46 PM

What?, so you're say tough luck, no 4.2 for the mini?



#13 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 21 April 2015 - 06:01 AM

Hi eschneider,

You can find 4.2 firmware for Netduino Mini here:
http://forums.netdui...-v420-update-1/

We typically stick with 4.1 in our Netduino Mini projects (due to some advantages in the way that NETMF 4.1's debug channel and reset scheme works)--but lots of people use 4.2 as well.

Chris

#14 eschneider

eschneider

    Member

  • Members
  • PipPip
  • 16 posts

Posted 21 April 2015 - 02:16 PM

I don't understand, are people able to deploy a fully functional MF 4.2? If not what's wrong?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.