mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: RK3588 optee question
Date: Fri, 14 Aug 2026 09:49:40 +0300	[thread overview]
Message-ID: <CAP1tNvT7fBV90WAoXNwuhXes=j--ZshKdJxbOe5_HmMGWmwn_w@mail.gmail.com> (raw)
In-Reply-To: <6a7d6747.1bdbcb37.263332.61abSMTPIN_ADDED_MISSING@mx.google.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 |
>
>



      parent reply	other threads:[~2026-08-14  6:51 UTC|newest]

Thread overview: 9+ 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 [this message]

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='CAP1tNvT7fBV90WAoXNwuhXes=j--ZshKdJxbOe5_HmMGWmwn_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