Skip to content

Remove obsolete nrf54l09pdk board #93560

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

nordic-segl
Copy link
Contributor

Board nrf54l09pdk was renamed to nrf54lv10dk.
Remove nrf54l09pdk from supported boards in samples and tests.
Remove obsolete board definition.

@nordic-segl
Copy link
Contributor Author

FYI: @carlescufi , @nordic-piks

nordicjm
nordicjm previously approved these changes Jul 23, 2025
carlescufi
carlescufi previously approved these changes Jul 23, 2025
kl-cruz
kl-cruz previously approved these changes Jul 23, 2025
Copy link
Contributor

@kartben kartben left a comment

Choose a reason for hiding this comment

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

You can't just drop a board and not mention it in the release notes / migration guide.
You may also want to update doc/_scripts/redirects.py in case you want to redirect people browsing the Zephyr 4.1 / 4.2 docs to properly be re-routed to whatever is the replacement

@nordic-segl
Copy link
Contributor Author

You can't just drop a board and not mention it in the release notes / migration guide. You may also want to update doc/_scripts/redirects.py in case you want to redirect people browsing the Zephyr 4.1 / 4.2 docs to properly be re-routed to whatever is the replacement

nrf54l09pdk and nrf54l20pdk were targets for "emulator" (not a real HW). I'm 100% sure that nobody outside the Nordic have ever used that targets.
nrf54l09pdk is superseded by nrf54lv10dk. LV10DK will be moved to upstream soon.

I need to discuss how to proceed.
(I think, we would like to delete any occurrence of nrf54L09. "Replacement" is not yet in the upstream.)

@nordic-segl nordic-segl dismissed stale reviews from kl-cruz, carlescufi, and nordicjm via 92562d8 July 23, 2025 12:53
@nordic-segl nordic-segl force-pushed the Remove-obsolete-nrf54l09pdk-board branch from 5effab7 to 92562d8 Compare July 23, 2025 12:53
@nordic-segl
Copy link
Contributor Author

I mentioned removal of the board in Release Notes for the Zephyr 4.3.

@nordic-segl nordic-segl requested a review from kartben July 23, 2025 13:23
@carlescufi carlescufi requested a review from kl-cruz July 24, 2025 10:15
@carlescufi carlescufi requested a review from nordicjm July 24, 2025 10:15
carlescufi
carlescufi previously approved these changes Jul 24, 2025
nordicjm
nordicjm previously approved these changes Jul 24, 2025
@nordic-segl nordic-segl dismissed stale reviews from nordicjm and carlescufi via dd6aa1f July 24, 2025 11:13
@nordic-segl nordic-segl force-pushed the Remove-obsolete-nrf54l09pdk-board branch from 92562d8 to dd6aa1f Compare July 24, 2025 11:13
@nordic-segl nordic-segl requested a review from anangl July 24, 2025 11:15
Remove possibility to run samples on nrf54l09pdk as this is
an obsolete board that is going to be removed.

Signed-off-by: Sebastian Głąb <[email protected]>
Remove possibility to run tests on nrf54l09pdk as this is
an obsolete board that is going to be removed.

Signed-off-by: Sebastian Głąb <[email protected]>
Board nrf54l09pdk was renamed to nrf54lv10dk.
Remove obsolete board definition.

Signed-off-by: Sebastian Głąb <[email protected]>
@nordic-segl nordic-segl force-pushed the Remove-obsolete-nrf54l09pdk-board branch from dd6aa1f to cc02649 Compare July 25, 2025 06:28
Copy link

@nordic-segl
Copy link
Contributor Author

I had to resolve merge conflict.

@kartben kartben assigned anangl and unassigned kartben Jul 29, 2025
@kartben kartben dismissed their stale review July 29, 2025 09:00

Addressed

@fabiobaltieri fabiobaltieri merged commit ee89450 into zephyrproject-rtos:main Aug 5, 2025
27 checks passed
@nordic-segl nordic-segl deleted the Remove-obsolete-nrf54l09pdk-board branch August 6, 2025 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants