-
Notifications
You must be signed in to change notification settings - Fork 662
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.
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
boot: bootutil: Add boot information #1692
Conversation
dddf0f5
to
8caa6c1
Compare
@utzig @de-nordic @nvlsianpu @d3zd3z can you review this PR please? |
boot/bootutil/src/loader.c
Outdated
BOOT_IMG_AREA(state, active_slot), | ||
active_slot); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure whether this is correct. I mean sharing active_slot
may be correct because this is MCUboot/MCUmgr established slot numbering, but the BOOT_IMG_AREA(state, active_slot) pointer (struct flash_area
) may differ between MCUboot and app builds, so sharing it does not help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
active_slot
is what I added for XIP, the boot image area is part of the original API which presumably things like mynewt use so don't want to change/break it.
7180d75
to
05192ef
Compare
@nordicjm, I am surprized that you have not taken any action to remove this PR. The solution provided is not beneficial for mcuboot. The introduction of a zephyr dependent config |
My suggestions would be to perhaps split this into two PRs, as we are kind of doing two different things here. One is using the retention system in Zephyr as a mechanism to share data. The other is a new type of boot record. I think both of these are fine, but the new type of boot record should probably just be in the main boot code, and not Zephyr specific, and just the use of retention would be in the Zephyr code. These could be selected by configs. |
f549d1a
to
a235aab
Compare
This allows the currently executing slot number to be checked by the external function, which can be used by XIP images to know which slot is currently being executed from to allow for correct uploading/positioning of firmware files, and also provides the maximum size of an upgrade that can be loaded so that applications can reject images that are too large. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds TLV defines for use with the bootloader shared data feature. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
a235aab
to
781dd08
Compare
781dd08
to
25a316c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small issue with a weird include that I think is redundant anyway.
25a316c
to
94d1116
Compare
94d1116
to
edecf3e
Compare
IMO this PR does not follow the intended use of mcuboot shared data:
If the |
Adds the ability to share MCUboot configuration with applications via shared memory. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds a note that there is now additional information that can (optionally) be provided via shared boot information. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Adds additional information on the new BOOTINFO data sharing functionality Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
edecf3e
to
0d72961
Compare
Adds TLV defines and optional function for use with the bootloader shared data feature.