From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: v2026.05.0
Date: Wed, 20 May 2026 15:11:44 +0300 [thread overview]
Message-ID: <CAP1tNvQh2dCn9_+dwiOzRgCeNFT6AC9n4rJNC39AB2tNYC_W-w@mail.gmail.com> (raw)
In-Reply-To: <E1wPaJS-00000001yEr-2gmZ@pty.whiteo.stw.pengutronix.de>
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
Everything looks good, but it hangs at this step.
ср, 20 мая 2026 г. в 09:21, Sascha Hauer <s.hauer@pengutronix.de>:
>
> Hi Alexander,
>
> On 2026-05-20 08:15, Alexander Shiyan wrote:
> > Hello Sascha.
> >
> > The first launch of the new release has failed.
> > On the RK3568 platform, BL31 does not start. The size of the final
> > binary has decreased from 1.5 MB
> > to 930 KB - possibly due to the announced compression, but it seems to
> > me that this is too
> > large a reduction...
> > Are there any additional settings/calls required for custom boards in
> > the new release?
>
> No board level adjustments required. I just re-tested the relase on a
> Rock-3a board using rockchip_v8_defconfig. It works here.
>
> The size reduction depends on the size of your firmware binaries. You
> could look at the firmware/*.z files and compare with the original files
> to see if that explains the size reduction. The TF-A and OP-TEE files
> that I use only have around 700KiB in total, so a size reduction of
> 600KiB would be unreasonable in my case.
>
> Do you have any console output to share?
>
> 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 12:13 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 ` Alexander Shiyan [this message]
2026-05-20 13:17 ` v2026.05.0 Sascha Hauer
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=CAP1tNvQh2dCn9_+dwiOzRgCeNFT6AC9n4rJNC39AB2tNYC_W-w@mail.gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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