Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Flash area functions for listing active and specified type flash memory areas/partitions #33144

Closed
wants to merge 7 commits into from
Closed

Flash area functions for listing active and specified type flash memory areas/partitions #33144

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
491b501
dts: bindings: Add bindings for Zephyr partition types
de-nordic Mar 8, 2021
3d8054e
storage/flash_map: Add filed for area type field flash_area structure
de-nordic Mar 8, 2021
b7798a0
flash_area: Add flash area type support macros
de-nordic Mar 8, 2021
edceabb
boards: nrf: Example usage of flash area type compatibles
de-nordic Mar 8, 2021
02de549
storage/flash_map: Add macros for accessing flash area type
de-nordic Mar 9, 2021
38651ef
flash_area: Partition type functions
de-nordic Mar 8, 2021
87287ea
samples/storage: Usage of flash_area API with partition types
de-nordic Mar 9, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions dts/bindings/mtd/zephyr,application-image.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Copyright (c) 2021 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0

description: |
Partition or other storage area for application binary image.

compatible: "zephyr,application-image"

include: base.yaml

properties:
label:
required: true
reg:
required: true
15 changes: 15 additions & 0 deletions dts/bindings/mtd/zephyr,mcuboot-image.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Copyright (c) 2021 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0

description: |
Partition or other storage area for mcuboot bootloader image.

compatible: "zephyr,mcuboot-image"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason not to use generic identifiers, e.g. just bl-image/bl-scratch, for bootloader areas?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is zephyr/mcuboot specific. Probably other bootloader could be used, or be chained to/in front of the mcuboot, and that booloader would have different compatibility to recognize its partitions.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not explain why generic partition identifiers cannot be used. MCUboot is also only a Zephyr application.


include: base.yaml

properties:
label:
required: true
reg:
required: true
15 changes: 15 additions & 0 deletions dts/bindings/mtd/zephyr,mcuboot-scratch.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Copyright (c) 2021 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0

description: |
Partition or other storage area for mcuboot bootloader scratch.

compatible: "zephyr,mcuboot-scratch"

include: base.yaml

properties:
label:
required: true
reg:
required: true