Netduino home hardware projects downloads community

Jump to content


Photo

Cannot deploy to old Netduino Plus

deploy firmware

  • Please log in to reply
3 replies to this topic

#1 BanksySan

BanksySan

    Member

  • Members
  • PipPip
  • 28 posts
  • LocationBristol, United Kingdom

Posted 03 April 2016 - 05:57 PM

I have a pretty old Netduino Plus.

 

I've just got it out and dusted it off, installed the prerequisites on my new Windows 10 machine but now I can't deploy to it.

 

When I ping with MFDeploy I get:

Pinging... Found debugger!
NoConnection
Create TS.
 Loading start at 14d324, end 162e8c

If I select Device Configuration it just returns:  

Not Supported

I suspect I have some out of date firmware.    Maybe the Micro Framework has incremented a bit since I was last playing with it.

 

I've tried following the instructions here: http://forums.netdui...-firmware-v431/

 

The update tool doesn't see my device at all, and I can't figure out what I'm supposed to to (if anything) with the STDFY_Drivers that's linked to.

 

Any help?

 

Thanks

 

Dave



#2 BanksySan

BanksySan

    Member

  • Members
  • PipPip
  • 28 posts
  • LocationBristol, United Kingdom

Posted 03 April 2016 - 08:25 PM

I've got a bit further.  I was plugging in via a USB hub, plugging directly into the PC gets me further.  Now when I ping I get

Pinging... TinyCLR
Which I seem to remember is a good thing.

 

Now when I run via Visual Studio I get:

 

Found debugger!


Create TS.


 Loading start at 14d324, end 162e8c


Attaching file.


Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA)




Attaching file.


Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA)




Attaching file.


Assembly: Microsoft.SPOT.Hardware (4.1.2821.0) (1752 RAM - 11440 ROM - 7371 METADATA)




Attaching file.


Assembly: Microsoft.SPOT.Net (4.1.2821.0) (704 RAM - 5060 ROM - 2452 METADATA)




Attaching file.


Assembly: System (4.1.2821.0) (872 RAM - 5992 ROM - 3206 METADATA)




Attaching file.


Assembly: Microsoft.SPOT.IO (4.1.2821.0) (740 RAM - 4620 ROM - 2522 METADATA)




Attaching file.


Assembly: System.IO (4.1.2821.0) (1548 RAM - 13292 ROM - 5862 METADATA)




Attaching file.


Assembly: Microsoft.SPOT.Hardware.SerialPort (4.1.2821.0) (512 RAM - 3488 ROM - 1543 METADATA)




Attaching file.


Assembly: Microsoft.SPOT.Hardware.Usb (4.1.2821.0) (580 RAM - 3740 ROM - 1844 METADATA)




Attaching file.


Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) (256 RAM - 1108 ROM - 491 METADATA)




Attaching file.


Assembly: SecretLabs.NETMF.Diagnostics (4.1.0.0) (180 RAM - 440 ROM - 166 METADATA)




Loading Deployment Assemblies.


Attaching deployed file.


Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) (268 RAM - 796 ROM - 423 METADATA)




Attaching deployed file.


Assembly: NetduinoApplication1 (1.0.0.0) (196 RAM - 388 ROM - 175 METADATA)




Attaching deployed file.


Assembly: GoBus (1.0.0.0) (540 RAM - 4016 ROM - 1631 METADATA)




Resolving.


Link failure: some assembly references cannot be resolved!!




Assembly: GoBus (1.0.0.0) needs assembly 'mscorlib' (4.2.0.0)


Assembly: GoBus (1.0.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.2.0.0)


Assembly: GoBus (1.0.0.0) needs assembly 'Microsoft.SPOT.Native' (4.2.0.0)


Error: a3000000


Waiting for debug commands...


The program '[4] Micro Framework application: Managed' has exited with code 0 (0x0).

So... still can't run anything but I think it's a step in the right direction.



#3 Nevyn

Nevyn

    Advanced Member

  • Members
  • PipPipPip
  • 1072 posts
  • LocationNorth Yorkshire, UK

Posted 04 April 2016 - 05:30 AM

It sounds like you have a different version f the firmware on the board to the one you are trying to compile against.

 

When looking at the new firmware make sure you get the one for the N+ and not the N+2 or N+3 boards as the microcontroller changed for these boards.

 

Regards,

Mark


To be or not to be = 0xFF

 

Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life

Follow @nevynuk on Twitter


#4 BanksySan

BanksySan

    Member

  • Members
  • PipPip
  • 28 posts
  • LocationBristol, United Kingdom

Posted 04 April 2016 - 12:39 PM

Thanks Nevyn,

 

I guess this is the one I should be using?  http://forums.netdui...-v420-update-1/

 

However, I'm still getting troubles.

 

When I go to Device Capabilities on MFDeploy, it just says `Not Supported`.

 

I tried deploying anyway, I get through the config deployment but fail with an error dialogue box.

 

---------------------------
.NET Micro Framework Deployment Tool
---------------------------
Error: Unable to deploy to device
---------------------------
OK   
---------------------------






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.