-
Notifications
You must be signed in to change notification settings - Fork 21
Fix board file styling and fixed partition compatible #144
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
Conversation
Adds line gaps where they should be Signed-off-by: Jamie McCrae <[email protected]>
RAM is not a fixed partition Signed-off-by: Jamie McCrae <[email protected]>
Fixes wrongly using Kconfigs Signed-off-by: Jamie McCrae <[email protected]>
Adds offsets when MCUboot is enabled Signed-off-by: Jamie McCrae <[email protected]>
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.
Is using fixed-partition
wrong for RAM when we separate the memory in partitions, e.g. for SoftDevice? I would like to understand the reason for the change.
yes, fixed-partition is for flash devices and goes into the flash map, it is wrong to use this binding with RAM. From the devicetree binding:
|
Enables GPREGRET1 and assigns it as a retention device for use with boot mode selection Signed-off-by: Jamie McCrae <[email protected]>
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.
Generally we would like to use the devicetree as little as possible. Though, I guess there is no good way to do this without?
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.
correct, this is used by MCUboot
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 saw you fixed the start address of the gpregret registers in zephyr upstream. Do we need some patch until this has trickled down? Or do we expect it to be available downstream soon?
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.
@lemrey please review |
No description provided.