From: edrose <edrose@outramresearch.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Raspberry Pi Compute Module 1 mini-UART
Date: Fri, 29 Nov 2019 09:34:56 -0700 (MST) [thread overview]
Message-ID: <1575045296152-0.post@n7.nabble.com> (raw)
In-Reply-To: <1574852196100-0.post@n7.nabble.com>
I've done some more digging, and have made a bit of progress (I think).
After fiddling with the device-tree, I've managed to get the serial port to
show up when running `dm tree`. I appended this block to the end of
bcm2835-rpi-b.dts:
&uart1 {
pinctrl-names = "default";
pinctrl-0 = <&uart1_gpio40>;
status = "okay";
};
And the relevant output of `dm tree is:
Class index Probed Driver Name
-----------------------------------------
...
pinconfig 32 [ + ] pinconfig | | |-- uart0_gpio14
...
pinconfig 42 [ ] pinconfig | | |-- uart1_gpio40
...
serial 0 [ + ] bcm283x_pl | |-- serial at 7e201000
serial 1 [ ] serial_bcm | |-- serial at 7e215040
So that indicates that it sees the serial port, knows which driver to use,
and has the correct address. However it has not probed the device, nor has
it probed the pinconfig that MUXes it to the pin I've set in the dts file.
It also appears to have an index , however specifying CONFIG_CONS_INDEX
doesn't change the port that is used, nor does it change the output of
`dm-tree`.
So I'm still a bit stuck. How do I force uboot to use a different (already
known) serial port for the console? The drivers are there, it sees the port,
it just doesn't want to use it...
--
Sent from: http://u-boot.10912.n7.nabble.com/
next prev parent reply other threads:[~2019-11-29 16:34 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 [this message]
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=1575045296152-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