Part Number:AM5718
Tool/software: Linux
I have a AM5718 custom board. The board has QSPI boot options.
(0b000110 : First device SD / Second device QSPI_1)
we had it working in u-boot 2018 in linux SDK 05.00.00.15
SPI boot is not working properly . we are facing following errors
Below is a QSPI flash boot failure log.
U-Boot SPL 2018.01 (Dec 26 2018 - 15:52:46)
DRA722-GP ES2.0
Trying to boot from SPI
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
But, After booting to the SD card, the spi flash will work normally when the sf probe is used.
Below is sf probe log after SD boot.
U-Boot SPL 2018.01 (Dec 26 2018 - 11:16:35)
DRA722-GP ES2.0
Trying to boot from MMC1
no pinctrl state for default mode
no pinctrl state for default mode
*** Warning - bad CRC, using default environment
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img
U-Boot 2018.01 (Dec 26 2018 - 11:16:35 +0900)
CPU : DRA722-GP ES2.0
Model: TI AM5718 IDK
Board: AM571x IDK REV
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment
Net:
Warning: ethernet@48484000 using MAC address from ROM
eth0: ethernet@48484000
Hit any key to stop autoboot: 0
HUR-BOOT>
HUR-BOOT> sf probe
SF: Detected s25fl256s_64k with page size 256 Bytes, erase size 64 KiB, total 32 MiB, mapped at 5c000000
Q: Why does spi probe fail in spl_spi_load_image function in spl_spi.c?
/*
* Load U-Boot image from SPI flash into RAM
*/
flash = spi_flash_probe(CONFIG_SF_DEFAULT_BUS,
CONFIG_SF_DEFAULT_CS,
CONFIG_SF_DEFAULT_SPEED,
CONFIG_SF_DEFAULT_MODE);
if (!flash) {
printf("SPI probe failed. Bus:%d, CS:%d, Speed:%d, mode:%d\n", CONFIG_SF_DEFAULT_BUS ,CONFIG_SF_DEFAULT_CS, CONFIG_SF_DEFAULT_SPEED, CONFIG_SF_DEFAULT_MODE);
return -ENODEV;
}
Best regards,
John Kim.