- Netduino Forums
- → Viewing Profile: Posts: lor3
The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
Community Stats
- Group Members
- Active Posts 12
- Profile Views 3776
- Member Title Member
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
0
Neutral
User Tools
Friends
lor3 hasn't added any friends yet.
Posts I've Made
In Topic: How to deploy over COM
20 November 2012 - 04:28 PM
OK all is working well... a slightly unrelated question; is Microsoft.SPOT.Hardware.UsbClient supported by the Netduino+ 4.2 firmware (or standard Netduino)? I'm getting an UnsupportedException from the UsbController constructor so I'm guessing not?
In Topic: How to deploy over COM
20 November 2012 - 01:43 PM
The first time you run the app, press the button to change the transport. Then once it reboots, erase the current app (using the new transport port) and you'll be good to go.
Fantastic, works like a charm. I've tried with COM1 and COM2 and both work fine so the reset IRQ doesn't appear to be a problem. The only thing I did notice is that MFDeploy doesn't work via serial (Ping/Erase) but VS can deploy and debug fine.
Thanks for your help Chris.
In Topic: How to deploy over COM
20 November 2012 - 12:01 AM
Can you try using COM2 for debug really quickly, instead of COM1?
Just tried with COM2, exactly the same (reset on boot).
In Topic: How to deploy over COM
19 November 2012 - 10:18 PM
Does that get you connected alright?
Well it helps if the test program doesn't use the COM :-) I've managed to get a response in MFDeploy via serial but it just seems to be resetting constantly. This is the serial output:
DM9161_AutoNegotiate Valid PHY Found: 31 PHY: Vendor Number Model = 0xA PHY: Model Revision Number = 0x0 DM9161_DSCSR = 0xF3F0 DM9161_BMCR = 0x3100 DM9161_DSCR = 0x414 Error: AutoNegotiate TimeOut PHY AutoNegotiate ERROR! ip address from interface info: 192.168.5.100 .NetMF v4.2.0.0 NetduinoPlus, Build Date: Sep 19 2012 17:01:50 ARM Compiler version 410894 TinyCLR (Build 4.2.0.0) Starting... Created EE. Started HasÀ0¼qðCreate TS. Loading start at 1542e0, end 16c5dc Assembly: mscorlib (4.2.0.0) Assembly: Microsoft.SPOT.Native (4.2.0.0) Assembly: Microsoft.SPOT.Hardware (4.2.0.0) Assembly: Microsoft.SPOT.Net (4.2.0.0) Assembly: System (4.2.0.0) Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) Assembly: Microsoft.SPOT.IO (4.2.0.0) Assembly: System.IO (4.2.0.0) Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Assembly: SecretLabs.NETMF.Diagnostics (4.2.0.0) Loading Deployment Assemblies. Attaching deployed file. Assembly: NetduinoApplication1 (1.0.0.0) Attaching deployed file. Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.2.0.1) Resolving. Ready.
Then reset. The code is just:
Transport.SetInterface(TransportInterface.Com1); Thread.Sleep(Timeout.Infinite);
In Topic: How to deploy over COM
19 November 2012 - 08:07 PM
Can you try adding SecretLabs.NETMF.Diagnostics.dll as a reference to your project? And then running the following line of code (deployed via WinUSB)?
SecretLabs.NETMF.Diagnostics.Transport.SetInterface(TransportInterface.Com1);Chris
Done this, the N+ now has the ethernet lights and the blue LED flashing every 5 seconds and the USB device isn't recognised. I'm using a 3.3V TTL <-> Usb cable plugged into D3/4 (and ground), tried swapping the two around in case I had RX/TX the wrong way around but am unable to ping with MfDeploy either way.
- Netduino Forums
- → Viewing Profile: Posts: lor3
- Privacy Policy