• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 1337 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TDA4VM: TDA4VM EVM cannot load kernel

TDA4VM: TDA4 cannot partition OSPI flash when booting through OSPI flash

yongliang li
Intellectual 490 points

Part Number: TDA4VM

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)

  • 0
    TI__Guru**** 504545 points

    Hi,

    Could you please provide some more inforamtion? 

    Which boot flow are you using? What is the SDK version that you are using?

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 490 points

    I am using SDK ti-processor-sdk-linux-j7-evm-08_00_00_08. I used the "sf probe" u-boot command before loading the linux kernel and it worked, but I don't know why I have to execute "sf probe" before loading the linux kernel while (no need to execute "sf probe" when booting through MMC card).Could you get me some details about MTD partition for TDA4?

  • +1 in reply to yongliang li
    TI__Guru**** 171230 points

    Hi,

    This is because the flash was initialized by A72 SPL during the boot process to 8D mode. Linux needs the flash to be in 1S mode to be able to discover it. Try adding "sf probe" to your bootcmd. That would re-initialize the flash in U-Boot and then it will soft reset it before booting Linux.

    If the above helps please click on verify answer.

    Best Regards,
    Keerthy