- 积分
- 17
贡献138
飞刀5 FD
注册时间2020-5-6
在线时间1 小时
|
楼主 |
发表于 2020-5-6 14:46:43
|
显示全部楼层
U-Boot 2018.03 (Aug 21 2019 - 16:34:34 +0800)
SoC: LS1043AE Rev1.1 (0x87920211)
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 40044000 c1002000
00000020: 00000000 00000000 00000000 00238800
00000030: 20044500 00001102 00000096 00000001
Model: OK1043-C
Board: LS1043ARDB, boot from QSPI
SERDES Reference Clocks:
SD1_CLK1 = 156.25MHZ, SD1_CLK2 = 100.00MHZ
I2C: ready
DRAM: Initialzing DDR using fixed setting
Configuring DDR for 1600 MT/s data rate
1.9 GiB (DDR4, 32-bit, CL=11, ECC off)
DS2460 OK
Using SERDES1 Protocol: 5205 (0x1455)
SEC0: RNG instantiated
PPA Firmware: Version LSDK-18.06-Forlinx
SEC Firmware: 'loadables' present in config
loadables: 'trustedOS@1'
MMC: FSL_SDHC: 0
Loading Environment from SPI Flash... SF: Detected n25q128 with page size 256 Bytes, erase size 64 KiB, total 16 MiB
OK
In: serial
Out: serial
Err: serial
SATA link 0 timeout.
AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst
Found 0 device(s).
SCSI: Net: SF: Detected n25q128 with page size 256 Bytes, erase size 64 KiB, total 16 MiB
Fman1: Uploading microcode version 106.4.18
Could not get PHY for FSL_MDIO0: addr 8
Failed to connect
Could not get PHY for FSL_MDIO0: addr 9
Failed to connect
Could not get PHY for FSL_MDIO0: addr 10
Failed to connect
Could not get PHY for FSL_MDIO0: addr 11
Failed to connect
Could not get PHY for FM_TGEC_MDIO: addr 0
Failed to connect
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
=> boot
starting USB...
USB0: Register 200017f NbrPorts 2
Starting the controller
USB XHCI 1.00
USB1: Register 200017f NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2: Register 200017f NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 5 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Device 0: Vendor: Rev: 1.00 Prod:
Type: Removable Hard Disk
Capacity: 7424.0 MB = 7.2 GB (15204352 x 512)
... is now current device
Scanning usb 0:4...
Found U-Boot script /ls1043ardb_update.scr
365 bytes read in 20 ms (17.6 KiB/s)
## Executing script at 80000000
** Invalid partition 1 **
** Invalid partition 1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
Found U-Boot script /boot/ls1043ardb_boot.scr
872 bytes read in 30 ms (28.3 KiB/s)
## Executing script at 80000000
** Invalid partition 3 **
** Invalid partition 2 **
** Invalid partition 2 **
** Invalid partition 2 **
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Scanning mmc 0:2...
Scanning mmc 0:3...
Trying load from qspi..
SF: Detected n25q128 with page size 256 Bytes, erase size 64 KiB, total 16 MiB
Offset exceeds device limit
sf - SPI flash sub-system
Usage:
sf probe [[bus:]cs] ** [mode] - init flash device on given SPI bus
and chip select
sf read addr offset|partition len - read `len' bytes starting at
`offset' or from start of mtd
`partition'to memory at `addr'
sf write addr offset|partition len - write `len' bytes from memory
at `addr' to flash at `offset'
or to start of mtd `partition'
sf erase offset|partition [+]len - erase `len' bytes from `offset'
or from start of mtd `partition'
`+len' round up `len' to block size
sf update addr offset|partition len - erase and write `len' bytes from memory
at `addr' to flash at `offset'
or to start of mtd `partition'
sf protect lock/unlock sector len - protect/unprotect 'len' bytes starting
at address 'sector'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>
|
|