[nRF Connect] Use hardware-accelerated crypto functions

[Damian-Nordic]

Problem

nRF Connect lock-app uses Zephyr's built-in mbedtls which doesn't include hardware-accelerated cryptographic functions.

Summary of Changes

Configure the example to use nrf_security library which provides implementation optimized for Nordic platforms.

fixes #2369

[github-actions]

Size increase report for "nrfconnect-example-build"

File	Section	File	VM
chip-nrf52840-lock-example.elf	text	102072	102072
chip-nrf52840-lock-example.elf	bss	0	14796
chip-nrf52840-lock-example.elf	rodata	2864	2864
chip-nrf52840-lock-example.elf	datas	68	68
chip-nrf52840-lock-example.elf	[LOAD #3 [RW]]	0	20
chip-nrf52840-lock-example.elf	[LOAD #2 [RW]]	-4	-4
chip-nrf52840-lock-example.elf	[LOAD #1 [RWX]]	-8	-8

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-nrf52840-lock-example.elf and ./pull_artifact/chip-nrf52840-lock-example.elf:

sections,vmsize,filesize
.debug_info,0,305709
text,102072,102072
.debug_line,0,48791
.debug_loc,0,47739
.symtab,0,26448
.strtab,0,15918
bss,14796,0
.debug_str,0,12383
.debug_abbrev,0,8853
.debug_frame,0,4784
.debug_ranges,0,3880
rodata,2864,2864
.debug_aranges,0,1648
datas,68,68
[LOAD #3 [RW]],20,0
[Unmapped],0,3
[LOAD #2 [RW]],-4,-4
[LOAD #1 [RWX]],-8,-8

[github-actions]

Size increase report for "esp32-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-wifi-echo.elf and ./pull_artifact/chip-wifi-echo.elf:

sections,vmsize,filesize

[github-actions]

Size increase report for "gn_nrf-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

[github-actions]

Size increase report for "gn_linux-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

[github-actions]

Size increase report for "gn_efr32-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-efr32-lock-example.out and ./pull_artifact/chip-efr32-lock-example.out:

sections,vmsize,filesize

[rwalker-apple]

is this image pushed yet?

[Damian-Nordic]

Yes and no :)
Initially I asked Andrei to rebuild nrf image with "--no-cache" flag so that fresh sources are picked up. Later we agreed that a cleaner approach would be using specific commit-ids in Dockerfile and not having to bypass the docker cache, so I updated the definition as you have seen. The 0.4.2 image which is on dockerhub right now is the one built with "--no-cache", so it's not the final version yet, but is good enough to build this PR.

[andy31415]

We will have to merge them ... I originally needed 0.4.2 to have a JDK in the android-build, so I built one and Damian noticed that the nRF build was odd. We probably want both the nRF build updates and JDK commits in before we create another 'real/final 0.4.3'.

That being said, I have no plans to push any other 0.4.2 until then so this should be safe.