I have problems with sending serial data (for informational messages) to the serial monitor from the programming port of the DUE. I'am using the vMicro IDE in the VisualStudio environment for developing my controls. The MEGA 2560 does not have this problem. It seems that after sending some data the port is locked (not sending or receiving data). It must be some software problem; i tried 2 DUE's and the are acting the same; the port is locked after the same amount of received data by the monitor.
When i put a flush() statement after every serial.println, more data is processed before locking…(?). Not sure what the flush() is exactly doing; but just a fact.
Other serials in the same control, e.g. Serial1 and Serial3 are working perfect. Serial1 is connect by a serial to usb connection to my (windows)PC and Serial3 is connected to a GSM module. Uploading the software via the programming port is no a problem.
Is this a known problem? Who has some information to solve this issue...
How about posting a minimal sketch to show the issue ?
If Serial1,2,3 and Serial4 work, why not using one of them ?
The sketch is about 6500 lines. I asked for the same sort of problem, forum members have had with respect to this issue and a possible solution they have. Reading your reaction, i don't think you have faced the same problem (or am i wrong?). It annoys me when things are not working. The standard serial on a MEGA2560 with same sort of sketch is working perfectly, why not on a DUE? That is the question.
The ONLY serious way to debug your code is to run a MINIMAL sketch showing the issue. Moreover, this is the best effort you could do by yourself to help yourself and find the issue.
It may be an incorrect baud rate (too slow, have you selected 250000 ?), or an interruption somewhere which hangs the Serial interruptions, or something else....
I've tried every possible baudrate (slow, quick). No result, still locking after the same amount of data.
But you still don't answer my question; did you experienced the same problem, and what about the extra Serial.flush() after each Serial.println() with the resulting extra data on the monitor? Any idea?
I've added the sketch as attachment.
Sketch.ino (183 KB)