Part Number: DRA722
Tool/software: Linux
Hi,
I'm trying to load u-boot from QSPI(micron 64 MB SPI NOR FLASH on a custom board based on DRA722).But I'm stuck at this point:
U-Boot SPL 2016.05 (Nov 28 2017 - 17:44:59)
DRA722-GP ES2.0
Trying to boot from SPI
ti_spi_set_speed: hz: 76800000, clock divider 0
spi_claim_bus: bus:0 cs:0
spi_xfer: bus:0 cs:0 bitlen:8 flags:1
tx cmd 003a0fff dc 00000000
tx done, status 00010002
spi_xfer: bus:0 cs:0 bitlen:40 flags:2
rx cmd 00390fff dc 00000000
rx done, status 00020002, read 20
rx cmd 00390fff dc 00000000
rx done, status 00030002, read ba
rx cmd 00390fff dc 00000000
rx done, status 00040002, read 22
rx cmd 00390fff dc 00000000
rx done, status 00050002, read 10
rx cmd 00390fff dc 00000000
rx done, status 00060002, read 44
SF: Got idcodes
00000000: 20 ba 22 10 44 .".D
spi_claim_bus: bus:0 cs:0
spi_xfer: bus:0 cs:0 bitlen:8 flags:1
tx cmd 003a0ff00000
tx done, status 00010002
spi_xfer: bus:0 cs:0 bitlen:8 flags:2
rx cmd 00390fff dc 00000000
rx done, status 00020002, read 00
spi_release_bus: bus:0 cs:0
spi_release_bus: bus:0 cs:0
Unsupported OS image.. Jumping nevertheless..
loaded - jumping to U-Boot...image entry point: 0x0
boot-common.c:image size :0x0
image load_addr:0x0
This is my dtb config
&qspi {
status = "okay";
/*spi-max-frequency = <76800000>;*/
spi-max-frequency = <1000>;
m25p80@0 {
compatible = "mt25ql02g","m25p80";
/*spi-max-frequency = <76800000>;*/
spi-max-frequency = <1000>;
reg = <0>;
spi-tx-bus-width = <1>;
spi-rx-bus-width = <2>;
#address-cells = <1>;
#size-cells = <1>;
/*MTD partition table.
* The ROM checks the first four physical blocks
* for a valid file to boot and the flash here is
* 64KiB block size.*/
partition@0 {
label = "QSPI.SPL";
reg = <0x00000000 0x00040000>;
};
partition@1 {
label = "QSPI.u-boot";
reg = <0x00040000 0x00100000>;
};
partition@2 {
label = "QSPI.u-boot-spl-os";
reg = <0x00140000 0x00080000>;
};
partition@3 {
label = "QSPI.u-boot-env";
reg = <0x001c0000 0x00010000>;
};
partition@4 {
label = "QSPI.u-boot-env.backup1";
reg = <0x001d0000 0x0010000>;
};
partition@5 {
label = "QSPI.kernel";
reg = <0x001e0000 0x0800000>;
};
partition@6 {
label = "QSPI.file-system";
reg = <0x009e0000 0x01620000>;
};
};
};
I flashed MLO,u-boot.img,uImage and the dtb file to corresponding partitions(tried flashing using both sf write and mtd_debug write).After flashing i used hexdump -C /dev/mtd0 etc to check whether the files are written successfully.Writing seems fine.I tried changing frequencies,dtb configs,sf_param.c configs ,but it never went past this point.
What can be the root cause?What might be the reason that image entry point,image size and image load_addr is 0x0?
Regards,
Murugan
