RubikPi as a development platform

Technical Sharing
1

I would like to use this device as a development platform and will require a way to sign and load images directly on the Hexagon DSP. Typically I would use a program called sectools along with a device security profile file to sign images. If they are already provided please let me know where to find them, otherwise please add them to a existing repo or create a new one.

I will also require the devcfg.mbn without access controls, named devcfg_noac.mbn.

Having a technical reference manual that describes the address ranges within the SOC would also be very helpful.

2

You need to ask Qualcomm for the QCM6490 (will work on QCS, because the soc is just a APQ variant. source is entirely compatible) BSPs (specifically trustzone_images for devcfg) and sectools.
It is not allowed to be shared

3

Hey Qualcomm where are these things? Is this the official position of the device vendor?

4

Qualcomm is the SoC vendor who also distributes the BSPs (board support package) to device vendors, vendors usually modify the bsps to some extent, but the rubik seems to be rather clean.

5

We can build the devcfg.mbn without access controls for you, named devcfg_noac.mbn.
Due to license restrictions, the image signing-related content is not yet open-sourced. If you are an enterprise-level user, please leave your email, and we will continue the discussion via email.

6

Limiting devcfg_noac.mbn to enterprise users isn’t ideal for the community at large. I acknowledge that poor choices in memory access with noac will result in system crashes but the role of a development target is to grant users willing to experiment that option.

With respect to signing (sectools) please take note that Qualcomm has recently released H2, see: GitHub - qualcomm/hexagon-hypervisor: Hexagon Hypervisor (AKA h2) is a light weight OS / Hypervisor for the Qualcomm Hexagon processor family · GitHub My only experience loading custom firmware is by using sectools and the device security profile to create the mbn.

When the above is available on RubikPI, getting linux to run on the device might be possible given the recent updates seen here: https://git.kernel.org/pub/scm/linux/kernel/git/bcain/linux.git/

No good deed goes unpunished, and if the the above is made public the next ask will be for a technical reference so developers can understand the memory layout and MMIO spaces of the SOC.

7

Regarding the devcfg_noac.mbn image, we can build and provide a version with access controls disabled for you.
Thank you as well for your response and suggestions. We are currently aligning internally and will carefully review and consider the items raised.