27 replies to this topic

[Chris Walker]

For some reason this only works once. I am debugging on RS232 and have an XBee connected to TTL. In the code I open up COM2 to read data from the XBee. If I stop debugging and then start again I can't. I cannot even connect via MFDeploy. At that point I have to reflash TinyBooter and the firmware to get the Netduino Mini working again.

Not sure if it's just me, but fyi.

phantomtypist,

Do you have any more info on this? That should not happen at all.

BTW, you can force your Netduino Mini into bootloader mode (so that you can erase your current app) by applying power to the DTR pin (pin 3) during power up. No need to erase and reflash.

Chris

[phantomtypist]

phantomtypist,

Do you have any more info on this? That should not happen at all.

BTW, you can force your Netduino Mini into bootloader mode (so that you can erase your current app) by applying power to the DTR pin (pin 3) during power up. No need to erase and reflash.

Chris

I totally didn't know about the DTR pin to force the Mini into bootloader mode. I kinda wondered how to do that.

As for more info, I just create a SerialPort, assign COM2 to it (9600, Parity.None, 8, StopBits.One) and I have the XBee connected to pins 11 and 12. I then open the serial port and just look trying to read the buffer. If for whatever reason stop debugging, then try running debug again (F5), I can not connect to the Mini anymore (using RS232 PL2303 Prolific USB cable). I also can not get into the TinyCLR on the Mini using MFDeploy. I can now use the DTR to get to the bootloader so at least I don't have the reflash TinyBooter.

EDIT: Forgot to mention I am using 4.1.1.0 Alpha 5

[Chris Walker]

phantomtypist, You're deploying over a TTL cable (pins 11,12), not an RS232 cable (pins 1,2)--correct? Also, COM2 is pins 1,2. COM1 is pins 11,12. Are you actually wanting to use the COM1 SerialPort for XBee instead? Chris

[phantomtypist]

phantomtypist,

You're deploying over a TTL cable (pins 11,12), not an RS232 cable (pins 1,2)--correct?

Also, COM2 is pins 1,2. COM1 is pins 11,12. Are you actually wanting to use the COM1 SerialPort for XBee instead?

Chris

I am deploying over COM2 (pins 1,2) RS232

I have the XBee plugged into COM1 (pins 11, 12) TTL.

My assumption was that since the internal swapping between COM 1 and 2 still had a bug, I was thinking I could just call COM2 since it was physically mapped to pins 11 and 12 (TTL). I'm just going to give up at this point until a new firmware is released because the other bug in DataReceived is a show stopper.

[neuron uav]

The only way to trigger an event is to a delegate within the loop of reading. We SerialPort class to encapsulate a singleton. It's good for you. I think there is an error in the SerialPort class. PD-I've tried from Visual Studio and the emulator and I have not been able to shoot the event. Only the solution of Singleton. Greetings

[Chris Walker]

Okay, this has hopefully been fixed in v4.1.1 alpha 6 as well (and v4.1.0.6 RC1). Please test out the new release and let me know if it works for you. Chris

[phantomtypist]

Works for me! Thank you!

[Tecchie]

Please test out the new release and let me know if it works for you.

Does work for me, too. Thanks for fixing!