Serial port not found, Quickstart Rev A, Propeller Tool, Linux Mint 17.2 64 bit
mmgood
Posts: 19
I've looked around the forum here, and I've tried all the suggestions I've found that seemed relevant. I've got a Quickstart Rev A with the 10k resistor installed per the Quickstart Guide v1.3. This board was working fine the last time I used it with a Windows machine, but I don't have one available at the moment.
I'm running Linux Mint 17.2 [Cinnamon] 64-bit. Now, FTDI, at http://www.ftdichip.com/Drivers/VCP.htm says "All FTDI devices now supported in Ubuntu 11.10, kernel 3.0.0-19", and my version of Mint is based on Ubuntu 14.04 [LTS], so I haven't done any driver installation. I'm using v1.3.2 Propeller Tool.
When I plug the USB cable in, I get what looks like the typical blue & red LED flashing, followed by a single red pulse a second or so later.
Run --> Identify Hardware reports "No serial ports found".
Here's what I've checked so far:
1) Does Linux see a USB device? Yes:
~ $ lsusb
# [The relevant entry is...]
Bus 004 Device 027: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
2) Does Linux see a tty? Yes, and it's ttyUSB0, as I'd expect. So let's check permissions:
~ $ ls -alF /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Mar 1 01:43 /dev/ttyUSB0
# [root owns it.]
3) OK, so let's give everyone access just in case that's a problem:
~ $ sudo chmod 777 /dev/ttyUSB0
~ $ ls -alF /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Mar 1 01:43 /dev/ttyUSB0
Even after the chmod, Propeller Tool Identify Hardware says "Serial port not found". [And if chmod helped I'd have to do it every time I connected the board, unless there's some tricky way to automate that?]
So I'm stuck. Suggestions from knowledgeable people would be most welcome. Is the 64-bit OS a problem? Should I install a driver?
Mike Butler
I'm running Linux Mint 17.2 [Cinnamon] 64-bit. Now, FTDI, at http://www.ftdichip.com/Drivers/VCP.htm says "All FTDI devices now supported in Ubuntu 11.10, kernel 3.0.0-19", and my version of Mint is based on Ubuntu 14.04 [LTS], so I haven't done any driver installation. I'm using v1.3.2 Propeller Tool.
When I plug the USB cable in, I get what looks like the typical blue & red LED flashing, followed by a single red pulse a second or so later.
Run --> Identify Hardware reports "No serial ports found".
Here's what I've checked so far:
1) Does Linux see a USB device? Yes:
~ $ lsusb
# [The relevant entry is...]
Bus 004 Device 027: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
2) Does Linux see a tty? Yes, and it's ttyUSB0, as I'd expect. So let's check permissions:
~ $ ls -alF /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Mar 1 01:43 /dev/ttyUSB0
# [root owns it.]
3) OK, so let's give everyone access just in case that's a problem:
~ $ sudo chmod 777 /dev/ttyUSB0
~ $ ls -alF /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Mar 1 01:43 /dev/ttyUSB0
Even after the chmod, Propeller Tool Identify Hardware says "Serial port not found". [And if chmod helped I'd have to do it every time I connected the board, unless there's some tricky way to automate that?]
So I'm stuck. Suggestions from knowledgeable people would be most welcome. Is the 64-bit OS a problem? Should I install a driver?
Mike Butler
Comments
My first question is how are you running Propeller Tool 1.3.2 under Linux? It is a Windows exercise only. PropellerIDE, SimpleIDE and BST run under linux. Propeller Tool used to run under older releases of Wine but I haven't been able to make it work under newer versions.
So, whatcha really trying to run?
BST 0.29.4-pre12 runs and finds the Prop after I issue the chmod. Peter, what's your experience like? Any hints on how to set-and-forget the /dev/ttyUSB0 permissions? Do I need to muck with the sudoers file?
Thanks to you both for the prompt and courteous responses.
Glad we could help! We're here to serve and protect (even from sleep deprivation!)
Go have some Propeller fun , now!