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.

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

CONFIG_IS_BOOTLOADER is poorly named and documented #6180

Closed
SebastianBoe opened this issue Feb 13, 2018 · 2 comments
Closed

CONFIG_IS_BOOTLOADER is poorly named and documented #6180

SebastianBoe opened this issue Feb 13, 2018 · 2 comments
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug Good first issue Good for a first time contributor to take priority: low Low impact/importance bug

Comments

@SebastianBoe
Copy link
Collaborator

See mcu-tools/mcuboot#230 for details

@nashif nashif added bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug labels Feb 15, 2018
@galak galak added the Good first issue Good for a first time contributor to take label Dec 6, 2018
@nashif
Copy link
Member

nashif commented Jan 30, 2019

put MCUBOOT aside, you can build zephyr to act as a bootloader, so there is nothing confusing here

This option indicates that Zephyr will act as a bootloader to execute
a separate Zephyr image payload.

Not sure how this can be written in some other way, IMO it is clear enough.

@nashif nashif closed this as completed Jan 30, 2019
@SebastianBoe
Copy link
Collaborator Author

Perhaps:

This option will offset the ORIGIN of the MEMORY region SRAM by "CONFIG_BOOTLOADER_SRAM_SIZE" kB and reduce it's SIZE by the same amount.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug Good first issue Good for a first time contributor to take priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants