Using SDP with software decoding in Hikey620



Following by @vchong, I am able to set-up Hikey 620 with AOSP + OPTEE. Xtest 1014 for SDP passed.

I am trying to use SDP with Software decoding in Hikey620. How can I achieve this?

Please help. Thanks in advance.


Chromium crash while using SDP with software decoder in Hikey620

Try referencing and


Thanks. I will check these.


Hi @vchong,

I have compiled the code after taking the changes from the links shared by you. The code compiles successfully. But in order to use SDP, the codec name must end with .secure.

Thus I added .secure suffix with “” in device/linaro/hikey/etc/media_codecs.xml to get “”

But the chromium browser crashes while I try to stream a content in HIkey 620 with these changes.

The error log is as follows:

01-01 00:00:47.002  1948  1956 I OMXMaster: makeComponentInstance( in omx@1.0-service process
01-01 00:00:47.002  1948  1956 E /vendor/bin/hw/ Failed to allocate omx component ''  err=InvalidComponentName(0x80001002)
01-01 00:00:47.003  1945  1964 W OmxInfoBuilder: Fail to add mime video/avc to codec
01-01 00:00:47.004  1849  1849 W /system/bin/hwservicemanager: getTransport: Cannot find entry in either framework or device manifest.

I must be missing something. Do you have any idea?


Hi Sayan,

Full SDP on HiKey with software decoding can’t really be done as the OMX decoder is running on the host CPU, so it makes little sense to enable the .secure for the OMX codecs (unless you want to put the codec in OP-TEE but that is unadvised).

We did do a SDP_PROTOTYPE feature, which relies on the memory firewall protection in ATF being disabled, and then maps the secure buffer and memcpy() the contents. But that was really just for testing purposes.

In addition for Android you should be using the ClearKey mediadrm [1] plugin. However with regards to Chromium browser some changes are required in Chromium source for an Android build as it has a built-in ClearKey OpenSSL CDM which is uses for ClearKey playback rather than searching for a mediadrm plugin on the target.

With other key systems such as Widevine or Playready, it will use mediadrm plugin on Android straight away, but with ClearKey it we found it uses the built in OpenSSL decryptor rather than searching for the plugin.

If you want to do SDP development you are better off using a platform which actually has secure codec support such as iMX8M-evk board. Here the OMX plugins for the platform have been updated to allocate a secure buffer using ION, and the memory protection firewall is configured so that the only the decoder and display hardware can access the memory.




Hi Peter,

Thanks for the explanation. I can understand the problems.
But is it the case that SDP cannot be achieved without Hardware decoding?

While debugging, I somehow managed to use the mediadrm plugin but unfortunately Chromium crashed. I already posted this issue in the link Chromium crash while using SDP with software decoder in Hikey620



Hi Sayan,

Yes, SDP can only be achieved when using hardware decoding, (or by putting the software codec into secure world, but that is unadvised).

The crash you posted is crashing in OMX library code, I believe because the default OMX software codecs that google provide don’t support allocating a secure buffer.



Hi Peter,

Thank you very much for the information.



Hi @peter-griffin,

Could you please point me to the code base from where I can use SDP_PROTOTYPE feature. I came across some forked versions but not sure whether those works.



Hi Sayan,

To get a working Android plus OP-TEE working baseline your best bet is to follow these instructions here

Then to add in ExoPlayer and ClearKey op-tee mediadrm plugin plus the best instructions are Although due to a Linaro re-organisation MMWG don’t look after Android activities any longer so this isn’t being actively maintained atm (although patches are welcome :slight_smile: ).

The code to disable memory firewall in ATF is here



Thanks Peter for the information.

Let’s see what can be done :slight_smile: