• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 177 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.

TDA4VM: Run time error while migrating the object detection application from PSDK 08.05.00.11 to 08.06.01.03

Seetharama Raju
Prodigy 170 points
Part Number: TDA4VM

Hello TI,

I'm working for an object detection application that is developed from taking "app_tidl_od" application as the reference on sdk 08_05_00_11. It is successfully running on PSDK 08.05.00.11. Now I want to migrate the code changes of tiovx and vision_apps into the latest sdk 08.06.01.03 . New sdk is installed and built successfully and demo applications are also tested for the verification. I have made necessary code changes into the latest sdk. It got built successfully but getting errors while running on the TI-TDA4VM board. I have attached the error log here. 

Note: Please ignore the debug print statements in the error log.

Could you please guide me based on the error log.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
root@j7-evm:/opt/vision_apps# ./run_app_tidl_rci_od.sh
APP: Init ... !!!
MEM: Init ... !!!
MEM: Initialized DMA HEAP (fd=4) !!!
MEM: Init ... Done !!!
IPC: Init ... !!!
IPC: Init ... Done !!!
REMOTE_SERVICE: Init ... !!!
REMOTE_SERVICE: Init ... Done !!!
43.696096 s: GTC Frequency = 200 MHz
APP: Init ... Done !!!
43.704544 s: VX_ZONE_INIT:Enabled
43.704574 s: VX_ZONE_ERROR:Enabled
43.704581 s: VX_ZONE_WARNING:Enabled
43.705648 s: VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
43.706931 s: VX_ZONE_INIT:[tivxHostInitLocal:93] Initialization Done for HOST !!!
enter app_tidl_rci_od_main
enter app_default_param_set
enter set_scaler_defaults
exit set_scaler_defaults
enter set_pre_proc_defaults
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Thanks,

S Seetharama Raju.

  • 0 in reply to Nikhil Dasan
    Prodigy 170 points

    Hi,

    I have followed the above thread. I have imported the model on latest SDK and replaced them with the old ones for the application.I have run the application followed by the "./vx_app_arm_remote_log.out &" command. I faced error after running the application. The log is attached below.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    root@j7-evm:/opt/vision_apps# ./run_app_tidl_rci_od.sh
    APP: Init ... !!!
    MEM: Init ... !!!
    MEM: Initialized DMA HEAP (fd=4) !!!
    MEM: Init ... Done !!!
    IPC: Init ... !!!
    IPC: Init ... Done !!!
    REMOTE_SERVICE: Init ... !!!
    REMOTE_SERVICE: Init ... Done !!!
    51.771249 s: GTC Frequency = 200 MHz
    APP: Init ... Done !!!
    51.779427 s: VX_ZONE_INIT:Enabled
    51.779451 s: VX_ZONE_ERROR:Enabled
    51.779457 s: VX_ZONE_WARNING:Enabled
    51.780353 s: VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
    51.782285 s: VX_ZONE_INIT:[tivxHostInitLocal:93] Initialization Done for HOST !!!
    enter set_scaler_defaults
    exit set_scaler_defaults
    enter set_pre_proc_defaults
    exit set_pre_proc_defaults
    enter set_display_defaults
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Can you please guide me based on the above error log?

    Thanks,

    S Seetharama Raju,

  • 0 in reply to Seetharama Raju
    TI__Guru* 81876 points

    Hi,

    Here the error is

    Config file size (-1 bytes) does not match size of sTIDL_IOBufDesc_t (37256 bytes)

    it means that the config.bin file that you have provided is not being read correctly. Could you please check this .bin file and also please check if the path to this file is being given correctly.

    Regardsm

    Nikhil

  • +1 in reply to Nikhil Dasan
    Prodigy 170 points

    Hi,

    The above mentioned reply and this one collectively helped me achieve the objective. 

    Thanks,

    S Seetharama Raju.

  • +1 in reply to Nikhil Dasan
    Prodigy 170 points

    Hi Nikhil,

    After importing the model in the latest sdk 08.06.01.03, the error Network version - 0x20221206, Expected version - 0x20230208 is eliminated.

    Thanks,

    S Seetharama Raju.