I want to debug VTA runtime details and check how they call API and run VTA internals.
(BTW, I already know where the driver code is, but I cannot find any examples, sequences or usages)
In my understanding,
vta.build() emits a binary object (vadd.o) that has a sequence of driver API.
And it finally will be linked with a shared VTA runtime library (libvta.so) to run.
But, the generated code is binary and I cannot debug those codes.
I think there might be a proper way to see details of “vadd.o” during development.
(e.g. Decompilation of the object file,
vadd.o, using llvm)
The following is some possible materials I found, but not solutions.
vta.lower(..., simple_mode=False)could be a possible option,
but it’s not available for the schedules generated from
I tried it but no success.
vta-torture (?) code illustrates some sequence of instruction memory setup,
but seems it’s only a part of tests and isn’t fully runnable. (Was quite helpful anyway)
At least, if you could just check whether I missed something, it’d be great.
Thank you in advance.