new u-boot shown error on LS1043A board based by QorIQ-SDK-V2.0

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

new u-boot shown error on LS1043A board based by QorIQ-SDK-V2.0

Jump to solution
1,153 Views
ken_liu
Contributor II

background introduce:

we buy LS1043A board, and run it successful

then we download the newest SDK package on NXP net. 

and use the SDK re-build a new u-boot image.

Problem:

when we programmer the u-boot image into bank4 and start up this bank. 

the error message is shown as below:

//================================================================

U-Boot 2016.012.0+ga9b437f (Oct 15 2019 - 13:15:21 +0800)

SoC: LS1043E (0x87920011)
Clock Configuration:
CPU0(A53):1600 MHz CPU1(A53):1600 MHz CPU2(A53):1600 MHz
CPU3(A53):1600 MHz
Bus: 400 MHz DDR: 1600 MT/s FMAN: 500 MHz
Reset Configuration Word (RCW):
00000000: 08100010 0a000000 00000000 00000000
00000010: 14550002 80004012 e0025000 c1002000
00000020: 00000000 00000000 00000000 00038800
00000030: 00000000 00001101 00000096 00000001
I2C: ready
Model: LS1043A RDB Board
Board: LS1043ARDB, boot from vBank 4
CPLD: V2.0
PCBA: V6.0
SERDES Reference Clocks:
SD1_CLK1 = 156.25MHZ, SD1_CLK2 = 100.00MHZ
DRAM: Initializing DDR....
Detected UDIMM Fixed DDR on board
2 GiB (DDR4, 32-bit, CL=11, ECC off)
SEC0: RNG instantiated
fsl-ppa: Bad firmware image (not a FIT image)
fsl-ppa: error (-22)
Not a microcode
fsl-ppa: Bad firmware image (not a FIT image)
Waking secondary cores to start from ffd0a000
All (4) cores are up.
Using SERDES1 Protocol: 5205 (0x1455)
Flash: 128 MiB
NAND: 512 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
PCIe1: disabled
PCIe2: Root Complex no link, regs @ 0x3500000
PCIe3: Root Complex no link, regs @ 0x3600000
In: serial
Out: serial
Err: serial
SCSI: Error: SCSI Controller(s) 1B4B:9170 not found
Net: Fman1: Data at 0000000060300000 is not a firmware
No ethernet found.
Hit any key to stop autoboot: 0

//============================================================

and when switch to bank0 (this is the default u-boot)

the normally print is shown as below:

//===================================================================

U-Boot 2017.07-g503eff0 (Sep 26 2017 - 15:00:50 +0800)

SoC: LS1043AE Rev1.1 (0x87920011)
Clock Configuration:
CPU0(A53):1600 MHz CPU1(A53):1600 MHz CPU2(A53):1600 MHz
CPU3(A53):1600 MHz
Bus: 400 MHz DDR: 1600 MT/s FMAN: 500 MHz
Reset Configuration Word (RCW):
00000000: 08100010 0a000000 00000000 00000000
00000010: 14550002 80004012 e0025000 c1002000
00000020: 00000000 00000000 00000000 00038800
00000030: 00000000 00001101 00000096 00000001
Model: LS1043A RDB Board
Board: LS1043ARDB, boot from vBank 0
CPLD: V2.0
PCBA: V6.0
SERDES Reference Clocks:
SD1_CLK1 = 156.25MHZ, SD1_CLK2 = 100.00MHZ
I2C: ready
DRAM: Initializing DDR....
Detected UDIMM Fixed DDR on board
1.9 GiB (DDR4, 32-bit, CL=11, ECC off)
Using SERDES1 Protocol: 5205 (0x1455)
SEC0: RNG instantiated
PPA Firmware: Version LSDK-17.09
Firmware 'Microcode version 0.0.1 for LS1021a r1.0' for 1021 V1.0
QE: uploading microcode 'Microcode for LS1021a r1.0' version 0.0.1
Flash: 128 MiB
NAND: 512 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
In: serial
Out: serial
Err: serial
Net: Fman1: Uploading microcode version 108.4.9
PCIe0: pcie@3400000 disabled
PCIe1: pcie@3500000 Root Complex: no link
PCIe2: pcie@3600000 Root Complex: no link
FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3 [PRIME], FM1@DTSEC4, FM1@DTSEC5, FM1@DTSEC6, FM1@TGEC1
Hit any key to stop autoboot: 0

=================================================================================>

Question:

there are 3 question:

1. we use the newest SDK package on NXP website. the version is QorIQ-SDK-V2.0-20160527-yocto

    based on the SDK, we re-build new u-boot version is U-Boot 2016.012.0+ga9b437f\

    but the LS1043A board default u-boot version is U-Boot 2017.07-g503eff0

    it is different , so How to fix it?

2. the error shown that 

    fsl-ppa: Bad firmware image (not a FIT image)
    fsl-ppa: error (-22)

    Not a microcode
    fsl-ppa: Bad firmware image (not a FIT image)

    

     but I try to md the memory address, and compare bank0 to bank4.  it seems same.

      the Fman is not broken.

       so pls help me to check it

3. Net: Fman1: Data at 0000000060300000 is not a firmware
    No ethernet found.

    the ehernet is really miss, pls help me to fix it 

thank you very much

0 Kudos
1 Solution
1,038 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Ken Liu,

2. On bank 0, please deploy PPA image at 0x64500000 for bank4.

3. On bank 0, please deploy FMAN ucode at 0x64300000 for bank4.

1. If bank4 u-boot works normally, please replace u-boot image at 0x60100000 on bank0.

Thanks,

Yiping

View solution in original post

0 Kudos
2 Replies
1,039 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Ken Liu,

2. On bank 0, please deploy PPA image at 0x64500000 for bank4.

3. On bank 0, please deploy FMAN ucode at 0x64300000 for bank4.

1. If bank4 u-boot works normally, please replace u-boot image at 0x60100000 on bank0.

Thanks,

Yiping

0 Kudos
1,038 Views
ken_liu
Contributor II

Hi Yiping

I try it following you suggestion 2 and 3

the basic problem has been fixed

thank you very much

0 Kudos