Firmware over the air - Produce hash calculation

RE: Firmware over the air - Produce hash calculation

Hung Bui — Tue, 01 Oct 2024 13:23:01 GMT

Hi HKhan,
I can build (and run) the sha256 with no problem.

But from what I can see the Oberon driver is used in the sample. Is there any reason you don't want to enable Oberon ?

RE: Firmware over the air - Produce hash calculation

Hkhan7861 — Tue, 01 Oct 2024 11:27:11 GMT

It is essentially not a building issue as the program runs.

RE: Firmware over the air - Produce hash calculation

Hkhan7861 — Tue, 01 Oct 2024 11:23:39 GMT

Hi Hung

Unfortunately we have custom board which uses the nrf9160. Have you tried building the sha256 sample? In my configuration i have this :

CONFIG_MBEDTLS_PSA_CRYPTO_C=y

CONFIG_MBEDTLS_ENABLE_HEAP=y

CONFIG_MBEDTLS_HEAP_SIZE=8192

CONFIG_PSA_CRYPTO_DRIVER_OBERON=n

CONFIG_PSA_CRYPTO_DRIVER_CC3XX=y

But im still getting the above error. Do you any idea why this could be happening. We are building this into the lwm2m sample.

RE: Firmware over the air - Produce hash calculation

Hung Bui — Tue, 01 Oct 2024 10:56:31 GMT

Hi HKhan,

Building an application on _ns non-secure board is the correct way of getting security, especially for PSA.

Please take a look here: An Introduction to Trusted Firmware-M (TF-M)

I did a quick test here with a cryto sample (rsa ) and I don't see a problem when building for nRF9160dk_nrf9160ns board.

RE: Firmware over the air - Produce hash calculation

Hkhan7861 — Tue, 01 Oct 2024 08:13:01 GMT

Hi Hung

I'm having trouble running crypto samples on our custom board that uses the nrf9160 chip. The error i get when trying to use 'psa_crypto_init' is " Could not setup the hash operation! Error -134" I'm assuming its because its not on the list of boards and because it is a non-secure version of the board. Is there a way i can bypass this?

Thank you in advance!

RE: Firmware over the air - Produce hash calculation

Hung Bui — Mon, 30 Sep 2024 09:12:30 GMT

Hi Hkhan,
I assume you are using the dfu libraries in nRF Connect SDK and the function you mentioned is dfu_target_write , not dfu_write ?

I am not so familiar with the dfu library but maybe you can refer to function get_has_from_flash() to get the hash value. You can see how it's used to compare the actual calculated hash and the received hash on the manifest.
https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/dfu/fmfu_fdev/src/fmfu_fdev.c#L237