Hi, I am using Jacinto 6, GLSDK 7.04.03.
If we replace eMMC to "N25Q064A13E12H0F" on DRA742-EVM 577G-02-21-00 board, should i modify any code?
As i see in dra7-evm.dts file, there are description about QSPI like below
&qspi {
status = "okay";
spi-max-frequency = <64000000>;
m25p80@0 {
compatible = "s25fl256s1";
spi-max-frequency = <64000000>;
the value of compatible is the original QSPI flash, so i think i should modify here, am i right?
besides, is there any place should i modify too?
Shawn,
shawn lin said:I modify below files,
1. J6_SDK/board-support/u-boot/boards.cfg => use "QSPI_BOOT" to replace "ENV_IS_IN_MMC" in our config
2. J6_SDK/board-support/u-boot/include/configs/xxx.h =>add " #define CONFIG_SPI_FLASH_STMICRO" to replace " #define CONFIG_SPI_FLASH_SPANSION". xxx is our project name
Do you modify u-boot/arch/arm/dts/dra7-evm.dts file?
shawn lin said:The fail flash log=>(Please visit the site to view this file)
You are using the below wiki:
Can you try with the exact commands:
uboot# mmc dev 0 (not U-Boot# M mmc dev 0)
uboot# fatload mmc 0 0x82000000 MLO.qspi (not U-Boot# fatload mmc 0 0x82000000 MLO.Q qspi)
Can you also try with the below set of commands, will be there any difference?
http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User's_Guide#Writing_to_QSPI_from_U-Boot
shawn lin said:I flash MLO.qspi into flash and read 256bytes back to compare with MLO.qspi file. The result in successful one is the same, but is different in N25Q128.
So you have different DDR3 dump every time for N25Q128. Have you verify your DDR3 memory is correct? That might be DDR3 memory issue, not QSPI.
Regards,
Pavel
Shawn,
You should be able to boot MLO and u-boot.img from QSPI with both dra7xx_evm_qspiboot_config and dra7xx_evm_config. The difference is that with dra7xx_evm_config, the environment variables should be stored in MMC instead of QSPI.
For more info regarding u-boot environment variables refer to the below wiki pages:
http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User's_Guide#U-Boot_Environment
Regards,
Pavel
shawn lin said:I already try it, but fail. The log is =>(Please visit the site to view this file)
I still don't know why it stuck.
Can you try to replace QSPI_BOOT with ENV_IS_IN_MMC, will you have any difference in the boot log?
From the log you have attached I see that MLO is booting, but stuck at DDR3 setup.
Please enable debug() messages in u-boot to get more prints and see how your flow goes:
It seems to me that your flow stuck at the sdram_init() function from the below sequence:
u-boot/arch/arm/cpu/armv7/start.S
u-boot/arch/arm/cpu/armv7/lowlevel_init.S
u-boot/arch/arm/cpu/armv7/omap-common/hwinit-common.c
void s_init(void)
{
/*
* Save the boot parameters passed from romcode.
* We cannot delay the saving further than this,
* to prevent overwrites.
*/
#ifdef CONFIG_SPL_BUILD
save_omap_boot_params();
#endif
init_omap_revision();
hw_data_init();
......
preloader_console_init(); -> this function prints "U-Boot SPL 2014.07" and "DRA752-GP ES2.0"
.....
do_board_detect(); -> this function prints "ti_i2c_eeprom_init failed 1"
.....
sdram_init(); -> I suspect your flow stuck here
#endif
}
Please check if your flow stuck in sdram_init(). If yes, check where exactly inside sdram_init() it stuck. sdram_init() is located at u-boot/arch/arm/cpu/armv7/omap-common/emif-common.c
Regards,
Pavel
