From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 520B5C43613 for ; Mon, 24 Jun 2019 14:23:50 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 09998208E4 for ; Mon, 24 Jun 2019 14:23:49 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 09998208E4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92) (envelope-from ) id 1hfPsR-0002B5-Ih; Mon, 24 Jun 2019 10:23:23 -0400 Received: from mail-lj1-f196.google.com ([209.85.208.196]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1hfPsP-0002Az-TY for kernelnewbies@kernelnewbies.org; Mon, 24 Jun 2019 10:23:21 -0400 Received: by mail-lj1-f196.google.com with SMTP id 16so12784630ljv.10 for ; Mon, 24 Jun 2019 07:23:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=hGHNzjTTkC7XSqkNKO0Dj0BBPmg9DOd1ASPbbQfSUIQ=; b=R+SOVYtIjzSchJQLkBSURG4/QsAlnjUh4S7pJzap4QlPq5vT8nEwYvqv5XGLfj0iwR bZF5HHIPsMpiUBP5d5wWThifYo9YIBYOZ5g26c3zRxuudYv00PoVQa0qDNiJA8EX7z6z w+S6cnSzTjn5QvvlP+naSKmB7x1XV+/8ZzKw0osM+2ZNeYEe/z/qZihC+KV5FKcEiCa/ Z0f7SeOoQYdempxRCFrmK9Hnledzym+EBXaGlVXdKYOzCVrhJdm6HtglowP3bXwgyfBL apc5mkBXs7AALbOfuT4jCsPz2bTWbLpcQ9IEIYkwV96BmJlNPmARDS/iFjnBBmAeBuic cjMg== X-Gm-Message-State: APjAAAX21jVJ6ob2d5JMxEkTX+oaMJ6ZQSzOrFm2mttVu4MgSse9nYE7 tzYd/oKr9rhYOoQ+IZmib7U= X-Google-Smtp-Source: APXvYqxQFnqLSlWHbgblNv8zbvjH5AV2mWcwcU0h0Y8jlXvW2YH/P7kGeDL2xDiHxr1mKCDpUpmNMw== X-Received: by 2002:a2e:8793:: with SMTP id n19mr1094836lji.174.1561386199989; Mon, 24 Jun 2019 07:23:19 -0700 (PDT) Received: from xi.terra (c-74bee655.07-184-6d6c6d4.bbcust.telenor.se. [85.230.190.116]) by smtp.gmail.com with ESMTPSA id m17sm1784222lfb.9.2019.06.24.07.23.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Jun 2019 07:23:19 -0700 (PDT) Received: from johan by xi.terra with local (Exim 4.92) (envelope-from ) id 1hfPsN-0003Iw-QI; Mon, 24 Jun 2019 16:23:19 +0200 Date: Mon, 24 Jun 2019 16:23:19 +0200 From: Johan Hovold To: Shyam Saini Subject: Re: junk character issue on minicom and screen Message-ID: <20190624142319.GB14667@localhost> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Cc: linux-usb@vger.kernel.org, linux-serial@vger.kernel.org, Kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org 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 _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies