Hello, I used released SDK 3.0.
Unfortunately, when I proceed to running the calculator app I get the following error
1|ailsa_ii:/data # ./calculator 0 1 1000
./calculator 0 1 1000
- starting calculator test
- allocate 4000 bytes from ION heap
- creating sequence of numbers from 0 to 999
- compute sum on the aDSP
Error: compute on aDSP failed
usage: ./calculator <1/0 run locally> <1/0 logcat> <uint32 size>
Here is what I see in logcat:
01-14 14:59:43.466 3027 3028 E adsprpc : sigverify.c:684:0x10af:codesig root: 0c,09,76,0d (qc test)
01-14 14:59:43.469 3027 3028 E adsprpc : sigverify.c:699:0x10af: image root[0]: b6,6f,91,3f
01-14 14:59:43.470 3027 3027 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:421::error: -5: 0 == (nErr = dlerr)
01-14 14:59:43.470 3027 3027 D adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:425: dlopen error: calculator signature verify start failed for libcalculator_skel.so
01-14 14:59:43.471 3027 3028 E adsprpc : sigverify.c:701:0x10af::error: signature does not match image root
Thanks in advance for any help.
I guess you are trying on OpenQ 8096 DB, the build that these dragonboards are shipped with has problems in generating testsig.
Please follow the steps mentioned below to generate test-sig
-> to get the serial number run this command adb shell cat /sys/devices/soc0/serial_number
-> convert the serial number to hex, and pass it to elfsigner.py as follows
python tools/elfsigner/elfsigner.py -t serialNum
-> testsignature will be saved at tools\elfsigner\output\testsig-xxxx.so
push it to device
adb push testsig-xx.so /system/lib/rfsa/adsp/
and try rerunning the calculator
hi chenna
i now work on P996A01_N of zte, it is msm8996 platform. i had tried your method, it is still error.
what do it need to do additionally if i use zte board?
can you provide me the getserial output
adb shell /data/getserial
ok , cool
can you just run python C:\Qualcomm\Hexagon_SDK\3.0\scripts\testsig.py and provide the ouput
hi chenna
C:\Qualcomm\Hexagon_SDK\3.0\tools\elfsigner>python C:\Qualcomm\Hexagon_SDK\3.0\scripts\testsig.py
ok , for the time being you can comment this line in testsig.py
serialNum = subprocess.check_output(getSerialNum, shell=True)
and add serialNum=0x89ce0d82 and continue running the script.
to find the actual problem with that command, can you provide use the output of this command
adb shell /data/getserial | grep -o \"0.*\"
ok
i had find the reason when run testsig.py
i update python version to 2.7 and modify the cmd to
getSerialNum='adb shell /data/getserial | grep -o "0.*" | tr -d "\\n\\r"'
and the output is
You can run the calculator now . It will work
hi chenna
i had reboot the phone to run the calculator, the previous relay is the log output, it had still error.
can you call me 02168896132
Test-sig command script output suggest that the test-sig has pushed to target but not sure why the logcat is showing the same error again , can you clean the logcat and rerun the calculator walkthrough script and proivde both calc walkthrough and logcat output
hi chenna
i used the getserial to get the device serial number before,
then you ask me to get device serial number by testsig.py,we solve the script problem.
but this both generate testsig-0x89ce0d82.so, i think that they are alike.
hi chenna
in the sdk doc, i see
Signatures generated using the elfsigner from the SDK allow SDK users to prototype and test their software on debug devices such as Dragon Boards. However these testsigs and signed .so files would not authenticate successfully on production devices such as OEM phones and tablets.
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.
i need how to check the info in zte devices.
that should be fine.
regarding the signing of dynamic modules on production devices, I am discussing with my team internally and will get back to you
hi chenna
how about the problem?
Any updates on, how we can sign .so on production build? Thanks.
Hi Chenna,
I am also facing similar problem, waiting for your reply,
In my case the device is OnePlus3T running 821 SOC. Thanks.
Regards
Milind
I algo got this error.hope for any help.
Hi chenna, do you know the correct way to sign production device .so now?
I had the same problem recently when I tried to run my APP on production device using DSP.
Need help !
Hello Chenna
it appears that i also have similar problem when i try calculagtor example by using calculator_walthrough.py -T 8996 -D adsp options. Rest all appears to be good but the following . Could you kindly advice me... thanks in advance
Hello ,
I had the same problem. I am current tryinh to run the same calculator example on hamoa device on adsp domain and getting the same error. One thing that worked was runnig this command from elfsigner "python elfsigner.py -r "path to the hexagon build/ship" directory. The -r argumnent indicates the input directory for image files that are to be signed". This command would then produce a libcalculator_skel.so. This file then has to be manually put into the device and this enables to fix the problem atleast by signing the skel file this way.