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.

  • Resolved

TDA4VM: Regarding boot up of custom board with new SDK 07 and patch

Expert 1350 points

Replies: 35

Views: 421

Part Number: TDA4VM

Dear TI,

I have following error during the boot with custom board using SDK 07, please see the attachment. Can you please help me to figure out which DT has the issue ?

Also, I found a small error related to make u-boot which is in the rules .make , in "arm-none-linux-gnueabihf" you have missing none word which fails the make.

# Add CROSS_COMPILE and UBOOT_MACHINE for the R5
export CROSS_COMPILE_ARMV7=$(LINUX_DEVKIT_PATH)/sysroots/x86_64-arago-linux/usr/bin/arm-none-linux-gnueabihf-
UBOOT_MACHINE_R5=j721e_evm_r5_config



Regards

Manish

  • In reply to Manish Ahlawat:

    Hello ,

    So what works is the Image from 06 and dtb from 07. So device tree is not the issue , Image is the issue.

    Attaching the log here.

    ManishImage_06_Dtb_07.txt

  • In reply to Manish Ahlawat:

    Hi Manish,

    Could you do below commands in u-boot console once and test?

    => env default -f -a
    => env save

    Regards,
    Vishal

  • In reply to Vishal Mahaveer:

    Hi Vishal,

    I tried by setting the env variable to default as per above but still didn't work. I just replaced the Image file from 06 Version and it was able to boot up the kernel again.

    I am attaching the not working log again. My question is since it doesn't seem to be failure in RootFS (DT) where does the error in Kernel Image come from ?latest_log.txt

  • In reply to Manish Ahlawat:

    Hi Manish,

    I believe you are using the latest sysfw.itb from the 7.0 release. Can you paste the u-boot log as well?

    Best Regards,
    Keerthy

  • In reply to Keerthy J:

    Hi Keerthy,

    The log in the last message doesn't help ? Yes the sysfw.itb is from the 7.0 release.

    Regards

    Manish

  • In reply to Manish Ahlawat:

    Manish,

    U-Boot SPL 2020.01-dirty (Jun 30 2020 - 17:15:48 +0200)
    SYSFW ABI: 3.0 (firmware rev 0x0014 '20.04.1-v2020.04a (Terrific Lla')
    Reading on-board EEPROM at 0x50 failed 1
    Trying to boot from MMC2

    So your board is booting from SD boot.

    The for kernel:


    [    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128k(ospi.env.backup),1m(ospi.sysfw),-@8m(ospi.rootfs);47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),1m(hbmc.sysfw),-@8m(hbmc.rootfs) root=PARTUUID=569de07f-02 rw rootfstype=ext4 rootwait

    You are trying to boot from OSPI? Where is your Image & dtb stored?

    Have you tried any other boot media?

    Just for your information i checked the Image(kernel) size on 6.02 is around 13MB & in 7.0 it is around 16MB.

    Request you to give full boot log in text format & also the bootargs that you are using.
    - Keerthy

  • In reply to Keerthy J:

    Hi,

    Below line in your failing log does not look correct
    [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: -1037

    Same line from your working log (Image from 06 and dtb from 07)
    [    0.000000] Built 1 zonelists, mobility grouping off.  Total pages: 13171


    Regards,
    Vishal

  • In reply to Keerthy J:

    Manish,

    Can you remove all the reserved-memory nodes and try to boot with that dtb on 7.0?

    - Keerthy

  • In reply to Keerthy J:

    Hi Keerthy,

    I am booting with bootmode SD card at the moment so no OSPI. Please find the boot log attached and the bootargs.env_var.txt

    Log_3rd_July.txt

  • In reply to Manish Ahlawat:

    Hi Keerthy,

    i disabled the node k3-j721e-som-p0.dtsi nd &k3-arm654-base-board.dts. still doesn't work. Are these the right files to deactivate the node ?

    regards

    manishlast_log.txt

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.