• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 283 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.

TDA4VM: auto init Vision Apps and / or change UART instance

Yannik Muendler
Prodigy 305 points
Part Number: TDA4VM

Hi,

we succesfully build the vision apps including the ETHFW. We are using SDK 07.03.

During boot the follwing log appears on UART Instance 2:

Enabling clocks!
[NIMU_NDK] ENET has been started successfully

now if we want to start the ETHFW we issue following commands over SSH or UART instance 0:

cd /opt/vision_apps
source ./vision_apps_init.sh
This leads to having the log output in the same window as linux runs.
What needs to be changed, that the log keeps on UART Instance 2.
And is there a way to automatically init the vision apps? The firmware is loaded during boot, but  we do not want to issue source ./vision_apps_init.sh every time we reboot.
Thanks for your help.
  • 0
    TI__Genius 9295 points

    EthFw logging relies on external function appLogPrintf. This is defined globally in VisionApps, so one cannot redirect EthFw logs to UART without affecting VisionApps loggin as well.

    Enet LLD logs (which EthFw relies on for CPSW configuration) can be printed in UART console. Please set "mcmCfg.print" to a different function that prints to UART. This parameter is located in <ethfw>/ethfw/src/ethfw.c.

  • 0 in reply to Misael Lopez Cruz
    TI__Prodigy 305 points

    Hi Misael,

    I changed the .print from appLogPrintf to EnetAppUtils_print

    mcmCfg.print = EnetAppUtils_print;

    but I observe the same behaviour.

    It behaves like the ethfw log is written into a buffer and when calling "source ./vision_apps_init.sh", this buffer is printed to the current session.