hexagon-dsp

Android - Dynamic module(.so) needs to be production signed

十年热恋 提交于 2020-07-07 12:23:21
问题 As i understand this from Hexagon DSP document: To enable a .so to be successfully deployed on production devices across a large number of OEM devices, the dynamic module needs to be production signed by the OEM. ISVs are encouraged to work with their OEM POCs to have the modules production signed for OEM devices. So, is there any way i can get my .so(s) to work on production device (OnePlus 3T running OxygenOS originally)? I have tried to root the device by compiling LineageOS and installing

How to profile code in hexagon dsp simulator

狂风中的少年 提交于 2020-01-05 04:23:08
问题 I have been trying to compile my code using -pg to enable profiling in the simulator and once I do that it gives me linker errors. Compilation command hexagon-clang++ main.cpp -o hello -mv62 -pg Error hexagon-clang++ main.cpp -o hello -mv62 -pg Error: /tmp/main-924ac3.o(.text+0x30): undefined reference to `mcount' Error: /tmp/main-924ac3.o(.text+0x130): undefined reference to `mcount' Fatal: Linking had errors. This is my first time to write code for DSP chip, specifically the hexagon 682.

TensorFlow HVX Acceleration support

柔情痞子 提交于 2019-12-10 17:27:12
问题 I successfully built and ran the test application from https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/hvx. I'd now like to benchmark HVX against the CPU implementation of https://github.com/tensorflow/tensorflow/tree/master/tensorflow/tools/benchmark, and if possible, the Android camera demo, to see how much it would help, but I wasn't able to find any documentation describing how to build said apps with HVX support (my builds run on the CPU). I'm testing on the Open