Hi, i'm trying to use the native port for serial communication.
When i plug the usb of the secondary (native) port windoes 7 recognizes the port as "COM11"
In Control Panel the atmelwinrvr (jungo, what is it?) show a digital signature warning.
When i run my c program, which activates both serial ports (programming COM10, native port 11)
windows lose the COM11 port. If i close my program and re run it, the native COM11 is recognized again.
I can communicate via the programming serial normally but no led is blinking when i send serial via the native port, and i got no responce, i positively sure, it does not work correctly (the native port)
Is it a problem with the digital signature (i have read to install a security update for windows 7 ) that fixes
the problem with the atmel jungo non digitally signed signature warning.
\or is it something else.
I'm "SerialUSB" in the sketch i upload to the due. Is this right?
Now the last problem is that after every reprogramming, i have to unplug and replug the native port usb cable so to restablish the native COM port. Is there any way to avoid this behavior?
Why windows lose the native COM port after programming of the Due?
If the memory is erased and the mcu is reset, then how when i disconnect it and then reconnect it it appears again and works ok?
I 'm not using the serial monitor but a c windows program ( i program this). So when i run it and i have enabled both the native and the programming COM. The reset that is triggered by the initialization of the programming port makes the native port be seen again by windows (without physically plug it and un-plug it). But in this case the native port don't work any more for serial communication.
So in general i'm looking for a procedure to "reset" the native port so windows be able to see it again without loosing the functionality.
Isn't possible to use at the same time both the programming and the native port of the Due for serial communication?
Because I skipped a step. The memory is erased, a new program is uploaded and then it resets. It can't possibly maintain communication with the native port during that process.
The best I can offer is to look at the source code for the serial monitor. See how that works.
When Arduino Due resets, the native USB port disconnects. To your PC, it's electrically the same as the cable being unplugged.
Then when it reboots, the program the Arduino IDE creates causes the USB port to connect again. To your PC, it's the same as if you quickly plugged the cable back in.
The Arduino IDE automatically closes the serial port when you click Upload. But if you use other software like putty or coolterm, it has no way to know when you click upload in the Arduino IDE window. On Linux and Windows 10, that's not a problem. But if you use Windows 7, there's a bug in the Windows driver. Here's a video I made for Microsoft years ago to document the issue.
Thanks, i use win7 64bit, the program i use for serial communication is a c++ (c) i program in vs2013.
Of course when i program the Due(s) or the Uno(s) with Atmel Studio 7, my program is closed so to let the COM ports free and accesible from the IDE.
The problem is (i haven't investigated a lot), some people say the new serial monitor is able to do it, so i have to check.
Otherwise,
i. Both serial Ports don't work together in my case, if the Programming serial resets, i can access the native port but it does not work anymore for serial.
ii. If i disable the programming port and establish communication only with the native then i have to disconnect and reconnect the cable so to make windows identify it, but after this it works ok.
