Hi,
I currently have issues opening a USB Serial Terminal
I tried to follow the following instructions:
https://pynq.readthedocs.io/en/v2.5.1/getting_started/terminal.html
—
The above .html doc had a PuTTY link which I downloaded :
MSI (windows installer) 64bit
putty-64bit-0.74-installer.msi
I then installed this PuTTY 64bit (my Windows 10 is 64bit) package file from the above link
Noticed there are also several other Alternative files listed. It stated that the installer package will provide versions of all of these (except PuTTYtel) but I can download standalone binaries one by one if I prefer.
The one listed within the alternative binary files :
puttytel.exe (a Telnet only client)
I also installed this 64-bit version & tried the same test here
ie followed the following instructions :
In the Windows Device Manager of the control panel.
- Open the Device Manager, expand the Ports menu
- Find the COM port for the USB Serial Port . e.g. COM5
The COM port for me showed COM3
- Open PuTTY
(I opened either PuTTY or PuTTYtel configuration)
Once PuTTY is open, enter the following settings:
- Select serial
- Enter the COM port number
I entered COM3- Enter the serial terminal settings (below)
- Click Open
Full terminal Settings:
- 115200 baud
- 8 data bits
- 1 stop bit
- No Parity
- No Flow Control
Hit Enter in the terminal window to make sure you can see the command prompt:
—-
I had to select first category “Session”
Serial line: COM3
Speed: 115200
Then I selected category “Serial”
- 115200 baud
- 8 data bits
- 1 stop bit
- No Parity
- No Flow Control
After I select ‘open’
Got:
PuTTY or PuTTtel error
Unable to open connection to COM3
Unable to open serial port
I checked the latest driver of Port (COM3) and it reported that the best drivers for my device are already installed.
I also tried disabling the COM3 port and re-enabled it few minutes later & rerun the test but for same PuTTY error as reported above.
Looks like I am stuck here not able to proceed to the next stage…
Any assistance to this matter will be appreciated.
Thanks,
Kevin