Quickstart and Linux: FTDI FT231x vs FT232R
prof_braino
Posts: 4,313
I'm talking to a quickstart using minicom terminal program.
Quickstart boards rev A with FTDI FT232R USB UART [0600] work as always.
Quickstart boards rev B with FT231X USB UART [1000] will display as normal, but do not respond to terminal input. The quickstart LEDs don't even flash.
What am I doing wrong? Do I have to create a lockfile or something? Is this something to do with running a 64 bit linux instead of 32 bit?
Thanks!
Answer 1 - if minicom worked with Quickstart Rev A but not with Rev B:
The sudo here allows saving the default configuration file.
Answer 2 - if minicom won't start and gives a permissions error :
Quickstart boards rev A with FTDI FT232R USB UART [0600] work as always.
Quickstart boards rev B with FT231X USB UART [1000] will display as normal, but do not respond to terminal input. The quickstart LEDs don't even flash.
What am I doing wrong? Do I have to create a lockfile or something? Is this something to do with running a 64 bit linux instead of 32 bit?
Thanks!
Answer 1 - if minicom worked with Quickstart Rev A but not with Rev B:
sudo minicom /dev/ttyUSB0 ctl^a z o (cOnfigure) serial port setup F - Hardware Flow Control : No G - Software Flow Control : No
The sudo here allows saving the default configuration file.
Answer 2 - if minicom won't start and gives a permissions error :
sudo addgroup $USERNAME dialout
Comments
What does the command below return? when the Board is connected versus when it is removed? Does it show evaluating as a COM port or something different?
dmesg | grep attached
You might also need to chmod the attached device ....
i.e.
If my USB enumerated to /dev/ttyUSB0 then .....
For proper permissions you may need to chmod /dev/ttyUSB0 for READ on some systems as a root user.
save as default. minicom now responds as before.
I think the difference is the FT231x supports DTR, and the FT232R uses ...?
If you add yourself to group uucp (or whatever the group of /dev/ttyUSB0 is, obtained by ls -l /dev/ttyUSB0), you won't need sudo:
I'm using the standard drivers that come with linux by default. No additional driver installation is needed (so far).
Same whether connected or removed.
So these premissions need Read added to Group and everyone?
On Ubuntu/Mint, the group is dialout; and I did:
I've not seen the gpasswd command in the context of fixes to /dev/ttyUSB0. Is gpasswd doing the same as addgroup, or is there another permission involved?