From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jg3d1-0007Hk-Ol for barebox@lists.infradead.org; Tue, 02 Jun 2020 09:54:41 +0000 From: Ahmad Fatoum References: <00a601d638be$2f10f330$8d32d990$@mobius-embedded-systems.co.uk> Message-ID: Date: Tue, 2 Jun 2020 11:54:37 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Mini UART support for Raspberry Pi CM3 ? To: "john@mobius-embedded-systems.co.uk" , barebox@lists.infradead.org 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