From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Alexander Shiyan" <eagle.alexander923@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: v2026.05.0
Date: Wed, 20 May 2026 13:17:13 +0000 [thread overview]
Message-ID: <E1wPgnR-0000000264u-3MOI@pty.whiteo.stw.pengutronix.de> (raw)
In-Reply-To: <CAP1tNvQh2dCn9_+dwiOzRgCeNFT6AC9n4rJNC39AB2tNYC_W-w@mail.gmail.com>
On 2026-05-20 15:11, Alexander Shiyan wrote:
> Here is output with lowlevel debug:
> DDR 03ea844c5d typ 24/09/03-10:42:57,fwver: v1.23
> In
> ...
> out
> >rockchip-dmc: rockchip_sdram_size(reg2=1000ea01, reg3=30000031)
> rockchip-dmc: rank 2 cs0_col 10 cs1_col 10 bk 3 cs0_row 17 cs1_row 17
> bw 2 row_3_4 0
> rockchip-dmc: rk3568_ram_sizes() = 8589934592
> mmu: enabling MMU, ttb @ 0xedf80000
> mmu: __arch_remap_range: 0x00000000+0x8000000000 type UNCACHED
> mmu: __arch_remap_range: 0x8000000000+0x8000000000 type UNCACHED
> mmu: __arch_remap_range: 0x00a00000+0xef600000 type RWX
> mmu: __arch_remap_range: 0xee000000+0x2000000 type FAULT
> mmu: __arch_remap_range: 0x00b00000+0x60000 type RWX
Damn. I introduced this:
pbl_malloc_init(membase[0] + memsize[0] - PBL_MALLOC_SIZE, PBL_MALLOC_SIZE);
This exactly ends up in the area marked as FAULT above (reserved for
OP-TEE).
Try this:
pbl_malloc_init(membase[0] + memsize[0] - OPTEE_SIZE - PBL_MALLOC_SIZE,
PBL_MALLOC_SIZE);
You have XZ as image compression, right?
The rockchip_v8_defconfig uses LZ4 which doesn't need any dynamic memory
for decompression. I tested with XZ as well, but the configuration I
used for this test doesn't have OP-TEE enabled, so the faulting area was
not there.
Sascha
--
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 |
next prev parent reply other threads:[~2026-05-20 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 19:34 v2026.05.0 Sascha Hauer
2026-05-20 5:15 ` v2026.05.0 Alexander Shiyan
2026-05-20 6:21 ` v2026.05.0 Sascha Hauer
2026-05-20 11:16 ` v2026.05.0 Alexander Shiyan
2026-05-20 12:40 ` v2026.05.0 Sascha Hauer
2026-05-20 12:11 ` v2026.05.0 Alexander Shiyan
2026-05-20 13:17 ` Sascha Hauer [this message]
2026-05-20 13:27 ` v2026.05.0 Alexander Shiyan
2026-05-20 13:38 ` v2026.05.0 Ahmad Fatoum
2026-05-20 13:42 ` v2026.05.0 Alexander Shiyan
2026-05-20 13:43 ` v2026.05.0 Ahmad Fatoum
2026-05-20 13:47 ` v2026.05.0 Alexander Shiyan
2026-05-22 11:00 ` v2026.05.0 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=E1wPgnR-0000000264u-3MOI@pty.whiteo.stw.pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.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