From: Fabian Pflug <f.pflug@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Cc: maud_spierings@hotmail.com
Subject: Re: [PATCH v2 2/2] ARM: boards: i.MX93: Add NXP FRDM i.MX93 support
Date: Tue, 21 Oct 2025 13:37:04 +0200 [thread overview]
Message-ID: <1a4b90c0b61abfc0ea15f81021656d467ecc818a.camel@pengutronix.de> (raw)
In-Reply-To: <22735bfd-c673-45ec-8b98-4bb4ae6cfad0@pengutronix.de>
Hello Ahmad,
On Tue, 2025-10-21 at 13:11 +0200, Ahmad Fatoum wrote:
> Hello Fabian,
>
> > +static noinline void frdm_imx93_continue(void)
> > +{
> > + void __iomem *base = IOMEM(MX9_UART1_BASE_ADDR);
> > + void __iomem *muxbase = IOMEM(MX9_IOMUXC_BASE_ADDR);
> > +
> > + /* configure LPUART1 TX pin */
> > + writel(0x0, muxbase + 0x184);
> > +
> > + imx9_uart_setup(base);
> > + pbl_set_putc(lpuart32_putc, base + 0x10);
> > + putchar('>');
>
> Do you see the > character on bootup if CONFIG_PBL_CONSOLE is enabled?
> Maud (Cc'd) mentioned on the IRC that the 0x10 offset shouldn't be
> necessary.
>
I did see the > character with (working with a 2025.07.0 barebox here):
>NOTICE: TRDC init done
NOTICE: BL31: v2.12.0(release):v2.12
NOTICE: BL31: Built : 00:00:00, Sep 1 2025
>
barebox 2025.07.0-00002-g597819f252f1 #5 2025-10-21T11:27:47+00:00
Buildsystem version: DistroKit-2019.12.0-741-g6e3d355a
Board: NXP i.MX93 11X11 FRDM board
imx9: Detected IMX9352C (-40 - 105C)
ele: Current lifecycle: OEM Open
ele: Event 0x0287eed6:
ele: IPC = MU APD (0x02)
ele: CMD = ELE_OEM_CNTN_AUTH (0x87)
ele: IND = ELE_NO_AUTHENTICATION_FAILURE (0xee)
ele: STA = ELE_SUCCESS (0xd6)
netconsole: registered as netconsole-1
psci psci.of: detected version 1.1
pca9450-i2c pca9451a0: PMIC Chip ID: 0x9
imx-esdhc 42850000.mmc@42850000.of: registered as mmc0
imx-esdhc 42860000.mmc@42860000.of: registered as mmc1
mdio_bus: miibus0: probed
mdio_bus: miibus1: probed
imx-usb 4c200000.usb@4c200000.of: USB EHCI 1.00
mmc1: detected SD card version 2.0
WARNING: mmc1: GPT:Primary header thinks Alt. header is not at the end of the disk.
WARNING: mmc1: GPT:333863 != 61071359
WARNING: mmc1: GPT:Alternate GPT header not at the end of the disk.
WARNING: mmc1: GPT:333863 != 61071359
WARNING: mmc1: GPT: Use parted to correct GPT errors.
mmc1: registered mmc1
state: New state registered 'state'
state: Using bucket 0@0x00000000
malloc space: 0xbfe80000 -> 0xffcfffff (size 1022.5 MiB)
found force-builtin environment, using defaultenv
multi_bind: creating Fastboot function
g_multi gadget0: Multifunction Composite Gadget
g_multi gadget0: g_multi ready
mmc0: detected MMC card version 5.1
mmc0: registered mmc0.boot0
mmc0: registered mmc0.boot1
mmc0: registered mmc0
detect: No such device
Hit m for menu or any to stop autoboot: 3
barebox@NXP i.MX93 11X11 FRDM board:/ eth0: 1000Mbps full duplex link detected
But there seems to be another Problem. If I enable
CONFIG_DEBUG_LL=y
CONFIG_DEBUG_IMX_UART=y
CONFIG_DEBUG_IMX8M_UART=y
CONFIG_DEBUG_IMX_UART_PORT=1
CONFIG_DEBUG_PBL=y
The PBL fails to start the barebox
>imx9-ddr: DDRINFO: start DRAM init
imx9-ddr: DDRINFO: cfg clk
imx9-ddr: DDRINFO:ddrphy config start
imx-ddr: DRAM PHY training for 3733MTS
imx-ddr: DRAM PHY training for 3733MTS
imx9-ddr: DDRINFO: ddrphy config done
imx9-ddr: DDRINFO: ddrc config start
imx9-ddr: DDRINFO: ddrc config done
romapi: imx93_romapi_load_image: IVT offset on boot device: 0x00008000
romapi: imx93_romapi_load_image: offset in image: 0x00002000
NOTICE: TRDC init done
NOTICE: BL31: v2.12.0(release):v2.12
NOTICE: BL31: Built : 00:00:00, Sep 1 2025
>uncompress.c: memory at 0x80000000, size 0x80000000
mmu: enabling MMU, ttb @ 0xfffe0000
endmem = 0x100000000
arm_mem_scratch = 0xffff8000+0x00008000
arm_mem_stack = 0xffff0000+0x00008000
arm_mem_ttb = 0xfffe0000+0x00010000
arm_mem_barebox_image = 0xffd00000+0x00300000
arm_mem_early_malloc = 0xffce0000+0x00020000
membase = 0x80000000+0x80000000
uncompress.c: uncompressing barebox binary at 0x0000000080223a60 (size 0x000773c0) to 0xffd00000 (uncompressed size:
0x001b81b0)
uncompress.c: jumping to uncompressed image at 0x00000000ffd00000
--> from here on out nothing.
If I remove the 0x10, then there is nothing at all in either case.
> Cheers,
> Ahmad
next prev parent reply other threads:[~2025-10-21 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:42 [PATCH] " Fabian Pflug
2025-05-27 12:23 ` Marco Felsch
2025-05-27 12:37 ` Ahmad Fatoum
2025-10-21 10:59 ` [PATCH v2 0/2] " Fabian Pflug
2025-10-21 10:59 ` [PATCH v2 1/2] common: deep-probe: include of for of_device_id Fabian Pflug
2025-10-21 10:59 ` [PATCH v2 2/2] ARM: boards: i.MX93: Add NXP FRDM i.MX93 support Fabian Pflug
2025-10-21 11:11 ` Ahmad Fatoum
2025-10-21 11:37 ` Fabian Pflug [this message]
2025-10-21 11:43 ` Ahmad Fatoum
2025-10-21 11:53 ` Fabian Pflug
2025-10-21 11:58 ` Maud Spierings
2025-10-21 18:01 ` [PATCH v2 0/2] " Maud Spierings
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=1a4b90c0b61abfc0ea15f81021656d467ecc818a.camel@pengutronix.de \
--to=f.pflug@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=maud_spierings@hotmail.com \
/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