From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 210351] New: Wrong setting baudrate for FTDI chip FT230X
Date: Wed, 25 Nov 2020 05:14:18 +0000 [thread overview]
Message-ID: <bug-210351-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=210351
Bug ID: 210351
Summary: Wrong setting baudrate for FTDI chip FT230X
Product: Drivers
Version: 2.5
Kernel Version: all
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: svv75@mail.ru
Regression: No
Hello!
I have three chips FT232BL, FT232R and FT230X. I am using them as a VCP on
Linux (Ubuntu 18.04). According to Application Note AN_120 from FTDI, the baud
rate generators of all these chips have 8 sub-integer prescalers. Divisor =
3000000 / baudrate = n + 0, 0.125, 0.25, 0.375, 0.5, 0.625, 0.75, 0.875. Where
n is an integer between 2 and16384.
So, I measured real baud rates, for n = 2 in combination with all possible
sub-integer prescalers.
And it turned out that all sub-integer prescalers worked for FT232BL, FT232R
chips.
And for the FT230X, only a few prescalers work correctly. The following shows
exactly how prescalers behave:
0 - correct
0.125 - correct
0.25 - correct
0.375 - WRONG! (works like 0.125)
0.5 - correct
0.625 - WRONG! (works like 0.5)
0.75 - WRONG! (works like 0.25)
0.875 - WRONG! (works like 0.125)
The same for the other n.
I think it is a driver problem, it initializes the sub-integer prescaler
incorrectly. Since under Windows FT230X works fine with all sub-integer
prescalers.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-11-25 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 5:14 bugzilla-daemon [this message]
2021-01-08 10:37 ` [Bug 210351] Wrong setting baudrate for FTDI chip FT230X bugzilla-daemon
2021-01-08 11:37 ` bugzilla-daemon
2021-01-08 13:30 ` bugzilla-daemon
2021-01-26 14:09 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-210351-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.