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

init_levels build target should be documented #63867

Closed
kartben opened this issue Oct 12, 2023 · 0 comments · Fixed by #64485
Closed

init_levels build target should be documented #63867

kartben opened this issue Oct 12, 2023 · 0 comments · Fixed by #64485
Assignees
Labels
area: Build System area: Documentation Enhancement Changes/Updates/Additions to existing features

Comments

@kartben
Copy link
Collaborator

kartben commented Oct 12, 2023

Is your enhancement proposal related to a problem? Please describe.

The newly introduced initlevels build target (#62459) is a pretty cool tool, but it's not documented (although to be 100% complete it is mentioned in the 3.5 release notes) and people could easily miss it.

Describe the solution you'd like

Add documentation about the target and how it can be used somewhere in docs. Maybe https://docs.zephyrproject.org/latest/develop/west/build-flash-debug.html, but would probably be nice to also mention it as a useful troubleshooting tool in e..g https://docs.zephyrproject.org/latest/kernel/drivers/index.html#initialization-levels

Describe alternatives you've considered

N/A

Additional context

N/A

@kartben kartben added Enhancement Changes/Updates/Additions to existing features area: Build System area: Documentation labels Oct 12, 2023
@kartben kartben changed the title west init_levels command should be documented init_levels build target should be documented Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Build System area: Documentation Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants