All of lore.kernel.org
 help / color / mirror / Atom feed
From: edrose <edrose@outramresearch.co.uk>
To: u-boot@lists.denx.de
Subject: Raspberry Pi Compute Module 1 mini-UART
Date: Tue, 3 Dec 2019 13:14:37 -0700 (MST)	[thread overview]
Message-ID: <1575404077921-0.post@n7.nabble.com> (raw)
In-Reply-To: <1575045296152-0.post@n7.nabble.com>

I've done a little more work on this. I've been able to swap the UART pins
around to a certain extent, but it's still being stubborn. I've been able to
move the console output from the main UART from GPIO14 to GPIO32. I've
somehow also managed to get the main UART to output to both GPIO32 and
GPIO14 simultaneously (although it wouldn't RX anything when that was
happening)! However I still can't get it to simply move the console over to
using the mini-UART.

I've worked out that the serial port seems to be selected by the status of
the pin multiplexers. It checks to see whether GPIO15 is multiplexed to the
main port. If not, it checks to see whether GPIO15 is multiplexed to the
alternate port. I tried forcing it to think that the secondary UART was
multiplexed by forcing a return value in the is_serial_muxed() functions to
be false for the main UART and true for the mini-UART, however it just gives
me a rainbow splash screen of death.

Can I have some pointers as to how I debug what's causing the Pi to fail to
boot when I try forcing the mini-UART? Clearly something is wrong and
causing it to fail. Will it output anything over the early debug UART and,
if so, what values do I need to put into the config for that to work? I
tried adding the register addresses I found in the datasheet, however I
couldn't get anything out of it.

Kindest regards,
Ed



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

      reply	other threads:[~2019-12-03 20:14 UTC|newest]

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

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=1575404077921-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 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.