RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

adamfowleruk — Wed, 10 Mar 2021 08:02:12 GMT

This seems to have resolved my issue. It won't run - but that's entirely my own bug! Libraries are now compiling, linking, and executing fine. Thanks for your help!

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

adamfowleruk — Mon, 08 Mar 2021 21:56:32 GMT

So this configuration allowed me to build and still allows me to call

nrf_cc3xx_platform_entropy_get(buf,buflen,&olen);

#CONFIG_NRF_CC3XX_PLATFORM=y
#CONFIG_CC3XX_BACKEND=y
#CONFIG_NORDIC_SECURITY_BACKEND=y
CONFIG_NRF_SECURITY_RNG=y
CONFIG_ENTROPY_GENERATOR=y

# Simple Payload support BEGINS
# Option 1: MBEDTLS
CONFIG_MBEDTLS_VANILLA_BACKEND=y
CONFIG_MBEDTLS_MAC_SHA256_ENABLED=y
CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_BUILTIN=y
CONFIG_MBEDTLS_CFG_FILE="config-tls-generic.h"

I now have a runtime issue which may or may not be in the sha256 code. I'll investigate further and let you know if this has resolved my issue. Thanks!

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

adamfowleruk — Mon, 08 Mar 2021 21:37:14 GMT

Using your config as a starting point I've found the below are required for the warnings about missing config items to disappear:-

CONFIG_NRF_CC3XX_PLATFORM=y
CONFIG_NORDIC_SECURITY_BACKEND=y
CONFIG_NRF_SECURITY_RNG=y
CONFIG_ENTROPY_GENERATOR=y

# Simple Payload support BEGINS
# Option 1: MBEDTLS
CONFIG_MBEDTLS_VANILLA_BACKEND=y
CONFIG_MBEDTLS_MAC_SHA256_ENABLED=y
CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_BUILTIN=y
CONFIG_MBEDTLS_CFG_FILE="config-tls-generic.h"

But I get the original errors around the mbedtls library:-

[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:499:5: error: incompatible types when initializing type 'enum <anonymous>' using type 'char *'
[build]   499 |     "SHA256",
[build]       |     ^~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:502:5: warning: excess elements in struct initializer
[build]   502 |     sha256_starts_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:502:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:503:5: warning: excess elements in struct initializer
[build]   503 |     sha224_update_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:503:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:504:5: warning: excess elements in struct initializer
[build]   504 |     sha224_finish_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:504:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:505:5: warning: excess elements in struct initializer
[build]   505 |     sha256_wrap,
[build]       |     ^~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:505:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:506:5: warning: excess elements in struct initializer
[build]   506 |     sha224_ctx_alloc,
[build]       |     ^~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:506:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:507:5: warning: excess elements in struct initializer
[build]   507 |     sha224_ctx_free,
[build]       |     ^~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:507:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:508:5: warning: excess elements in struct initializer
[build]   508 |     sha224_clone_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:508:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:509:5: warning: excess elements in struct initializer
[build]   509 |     sha224_process_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:509:5: note: (near initialization for 'mbedtls_sha256_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:569:5: warning: initialization of 'const char *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
[build]   569 |     MBEDTLS_MD_SHA384,
[build]       |     ^~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:569:5: note: (near initialization for 'mbedtls_sha384_info.name')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:570:5: error: incompatible types when initializing type 'enum <anonymous>' using type 'char *'
[build]   570 |     "SHA384",
[build]       |     ^~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:573:5: warning: excess elements in struct initializer
[build]   573 |     sha384_starts_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:573:5: note: (near initialization for 'mbedtls_sha384_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:574:5: warning: excess elements in struct initializer
[build]   574 |     sha384_update_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:574:5: note: (near initialization for 'mbedtls_sha384_info')
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md_wrap.c:575:5: warning: excess elements in struct initializer
[build]   575 |     sha384_finish_wrap,
[build]       |     ^~~~~~~~~~~~~~~~~~

And then later...


[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c: In function 'mbedtls_md':
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:300:20: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'digest_func'
[build]   300 |     return( md_info->digest_func( input, ilen, output ) );
[build]       |                    ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c: In function 'mbedtls_md_hmac_starts':
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:356:33: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'starts_func'
[build]   356 |         if( ( ret = ctx->md_info->starts_func( ctx->md_ctx ) ) != 0 )
[build]       |                                 ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:358:33: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'update_func'
[build]   358 |         if( ( ret = ctx->md_info->update_func( ctx->md_ctx, key, keylen ) ) != 0 )
[build]       |                                 ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:360:33: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'finish_func'
[build]   360 |         if( ( ret = ctx->md_info->finish_func( ctx->md_ctx, sum ) ) != 0 )
[build]       |                                 ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:379:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'starts_func'
[build]   379 |     if( ( ret = ctx->md_info->starts_func( ctx->md_ctx ) ) != 0 )
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:381:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'update_func'
[build]   381 |     if( ( ret = ctx->md_info->update_func( ctx->md_ctx, ipad,
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c: In function 'mbedtls_md_hmac_update':
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:396:25: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'update_func'
[build]   396 |     return( ctx->md_info->update_func( ctx->md_ctx, input, ilen ) );
[build]       |                         ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c: In function 'mbedtls_md_hmac_finish':
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:410:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'finish_func'
[build]   410 |     if( ( ret = ctx->md_info->finish_func( ctx->md_ctx, tmp ) ) != 0 )
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:412:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'starts_func'
[build]   412 |     if( ( ret = ctx->md_info->starts_func( ctx->md_ctx ) ) != 0 )
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:414:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'update_func'
[build]   414 |     if( ( ret = ctx->md_info->update_func( ctx->md_ctx, opad,
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:417:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'update_func'
[build]   417 |     if( ( ret = ctx->md_info->update_func( ctx->md_ctx, tmp,
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:420:25: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'finish_func'
[build]   420 |     return( ctx->md_info->finish_func( ctx->md_ctx, output ) );
[build]       |                         ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c: In function 'mbedtls_md_hmac_reset':
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:433:29: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'starts_func'
[build]   433 |     if( ( ret = ctx->md_info->starts_func( ctx->md_ctx ) ) != 0 )
[build]       |                             ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:435:25: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'update_func'
[build]   435 |     return( ctx->md_info->update_func( ctx->md_ctx, ipad,
[build]       |                         ^~
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c: In function 'mbedtls_md_process':
[build] D:/devtools/ncs/v1.4.2/modules/crypto/mbedtls/library/md.c:473:25: error: 'mbedtls_md_info_t' {aka 'const struct mbedtls_md_info_t'} has no member named 'process_func'
[build]   473 |     return( ctx->md_info->process_func( ctx->md_ctx, data ) );
[build]       |                         ^~

Any thoughts?

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

Einar Thorsrud — Mon, 08 Mar 2021 19:26:04 GMT

Hi,

I did not get a chance to look into this in detail today unfortunately, but looking briefly I would think you should have at least the following in your .conf file:

CONFIG_CC3XX_BACKEND=y
CONFIG_MBEDTLS_VANILLA_BACKEND=y
CONFIG_MBEDTLS_MAC_SHA256_ENABLED

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

adamfowleruk — Sat, 06 Mar 2021 14:20:07 GMT

Ah yes sorry, I did a fat fingered delete unfortunately. They're now back. I'll have a read of the sample and let you know the outcome. Thanks!

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

Einar Thorsrud — Sat, 06 Mar 2021 07:56:26 GMT

Hi,

It seems the github links are no longer valid. Perhaps you can update those, or even better include the files in your post? Most importantly prj.conf and any overlay files if used. I also suggest you look at the crypto test in NCS, which demonstrates most possible combinations, including combining CC3xx and mbed TLS vanilla (SW). You can find this code under <NCS>\nrf\tests\crypto\ and the documentation here (which is unfortunately slightly outdated).

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

adamfowleruk — Fri, 05 Mar 2021 20:31:33 GMT

Hi there. Thanks but this still didn't work for me. I've now stopped trying to use mbedtls for this and just use tinycrypt for my sha256 needs.

I would really like to know how to get this working though.

RE: App not compiling with both CC310 backend and mbedtls enabled in NCS

Einar Thorsrud — Mon, 01 Mar 2021 14:03:47 GMT

Hi,

If you want to use normal/vanilla mbedTLS (all in SW) then you can specify CONFIG_MBEDTLS_VANILLA_BACKEND=y.