Parallax Serial Terminal went terminal...
homosapien
Posts: 147
Hi folks, hoping someone can help me out with an issue with the Parallax Serial Terminal.
I have been using PST successfully as a debugging tool for awhile, but yesterday PST started acting weird. Instead of printing numbers and letters/strings, the terminal is now showing nonsense characters, as if the baudrate settings are not in sync, but they are (ie I use "start(19200)" in the object to start the PST.spin object and make sure the terminal window has the same 19200 baudrate selected).
I tried using a spare prop-plug, thinking the FTDI chip on the plug might be the issue, but got the same problem.
I then tried the same prop-plug,and same Propeller Proto Board on another computer (running Windows XP) - The PST worked fine. So, it appeared to me that the issue was in the original computer I was using.
I used Windows software remove program (running Windows 7 as OS) to remove the FTDI driver (and Parallax driver) and re-downloaded and installed from Parallax website. Still had a the bad communication issue.
Removed and re-installed the Propeller tool as well as Parallax Serial Terminal.exe. Still the bad communication issue.
Program downloads work fine, "Identify Hardware" button in the Prop IDE returns correct "Propeller Chip version 1..." so it seems that communication via the IDE is normal.
Anyone have any suggestions, ideas?
Thanks.
I have been using PST successfully as a debugging tool for awhile, but yesterday PST started acting weird. Instead of printing numbers and letters/strings, the terminal is now showing nonsense characters, as if the baudrate settings are not in sync, but they are (ie I use "start(19200)" in the object to start the PST.spin object and make sure the terminal window has the same 19200 baudrate selected).
I tried using a spare prop-plug, thinking the FTDI chip on the plug might be the issue, but got the same problem.
I then tried the same prop-plug,and same Propeller Proto Board on another computer (running Windows XP) - The PST worked fine. So, it appeared to me that the issue was in the original computer I was using.
I used Windows software remove program (running Windows 7 as OS) to remove the FTDI driver (and Parallax driver) and re-downloaded and installed from Parallax website. Still had a the bad communication issue.
Removed and re-installed the Propeller tool as well as Parallax Serial Terminal.exe. Still the bad communication issue.
Program downloads work fine, "Identify Hardware" button in the Prop IDE returns correct "Propeller Chip version 1..." so it seems that communication via the IDE is normal.
Anyone have any suggestions, ideas?
Thanks.
Comments
Did you use the same Propeller program when testing on both computers? The same Propeller board?
If you write to the wrong memory location in the Prop you can change the clock settings without realizing it. The changed clock settings will mess up serial communication. I'd make sure and test a very simple program using a serial object on the Prop to make sure the clock setting aren't the problem.
Did you define the clock settings in then CON section?
Thanks Duane