Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Changed 'built-in' LED used with Zephir boards from RED to GREEN#265

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
bogdanarduino wants to merge2 commits intoarduino:main
base:main
Choose a base branch
Loading
frombogdanarduino:built_in_LED_change_to_green

Conversation

@bogdanarduino
Copy link
Collaborator

In ArduinoCore-zephyr\cores\arduino\Arduino.h, the built-in LED index was changed from 0 (RED) to 1 (GREEN).

Copy link

@pillo79pillo79 left a comment

Choose a reason for hiding this comment

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

This PR is changing a global default, which must be available even on boards that only have 1 LED defined.
Please fix this by settingLED_BUILTIN to the appropriate number or macro in each variant (variants/xxx/pins_arduino.h).

sebromero reacted with thumbs up emoji
@sebromero
Copy link

@pillo79@bogdanarduino Maybe instead of changing it in the variant file, it might be cleaner to change it in the device tree overlay? I supposebuiltin-led-gpios can have duplicate entries. So, the first index could always refer to the BUILTIN_LED, while the other entries are for RGB etc. e.g. for Giga it could be:

builtin-led-gpios = <&gpioj 13 GPIO_ACTIVE_LOW> // Green                    <&gpioi 12 GPIO_ACTIVE_LOW>, // Red                    <&gpioj 13 GPIO_ACTIVE_LOW>, // Green                    <&gpioe 3 GPIO_ACTIVE_LOW>; // Blue

Wdyt?

@facchinm
Copy link
Member

Compeltely agree with@sebromero , the right way to tackle this is via device tree

…ed the fix as overlay config instead, for R1, C33 and H7.
@bogdanarduino
Copy link
CollaboratorAuthor

Thank you all for your feedback! Please recheck the updated fix when you have time.

@pennam
Copy link

Hi@bogdanarduino could you please reword the commits and the PR title to make CI happy ? The pattern is

<scope>: <description>

Copy link

@pennampennam left a comment

Choose a reason for hiding this comment

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

not a dts expert here, but I'm wondering if there is any specific reason to add a new

/ {zephyr,user {

instead of changing what we already have some lines above

builtin-led-gpios = <&ioport1 7 GPIO_ACTIVE_LOW>,                            <&ioport4 0 GPIO_ACTIVE_LOW>,                            <&ioport8 0 GPIO_ACTIVE_LOW>;

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@pennampennampennam left review comments

@sebromerosebromeroAwaiting requested review from sebromero

@pillo79pillo79Awaiting requested review from pillo79

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@bogdanarduino@sebromero@facchinm@pennam@pillo79

[8]ページ先頭

©2009-2025 Movatter.jp