topic Re: kernel panic when booting the s32v234sbc in MBDT for VISION

kernel panic when booting the s32v234sbc

nskang — Wed, 18 Mar 2020 08:18:33 GMT

Sorry, i'm not good at using English.

I have a s32v234sbc package and i am trying to boot it with yocto image.

(* VisionSDK_S32V2_RTM_1_5_0_img_yocto.tar.gz)

Used image is yocto origianl image(Image, fsl-s32v234sbc.dtb, u-boot.s32)

however, always kernel panic occurs as below.

please, let me know how to figure out it.

* i already check that kernel panic occurs when loading the seq.ko module.

---------------------------------------------------------------------------------------

U-Boot 2018.07+g21d6118 (Sep 24 2019 - 18:09:50 +0000)

CPU: NXP S32V234 V2.0 at 1000 MHz
Reset cause: Software Functional reset
Board: mpxs32v234-R2
I2C: ready
DRAM: 2 GiB
RTC: PCF85263
All (4) cores are up.
MMC: FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Failed (-5)

Forcing PCIe to Gen1 operation
phy link never came up
DEBUG_R0: 0x007dc100, DEBUG_R1: 0x08200000
In: serial
Out: serial
Err: serial
** Unable to read file cse.bin **
CSE firmware loading failed
Failed to initialize CSE3 security engine
Net: FEC
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
8767496 bytes read in 416 ms (20.1 MiB/s)
Booting from mmc ...
21981 bytes read in 18 ms (1.2 MiB/s)
## Flattened Device Tree blob at 82000000
Booting using the fdt blob at 0x82000000
reserving fdt memory region: addr=80000000 size=10000
Loading Device Tree to 000000009fff7000, end 000000009ffff5dc ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 4.19.31-rt18+g9efc51a (oe-user@oe-host) (gcc version 6.3.1 20170509 (Linaro GCC 6.3-2017.06~dev)) #1 SMP Tue Sep 24 18:10:27 UTC 2019
[ 0.000000] Machine model: Freescale S32V234
[ 0.000000] cma: Reserved 32 MiB at 0x00000000fe000000
[ 0.000000] random: get_random_bytes called from start_kernel+0xa4/0x400 with crng_init=0
[ 0.000000] percpu: Embedded 22 pages/cpu @(____ptrval____) s49688 r8192 d32232 u90112
[ 0.000000] Detected VIPT I-cache on CPU0

INIT: version 2.88 booting
[ 1.241503] random: fast init done
[ 1.430363] apex: loading out-of-tree module taints kernel.
[ 1.437668] APEX kernel module - IRQ 34, ID 0, 1 devices loaded.
[ 1.443459] APEX kernel module - IRQ 35, ID 1, 2 devices loaded.
[ 1.687735] Managing the chunk [0x89000000 - 0x8fd00000]
[ 1.687735] (align = 0x1000, id = 0, autobalance = 1, init = 0)
[ 1.698852] Managing the chunk [0xc9000000 - 0xd0000000]
[ 1.698852] (align = 0x1000, id = 1, autobalance = 1, init = 0)
[ 1.714181] Managing the chunk [0x3e801000 - 0x3eb00000]
[ 1.714181] (align = 0x8, id = 2, autobalance = 0, init = 1)
[ 1.724960] Initializing '3e801000.oalsramS'
[ 1.774133] Managing the chunk [0x3eb00000 - 0x3ec00000]
[ 1.774133] (align = 0x8, id = 3, autobalance = 0, init = 1)
[ 1.784914] Initializing '3eb00000.oalsramM'
[ 1.900160] CSI: driver ready -> CSI0 = enabled | CSI1 = enabled.
[ 1.983458] Load sbc board configuration
[ 1.987307] CGD: ready.
[ 2.095025] SError Interrupt on CPU2, code 0xbf000002 -- SError
[ 2.095028] CPU: 2 PID: 763 Comm: insmod Tainted: G O 4.19.31-rt18+g9efc51a #1
[ 2.095030] Hardware name: Freescale S32V234 (DT)
[ 2.095031] pstate: 20000005 (nzCv daif -PAN -UAO)
[ 2.095033] pc : SeqRamsInit+0x5c/0x130 [seq]
[ 2.095034] lr : SEQ_DRV_Setup+0x30/0xb0 [seq]
[ 2.095035] sp : ffffff800b4ebb30
[ 2.095037] x29: ffffff800b4ebb30 x28: 000000000000002f
[ 2.095041] x27: ffffffc07aedddd0 x26: ffffff8000c30550
[ 2.095044] x25: ffffff8000c30188 x24: ffffff80088e0000
[ 2.095047] x23: ffffff8000c30500 x22: ffffff8000c30000
[ 2.095051] x21: ffffff8000c30000 x20: ffffff8000c30000
[ 2.095054] x19: ffffff8000c30808 x18: ffffffffffffffff
[ 2.095057] x17: 0000000000000000 x16: 0000000000000000
[ 2.095061] x15: 0000000000000400 x14: 0000000000000400
[ 2.095064] x13: 0000000000000000 x12: 0000000000000001
[ 2.095067] x11: 0000000000026374 x10: 0000000001077b93
[ 2.095071] x9 : 0000000000000138 x8 : ffffffc07dfce040
[ 2.095074] x7 : 0000000000000000 x6 : ffffff8008895368
[ 2.095077] x5 : 0000000000000000 x4 : 0000000000000000
[ 2.095081] x3 : ffffff8008a45000 x2 : ffffff8000c30000
[ 2.095084] x1 : ffffff8008a66000 x0 : ffffff8008a65017
[ 2.095088] Kernel panic - not syncing: Asynchronous SError Interrupt

