Update propellerdevice.cpp

[dude789]

To use the alternative Serial Port connection attached in the Datasheet.

[PropGit]

Thanks @dude789

We specifically ignore tty ports because they cause problems communicating with the Propeller, particularly on Mac platforms if I remember correctly. These two articles explain what we think is the reason for the symptom we've seen, and the reason we exclude tty from the port options in order to provide the user with a single choice per port that works, cu ports.

If you have other evidence, please explain for consideration.

https://stackoverflow.com/questions/37688257/choosing-between-dev-tty-usbserial-vs-dev-cu-usbserial

https://stackoverflow.com/questions/8632586/macos-whats-the-difference-between-dev-tty-and-dev-cu

[dude789]

Hi, i use the originally RS-232 port on my PC (Linux) to communicate with the Propeller Chip, without a USB to serial converter and it works for me. The device called /dev/ttyS0.

[PropGit]

Interesting. Thanks for letting us know. Does a /dev/cu port also appear for that port?

[dude789]

No.