linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Shyam Saini <mayhs11saini@gmail.com>
Cc: linux-serial@vger.kernel.org,
	Kernelnewbies <kernelnewbies@kernelnewbies.org>,
	linux-usb@vger.kernel.org
Subject: Re: junk character issue on minicom and screen
Date: Mon, 24 Jun 2019 16:23:19 +0200	[thread overview]
Message-ID: <20190624142319.GB14667@localhost> (raw)
In-Reply-To: <CAOfkYf4kCTWdjDJSG0=KgZZG7F+HpE+m+RbgLZ=NeczZ5uWPRw@mail.gmail.com>

On Mon, Jun 24, 2019 at 02:57:34PM +0530, Shyam Saini wrote:
> Hello everyone,
> 
> I'm working on Rockchip rk3399 Nanopc t4 board and I'm trying get
> serial output from board using minicom and my board has baudrate
> 1500000.
> 
> I'm using a usb to serial converter. So, when i power on my board
> minicom starts to give junk characters.
> Minicom version:  2.7.1
> USB driver probed : cp210x
> 
> But when I use the same setup with my colleagues laptop it gives
> correct output (kernel version 4.15.0-52-generic ).
> 
> Note that my colleague and i used same setup
> Same usb driver probed
> Same power adapter
> same usb to serial converter wire
> same minicom version.
> same baudrate
> 
> Other thing which i tried is switching kernel version and it turns out
> that one of the older distro kernel on my system (debian 4.9.0-5-amd64
> ) is working fine and it seems like there is something changed in
> newer kernel vesions.
> Here is the quick summary
> 4.19.0-4-amd64    -> not working
> 4.15.0-52-generic -> working
> 4.9.0-5-amd64      -> working
> 5.2.0-rc4+             -> not working

Thanks for the report. There were some changes between 4.15 and 4.19
related to the line speed handling which may have broken something in
your setup.

Do you know which variant of cp210x you have? Can your provide the
output of lsusb -v?

Also if you can run driver with debugging enabled when connecting the
device and setting the line speed, that may give a clue about what is
going on. For example,

	echo module cp210x =p > /sys/kernel/debug/dynamic_debug/control

Does 115200 bps still work by the way?

Johan

           reply	other threads:[~2019-06-24 14:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOfkYf4kCTWdjDJSG0=KgZZG7F+HpE+m+RbgLZ=NeczZ5uWPRw@mail.gmail.com>]

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=20190624142319.GB14667@localhost \
    --to=johan@kernel.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mayhs11saini@gmail.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;
as well as URLs for NNTP newsgroup(s).