From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "john@mobius-embedded-systems.co.uk"
<andrew@mobius-embedded-systems.co.uk>,
barebox@lists.infradead.org
Subject: Re: Mini UART support for Raspberry Pi CM3 ?
Date: Tue, 2 Jun 2020 11:54:37 +0200 [thread overview]
Message-ID: <c52611ab-77d3-540c-2bd4-8959dc811510@pengutronix.de> (raw)
In-Reply-To: <cf5280fe-d0e8-5fc9-bada-e95667ead7f9@pengutronix.de>
On 6/2/20 11:43 AM, Ahmad Fatoum wrote:
> On 6/2/20 11:14 AM, john@mobius-embedded-systems.co.uk wrote:
>> Hi
>>
>> I have been trying to get the mini UART (UART1) to work in Barebox on the
>> RPI Compute Module 3+. I already have the changes made in config.txt and
>> this works fine when I boot into the main Linux code. However, in Barebox,
>> the output always comes out on the main UART (UART0) and that is wired to
>> the Bluetooth module on my platform. I have tried modifying the device
>> trees and cannot seem to get any output. I also ensured that I added the
>> RPI CM3 output target as a config in rpi_defconfig.
>>
>> I've tried turning off the PL011 config option and also changing the device
>> tree to reference UART1 and set the chosen stdout-path to point to this
>> UART, but when I do this I just get a lack of any serial output.
>>
>> I am also wanting to use the alternate pins (32 & 33) for UART1, so I am
>> thinking that something else needs to be changed. Has anyone managed to get
>> this to work?
>
> Which barebox version are you on? v2020.03.0 contains a series for mini UART
> support culminating in ab76f9d09d3b ("ARM: rpi: choose miniuart as stdout"),
> which sounds like something you will want to have.
Oh, I see now that this is in since v2019.03.0. I assume you are already
on a newer version?
> Also what's you "Console activation strategy"? (Kconfig symbols
> CONSOLE_ACTIVATE_.*) You'll want to have CONSOLE_ACTIVATE_NONE, so only
> the stdout-path from the device tree is activated by default.
>
> Cheers
> Ahmad
>
>>
>> Regards
>>
>> John
>>
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-06-02 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 9:14 john@mobius-embedded-systems.co.uk
2020-06-02 9:43 ` Ahmad Fatoum
2020-06-02 9:54 ` Ahmad Fatoum [this message]
2020-06-02 9:57 ` john@mobius-embedded-systems.co.uk
2020-06-02 10:11 ` Ahmad Fatoum
2020-06-03 22:14 ` john@mobius-embedded-systems.co.uk
2020-06-04 6:22 ` Ahmad Fatoum
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=c52611ab-77d3-540c-2bd4-8959dc811510@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=andrew@mobius-embedded-systems.co.uk \
--cc=barebox@lists.infradead.org \
/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