• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 424 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.

TDA4X :Quant_Stats_Tool in the latest release

Sithara Tresa Chacko
Expert 1120 points


Dear Sir,

With latest release of psdk version psdk_rtos_auto_j7_06_02_00_21 and tidl version tidl_j7_01_01_00_10,

TIDL_quant_stats tool was not present by default  in the ti_dl/test folder. Ran make from test folder

While  running ./PC_dsp_test_dl_algo.out   ,observed the following error:

Processing config file #0 : testvecs/config/infer/public/caffe/tidl_infer_jdetNet.txt
Error at line:   217 : in file          src/tidl_tb.c, of function : tidl_tb_algCreate
Error Type: TIDL_E_QUANT_STATS_NOT_AVAILABLE           
Error at line:   496 : in file          src/tidl_tb.c, of function : tidlMultiInstanceTest
Error Type: TIDL_E_QUANT_STATS_NOT_AVAILABLE    

Kindly let us know why.

Regards,

Sithara Tresa Chacko

  • 0
    TI__Expert 6335 points

    Hi,

    Now there is no separate quant tools. The PC_dsp_test_algo.out can perform either quant tools or inference processing depending on the value of the new parameter flowCtrl from the inference config file.

    If flowCtrl = 2, it will force PC_dsp_test_algo.out to behave like the quant stat tool.

    flowCtrl=0 is the normal behaviour of inference processing. On PC, it will run reference C code and on EVM, it will use hardware accelerator.

    flowCtrl=16 will validate each layer's output executed on hardware with reference code. Note that  debugTraceLevel must be set to 1 to see the output log on the console. Also it is recommended to execute this mode on the EVM because on PC, the hardware is emulated by C-code is very slow.

    Since the quant tools no longer exist, you have to update your import config file by removing the line that specifies the path to the quant tool. Then by default, the import tool will look for PC_dsp_test_algo.out and execute the calibration/quantization  stage successfully, This will get rid of the error you are having at inference because the quantization data will be there.

    regards,

    Victor