Questions about DM8148 hardware crypto engine

Hongfeng Wang

Environment: custom DM8148 board, kernel based on psp4.04

1. I followed the instructions on Wiki to patch the kernel, I see /dev/hwrng and /dev/crypto and following messages during boot up:

nss_aes_mod_init: loading NSS AES driver
nss-aes nss-aes: NSS AES hw accel rev: 3.2 (context 0 @0x41140000)
nss-aes nss-aes: NSS AES hw accel rev: 3.2 (context 1 @0x41141000)
nss-aes nss-aes: NSS AES hw accel rev: 3.2 (context 2 @0x411a0000)
nss-aes nss-aes: NSS AES hw accel rev: 3.2 (context 3 @0x411a1000)
nss_aes_probe: probe() done
nss_des_mod_init: loading NSS DES driver
nss-des nss-des: NSS DES hw accel rev: 2.2 (context 0 @0x41160000)
nss-des nss-des: NSS DES hw accel rev: 2.2 (context 1 @0x41161000)
nss_des_probe: probe() done
nss_sham_mod_init: loading NSS SHA/MD5 driver
nss-sham nss-sham: NSS SHA/MD5 hw accel rev: 4.3 (context 0 @0x41100000)
nss-sham nss-sham: NSS SHA/MD5 hw accel rev: 4.3 (context 1 @0x41101000)
nss-sham nss-sham: NSS SHA/MD5 hw accel rev: 0.0 (context 2 @0x411c0000)
nss-sham nss-sham: NSS SHA/MD5 hw accel rev: 0.0 (context 3 @0x411c1000)
nss_sham_probe: probe() done

notice the part I marked in red is different from the example on Wiki.

When I run des test, the device appears ok, but every other test I tried include 3des, aes, sha1 will cause system hang.

2. How do I use openssl with hw crypto?
I am using OpenSSL 1.0.0e 6 Sep 2011 that comes with ubuntu11.10 armel.

I tried openssl engine cryptodev, it will give me this error:

DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:184:filename(/usr/lib/arm-linux-gnueabi/openssl-1.0.0/engines/libcryptodev.so): /usr/lib/arm-linux-gnueabi/openssl-1.0.0/engines/libcryptodev.so: cannot open shared object file: No such file or directory

Nowhere could I find the libcryptodev.so needed.

over 12 years ago

0 Hongfeng Wang over 12 years ago

Genius 3925 points

one more thing:

when I "cat /dev/hwrng", there's no output at all. When I read the register of RNG_REG_STATUS, it always returns zero.

0 Hongfeng Wang over 12 years ago

Genius 3925 points

After migrating to RDK3.2 from 2.8, I am still experiencing same issue.

BTW: is there a detailed datasheet for the crypto engine?

0 Hongfeng Wang over 12 years ago in reply to Hongfeng Wang

Genius 3925 points

This is weird:

In user space, I could read the HWRNG registers use mem_rdwr.out and the result makes sense.

But in kernel space, trng_read(STATUS) returns totally different value, which has ready bit always zero.

0 Hongfeng Wang over 12 years ago in reply to Hongfeng Wang

Genius 3925 points

I still haven't figured out the HWRNG issue. But AES encryption using OCF is working fine.

There's one issue with the SHA though, for example I have one file which should have SHA1 hash "928f3a0bf22f3654b0d5db263c8d71f20d1fb278",

but the cryptodev sometimes give a output of "00000000928f3a0bf22f3654b0d5db263c8d71f2", have anybody seen something like this?

0 Vladimir-XID over 12 years ago in reply to Hongfeng Wang

TI__Genius 11470 points

Hello,

Please, let us know what is the software release you are using.

Also can you please post the exact link to the guide you are following?

Thank you.

Vladimir

0 Hongfeng Wang over 12 years ago in reply to Vladimir-XID

Genius 3925 points

I am using RDK3.2, I have a custom DM8148 board, the chip has silicon version 2.1

The wiki article I followed:

http://processors.wiki.ti.com/index.php/Installing_AM387x_C6A814x_DM814x_Crypto_Support

0 Vladimir-XID over 12 years ago in reply to Hongfeng Wang

TI__Genius 11470 points

Hello,

That is DVR RDK, right?

In that wiki page clicking the link to the NSS-Crypto-driver-software results in downloading corrupted 0 bytes archive. So which patches you are applying?

Vladimir