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.

TDA2EG-17: Error when running apps.out

Genius 13655 points
Part Number: TDA2EG-17

Hello Champs,

SW:  VISION_03_08_00_00
HW: own board

When running apps.out, a messed message appears in vsdk/link_fw/src/hlos/osa/src/osa_remote_log_clent.c OSA_printf("%s%s\r\n", procName, for the RemoteLog_clientRun thread gRemoteLog_clientObj.lineBuf);, and the following is the log that the system application launches: 

DRA722-GP ES2.1
Trying to boot from MMC1
*** Warning - bad CRC, using default environment
spl: falcon_args_file not set in environment, falling back to default
Booting Linux on physical CPU 0x0
Linux version 4.19.73 (rd22673@RD08) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #9 PREEMPT Thu Feb 29 10:21:20 CST 2024
CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=30c53c7d
CPU: div instructions available: patching division code
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
OF: fdt: Machine model: TI DRA718 EVM
bootconsole [earlycon0] enabled
============================================================
                        come in rootfs
============================================================
--------------------------------------
      start check lock
--------------------------------------
environment: line 35: echo: write error: Device or resource busy
ERROR: 77 file /sys/class/gpio/136 is not exist.
WARE :  used default dir /app/firm
INFO :  *.rsc file is exist, continue.
INFO :  Loading dra7-dsp1-fw.xe66
INFO :  Loading dra7-ipu2-fw.xem4
Loaded PowerVR consumer services.
Starting avm apps: 

============================================================
                /app/start_avm_app.sh 
============================================================

INFO : check data dir...
Filesystem                Size      Used Available Use% Mounted on
/dev/root               147.1M     46.3M     89.8M  34% /
devtmpfs                 90.7M         0     90.7M   0% /dev
tmpfs                   135.7M         0    135.7M   0% /dev/shm
tmpfs                   135.7M         0    135.7M   0% /tmp
tmpfs                   135.7M         0    135.7M   0% /run
tmpfs                   135.7M         0    135.7M   0% /var/run
/dev/mmcblk0p3          205.2M     89.0M    101.4M  47% /app
/dev/mmcblk0p4           14.2G     43.8M     13.4G   0% /data
current apps process pid 123
current eventhy process pid 144
current ui process pid 145
Starting syslogd: OK
Running sysctl: OK
Starting mdev... app_root=/app/release
[awtk-port/main_loop_linux.c|main_loop_init:134] 
 [HOST]  OSA: HOST Remote Log Shared Memory @ 0x9fd4f140
 [HOST]  OSA: DSP1 Remote Log Shared Memory @ 0x9fd769e0
 [HOST]  OSA: IPU2 Remote Log Shared Memory @ 0x9fe63da0
 [HOST] [HOST  ]      3.567528 s:  SYSTEM: System A15 Init in progress !!!
 [HOST] [IPU2  ] 
                    [HOST] [IPU2  ]  [HOST] [IPU2  ] @
[HOST] [IPU2  ] A
[HOST] [IPU2  ] 
 [HOST] [IPU2  ] 

 [HOST] [IPU2  ] 
 [HOST] [IPU2  ] 0@
 [HOST] [IPU2  ] -
 [HOST] [IPU2  ]
  [HOST] [IPU2  ] S++
 [HOST] [IPU2  ] @
 [HOST] [IPU2  ] 
 [HOST] [IPU2  ] {+
 [HOST] [IPU2  ] @
 [HOST] [IPU2  ] `



Thanks
Regards
Shine

  • Hi Shine,

    This seems some corruption on the terminal. Have you tried restarting the terminal to see if the issue goes away?

    Regards,

    Brijesh 

  • Hello Brijesh,

    Thank you very much.

    Below is the customer's reply.

    Restarting the terminal doesn't work, I got my thread to /link_fw/src/hlos/osa/src/osa_remote_log_clent.c RemoteLog_clientRun. This thread takes the memory content from DSP and the IPU via VPS_printf and prints it on the A15 side. Look at log "[HOST] [IPU2] " and you can see the message for the IPU is printing out, but why is it mess data?  Is there a problem with ipu and dsp startup? What is the way to verify that ipu and dsp are properly initialized? 

    Thanks
    Regards
    Shine

  • Hi Shine,

    ok i see the message before corruption. Most likely it is not an issue in the startup, Is the issue only seen with perticular IPU and DSP core? Maybe some code is then corrupting this region for these cores.. 

    Regards,

    Brijesh

  • Hello Brijesh,

    Thank you very much.

    Is the issue only seen with perticular IPU and DSP core?

    They only used the dsp1 and ipu2 kernels, and both had this problem. 


    Maybe some code is then corrupting this region for these cores.. 

    The previous application on 1G size ddr board is normal, now the board is 512Mddr, he only modified the memory map. Is there a possible memory related issue? Is there any suggestion about what causes these core anomalies? 

    Regards

    Shine

  • Hi Shine,

    Well, if the memory map changes are not done properly, there could be issue. Lets say, these messages are stored in a dedicated separate part of the memory and if it is not properly carved our, or some issue in IPU MMU or C6x MMU configuration, the messages might get corrupted and then we will not see them correctly on the console.  

    Regards,

    Brijesh