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.

[FAQ] TDA4VM: How to reduce the EthFW initialization time to avail CPSW H/W Switch functionality as soon as possible after the core boot up in Vision Apps use-case?

Part Number: TDA4VM

How to reduce the EthFW initialization time to avail CPSW H/W Switch functionality as soon as possible after the core boot up in Vision Apps use-case?

  • In vision apps, EthFW and other modules' initialization is from the app_init file corresponding to RTOS core specific.

    In the app_init file, the initialization of all the components will happen in sequence, here before initialization of EthFW, IPC (Interprocess communication) gets initialized for establishing the communication with remote cores, where it will wait for A72 Linux VDev ready.

    As Linux is running on A72, the boot time of Linux will be higher in seconds which causes all the modules/components initialized after IPC will get delayed.

    If you want to initialize EthFW early, move the EthFW initialization early than IPC initialization as shown below from the “appInit()” function in vision_apps/platform/<SOC>/rtos/common/app_init.c file

    Note:

    1. Above change will initialize the EthFw earlier than IPC so that the switch functionality of CPSW can be availed as soon as possible after the core boots up.
    2. The communication with remote client cores from EthFW will not happen as it needs IPC to be initialized. So, the initialization of EthFW remote services will be post IPC initialization.

    Best Regards,
    Sudheer