- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Original question:
Hi
I was planning to partition the OSPI flash of TDA4 EVM. But it didn't work.
Here are my steps.
1. Burn the tiboot3.bin sysfw.itb tispl.bin u-boot.img into OSPI flash.
2. Change the boot mode to OSPI flash boot and Power on the EVM board.
3. Stop the counting ot u-boot. Put the board booting through network(get the kernel and device tree through tftp and mount NFS as root file system).
(My host PC's IP address is 192.168.10.172)
==>setenv serverip 192.168.10.172;setenv ipaddr 192.168.10.5;setenv loadaddr 82000000;setenv bootfile Image;tftpboot;setenv loadaddr 88000000;setenv bootfile k3-j721e-common-proc-board.dtb;tftpboot;setenv bootargs "console=ttyS2,115200n8 mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128k(ospi.env.backup),1m(ospi.sysfw),57216k@8m(ospi.rootfs),128k(ospi.phypattern);47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),1m(hbmc.sysfw),-@8m(hbmc.rootfs) root=/dev/nfs rw nfsroot=192.168.10.172:/home/pc/rootfs,proto=tcp,nfsvers=3 ip=192.168.10.5:192.168.10.172:192.168.10.1:255.255.255.0::eth0:off";booti 82000000 - 0x88000000
4. The board is booted OK but when it comes to the terminal, I can't find any mtd partition.
PS: SPI failed printed at about 8s when I use OSPI boot mode. BUT MTD PARTITION IS OK WHEN I USE MMC OR OTHERS TO BOOT THE BOARD(and no SPI failed prints).
[ 8.116916] spi-nor spi0.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
[ 8.123787] spi-nor: probe of spi0.0 failed with error -2
[ 8.131020] spi-nor spi1.0: mt25qu512a (65536 Kbytes)
