secure bootloader in NCS v1.6.1

RE: secure bootloader in NCS v1.6.1

Sunil vignesh — Sat, 04 Sep 2021 15:21:35 GMT

I have solved the reamining work .

Just added b0.confg to child image folder

# Clock configuration
CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=y

RE: secure bootloader in NCS v1.6.1

Amanda Hsieh — Wed, 01 Sep 2021 13:49:25 GMT

Please create a new support case for the new issue. I will be out of the office next few days. Sorry for the inconvenience.

-Amanda

RE: secure bootloader in NCS v1.6.1

Sunil vignesh — Wed, 01 Sep 2021 13:46:29 GMT

Yes, I found the error is coming for the custom board config and in that i have no 32.768khz crystal. How to run the boot in HSRC

RE: secure bootloader in NCS v1.6.1

Sunil vignesh — Wed, 01 Sep 2021 13:27:12 GMT

I found that child_image folder is not there does i need to work the board with only 32MHZ.

RE: secure bootloader in NCS v1.6.1

Amanda Hsieh — Wed, 01 Sep 2021 12:42:31 GMT

Hi,

I am working on your case, but cannot reproduce the issue.

It should generate s1_image.hex in the early stage. Try to delete the build folder and create again.

Here is for your reference. devzone.nordicsemi.com/.../peripheral_5F00_uart_5F00_v1.6.1_5F002300_275731.zip

-Amanda

RE: secure bootloader in NCS v1.6.1

Sunil vignesh — Wed, 01 Sep 2021 11:46:44 GMT

Hi Amanda, Have you check it.

Is there any holidays or still lock down going there.

Why there is an delay in response and assigning engineer for new ticket getting late

RE: secure bootloader in NCS v1.6.1

Sunil vignesh — Tue, 31 Aug 2021 17:47:00 GMT

when i add only the lines above you mentioned in prj.conf

i received

[Errno 2] No such file or directory: 'D:/nRF5xx/nRF_Connect_SDK_v1.6/WORKSPACE/GlosdexHeadset_v1.3.99/build_fanstel_bt840/zephyr/s1_image.hex'

RE: secure bootloader in NCS v1.6.1

Sunil vignesh — Tue, 31 Aug 2021 13:36:37 GMT

does anything i need to change in cMakelist.txt

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
#
cmake_minimum_required(VERSION 3.13.1)
list(APPEND mcuboot_OVERLAY_CONFIG
  "${CMAKE_CURRENT_SOURCE_DIR}/child_image/mcuboot.conf"
  )
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(NONE)
# bt_services/*.c MLX90393/*.c NFC/*.c
FILE(GLOB app_sources src/*.c ../driverSource/bt_services/*.c ../driverSource/MLX90393/*.c ../driverSource/NFC/*.c)
# NORDIC SDK APP START
target_sources(app PRIVATE ${app_sources})
# NORDIC SDK APP END

zephyr_library_include_directories(.)

RE: secure bootloader in NCS v1.6.1

Amanda Hsieh — Tue, 31 Aug 2021 13:24:17 GMT

Hi Sunil,

See this tutorial. You need the following configuration:

CONFIG_SECURE_BOOT=y
CONFIG_BUILD_S1_VARIANT=y
CONFIG_FW_INFO=y
CONFIG_FW_INFO_FIRMWARE_VERSION=1
CONFIG_SB_SIGNING_KEY_FILE="priv.pem"

You could do serial dfu within the bootloader itself. Otherwise, it has to be "dual banked"

Regards,
Amanda