Skip to content

Conversation

@aaillet
Copy link
Member

@aaillet aaillet commented May 13, 2025

While following the "install linux host dependencies" guide to install Zephyr and it's dependencies on a fresh Fedora 41 install, when I first tried flashing a firmware on a board, I realized that the part of the guide concerning the installation of the udev rule was missing.
I think that it could be a bit harsh for a new user to find out what's the problem.

As a regular Zephyr user, I'm not using the west sdk install command but it could also be a way to rework this doc to use it instead (if it include the udev rule installation commands) if the solution i proposed is not following the current documentation spirit.

Harmonize the sdk install part of the "install linux host dependencies" with the common sdk installation guide under develop/toolchains/zephyr_sdk.html.

  • Add udev rules installation guide
  • Relocate some notes

@aaillet aaillet requested review from fabiobaltieri and kartben May 13, 2025 14:44
@aaillet aaillet changed the title doc: Harmonize linux sdk install docs doc: Harmonize linux sdk install docs + add udev rules guide to other linux distro guide May 13, 2025
@github-actions github-actions bot requested review from carlescufi and nashif May 13, 2025 14:45
@sonarqubecloud
Copy link

fabiobaltieri
fabiobaltieri previously approved these changes May 14, 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.

Harmonize the sdk install part of the "install linux host dependencies" with the common sdk installation guide under develop/toolchains/zephyr_sdk.html.

"Harmonize" as-in "copy-paste" (not blaming you at all! you just followed what was already there) :| Not sure why I never realized we had duplicated content before.

The "Install the Zephyr Software Development Kit (SDK)" section should really just send the reader to https://docs.zephyrproject.org/latest/develop/toolchains/zephyr_sdk.html#zephyr-sdk-installation -- no ?

@aaillet
Copy link
Member Author

aaillet commented May 15, 2025

@kartben

Harmonize the sdk install part of the "install linux host dependencies" with the common sdk installation guide under develop/toolchains/zephyr_sdk.html.

"Harmonize" as-in "copy-paste" (not blaming you at all! you just followed what was already there) :| Not sure why I never realized we had duplicated content before.

Yep, exactly 😄
I figured that if we're going to have duplicate text in the documentation, it might as well be exactly the same, to simplify maintenance.

The "Install the Zephyr Software Development Kit (SDK)" section should really just send the reader to https://docs.zephyrproject.org/latest/develop/toolchains/zephyr_sdk.html#zephyr-sdk-installation -- no ?

It would indeed solve the lack of information and simplify maintenance, but do we want links between docs in this kind of guide? This could spoil the user experience.

I say this because, to simplify maintenance even further, we could also link to this page in the main “getting started” section when talking about SDK installation, but I don't think that's advisable.

@aaillet
Copy link
Member Author

aaillet commented May 20, 2025

So, from your POV @kartben, should I move sdk installation guide for all operating systems (Ubuntu,macOS,Windows,Fedora,Clear Linux,Arch Linux) to https://docs.zephyrproject.org/latest/develop/toolchains/zephyr_sdk.html#zephyr-sdk-installation and just put a link to it here https://docs.zephyrproject.org/latest/develop/getting_started/installation_linux.html#install-the-zephyr-software-development-kit-sdk ?

We may keep the current "base" sdk installation guide in the getting started guide or make it a link too later

Thanks for your answers

@github-actions
Copy link

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Jul 20, 2025
@aaillet
Copy link
Member Author

aaillet commented Jul 29, 2025

Hmm, forgot this, I'll check current status since 4.2 release and edit my changes 👍

@sonarqubecloud
Copy link

sonarqubecloud bot commented Aug 1, 2025

@aaillet
Copy link
Member Author

aaillet commented Aug 1, 2025

Just pushed a new version:

  • rename common linux sdk install guide from ubuntu to linux
  • linux setup sdk installation guide is now sending reader to common linux sdk install guide

Also updated SDK supported architectures list in doc

(rebased on top of master)

@aaillet aaillet requested a review from kartben August 1, 2025 13:18
@github-actions
Copy link

github-actions bot commented Oct 9, 2025

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Oct 9, 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.

Thanks for your patience 🫣

* ARM (32-bit and 64-bit; ARMv6, ARMv7, ARMv8; A/R/M Profiles)
* Microblaze (32-bit)
* MIPS (32-bit and 64-bit)
* Nios II
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* Nios II

Nios II support has been dropped

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, that was a thing I was not sure about, thanks 👍
Just fixed that

Copy link
Contributor

Choose a reason for hiding this comment

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

thank you! for the record nios toolchain will be gone in the next v1.0.0 version of the sdk so there shouldn't be any further confusion going forward
https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v1.0.0-beta1

Copy link
Member Author

Choose a reason for hiding this comment

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

Perfect 👌

@github-actions github-actions bot removed the Stale label Oct 23, 2025
@aaillet aaillet force-pushed the other-linux-udev-rules branch from 09d3b64 to 02826fa Compare October 23, 2025 12:23
@aaillet aaillet requested a review from kartben October 23, 2025 12:24
@kartben
Copy link
Contributor

kartben commented Oct 23, 2025

@aaillet please rebase on main for your CI issue

- rename ubuntu to linux for sdk install
- redirect duplication to linux sdk install guide

Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
Architecture list comes directly from SDK readme
This list is accurate since SDK 0.17.1

Signed-off-by: Aymeric Aillet <aymeric.aillet@iot.bzh>
@aaillet aaillet force-pushed the other-linux-udev-rules branch from 02826fa to 6908650 Compare October 23, 2025 12:59
@aaillet
Copy link
Member Author

aaillet commented Oct 23, 2025

@aaillet please rebase on main for your CI issue

just rebased, thanks

@sonarqubecloud
Copy link

@kartben kartben requested a review from fabiobaltieri October 23, 2025 16:54
@cfriedt cfriedt merged commit b4556ea into zephyrproject-rtos:main Oct 24, 2025
20 checks passed
@aaillet aaillet deleted the other-linux-udev-rules branch October 27, 2025 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants