Writing to sram causes kernel panic

tianwei — Mon, 04 Sep 2023 08:22:30 GMT

resetting ...
NOTICE: S32 TF-A: s32_system_reNOTICE: Reset status: Destructive Reset (RUN)
NOTICE: BL2: v2.5(release):
NOTICE: BL2: Built : 14:12:45, Sep 4 2023
NOTICE: BL2: Booting BL31
NOTICE: Entry point address = 0xff800000
NOTICE: SPSR = 0x3cd
NOTICE: BL31: v2.5(release):
NOTICE: BL31: Built : 14:12:52, Sep 4 2023
NOTICE: Entry point address = 0xffaa0000
NOTICE: SPSR = 0x3c5

U-Boot 2020.04 (Sep 04 2023 - 14:12:25 +0800)

CPU: NXP S32G399A rev. 1.1
Model: NXP S32G399A-RDB3
DRAM: 3.5 GiB
MMC: FSL_SDHC: 0
Loading Environment from SPI Flash... SF: Detected mx25uw51245g with page size 256 Bytes, erase size 64 KiB, total 64 MiB
OK
Using external clock for PCIe0, CRNS
Frequency 100Mhz configured for PCIe0
Configuring PCIe0 as SGMII(x2) [XPCS0 1G, XPCS1 1G]
XPCS0 power-up good failed
XPCS1 power-up good failed
XPCS0 pre power-up soft reset failed
XPCS0 power-up failed
XPCS1 pre power-up soft reset failed
XPCS1 power-up failed
Using external clock for PCIe1, CRNS
Configuring PCIe1 as RootComplex(x2)
WARNING: Failed to lock PCIe1 MPLLs
PCIe0: Not configuring PCIe, PHY not configured
PCIe1: Not configuring PCIe, PHY not configured
In: serial@401C8000
Out: serial@401C8000
Err: serial@401C8000
Board revision: Revision Unknown: (0x26a)
Net: EQOS phy: sgmii @ 14
ERROR: Failed to change the clock source of mux 1 to 40 (CGM = 0x4053c000)
ERROR: Failed to enable clock: 10116
ERROR: Failed to enable 18 clock
Failed to set GMAC TX frequency
ERROR: Failed to change the clock source of mux 2 to 41 (CGM = 0x4053c000)
ERROR: Failed to enable clock: 10117
ERROR: Failed to enable 17 clock
Failed to enable rx_sgmii clock
ERROR: Failed to change the clock source of mux 1 to 40 (CGM = 0x4053c000)
ERROR: Failed to enable clock: 10116
ERROR: Failed to enable 18 clock
Failed to enable tx_sgmii clock

Warning: eth_eqos (eth0) using random MAC address - ce:a6:2c:02:6b:e6
eth0: eth_eqos
Hit any key to stop autoboot: 0
=>
=>
=>
=> mw.b 0x34000000 0 1
=> boot
Setting bus to 0
Booting M7 from flash...
Booting A53 from flash...
device 0 offset 0x900000, size 0x100000
SF: 1048576 bytes @ 0x900000 Read: OK
device 0 offset 0xa00000, size 0x1600000
SF: 23068672 bytes @ 0xa00000 Read: OK
device 0 offset 0x2000000, size 0x2000000
SF: 33554432 bytes @ 0x2000000 Read: OK
## Flattened Device Tree blob at 80000000
Booting using the fdt blob at 0x80000000
Loading Ramdisk to fc1ff000, end fe1ff000 ... OK
Loading Device Tree to 00000000ffdbc000, end 00000000ffdc977f ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.10.90-v1.0.0-rt60 (root@14851fee6bd7) (aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #21 SMP PREEMPT Fri Sep 1 10:55:24 CST 2023
[ 0.000000] Machine model: Freescale S32G399A
[ 0.000000] earlycon: linflex0 at MMIO 0x00000000401c8000 (options '115200n8')
[ 0.000000] printk: bootconsole [linflex0] enabled
[ 0.000000] SError Interrupt on CPU0, code 0xbf000002 -- SError
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.10.90-v1.0.0-rt60 #21
[ 0.000000] Hardware name: Freescale S32G399A (DT)
[ 0.000000] pstate: 60000085 (nZCv daIf -PAN -UAO -TCO BTYPE=--)
[ 0.000000] pc : setup_arch+0x164/0x590
[ 0.000000] lr : setup_arch+0x15c/0x590
[ 0.000000] sp : ffffffc010c93ef0
[ 0.000000] x29: ffffffc010c93ef0 x28: 0000000080d30018
[ 0.000000] x27: 00000000ffaa50cc x26: 0000000000000000
[ 0.000000] x25: 00000000ffb1b140 x24: 00000000ffde8f18
[ 0.000000] x23: ffffffc010d35000 x22: ffffffc010c9e300
[ 0.000000] x21: fffffffefe7bc08c x20: ffffffc010ce6f88
[ 0.000000] x19: ffffffc010000000 x18: 0000000000000010
[ 0.000000] x17: 0000000000001400 x16: 0000000000001c00
[ 0.000000] x15: ffffffc010c9e768 x14: ffffffffffffffff
[ 0.000000] x13: 0000000000000000 x12: 0000000000000008
[ 0.000000] x11: 0000000000000007 x10: 0101010101010101
[ 0.000000] x9 : ffffffffffffffff x8 : 0000000000000008
[ 0.000000] x7 : 0000000000000007 x6 : 0080000000000080
[ 0.000000] x5 : 8000000000008000 x4 : 0000000000000042
[ 0.000000] x3 : 0000000000000063 x2 : 0000000000000042
[ 0.000000] x1 : 0000000000000000 x0 : 0000000000000080
[ 0.000000] Kernel panic - not syncing:
[ 0.000000] Asynchronous SError Interrupt
[ 0.000000] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

After I wrote 0 in the 34000000 address in uboot, panic occurred when starting kernel.

I am using BSP32

Re: Writing to sram causes kernel panic

nxf92355 — Tue, 05 Sep 2023 10:45:19 GMT

Hi chu tianwei

Hope you are doing well

I think there may reserved memory from 0x34000000. do you have spesific use case of use at 0x34000000 ? . can you try with 0x34100000

and also use dcache off.

can you try below

=> dcache off

=> mw.b 0x34100000 0 1

=> boot

Regards ,

Tushar

topic Re: Writing to sram causes kernel panic in S32 SDK

Writing to sram causes kernel panic

Re: Writing to sram causes kernel panic