From: Johan Hovold <johan@kernel.org>
To: David Frey <dpfrey@gmail.com>
Cc: "Alex Villacís Lasso" <a_villacis@palosanto.com>,
linux-usb@vger.kernel.org, "Pho Tran" <pho.tran@silabs.com>,
"Tung Pham" <tung.pham@silabs.com>,
Hung.Nguyen@silabs.com
Subject: Re: cp210x module broken in 5.12.5 and 5.12.6, works in 5.11.21 (with bisection)
Date: Mon, 7 Jun 2021 18:52:59 +0200 [thread overview]
Message-ID: <YL5O6/GrlnpNwGjT@hovoldconsulting.com> (raw)
In-Reply-To: <CAAvkfd-o+g2_uc-HqK8svrU_E3NB1m03md8J_F_eTc8pDkXmdQ@mail.gmail.com>
On Mon, Jun 07, 2021 at 09:44:59AM -0700, David Frey wrote:
> On Sat, Jun 5, 2021 at 3:13 AM Johan Hovold <johan@kernel.org> wrote:
> >
> > I found an errata for A01 on here, but no mention if this particular
> > bug:
> >
> > https://www.silabs.com/documents/public/pcns/190315471-CP2102N-Product-Revision-with-Datasheet-and-Errata-Update.pdf
>
> I believe this document has some more errata details:
> https://www.silabs.com/documents/public/errata/cp2102n-errata.pdf'
Thanks for the link.
This seems to confirm that this is a known issue with A01 that was fixed
in A02:
3.6 CP2102N_E104 – IO Exception in .NET Applications when
Manually Controlling RTS
The CP2102N uses the incorrect byte of the SERIAL_HANDFLOW
structure
(https://msdn.microsoft.com/en-us/library/windows/hard-
ware/jj680685(v=vs.85).aspx) to control the RTS signal. Instead
of looking at the first byte of FlowReplace, the device is
reading the first byte of the XonLimit and interpreting that as
the first byte of FlowReplace.
Applications written in .NET set the Xon/Xoff limits to 160,
equal to 0xA0, which the CP2102N interprets as hardware flow
control, and so it returns an error when manually setting RTS.
Now we just need to figure out how to determine the firmware revision.
Johan
next prev parent reply other threads:[~2021-06-07 16:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 17:38 cp210x module broken in 5.12.5 and 5.12.6, works in 5.11.21 (with bisection) Alex Villacís Lasso
2021-06-01 7:50 ` Johan Hovold
2021-06-01 14:51 ` Alex Villacís Lasso
2021-06-01 15:40 ` Johan Hovold
2021-06-01 17:18 ` Alex Villacís Lasso
2021-06-02 14:50 ` Johan Hovold
2021-06-02 15:54 ` Alex Villacís Lasso
2021-06-04 15:42 ` Johan Hovold
2021-06-04 18:25 ` Alex Villacís Lasso
2021-06-05 10:24 ` Johan Hovold
2021-06-05 10:54 ` Johan Hovold
2021-06-04 23:16 ` David Frey
2021-06-05 10:13 ` Johan Hovold
2021-06-07 15:16 ` Alex Villacís Lasso
2021-06-07 16:45 ` Johan Hovold
2021-06-07 16:44 ` David Frey
2021-06-07 16:52 ` Johan Hovold [this message]
2021-06-07 18:02 ` David Frey
2021-06-07 20:44 ` David Frey
2021-06-07 23:50 ` Alex Villacís Lasso
2021-06-08 9:10 ` Tung Pham
2021-06-08 9:52 ` Johan Hovold
2021-06-08 9:41 ` Johan Hovold
2021-06-09 16:15 ` [PATCH] USB: serial: cp210x: fix CP2102N-A01 modem control Johan Hovold
2021-06-09 17:00 ` Alex Villacís Lasso
2021-06-10 7:23 ` Johan Hovold
2021-06-10 14:55 ` Alex Villacís Lasso
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=YL5O6/GrlnpNwGjT@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=Hung.Nguyen@silabs.com \
--cc=a_villacis@palosanto.com \
--cc=dpfrey@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=pho.tran@silabs.com \
--cc=tung.pham@silabs.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox