From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9726] New: Raspberry Pi version B - Problems with UART speed in Buildroot 2016.11.2 and 2017.2
Date: Sat, 11 Mar 2017 13:36:06 +0000 [thread overview]
Message-ID: <bug-9726-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9726
Bug ID: 9726
Summary: Raspberry Pi version B - Problems with UART speed in
Buildroot 2016.11.2 and 2017.2
Product: buildroot
Version: 2016.11
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: wzab01 at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
We have a lab equipped with old Respberry Pi version B.
To allow student to modify the system image without removing and inserting SD
cards (which killed them in a few weeks), we use U-Boot bootloder, patched so
that it passes the boot parameters prepared via a standard RPi firmware.
I wanted to update our environment to Buildroot 2016.11.2 in this semester.
Unfortunately, it appears, that the U-Boot does not set the UART speed properly
in that scenario.
I've meassured the UART speed with the oscilloscope, and it appeared, that it
is equal to ca. 1840 kb/s. However, the kernel uses the correct UART speed -
115.2 kb/s.
I've also tested the operation with the Buildroot 2017.2
In this case things are even more interesting. The U-Boot sets the UART speed
correctly to 115.2 kb/s, but hte kernel works at 921.6 kb/s
What can be the reason of the experienced problems?
Can I easily cure them with the settings done in the config.txt file?
TIA & Regards,
Wojtek
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-03-11 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 13:36 bugzilla at busybox.net [this message]
2017-03-11 20:31 ` [Buildroot] [Bug 9726] Raspberry Pi version B - Problems with UART speed in Buildroot 2016.11.2 and 2017.2 bugzilla at busybox.net
2017-03-11 20:38 ` bugzilla at busybox.net
2017-03-28 20:34 ` bugzilla at busybox.net
2017-03-28 20:41 ` bugzilla at busybox.net
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-9726-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.