TDA4VM:Issue in running custom layer on target

Vyom Mishra1

We are trying to implement a custom layer which works fine during Importing and PC Emulation.Please find the details of last five layers after importing

68|TIDL_ConvolutionLayer |576 | 0| 1| 1| 64 x x x x x x x | 68 | 1 320 16 16 | 1 256 16 16 | 21102592 |
69|TIDL_ConcatLayer |577 | 0| 4| 1| 65 66 67 68 x x x x | 69 | 1 256 16 16 | 1 1024 16 16 | 262144 |
70|TIDL_ConvolutionLayer |580 | 0| 1| 1| 69 x x x x x x x | 70 | 1 1024 16 16 | 1 256 16 16 | 67239936 |
71|TIDL_CustomLayer |590 | 0| 1| 1| 70 x x x x x x x | 71 | 1 256 16 16 | 1 256 32 32 | 1048576 |
72|TIDL_DataLayer |590 | 0| 1| -1| 71 x x x x x x x | 0 | 1 256 32 32 | 0 0 0 0 | 0 |

But the results on target are not as expected.
We have build tidl using make rt and TI_DEVICE_a72_test_dl_algo_host_rt.out was generated.

We are also not able to dump layerwise outputs from target with debugtracelevel=1 and writetracelevel=3.
PFA the logs:

[C7x_1 ] 69.951423 s: 0 1.00000 0.00000 255.00000 0
[ 130.996498] Initializing XFRM netlink socket
[ 133.106569] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 133.124820] Bridge firewalling registered
[MCU2_0] 187.719442 s: DHCP client timed out. Retrying.....
[MCU2_0] 355.719440 s: DHCP client timed out. Retrying.....
[MCU2_0] 523.719443 s: DHCP client timed out. Retrying....

How to get layer dumps from target?

During inference we are using execmode "TIDL_EXEC_MODE_INFER_PROCESS_REF".Is this mode expected to run on target too?

NOTE: SDK used : ti-processor-sdk-rtos-j721e-evm-07_01_00_11

Regards

Vyom MIshra

over 4 years ago

0 Anshu Jain over 4 years ago

TI__Guru 56820 points

Hi Vyom,

Vyom Mishra1 said:
How to get layer dumps from target?

If you are following steps as mentioned in below document trace dumps should be working :
https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_02_00_05/exports/docs/tidl_j721e_08_02_00_11/ti_dl/docs/user_guide_html/md_tidl_sample_test.html#tidl_inference_4

Note that for comparison purpose you can use writeTraceLevel=1 ( no need to compare floating point output ). Other possible reason why it may not be working is if you dont have trace folder or looking at the wrong trace folder ( this is assuming you are using default location for trace dump). Default trace folder is expected to be at same directory as testvecs folder.

Vyom Mishra1 said:
During inference we are using execmode "TIDL_EXEC_MODE_INFER_PROCESS_REF".Is this mode expected to run on target too?

Assuming you are using all default parameters for inference then execMode should be coming as TIDL_EXEC_MODE_INFER_PROCESS

Regards,

Anshu

0 P C over 4 years ago

Prodigy 40 points

Hi, Vyom:

Have you worked the issue out? I had similar problem when trying to implement the custom layer. PC emulation worked fine but not on the device.

My post and experience details are here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1088991/custom-layer-works-in-pc-emulation-mode-but-not-for-evm-version-07_01_00_11/4052013#4052013

With all I can imagine tried, I doubt whether it is because the newly-bulit files were not correctly copy to the SD card. Seemed not only the binary execution file but also some system dynamic so file required to update. I plan to employ a new sd card on the board and update all the system files.

Appreciated for any suggestions and I would feed back when progress is made.

Regards

Peng Chen

Processors

Processors forum

TDA4VM:Issue in running custom layer on target