S32G274ARDB2 u-boot booting from QSPI

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32G274ARDB2 u-boot booting from QSPI

Jump to solution
3,238 Views
bootman
Contributor I

BSP 28.0 - 2020.04
Board: S32G274A-RDB2
QSPI Boot
u-boot image flashed with S32DS Flash Tool

Tried building u-boot both manually and using YOCTO as per instructions from Linux BSP 28.0 User Manual for S32G274A but board does not boot - no output on terminal.

Used defconfig s32g274ardb2_qspi_defconfig

When tried the same steps using s32g2xxaevb_qspi_defconfig the board boots but there are randomly issues with USB PHY initialization:

 

U-Boot 2020.04-dirty (Jun 07 2022 - 16:18:28 +0200)

CPU: NXP S32G274A rev. 2.1.0
Reset cause: External Reset
Model: NXP S32G2XX
Board: NXP S32G274A-EVB
DRAM: 3.5 GiB
CA53 core 1 running.
CA53 core 2 running.
CA53 core 3 running.
All (4) cores are up.
MMC: FSL_SDHC: 0
Loading Environment from SPI Flash... SF: Detected mx25uw51245g with page size 256 Bytes, erase size 64 KiB, total 64 MiB
65536 bytes read in 189 us (330.7 MiB/s)
*** Warning - bad CRC, using default environment

Using external clock for PCIe0
Configuring PCIe0 as RootComplex(x2)
Using external clock for PCIe1
Frequency 125Mhz configured for PCIe1
Configuring PCIe1 as SGMII [XPCS0 1G, XPCS1 OFF(PCIex1)]
PCIe0: Failed to get link up
Pcie0: LINK_DBG_1: 0x00000000, LINK_DBG_2: 0x00000800 (expected 0x000000d1)
DEBUG_R0: 0x000d6200, DEBUG_R1: 0x08200000
PCI: Failed autoconfig bar 20
PCI: Failed autoconfig bar 24
PCIe1: Not configuring PCIe, PHY not configured
In: serial
Out: serial
Err: serial
usb dr_mode not found
USB EHCI 1.00
ULPI integrity check failed
Failed to initialize SAF1508 PHY
failed to get usb@44064000 USB PHY
initcall sequence 00000000fcfc8e28 failed at call 00000000340a2fa8 (err=36)
### ERROR ### Please RESET the board ###

 

Now, I suppose that using s32g2xxaevb_defconfig for S32G274A-RDB2 board is wrong, but are we missing some other step here? 

Thank you for the support!

0 Kudos
1 Solution
3,174 Views
Tashia
NXP Employee
NXP Employee

Hi @bootman 

the binary I shared  was based on BSP30.

can you please try to build using BSP30, since I tested QSPI Binary using Linux BSP30 onwards also please make sure to erase the complete flash before flashing the device.

Kind Regards,

Tashia 

View solution in original post

0 Kudos
9 Replies
3,221 Views
Tashia
NXP Employee
NXP Employee

Hi @bootman s32g274ardb2_qspi_defconfig is the right defconfig file for rdb2 board.

how did you flashed using s32flash tool? can you please make sure that you have tried:

1. Target S32G274A , Algorithm: MX25UM51245G, correct COM port name selected

2. "upload target and algorithm to hardware"

3. "Erase memory region" till 0x100000

4. "upload file to device"

make sure when you are flashing the device the 

SW9[0:1] OFF:OFF

SW10[0:1] OFF:OFF

 

Make sure if you are booting up RDB2 board using QSPI flash then you need to set: 

SW9[0:1] OFF:OFF BOOT from RCON

SW10[0:1] ON:OFF

 

Kind Regards,

Tashia

0 Kudos
3,217 Views
bootman
Contributor I

Hi @Tashia ,

I flashed the QSPI with the S32 Flash Tool (switches set for serial boot) than changed the sw setting to QSPI boot and reset the board. 

I'm building the image for QSPI boot using s32g274ardb2_qspi_defconfig

Best Regards

 

 

0 Kudos
3,210 Views
Tashia
NXP Employee
NXP Employee

Hi @bootman 