Re: kernel panic when booting the s32v234sbc

Daniel_Popa — Wed, 18 Mar 2020 11:55:43 GMT

Hi stefans‌

FYI.

Do you know what might be wrong here?

Thank you!

Daniel

Re: kernel panic when booting the s32v234sbc

stefans — Fri, 20 Mar 2020 11:01:51 GMT

Root cause might be related to missing cse.bin. If the device is security enabled (which is true for latest SBCs) seq.ko will fail loading.

Best regards,

Stefan.

Re: kernel panic when booting the s32v234sbc

nskang — Mon, 23 Mar 2020 02:59:18 GMT

Thanks.

i got it your said's mean.

but, i'm not sure that what shall i do.

i already said that i used yocto binary image from web.

how can i solve this problem.?

Re: kernel panic when booting the s32v234sbc

nskang — Wed, 25 Mar 2020 06:55:50 GMT

Dear Stefan Schwarz

many thanks for your answer.

I'm in a trouble still playing demo with SBC-S32V234 board.

i can't anything with it.

i hope that you assist me to solve my issue.

Issue 1.

As you know My SBC-S32V234 board can't boot with Yocto binary Image which is downloaded from NXP web.

but i can't make cse.bin file because i only have a u-boot.s32(Yocto) Image not Yocto source code.

so, if you know that how to change device security option from enable to disable. please let me know. i will try.

Issue 2.

Always SBC-S32V234 board hangs with "Buffer overrun" message when executing a sample application(elf)

System Infomation

* u-boot.s32 : v2018.07_bsp23.0

kernel : v4.19.59_bsp23.0

10 kernel modules (viulite, jpegdcd,cam,csi,apex,h264dcd,h264enc,fdma,oal_cma,seq) are built manually

* S32DS_Vision_Linux_v2.0_b170913.bin

* application : isp_sonyimx224_h264enc_linux.elf (S32DS Project from Sample)

root@s32v234sbc:~# ./my_isp_sonyimx224_h264enc_linux.elf

**************************************************************
** H264 encoder demo
** Description:
** o Sony imx224 camera (on MipiCsi_0) expected as image input.
** o ISP generates histogram for AEC, converts pixel format from
** RGB to YUV420 and trigers H264 encoding.
** o H264Encoded stream data are located in SRAM.
**
** Usage:
** o 1 parameter: number of frames to be captured and encoded.
** o no params => 200 frames will be captured and encoded.
**
**************************************************************
**
** 200 frames will be encoded.
**
**************************************************************

Press Ctrl+C to terminate the demo.
[ 77.598909] Probing I2c client @ 0x1a on I2C bus #0.
[ 77.603780] Generic camera I2c driver added successfully.
VMAX = 745, Lines = 729, OB = 2
Framebuffer mapped at 0x7fb4922000.
*** Other error message received.
*** Sequencer error text:
Buffer overrun @4508:256

Best regards,

Namsu,

Re: kernel panic when booting the s32v234sbc

dakshina_dasari — Thu, 26 Nov 2020 10:38:06 GMT

I am also facing the same problem.

The solution is not clear.

Can you please elaborate -- how can i build the cse.bin? and where do i place it?

Also can i disable it for building the seq.ko?

Regards,

Dakshina