Another weird experience, this time with the Plus 2
#1
Posted 12 November 2012 - 02:23 AM
#2
Posted 12 November 2012 - 02:30 AM
A few quick things:The upshot is that the code definitely got sent to the NP2 because upon reset, my terminal program showed my string getting blasted over the port continuously. However, now I can't reprogram the NP2 -- every time I plug it in, it just comes up as an Unknown Device. MFDEPLOY can't see it, either.
I will probably resort to trying to reload the firmware after erasing via the erase pad, but I'd like to know how in the world what I did could have caused the NP2 to behave in this way.
1. There is no ERASE pad on the new Netduino Plus 2 and Netduino Go boards. To reflash you simply hold down the pushbutton while plugging in the board to put it into bootloader mode...and then run STDFU to erase the board and DFUSE to reflash the board. No risk of shocking your board with a stray wire.
2. You'll want to use the new "SecretLabs.NETMF.Hardware.Netduino.dll" hardware provider instead of the "SecretLabs.NETMF.Hardware.NetduinoPlus.dll" hardware provider from Netduino Plus 1. With the new firmware release there is only one provider used for both Netduino and Netduino Plus 2. If you try to deploy an old Netduino Plus application without switching out the hardware provider, it'll try using the old pins (some of which may overlap numberwise with the pins used by the USB port--which could cause your issue).
3. For now, please erase and reflash your board. Once you've verified that you have the correct HardwareProvider, let us know if you have any further troubles. If you're deploying an app which locks out Visual Studio, we'd like to take a look and see if there's anything we can do to prevent that.
Congrats on getting your new board!
Chris
#3
Posted 12 November 2012 - 05:04 AM
I actually was using the new assembly -- I created a Netduino Plus 2 app, ran it on the NP2, then ran it on the NP, then ran it again on the NP2. The only thing I changed was the device in the Deployment properties between boards.
I'll give the reflashing a try and will let you know if weird stuff happens in VS2010!
Hi Dave,
A few quick things:
1. There is no ERASE pad on the new Netduino Plus 2 and Netduino Go boards. To reflash you simply hold down the pushbutton while plugging in the board to put it into bootloader mode...and then run STDFU to erase the board and DFUSE to reflash the board. No risk of shocking your board with a stray wire.
2. You'll want to use the new "SecretLabs.NETMF.Hardware.Netduino.dll" hardware provider instead of the "SecretLabs.NETMF.Hardware.NetduinoPlus.dll" hardware provider from Netduino Plus 1. With the new firmware release there is only one provider used for both Netduino and Netduino Plus 2. If you try to deploy an old Netduino Plus application without switching out the hardware provider, it'll try using the old pins (some of which may overlap numberwise with the pins used by the USB port--which could cause your issue).
3. For now, please erase and reflash your board. Once you've verified that you have the correct HardwareProvider, let us know if you have any further troubles. If you're deploying an app which locks out Visual Studio, we'd like to take a look and see if there's anything we can do to prevent that.
Congrats on getting your new board!
Chris
#4
Posted 12 November 2012 - 05:11 AM
#5
Posted 12 November 2012 - 05:24 AM
using System; using System.Net; using System.Net.Sockets; using System.Threading; using Microsoft.SPOT; using Microsoft.SPOT.Hardware; using SecretLabs.NETMF.Hardware; using SecretLabs.NETMF.Hardware.Netduino; using System.IO.Ports; namespace NetduinoPlus2Test { public class Program { public static void Main() { // write your code here Debug.Print( "It's working"); OutputPort led = new OutputPort( Pins.ONBOARD_LED, false); SerialPort rs232 = new SerialPort( SerialPorts.COM1, 115200, Parity.None, 8, StopBits.One); rs232.Open(); string msg = "Hello World\r\n"; byte[] bytes = System.Text.Encoding.UTF8.GetBytes( msg); while( true) { led.Write( true); led.Write( false); // write serial data on COM1 with RS232 shield rs232.Write( bytes, 0, msg.Length); } } } }
#6
Posted 12 November 2012 - 05:49 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users