Thanks for reply.
I’m now trying with nvdla_runtime with kmd/umd from Xavier,
but I have found some inconsistency between Xavier’s umd and open-sourced version of umd.
Thus I can’t run open-sourced version of nvdla_runtime over Xavier’s umd.
Anywhere I can find header files for Xavier’s umd?
if (!i->runtime->initEMU())
ORIGINATE_ERROR(NvDlaError_DeviceNotFound, "runtime->initEMU() failed");
==
But I found that the open-sourced implementation for “bool Runtime::initEMU(void)” returns true if succeed, and false otherwise, while in Xavier’s implemenation, it seems to return “number of available DLA devices”.
That’s why I suspect the Xavier’s umd is inconsistent with open-sourced one.
I think I’ll need the Xavier’s umd headers, not the open-sourced ones, and modify RuntimeTest.cpp to make it work.
After checking with our internal team, the GitHub test app is for OpenDLA and cannot be used on the Xavier.
A possible workaround is to use nvdla_runtime app from OpenDLA with libnvdla_runtime.so released with the Jetpack.
They are API compatible. Would you mind to give it a try?
I don’t quite get it. Did you mean the libnvdla_runtime.so in
JetPack_4.2_Linux_P2888/Linux_for_Tegra/rootfs/usr/lib/aarch64-linux-gnu/tegra/libnvdla_runtime.so ?
Looks like it’s the same as the one already in Xavier’s file system, which is not working, as described before.
In general, the GitHub source is for OpenDLA and the version of JetPack4.2 is not open source.
But we think they are API compatible. I will check with the developer again.