Issues in compiling BLE Secure bootloader by enable macro-ecc

RE: Issues in compiling BLE Secure bootloader by enable macro-ecc

beemavishnu — Thu, 05 Dec 2019 09:37:17 GMT

Hi,

On nRF52840, I am able to do DFU by enabling NRF_CRYPTO_BACKEND_CC310_BL_ENABLED and disabling NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED.

https://devzone.nordicsemi.com/support/240436

For nRF52832, once I started if any issues I will raise a separate query.

Thank you for your support.

Thanks & Regards

Vishnu Beema

RE: Issues in compiling BLE Secure bootloader by enable macro-ecc

Jørgen Holmefjord — Wed, 04 Dec 2019 15:54:15 GMT

[quote user="beemavishnu"]Even I enabled NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED and NRF_CRYPTO_BACKEND_CC310_BL_ENABLED is enabled already in Secure BLE bootloader.[/quote]

It is possible to have both backend enabled, in case you want to use one backend for one cryptographic algorithm and another backend for a second algorithm. Not all backends support all cryptographic operations.

[quote user="beemavishnu"]But its nRF tools, DFU menu, I am not able to upload. Its getting disconnected.[/quote]

At what point is it getting disconnected? Have you debugged the bootloader to see if any errors are reported, causing a reset in the chip?

[quote user="beemavishnu"]2) Even in ble_app_blinky do I need to enable NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED. Even after enabling and without including micro_ecc_lib_nrf52.a still I am able to compile ble_app_blinky application.[/quote]

This is not enabled by default in this example, and it compiles just fine for me. What changes have you made to the example/SDK? If you are not able to compile the ble_app_blinky example, please try with a fresh copy of the SDK.

RE: Issues in compiling BLE Secure bootloader by enable macro-ecc

beemavishnu — Tue, 03 Dec 2019 14:34:30 GMT

Hi Jorgen,

Any updates on this issue. Though I am able to do DFU by disabling NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED. Still I am trying to understanding the reason why its failing if I enable micro-ecc macro. This will help me in further for nRF52832 where micro-ecc to be used.

Thanks & Regards

Vishnu Beema

RE: Issues in compiling BLE Secure bootloader by enable macro-ecc

beemavishnu — Mon, 02 Dec 2019 17:25:09 GMT

Thank you for your inputs. I have further query.

Sorry, I edited entire query. Please respond as soon as possible as I am totally struck up.

I missed this point to mentioned above. Even I enabled NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED and NRF_CRYPTO_BACKEND_CC310_BL_ENABLED is enabled already in Secure BLE bootloader.

With above settings I am able to compile bootloader and see "DFUCT40" in nRF Tools app. But I am not able to do DFU with my example code.

1) I created package with below command. Is this fine.

nrfutil pkg generate --hw-version 52 --application-version 2 --application ble_app_blinky_pca10056_s140.hex --sd-req 0xCA --key-file nRF52840_CT40_private.key ble_app_blinky_dfu_package_V2.zip

But its nRF tools, DFU menu, I am not able to upload. Its getting disconnected.

2) Even in ble_app_blinky do I need to enable NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED. Even after enabling and without including micro_ecc_lib_nrf52.a still I am able to compile ble_app_blinky application. Am I doing any mistake ?

a) Do I need to include micro_ecc_lib_nrf52.a ?

b) How about public key. Do I need to include even public_key.c file into ble_app_blinky.

I have lot of confusions. Similar to bootloader, I am attaching my application (By removing private key). Please cross check once and suggest appropriate settings.

devzone.nordicsemi.com/.../ble_5F00_peripheral.zip

Thanks & Regards

Vishnu Beema

RE: Issues in compiling BLE Secure bootloader by enable macro-ecc

Jørgen Holmefjord — Mon, 02 Dec 2019 17:18:18 GMT

Hi.

Steps in 1-4 look correct.

In the image in 5, the golden tick means that this is the default configured backend, it does not mean that other backends are not supported. nRF52840 is the only nRF52 series IC that includes HW crypto acceleration through the CC310 Cryptocell. This is the recommended backend when available, while other ICs must rely on software cryptography.

Best regards,
Jørgen