- Netduino Forums
- → lor3's Content
There have been 12 items by lor3 (Search limited from 28-January 20)
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.
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 v126.96.36.199 NetduinoPlus, Build Date: Sep 19 2012 17:01:50 ARM Compiler version 410894 TinyCLR (Build 188.8.131.52) Starting... Created EE. Started HasÀ0¼qðCreate TS. Loading start at 1542e0, end 16c5dc Assembly: mscorlib (184.108.40.206) Assembly: Microsoft.SPOT.Native (220.127.116.11) Assembly: Microsoft.SPOT.Hardware (18.104.22.168) Assembly: Microsoft.SPOT.Net (22.214.171.124) Assembly: System (126.96.36.199) Assembly: Microsoft.SPOT.Hardware.SerialPort (188.8.131.52) Assembly: Microsoft.SPOT.IO (184.108.40.206) Assembly: System.IO (220.127.116.11) Assembly: Microsoft.SPOT.Hardware.PWM (18.104.22.168) Assembly: SecretLabs.NETMF.Diagnostics (22.214.171.124) Loading Deployment Assemblies. Attaching deployed file. Assembly: NetduinoApplication1 (126.96.36.199) Attaching deployed file. Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (188.8.131.52) Resolving. Ready.
Then reset. The code is just:
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)?
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.