FOTA - BLE: Custom Keys issue on compilation

RE: FOTA - BLE: Custom Keys issue on compilation

Gokulnath — Wed, 14 May 2025 10:14:25 GMT

Hello,

No success ..

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/535247"]Try to escape all the "\"s:[/quote]

Done this.

But a new development:

I've did it like this....

But I still see in logs that the default key is getting used.

Another Development 2:

I did it like this ...

Tested this & it works correctly.

RE: FOTA - BLE: Custom Keys issue on compilation

Sigurd Hellesvik — Wed, 14 May 2025 06:54:59 GMT

Try to escape all the "\"s:

"C:\\Nordic\\Software\\BLE\\FOTA-Keys\\FOTA-Private-Key-ECDSA-P256.pem"

RE: FOTA - BLE: Custom Keys issue on compilation

Gokulnath — Tue, 13 May 2025 14:24:42 GMT

Hello

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/535160"]In this case, can you try to set the MCUboot key instead: SB_CONFIG_BOOT_SIGNATURE_KEY_FILE.[/quote]

yes this fails as well. tried it on both my personal project & the 52DK LBS project as well.

logs:
devzone.nordicsemi.com/.../2043.logs-lbs-sample-52DK-custom-key.txt

RE: FOTA - BLE: Custom Keys issue on compilation

Sigurd Hellesvik — Tue, 13 May 2025 14:07:05 GMT

Ah I thought this was the key for MCUboot, and not for NSIB.

I see now that it is for NSIb.

In this case, can you try to set the MCUboot key instead: SB_CONFIG_BOOT_SIGNATURE_KEY_FILE.

Does this fail as well?
This is a good test to see if it is a CMake can not find the file, or if the issue is specific to the NSIB option.

RE: FOTA - BLE: Custom Keys issue on compilation

Gokulnath — Tue, 13 May 2025 13:09:11 GMT

hello,
yes i'm using Full path only in sysbuild.conf

like this

SB_CONFIG_SECURE_BOOT_APPCORE=y
SB_CONFIG_SECURE_BOOT_SIGNING_KEY_FILE="C:\Nordic\Software\BLE\FOTA-Keys\FOTA-Private-Key-ECDSA-P256.pem"

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/535136"] so try to use a smaller key name.[/quote]

Tried this as well but no effect!

Also added this under cmakelist.txt (example on my original project.)

RE: FOTA - BLE: Custom Keys issue on compilation

Sigurd Hellesvik — Tue, 13 May 2025 13:00:16 GMT

The error in your logs say "Config points to non-existing PEM file
'C:NordicSoftwareBLEFOTA-KeysFOTA-Private-Key-ECDSA-P256.pem'"

Looks like the file is not found. Try to use the full path to the file instead.

Also, Windows is known to have some issues with path lengths, so try to use a smaller key name.

Can you show me the exact line where you configure the key?

RE: FOTA - BLE: Custom Keys issue on compilation

Gokulnath — Tue, 13 May 2025 09:58:10 GMT

Hello,

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/534449"]Does it work if you use imgtool instead?[/quote]

Unfortunately for me, no..imgtool didn't work, some errors.

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/534449"]It is a good idea to try a working sample:
Do you get the same error with the solution?[/quote]

My sample is based on the LBS sample under NCS 2.6.2. Just to be sure, I did this: (for the moment, let's forget my custom project)

My new try is as follows:
1) Under the new folder, I copied the sample LBS sample ncsv3.0.1
2) Just added FOTA support based on DEVacademy tutorial & compiled it, it works on 52dk (As default key)
3) An error occurs when I just added my custom FOTA key. Unable to build.

logs:
devzone.nordicsemi.com/.../logs-lbs-sample-52DK-custom-key.txt

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/534449"]This is with your project, right? Or do you use a sample?[/quote]

Yes, this is with my specific sample only. Let's say, for the bigger fish to fry for the moment, we shall solve the custom key issue, I guess. Then, if needed, I shall create another ticket specific to this.

[quote userid="106736" url="~/f/nordic-q-a/121262/fota---ble-custom-keys-issue-on-compilation/534449"]What install method have you used for the nRF connect SDK?[/quote]

directly installed from VS Code (manage SDK option, pre-packaged file)

RE: FOTA - BLE: Custom Keys issue on compilation

Sigurd Hellesvik — Thu, 08 May 2025 11:31:59 GMT

Hi,

[quote user=""]I followed this link, OPENSS,L to generate the custom key as mentioned [/quote]

It is a good idea to also try the alternatives:
Does it work if you use imgtool instead?

It is a good idea to try a working sample:
Do you get the same error with the solution?

[quote user=""]1) secure_boot = n (warning on terminal) -( MCUBoot bootloader key file: C:/ncs/v3.0.1/bootloader/mcuboot/root-rsa-2048.pem
CMake Warning at CMakeLists.txt:393 (message):
WARNING: Using default MCUboot signing key file, this file is for debug use
only and is not secure!)[/quote]

How do you add the configuration for the custom key?

[quote user=""]

2) warning: Deprecated symbol DEPRECATED_UART_NRFX_UARTE_LEGACY_SHIM is enabled. (How to solve this?)

3) warning: Deprecated symbol BT_CTLR is enabled (how to solve this?)

[/quote]

This is with your project, right? Or do you use a sample?

[quote user=""]4) When I run west update (technically I'm not using the wested workspace though) on ncsv3.0.1, I'm getting issues on old SDK v2.6.2, not found error on the terminal. (see screenshot attached.)[/quote]

What install method have you used for the nRF connect SDK?

Regards,
Sigurd Hellesvik