The Hexagon SDK allows custom programmability for the DSP coprocessor on the Snapdragon 800 platform. If I want to develop and test applications that use the DSP coprocessor, can I do so directly on the emerging smartphones featuring the Snapdragon 800 SoC such as Google Nexus 5? Or do I need to specifically use the MDP for development and the smartphones for deployment? If I can use directly the commercial devices for both development and deployment, are there any restrictions compared to the MDP case?
Thanks.
HI,
To develop applications and features on deployment devices, you need to enable signing process which is specific to every OEM. Hence MDP is the suggested platform for development. You can check 8074 dragonboard which is fully compliant with Hexagon SDK and provides smooth development experience.
Thanks.
It seems like running elfsigner.py is not enough. I've tried to do this for a Galaxy S5 and the the DSP application will fail as soon as it gets to the portion of code that's processed on the aDSP. Is the signing process to simply create a new testsig-0x<serial number>.so and put it in the /system/lib/rfsa/adsp folder? I've done this and it works on the dragonBoard but not on the Galaxy
After development is done on the MDP, can an app be created to be deployed on a production device? How would you sign an app for a specific OEM?
To run a shared library on production device, the library must be signed by respective OEM. As your library is not signed by Samsung, hence it fails to load on Samsung phone whereas it works fine on dragonboard(which is a development device).
You need to contact respective OEM to sign the shared library and plug it into their phone.
Thanks,
Abhikrant
Thanks for the response, you've been a huge help!
Hi,
As it has been some time since last post in this thread I am wondering if things have changed.
Are there any plans to "enable" aDSP support on commercial devices for developing purposes or maybe there were some solutions popped up already?
Br,
Edyta
HI,
This limitation is not from Qualcomm but from the phone manufacturer. Any shared object that's loaded on DSP of a commercial phone needs to be signed by respective OEM. So, you need to contact the OEM for getting your shared object signed to run it on DSP.
Thanks
How about development devcies such as Nexus 6 with custom built AOSP?
Is the signing still necessary or is there a workaround?
I see /dev/adsproc-smd exists but no adsprpcd is running.
Any ideas or clarifications?
Just as farleylai said, will that be possible to run the code on a Nexus/Pixel with custom built AOSP? Can we change the way the DSP code is signed and migrate our own code to run on the DSP?
I am bring up this topic again course deploying and running my code on actual devices is vital to our development.
Hope somebody can share the experience on this topic.