1. can you see at offset 0x200 5a5a5a5a header? (hexdump u-boot.s32 | head)

2. also using s32ds flash tool, can you try "Download from device to file.." and see the content of the log file with the hexdump of binary for qspi?

 

Kind Regards,

Tashia

0 Kudos
3,192 Views
bootman
Contributor I

Hi @Tashia,

thank you very much for the support.

Yes, the header for block containing QSPI parameters is there, please see the flash dump in attachment. 

Best Regards

0 Kudos
3,187 Views
Tashia
NXP Employee
NXP Employee

Hi @bootman can you please try booting with the binary attached to this thread?

just to check if the only issue is with the built binary .

the flash content that you shared is correct though.

Kind Regards,

Tashia

0 Kudos
3,179 Views
bootman
Contributor I

Hi @Tashia,

with the provided image we are able to boot, please see the log in attachment.

Kind regards

0 Kudos
3,175 Views
Tashia
NXP Employee
NXP Employee

Hi @bootman 

the binary I shared  was based on BSP30.

can you please try to build using BSP30, since I tested QSPI Binary using Linux BSP30 onwards also please make sure to erase the complete flash before flashing the device.

Kind Regards,

Tashia 

0 Kudos
3,161 Views
bootman
Contributor I

Hi @Tashia,

tried both u-boot bsp32.0-2020.04 and bsp30.0-2020.04 branches, the bsp32.0-2020.04 does not boot. The one from bsp30.0-2020.04 boots, here is the log:

 

U-Boot 2020.04 (Jun 09 2022 - 18:10:04 +0200)

 

CPU: NXP S32G274A rev. 2.1.0
Reset cause: Power-On Reset
Model: NXP S32G2XX
Board: NXP S32G274A-RDB
DRAM: 3.5 GiB
CA53 core 1 running.
CA53 core 2 running.
CA53 core 3 running.
All (4) cores are up.
MMC: FSL_SDHC: 0
Loading Environment from SPI Flash... SF: Detected mx25uw51245g with page size 256 Bytes, erase size 64 KiB, total 64 MiB
*** Warning - bad CRC, using default environment

 

Using external clock for PCIe0, CRNS
Configuring PCIe0 as RootComplex(x2)
Using external clock for PCIe1, CRNS
Frequency 125Mhz configured for PCIe1
Configuring PCIe1 as SGMII(x2) [XPCS0 2.5G, XPCS1 OFF]
PCIe0: Failed to get link up
Pcie0: LINK_DBG_1: 0x00000000, LINK_DBG_2: 0x00000800 (expected 0x000000d1)
DEBUG_R0: 0x00e53d00, DEBUG_R1: 0x08200000
PCI: Failed autoconfig bar 20
PCI: Failed autoconfig bar 24
PCIe1: Not configuring PCIe, PHY not configured
In: serial
Out: serial
Err: serial
Board revision: RDB2/GLDBOX Revision D
Net: EQOS phy: rgmii @ 1

 

Warning: eth_eqos (eth0) using random MAC address - 5a:00:35:96:2a:71
eth0: eth_eqos PFE: emac0: sgmii emac1: none emac2: rgmii
## No elf image at address 0xffd12488
PFEng firmware file '<NULL>@0x03000000:<NULL>' loading failed: -22

 

Hit any key to stop autoboot: 0
## No elf image at address 0xffd121d8
PFEng firmware file '<NULL>@0x03000000:<NULL>' loading failed: -22
PFE: emac0: sgmii emac1: none emac2: rgmii
pfeng_cfg_mode_enable: Invalid PFE device
Booting from flash...
device 0 offset 0x1f0000, size 0xd00000
SF: 13631488 bytes @ 0x1f0000 Read: OK
device 0 offset 0xef0000, size 0x100000
SF: 1048576 bytes @ 0xef0000 Read: OK
device 0 offset 0xff0000, size 0x2000000
SF: 33554432 bytes @ 0xff0000 Read: OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid

 

Thanks a lot for the support!

Best Regards

0 Kudos
3,155 Views
Tashia
NXP Employee
NXP Employee

@bootman glad it worked! you are welcome.

Kind Regards,

Tashia

0 Kudos