public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: edrose <edrose@outramresearch.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Raspberry Pi Compute Module 1 mini-UART
Date: Mon, 25 Nov 2019 13:47:56 -0700 (MST)	[thread overview]
Message-ID: <1574714876353-0.post@n7.nabble.com> (raw)

Hi,

I'm working on a project that uses the Raspberry Pi Compute Module 1. Much
like the CM 3, the CM 1 has two UART interfaces - the main UART at ttyAMA0,
and a second "mini-UART" at ttyS0. The project uses the main UART since it
works better at high speeds, so the console has been bumped over to the
mini-UART. This works fine for kernel messages and as a TTY console for
logging in and interacting with the device, however I've been unable to get
u-boot to present it's console over the mini-UART.

I've worked deep enough into this to know that u-boot doesn't use the device
tree that is set-up in config.txt, so the parameters that I've put in there
to activate and remap the mini-UART (UART1 in dts files) to pins 40/41
doesn't apply to u-boot. I'm using the bcm2835-rpi-b dts file currently
since it's the best fit for the hardware, but it leaves the mini-UART port
disabled. I've tried playing around with the dts files to enable/remap the
mini-UART port however I've been unsuccessful.

Can anyone give me any pointers as to how I modify the dts files to enable
and map the second UART for u-boot to be able to use it?

Kindest regards,
Ed



--
Sent from: http://u-boot.10912.n7.nabble.com/

             reply	other threads:[~2019-11-25 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 20:47 edrose [this message]
2019-11-26 18:09 ` [U-Boot] Raspberry Pi Compute Module 1 mini-UART Matthias Brugger
2019-11-27 10:56   ` edrose
2019-11-29 16:34     ` edrose
2019-12-03 20:14       ` edrose

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=1574714876353-0.post@n7.nabble.com \
    --to=edrose@outramresearch.co.uk \
    --cc=u-boot@lists.denx.de \
    /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