Rubik Pi 3 QCS6490: Is ADSP AudioReach custom CAPI module development supported?

Hi Rubik Pi / Thundercomm team,

I am a developer working on audio DSP experiments with the Rubik Pi 3 / QCS6490 platform.

I am trying to evaluate whether it is possible to add a custom AudioReach CAPI module into the ADSP AudioReach/SPF runtime on Rubik Pi 3.

So far, I have done the following:

  • Built a custom AudioReach module based on the open-source audioreach-engine
  • Successfully generated a Hexagon v68 DSP libspf.so
  • Confirmed that the generated libspf.so contains my custom CAPI symbols
  • Generated H2XML / JSON / AMDB metadata for the custom module
  • The custom module ID I am using is 0x0800F001

However, the actual board-side ADSP firmware appears to be loaded from:

qcom/qcs6490/Thundercomm/RubikPi3/adsp.mbn

My current understanding is that this adsp.mbn already contains the ADSP runtime, AudioReach/SPF, AMDB, and built-in CAPI modules such as the factory MSIIR module.

I would like to ask:

  1. Does Rubik Pi 3 provide any official BSP / SDK package that includes the ADSP source tree, such as adsp_proc, AudioReach/SPF integration sources, and ADSP firmware build scripts?

  2. Is it possible for developers to rebuild or customize the Rubik Pi 3 ADSP firmware image, especially:

qcom/qcs6490/Thundercomm/RubikPi3/adsp.mbn
  1. Is there an official way to add a custom AudioReach CAPI module into the ADSP AudioReach/SPF runtime?

  2. Should such a module be built statically into adsp.mbn, or is dynamic CAPI module loading supported on Rubik Pi 3?

  3. Is AudioReach Creator / ARC / QACT available for custom module registration on this platform?

  4. Are there any firmware packaging, test-signing, or signing requirements for loading a developer-built ADSP firmware image on Rubik Pi 3?

  5. If ADSP custom module development requires NDA, licensed developer access, or a partner program, could you please point me to the correct contact channel?

My goal is not to modify Linux user-space FastRPC libraries. I am specifically trying to understand whether a custom AudioReach CAPI module can be added to the ADSP AudioReach graph and executed on the QCS6490 ADSP.

Any guidance, documentation, or recommended development path would be greatly appreciated.

Thanks!

Please leave your email address, and we will discuss subsequent details via email.

Thank you for your reply.

My email address is: athrunchen0829@gmail.com

We have sent the email.