From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Alexander Shiyan" <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: RK3588 optee question
Date: Mon, 17 Aug 2026 06:04:54 +0000 [thread overview]
Message-ID: <20260817060454.xt03PcvtpcY8S4GP130YR12M5V4g9GnubmEk7lb8OMs@z> (raw)
In-Reply-To: <CAP1tNvRLYGdbNX_uK2bqHAOSqPDydYPi25fULCVTXop7VB227w@mail.gmail.com>
On 2026-08-14 11:42, Alexander Shiyan wrote:
> Update:
>
> Issue with RK3588 resolved by adding SPD=opteed to the TF-A build command line
So is everything resolved now?
Sascha
>
> пт, 14 авг. 2026 г. в 09:49, Alexander Shiyan <eagle.alexander923@gmail.com>:
> >
> > Hello, Sascha.
> >
> > With CONFIG_SCRATCH_SIZE=0x100000 compiles fine.
> >
> > Now about the current errors, one build is used for two images for
> > RK3568 and RK3588.
> >
> > RK3568, Rockchip BL31, tee.bin from OPTEE_OS:
> > arm-scmi firmware:scmi.of: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
> > optee: smc_abi: probing for conduit method.
> > optee: smc_abi: revision 4.10 (5c827bf3bc358e9a)
> > psci psci.of: detected version 1.1
> >
> > RK3588, open source TF-A, tee.bin from OPTEE_OS:
> > arm-scmi firmware:scmi.of: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
> > optee: smc_abi: probing for conduit method.
> > WARNING: optee: smc_abi: api uid mismatch
> > ERROR: optee firmware:optee.of: probe failed: Invalid argument
> >
> > Switching to a configuration using Rockchip BL31 with the TEE/OPTEE options
> > currently enabled results in a constant restart of DDR init code, meaning the
> > code never reaches BL31...
> >
> > What else can I watch?
> >
> > Thanks!
> >
> >
> > чт, 13 авг. 2026 г. в 09:42, Sascha Hauer <s.hauer@pengutronix.de>:
> > >
> > > On 2026-08-12 17:44, Alexander Shiyan wrote:
> > > > Hello Sascha.
> > > >
> > > > After enabling CONFIG_ARCH_ROCKCHIP_ATF_PASS_FDT=y the following build
> > > > errors occur:
> > > >
> > > > CC [P] arch/arm/mach-rockchip/rk3588.pbl.o
> > > > In file included from include/linux/array_size.h:6,
> > > > from include/linux/kernel.h:6,
> > > > from /home/ARM64/barebox/arch/arm/include/asm/barebox-arm.h:17,
> > > > from include/mach/rockchip/bootrom.h:9,
> > > > from arch/arm/mach-rockchip/bootrom.c:2:
> > > > include/linux/build_bug.h:100:41: error: static assertion failed:
> > > > "sizeof(structrockchip_scratch_space) <= CONFIG_SCRATCH_SIZE"
> > >
> > > Set CONFIG_SCRATCH_SIZE=0x100000
> > >
> > > Seems we have to look into it to get a sane default.
> > >
> > > 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 |
> > >
> > >
--
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-08-17 6:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 11:51 Alexander Shiyan
2026-08-11 12:19 ` Ahmad Fatoum
2026-08-11 12:54 ` Alexander Shiyan
2026-08-11 14:07 ` Ahmad Fatoum
2026-08-11 14:13 ` Alexander Shiyan
2026-08-12 6:25 ` Sascha Hauer
[not found] ` <6a7c11f4.bd9e1b36.35e6eb.4491SMTPIN_ADDED_MISSING@mx.google.com>
2026-08-12 14:44 ` Alexander Shiyan
2026-08-13 6:41 ` Sascha Hauer
[not found] ` <6a7d6747.1bdbcb37.263332.61abSMTPIN_ADDED_MISSING@mx.google.com>
2026-08-14 6:49 ` Alexander Shiyan
2026-08-14 8:42 ` Alexander Shiyan
2026-08-17 6:04 ` Sascha Hauer [this message]
[not found] ` <6a82a488.478ea94c.10bcfe.7909SMTPIN_ADDED_MISSING@mx.google.com>
2026-08-17 6:14 ` Alexander Shiyan
2026-08-17 7:30 ` Ahmad Fatoum
2026-08-17 12:21 ` Alexander Shiyan
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=20260817060454.xt03PcvtpcY8S4GP130YR12M5V4g9GnubmEk7lb8OMs@z \
--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