Only get duplex Serial1 communication to work properly when modifying inttab by commenting the ttyATH0 line.Maybe some of the tty experts can explain it to me. I still don't understand how it all plays together.
The answer to your question is quite clear: If the Bridge is running while your Python program is running, there is no mechanism to decide whether your Python program or the Bridge gets incoming data on the serial port resulting in data loss.
Edit: No, it's not the bridge, because calling /usr/bin/kill-bridge right before starting my python script does not solve my problem. Looks like I really have to get rid of the "ash --login".
I have not found where bridge.py is being started in the system - given what I am trying to do I prefer to completely defuse the Bridge/Process/etc code and simply let the 32U4 and the AR9331 talk directly via ttyATH0/Serial1.TIAsteve at donegan dot org
... // Bridge startup: // - If the bridge is not running starts it safely stream.print(CTRL_C); delay(250); stream.print(F("\n")); delay(250); stream.print(F("\n")); delay(500); // Wait for OpenWRT message // "Press enter to activate console" stream.print(F("run-bridge\n")); delay(500); dropAll();...
Thank you Priority. So if I do not include bridge.h/do any 32U4 side bridge related calls, and comment out the serial port in inittab then no process should run on either processor which uses Serial1? ....Thanks! And Merry Christmas!