• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 398 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: TDA4 Startup time optimation

TDA4VM: Question about TDA4 startup time optimation

SandalHao
Intellectual 665 points
Part Number: TDA4VM

Hi TI Expert,

I have the following questions:

1. In the link https://www.ti.com.cn/cn/lit/pdf/sprad09, the link of patch,eg TI Drive seems to have failed.Please provide the reference patch again, thanks!

2. How to load and use other cores in tiny rootfs? After uboot loads the firmware running other cores, how can rootfs also call remoteproc to run the firmware using other cores?

3. Bootloader is placed in the BOOT partition of EMMC and rootfs is placed in the USER partition of EMMC. Are there any patches to speed up or optimize the startup speed?

  • 0
    TI__Guru**** 156600 points

    Hi,

    Attaching the patches:

    5518.0001-arch-arm64-boot-dts-ti-k3-j7200-Optimize-DT-for-earl.patch

    0001-Remove-prints-to-optimize-U-Boot-time.patch

    SandalHao said:
    2. How to load and use other cores in tiny rootfs? After uboot loads the firmware running other cores, how can rootfs also call remoteproc to run the firmware using other cores?

    You will need to copy then to the /lib/firmware of the tinyrootfs. The above optimization is done to get the Linux boot time minimum so does not load remotecores.
    That would mean additional time added to the Linux bring up time.


    SandalHao said:
    3. Bootloader is placed in the BOOT partition of EMMC and rootfs is placed in the USER partition of EMMC. Are there any patches to speed up or optimize the startup speed?

    U-Boot & Linux optimization patches are shared above.

    - Keerthy

  • 0 in reply to Keerthy J
    Intellectual 665 points

    Hi,

    Thank you for the reply.

    I just want to know how to load and run remoteproc using tiny-rootfs so that other cores can run normally.

    Although it will cost bootting time and do some additional  step on rootfs.

  • 0 in reply to SandalHao
    TI__Guru**** 156600 points

    Hi,

    You can copy the firmware that you want to load from the default rootfs to /lib/firmware under the tiny rootfs.
    The default bootargs should load the remote core firmware.

    - Keerthy


  • 0 in reply to Keerthy J
    Intellectual 665 points

    Hi,Keerthy

    You said:

    You will need to copy then to the /lib/firmware of the tinyrootfs. The above optimization is done to get the Linux boot time minimum so does not load remotecores.
    That would mean additional time added to the Linux bring up time.

    So I tar <sdk8.2>/la/filesystem/tisdk-tiny-image-j7-evm.tar.xz  to the tda4 board and copied lib/*  and usr/lib/*  in the default rootfs to tiny rootfs , but I still didn't see that the remote core firmware has been loaded.

    Is there anything else that needs to be changed?

  • 0 in reply to SandalHao
    TI__Guru**** 156600 points

    Hi,

    Did you install all the modules to your tiny rootfs? The remoteprocs are all modules. Please install all the modules to the tiny rootfs.

    - Keerthy

  • 0 in reply to Keerthy J
    Intellectual 665 points

    Do you mean that I need to execute insmod myself?

  • 0 in reply to SandalHao
    TI__Guru**** 156600 points

    Hi Yes,

    The tiny rootfs will not have all the modules. Hence install all the modules to the tiny rootfs:

    make modules_install INSTALL_MOD_PATH=/media/$USER/rootfs

    - Keerthy