Skip to content

update dts link example #107

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.

Sign up for GitHub

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

Merged
szczys merged 1 commit into from
Jul 17, 2026
Merged

update dts link example #107

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/zephyr-training/03_LED/build_blinky.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ Overview](devicetree-overview), DT definitions for our board already exist in th
By convention, all Zephyr supported boards that have LEDs should alias those
LEDs to `led0`, `led1`, `...`, `led<n>` in the Devicetree. Let's take the
nRF9160 DK as an example. If we look at [the DTS file for this
board](https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_common.dtsi)
board](https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/nordic/nrf9160dk/nrf9160dk_nrf9160_common.dtsi)
we can find the relevant node information for the LED:

```
Expand Down