How to erase flash area s0 and s1?

RE: How to erase flash area s0 and s1?

Sigurd Hellesvik — Tue, 27 Dec 2022 13:20:01 GMT

Hi Devin,

Due to to the holiday here, I will continue to handle this case.

First I want to ask a question to understand your issue:
Why do you need to erase a slot?

When updating MCUboot, you first upload to slot 1.
Then next update to slot 0.
Then next update to slot 1.
And so on.

I have a sample for this here: https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/updatable_bootloader/nsib_mcuboot_smp.
It is only for the nRF52840, or only the app core, but maybe it can help.

Regards,
Sigurd Hellesvik

RE: How to erase flash area s0 and s1?

yang.hu — Tue, 20 Dec 2022 01:04:10 GMT

I am using vs code, not command line. You can using nrfjprog -e to erase all flash erase but netcore.

As your log shown, bootloader can't find application image because of a wrong image header.

But my log is 'Jumping to the first image slot...'.

Did you flash all images in your device, include B0 + MCUboot + application?

RE: How to erase flash area s0 and s1?

Hakon — Mon, 19 Dec 2022 13:01:05 GMT

Yeah, I guess the bug can be reproduced without the custom key.

It's building now, and I'm getting this output;

Also, I needed to run west flash --force, because it wouldn't let me erase the UICR. Do you have the same problem?

RE: How to erase flash area s0 and s1?

yang.hu — Fri, 16 Dec 2022 02:08:31 GMT

Hi,

You can move this line. This is key file, the projrct will use default key when you are not assign the key.

RE: How to erase flash area s0 and s1?

Hakon — Thu, 15 Dec 2022 14:18:26 GMT

Still unable to build. There is a .pem file that I don't have access to;

CONFIG_SB_SIGNING_KEY_FILE="D://priv.pem"

RE: How to erase flash area s0 and s1?

yang.hu — Wed, 14 Dec 2022 01:02:33 GMT

Yes.

You can open it with VS code, and boards name is nrf5340dk_nrf5340_cpuapp.

Then connect to SEGGER RTT View, you can see the log.

RE: How to erase flash area s0 and s1?

Hakon — Tue, 13 Dec 2022 16:04:26 GMT

Is this for the nrf5340dk? How to build?

RE: How to erase flash area s0 and s1?

Hakon — Tue, 13 Dec 2022 13:14:44 GMT

Okay, I will have a look at this.

RE: How to erase flash area s0 and s1?

yang.hu — Tue, 06 Dec 2022 09:27:39 GMT

Hi,

In my .config file, i have enabled these configs yet.

You can build this project to repeat the problem.

devzone.nordicsemi.com/.../hello_5F00_world.7z

RE: How to erase flash area s0 and s1?

Hakon — Fri, 02 Dec 2022 13:43:22 GMT

Have you enabled these configs?

# FLASH
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

RE: How to erase flash area s0 and s1?

yang.hu — Thu, 01 Dec 2022 01:03:08 GMT

bus falut:

r14/r15: nrf_nvmc.h:line:306:*(volatile uint32_t *)page_addr = 0xFFFFFFFF;

RE: How to erase flash area s0 and s1?

Hakon — Wed, 30 Nov 2022 15:24:57 GMT

Can try reading the Faulting instruction address by using arm-none-eabi-addr2line as explained here.

RE: How to erase flash area s0 and s1?

yang.hu — Wed, 30 Nov 2022 09:15:17 GMT

Hi,

This is bus falut log(flash_area_erase()):

[16:39:21.121]收←◆*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x46...0c

[16:39:21.221]收←◆Firmware signature verified.
Firmware version 3
Setting monotonic counter (version: 3, slot: 0)
Booting (0x8200).
[16:39:21.681]收←◆*** Booting Zephyr OS build v3.1.99-ncs1-1  ***

[16:39:26.743]收←◆I: Starting bootloader
W: flash_area: 12, flash_map_entries:17
W: flash_area: 16, flash_map_entries:17
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
W: flash_area: 7, flash_map_entries:17
W: flash_area: 16, flash_map_entries:17
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none

