Part Number: AM62A7
The SDK version burned into our AM62A is 11.01.07.05, the TIDL version is 11.01.06.05, and the tensorlab version is R11. When testing the output of the SDK version information on the board, it shows 11.1.0. When running the quantized model, the following error occurred:
/bin/Release/ort_main -f model-artifacts/3dod-8161_onnxrt_pandaset_mmdet3d_fastbev_mod_pandaset_nms_r18_f1_256x704_20250507_onnx/artifacts ***** Display run Config: start ***** verbose level set to: 3 accelerated mode set to: 1 device mem set to: 1 loop count set to: 1 model path set to: model artifacts path set to: model-artifacts/3dod-8161_onnxrt_pandaset_mmdet3d_fastbev_mod_pandaset_nms_r18_f1_256x704_20250507_onnx/artifacts image path set to: device_type set to: cpu labels path set to: test_data/labels.txt num of threads set to: 4 num of results set to: 5 num of warmup runs set to: 2 ***** Display run Config: end ***** libtidl_onnxrt_EP loaded 0x625fbf0 Final number of subgraphs created are : 1, - Offloaded Nodes - 207, Total Nodes - 207 APP: Init ... !!! 4234.789057 s: APP_LOG: ERROR: Unable to map memory @ 0xa1000000 of size 262144 bytes !!! APP: ERROR: Log writer init failed [ 4228.778759] audit: type=1701 audit(1748555806.056:96): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=2101 comm="ort_main" exe="/home/workspace/edgeai-tidl-tools-11_01_06_00/bin/Release/ort_main" sig=6 res=1 !!! APP_LOG: ERROR: Unable to map memory @ 0xa2000000 of size 3[ 4228.803178] audit: type=1334 audit(1748555806.080:97): prog-id=53 op=LOAD 288576 bytes !!! APP: ERROR: File IO writer init failed !!! AP[ 4228.812735] audit: type=1334 audit(1748555806.088:98): prog-id=54 op=LOAD P: Init ... Done !!! terminate called after throwing an instanc[ 4228.825031] audit: type=1334 audit(1748555806.100:99): prog-id=55 op=LOAD e of 'Ort::Exception'
There is another strange phenomenon: when I burned the official 11.1.7.5 SDK image to the am62a, the board failed to start normally and an error "can not reading u-boot.img" occurred. However, when I replaced the u-boot.img in the boot with a lower version (such as 10.x, 9.x), the board could start normally. Why is that?
