We faced an issue that we believe it was not in the SDK 8.2 but introduced in the SDK 8.6. (Simply saying, board output is the same as in the X86 emulation in SDK 8.2 but board output is diffeent in SDK 8.6).
About this matter, I was told to try:
"One quick reason I can think of for the difference b/w 8.2 and 8.6 is one optimization approach enabled in 8.6 which was not there in 8.2. So if you want to try one change, please change the `DEVICE_NAME=0` in device_config.cfg file before model import and see if the issue goes away"
May I ask a little bit about the "device_config.cfg"?
To import (onnx->tidl binaries) our model, we just use the SDK executables like
"{tidl_sdk_path}/utils/tidlModelImport/out/tidl_model_import.out SOME_IMPORT_CONFIG.txt"
The command apparently accepts a configuration from "SOME_IMPORT_CONFIG.txt", but I didn't know "device_config.cfg" was involved.
I'm seeing "devicde_config.cfg" files from
./..../targetfs/opt/tidl_test/testvecs/config/import/device_config.cfg
./..../tidl_j784s4_08_06_00_10/tidl_tools/device_config.cfg
./..../tidl_j784s4_08_06_00_10/ti_dl/test/testvecs/config/import/device_config.cfg
So could you please confirm my understanding?
- Before we import (onnx->tidl binaries) our model,
- Change the "device_config.cfg" with DEVICE_NAME=0 <-- but which path among above? In tidl_j784s4_08_06_00_10/tidl_tools?
- Run the import process with the command and create the tidl binary files.
- Is there "device_config.cfg" for emulator and board inference? or is it just for import process?