[16:39:26.969]收←◆I: Bootloader chainload address offset: 0x28000
I: Jumping to the first image slot

[16:39:32.033]收←◆*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
[00:00:00.000,701] [0m<inf> main: Hello World! nrf5340dk_nrf5340_cpuapp.[0m

[16:39:37.035]收←◆[00:00:05.012,023] [1;33m<wrn> main: align: 0x4[0m
[00:00:05.012,084] [0m<inf> main: read:
                               3d b8 f3 96 00 00 00 00  00 02 00 00 30 a4 00 00 |=....... ....0...
                               00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |........ ........[0m
[00:00:05.012,084] [1;33m<wrn> main: len: 0xd000.[0m
[00:00:05.012,115] [1;33m<wrn> main: fa_size: 0xd000.[0m
[00:00:05.012,145] [1;31m<err> os: ***** BUS FAULT *****[0m
[00:00:05.012,176] [1;31m<err> os:   Precise data bus error[0m
[00:00:05.012,207] [1;31m<err> os:   BFAR Address: 0x18000[0m
[00:00:05.012,237] [1;31m<err> os: r0/a1:  0x00000001  r1/a2:  0x0000d000  r2/a3:  0x00000002[0m
[00:00:05.012,268] [1;31m<err> os: r3/a4:  0xffffffff r12/ip:  0x0000d000 r14/lr:  0x00033037[0m
[00:00:05.012,298] [1;31m<err> os:  xpsr:  0x01000000[0m
[00:00:05.012,298] [1;31m<err> os: Faulting instruction address (r15/pc): 0x0003303a[0m
[00:00:05.012,390] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0[0m
[00:00:05.012,451] [1;31m<err> os: Current thread: 0x20000260 (ota_mod_thread)[0m
[00:00:05.112,121] [1;31m<err> fatal_error: Resetting system

And this is img_mgmt_impl_erase_slot() log:

[16:46:15.623]收←◆*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x46...0c

[16:46:15.722]收←◆Firmware signature verified.
Firmware version 3
Setting monotonic counter (version: 3, slot: 0)
Booting (0x8200).
[16:46:16.197]收←◆*** Booting Zephyr OS build v3.1.99-ncs1-1  ***

[16:46:21.251]收←◆I: Starting bootloader
W: flash_area: 12, flash_map_entries:17
W: flash_area: 16, flash_map_entries:17
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
W: flash_area: 7, flash_map_entries:17
W: flash_area: 16, flash_map_entries:17
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none

[16:46:21.484]收←◆I: Bootloader chainload address offset: 0x28000
I: Jumping to the first image slot

[16:46:26.595]收←◆*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
[00:00:00.000,701] [0m<inf> mcuboot_util: Swap type: none[0m
[00:00:00.000,762] [0m<inf> mcuboot_util: Swap type: none[0m
[00:00:00.053,466] [0m<inf> main: img_mgmt_impl_erase_slot: 0.[0m
[00:00:00.053,558] [0m<inf> mcuboot_util: Swap type: none[0m
[00:00:00.053,558] [0m<inf> main: 0img_mgmt_slot_in_use: 1.[0m
[00:00:00.053,619] [0m<inf> mcuboot_util: Swap type: none[0m
[00:00:00.053,649] [0m<inf> main: 1img_mgmt_slot_in_use: 0.[0m
[00:00:00.053,680] [0m<inf> mcuboot_util: Swap type: none[0m
[00:00:00.053,771] [0m<inf> mcuboot_util: Swap type: none[0m
[00:00:00.053,802] [0m<inf> main: img_mgmt_state_confirm: 0.[0m
[00:00:00.053,802] [0m<inf> main: Hello World! nrf5340dk_nrf5340_cpuapp.[0m

Regards,

Yang Hu

RE: How to erase flash area s0 and s1?

Hakon — Tue, 29 Nov 2022 12:51:18 GMT

Hello,

can you please include the log output of the bus fault?