All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: u-boot@lists.denx.de
Subject: STM32MP1: Adding TF-A causes kernel errors
Date: Thu, 1 Oct 2020 11:52:01 +0200	[thread overview]
Message-ID: <c9623d84-caef-6ca6-a92c-a10ea0981c92@web.de> (raw)
In-Reply-To: <4ccf4dcc-a340-6c34-c5b4-ff06d79aa29d@web.de>

On 30.09.20 11:51, Jan Kiszka wrote:
> [BCC'ed TF-A only, migrating to u-boot, including folks involved there]
>
> On 30.09.20 11:20, Yann GAUTIER wrote:
>> Hi Jan,
>>
>> After discussing with my colleagues, it seems there are 2 issues there.
>> One patch is missing in U-Boot:
>> http://patchwork.ozlabs.org/project/uboot/patch/20200605092244.1.I773bf523d9f4d1a6212483d030e34113b832a779 at changeid/
>>
>
> I can confirm that this resolves the errors I've seen.
>

Picking up again, this time for OP-TEE:
Do I need more patches, wherever, to get that one running as well?

NOTICE:  CPU: STM32MP157AAA Rev.B
NOTICE:  Model: STMicroelectronics STM32MP157C eval daughter on eval mother
NOTICE:  Board: MB1263 Var1 Rev.C-01
NOTICE:  BL2: v2.3():
NOTICE:  BL2: Built : 10:11:55, Sep 30 2020
NOTICE:  BL2: Booting BL32
I/TC: Early console on UART#4
I/TC:
I/TC: Pager is enabled. Hashes: 2144 bytes
I/TC: Pager pool size: 100kB
I/TC: No non-secure external DT
I/TC: Embedded DTB found
I/TC: OP-TEE version: Unknown (gcc version 8.3.0 (Debian 8.3.0-2)) #2 Thu Oct  1 06:53:58 UTC 2020 arm
I/TC: Primary CPU initializing
I/TC: Platform stm32mp1: flavor PLATFORM_FLAVOR - DT stm32mp157c-ev1.dts
I/TC: RCC is non-secure
I/TC: DTB enables console (non-secure)
I/TC: Primary CPU switching to normal world boot


U-Boot 2020.07 (Oct 01 2020 - 06:54:18 +0000)

CPU: STM32MP157AAA Rev.B
Model: STMicroelectronics STM32MP157C eval daughter on eval mother
Board: stm32mp1 in trusted mode (st,stm32mp157c-ev1)
Board: MB1263 Var1.0 Rev.C-01
DRAM:  1 GiB
Clocks:
- MPU : 650 MHz
- MCU : 208.878 MHz
- AXI : 266.500 MHz
- PER : 24 MHz
- DDR : 533 MHz
NAND:  1024 MiB
MMC:   STM32 SD/MMC: 0, STM32 SD/MMC: 1
Loading Environment from EXT4... ** File not found /uboot.env **

** Unable to read "/uboot.env" from mmc0:7 **
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet at 5800a000
Hit any key to stop autoboot:  0
Boot over mmc0!
Saving Environment to EXT4... Unsupported feature metadata_csum found, not writing.

** Unable to write "/uboot.env" from mmc0:7 **
Failed (1)
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:7...
Found U-Boot script /boot/boot.scr
562 bytes read in 26 ms (20.5 KiB/s)
## Executing script at c4100000
57629 bytes read in 38 ms (1.4 MiB/s)
9474560 bytes read in 429 ms (21.1 MiB/s)
4410487 bytes read in 212 ms (19.8 MiB/s)
Kernel image @ 0xc2000000 [ 0x000000 - 0x909200 ]
## Flattened Device Tree blob at c4000000
   Booting using the fdt blob at 0xc4000000
   Loading Ramdisk to cfbcb000, end cffffc77 ... OK
   Loading Device Tree to cfbb9000, end cfbca11c ... OK
OP-TEE: revision 3.10

Starting kernel ...

I/TC: Secondary CI/TC: Secondary CPU 1 switching to normal world boot
E/TC:1   tzc_it_handler:19 TZC permission failure
E/TC:1   dump_fail_filter:417 Overrun violation on filter 0
E/TC:1   dump_fail_filter:420 Permission violation on filter 0
E/TC:1   dump_fail_filter:430 Violation @0xff000000, non-secure privileged read, AXI ID 4a0
E/TC:1   Panic


Besides the U-Boot patch I also have the kernel fixup for gpu_reserved
applied.

Thanks,
Jan

  parent reply	other threads:[~2020-10-01  9:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d643d22d-58c5-1e02-d5be-cb26d3902c37@web.de>
     [not found] ` <fcf2dbe2-c5d8-7042-5c59-ab9bcb1e612d@web.de>
     [not found]   ` <e5533f9b-bf88-526d-5594-a719d928f01c@st.com>
     [not found]     ` <746e3c3b-7b2a-f815-a000-bcb2c31317cb@web.de>
     [not found]       ` <6a493688-6c0f-6e8b-d072-88855236e677@st.com>
2020-09-30  9:51         ` STM32MP1: Adding TF-A causes kernel errors Jan Kiszka
2020-09-30 10:03           ` Marek Vasut
2020-09-30 10:05             ` Jan Kiszka
2020-09-30 13:06             ` Tom Rini
2020-09-30 15:20               ` Etienne Carriere
2020-10-01  9:52           ` Jan Kiszka [this message]
2020-10-05  6:07             ` Jan Kiszka
2020-10-12 22:02               ` Jan Kiszka
2020-10-12 22:02                 ` Jan Kiszka
2020-10-13 11:06                 ` Patrick DELAUNAY
2020-10-13 11:06                   ` Patrick DELAUNAY
2020-10-13 14:26                   ` Jan Kiszka
2020-10-13 14:26                     ` Jan Kiszka
2020-10-15  9:45                     ` Jan Kiszka
2020-10-15  9:45                       ` Jan Kiszka

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=c9623d84-caef-6ca6-a92c-a10ea0981c92@web.de \
    --to=jan.kiszka@web.de \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.