s32g274abrd boot err using bsp30.0

[lily95]

Hello community:

I have got some errors ehilr i was boot my board: s32g274arbd

i used bsp30.0 to build my image dtb and u-boot ,

when i tried to boot my board , i got errors like:

CPU1: failed to come online
[ 5.117888] CPU1: failed in unknown state : 0x0
[ 10.243556] CPU2: failed to come online
[ 10.246953] CPU2: failed in unknown state : 0x0
[ 15.372612] CPU3: failed to come online
[ 15.376009] CPU3: failed in unknown state : 0x0

and also:

kB pagetables:4kB bounce:0kB free_pcp:28kB local_pcp:28kB free_cma:261760kB
[ 18.263183] lowmem_reserve[]: 0 0 0 0
[ 18.266829] DMA: 4*4kB (ME) 5*8kB (M) 1*16kB (M) 3*32kB (M) 2*64kB (M) 3*128k
B (MC) 5*256kB (ME) 4*512kB (MEC) 2*1024kB (EC) 1*2048kB (C) 63*4096kB (C) = 266
152kB
[ 18.281325] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepa
ges_size=1048576kB
[ 18.290004] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepa
ges_size=32768kB
[ 18.298510] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepa
ges_size=2048kB
[ 18.306930] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepa
ges_size=64kB
[ 18.315175] 27504 total pagecache pages
[ 18.318995] 130560 pages RAM
[ 18.321859] 0 pages HighMem/MovableOnly
[ 18.325678] 34679 pages reserved
[ 18.328890] 65536 pages cma reserved
[ 18.332449] Tasks state (memory values in pages):
[ 18.337136] [ pid ] uid tgid total_vm rss pgtables_bytes swapents o
om_score_adj name
[ 18.345738] Out of memory and no killable processes...
[ 18.350851] Kernel panic - not syncing:
[ 18.354670] System is deadlocked on memory
[ 18.358791] ---[ end Kernel panic - not syncing: System is deadlocked on memo
ry ]---

=====================================================================

the bsp building cmds i used is:

$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo
$: PATH=${PATH}:~/bin

$: mkdir fsl-auto-yocto-bsp
$: cd fsl-auto-yocto-bsp
$: repo init -u https://source.codeaurora.org/external/autobsps32/auto_yocto_bsp -b release/bsp30.0
$: repo sync

$ ./sources/meta-alb/scripts/host-prepare.sh

$ . nxp-setup-alb.sh -m s32g274ardb

$ bitbake fsl-image-auto

which all succed and i got the image, u-boot,and dtb

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

Image--5.10.41-r0-s32g274ardb-20211121115436.bin

fsl-image-auto-s32g274ardb-20211121115436.rootfs.cpio.gz.u-boot

fsl-s32g274a-rdb--5.10.41-r0-s32g274ardb-20211121115436.dtb

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

i upload all the above three file into mmc, and begin to boot:

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

ext4load mmc 0:3 0x80080000 Image--5.10.41-r0-s32g274ardb-20211121115436.bin

ext4load mmc 0:3 0x83E00000 fsl-s32g274a-rdb--5.10.41-r0-s32g274ardb-20211121115436.dtb

ext4load mmc 0:3 0x84000000 fsl-image-auto-s32g274ardb-20211121115436.rootfs.cpio.gz.u-boot

setenv bootargs console=ttyLF0,115200 root=/dev/ram rw earlycon rdinit=/sbin/init

${boot_mtd} ${loadaddr} ${ramdisk_addr} ${fdt_addr}

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

and I upload the bootlog.

Thanks for any suggestions!!

[murphy_xie]

Hi NXP

     when I try to bringup s32g274ardb with yocto bsp30,and  write the fsl-image-base-s32g274ardb-20220529032227.rootfs.sdcard with Win32DiskImager(or must using dd),but the uart0 didn`t print any things,the sw is on right position.Can you help with this issue?

tks

[Yi_Liu_Nxa22412]

1. Please show me your detail step to program the sd image into SD card.

And plus all SW settings on the RDB board.

         Like SW10[1] = ON, SW10[1] = OFF, .... etc

2. Please using one working SD card if available, to check the RDB board can bootup normally or not, make sure the SW settings are correct. 

3. Please program only u-boot to SD card, the file name is u-boot-s32g274ardb2.s32-sdcard, to check whether the u-boot can bootup or not.

[murphy_xie]

ok,tks

[lily95]

I tried https://nxp.flexnetoperations.com/control/frse/download?element=12593397 

this bsp28.0 , the pre_build image to boot my board, the cpu errors also occurs;

i tried s32g274ardb:

fsl-image-base-s32g274ardb.cpio.gz.u-boot

fsl-s32g274a-rdb.dtb

Image

as my u-boot dtb and image to boot.

[bpe]

Your u-Boot, based on the quoted output, is older than Automotive BSP 30.0
one. Using mixed BSP version target binaries is error-prone. As of the rest, it is
difficult to comment because the tests made appear almost random and none of
them follow the boot image deployment and subsequent target boot scenarios
described in the BSP documentation. Besides that, there is no point in playing
with obsolete BSP versions if your home project does not have any dependency
on any of them.

I would suggest taking a more consistent approach, namely to start with
something proven working. Use the NXP-provided pre-built images, make sure
what you put onto the boot media match your board model. Note that RDB and
RDB2 are different boards and RDB is obsolete. Follow the steps specified in
Automotive BSP 30.0 User Guide Section 3.1.1 strictly, see if it works for
you. This should allow to sort out potential build and non-standard
deployment scenario issues.

Hope this helps,
Platon

[lily95]

I also notified that in my board, when i run the original kernel version(4.19) , u-boot show the:

machine-model is:Machine model: Freescale S32G275

but

as i run the bsp build image 5.10, the machine model is:

Freescale S32G274

[lily95]

Here is my bord info:

U-Boot 2019.04+ga53a9fa1e9 (Aug 31 2020 - 05:07:39 +0000)

CPU: NXP S32G274A rev. 2.1.0
Reset cause: Power-On Reset
Model: NXP S32G27x
Board: NXP S32G274A-RDB
DRAM: 512 MiB
CA53 core 1 running.
CA53 core 2 running.
CA53 core 3 running.
All (4) cores are up.

[lily95]

i have tried to use another filesystem with my image and dtb, which turns out that the cpu errs still exists, but board could boot up.

and also i tried to use another image dtb whith my  filesystemwhich turns out that ererything OK!