Forums - getsignature failure

4 posts / 0 new
or Register
Last post
getsignature failure
KingCobra
Join Date: 19 Feb 13
Posts: 11
Posted: Mon, 2016-06-20 17:02
Top

Hello, I just got started recently released SDK 3.0.

Unfortunately, I am not able to get getsignature to retrieve the serial number from Qualcomm (Intrinsyc) DragonBoard 820. I loaded target with getserial that was in tools/elfsigner and tried to invoke it from adb shell as root.

I have no clue what I need to do to move past this hurdle which prevents me from successfully running example code.

Thanks in advance for any help.

  • Up0
  • Down0
Re: getsignature failure
chenna
Join Date: 4 Feb 16
Posts: 54
Posted: Mon, 2016-06-20 20:36
Top

Looks like getserial has issues on 820dbs, Please try the following to get the serial number 

adb shell cat /sys/devices/soc0/serial_number

  • Up0
  • Down0
Re: getsignature failure
KingCobra
Join Date: 19 Feb 13
Posts: 11
Posted: Tue, 2016-06-21 09:43
Top

Hello chenna, thank for the reply. I was able to get the serial number and generate/install the test signature. However, when I proceed to running the calculator app I get the following error:

root@thor:/ # cd /data
root@thor:/data # ./calculator 0 1 1000                                        

- starting calculator test
adspmsgd not supported
- 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>

adspmsgd_stop failed

Here is what I see in logcat:

1-01 17:11:05.464 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:307::error: -1: 0 == ioctl(dev, FASTRPC_IOCTL_INIT, (unsigned long)&init)
01-01 17:11:05.468 16228 16228 D adsprpc : vendor/qcom/proprietary/adsprpc/src/platform_libs.c:29: apps_dev init failed
01-01 17:11:05.468 16228 16228 D adsprpc : vendor/qcom/proprietary/adsprpc/src/platform_libs.c:29: apps_dev init failed
01-01 17:11:05.468 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:118::error: -1: dev != -1
01-01 17:11:05.468 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:169::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
01-01 17:11:05.468 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:118::error: -1: dev != -1
01-01 17:11:05.469 16228 16228 E adsprpc : src/rpcmem_android.c:271::error: -1: 0 <= ioctl(m->fd, ION_IOC_ALLOC_KK, &alloc)
01-01 17:11:05.470 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:118::error: -1: dev != -1
01-01 17:11:05.470 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:169::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
01-01 17:11:05.470 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:118::error: -1: dev != -1
01-01 17:11:05.471 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:118::error: -1: dev != -1
01-01 17:11:05.471 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:169::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
01-01 17:11:05.471 16228 16228 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:118::error: -1: dev != -1


Any ideas? Thanks!

 

  • Up0
  • Down0
Re: getsignature failure
KingCobra
Join Date: 19 Feb 13
Posts: 11
Posted: Tue, 2016-06-21 11:15
Top

Please ignore my last post. I am able to run the example after a reboot of the target.

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.