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

OpenThread Example Improvement #10299

Merged
merged 13 commits into from
Sep 9, 2024
Merged

OpenThread Example Improvement #10299

merged 13 commits into from
Sep 9, 2024

Conversation

SuGlider
Copy link
Collaborator

@SuGlider SuGlider commented Sep 5, 2024

Description of Change

Adds a new example that mixes OpenThread native API with different Arduino OThreadCLI API calls.
New example is ExtendedRouterNode.ino.

Adds OpenThread Native API calls to the current Router and Leader Examples.

Fixes the Library keywords.txt file that didn't use TAB to separate fields.

Tests scenarios

Tested using two ESP32-C6 one for the Leader and the other for the Child/Router.
Used the modified examples.

Related links

Closes #10295
Related to #9486

Creates a new example that mixes different APIs
Update ExtendedRoterNode.ino with more use of API
Adds OpenThread Native calls to the example
Update LeaderNode.ino example to add OpenThread Native calls.
Update keywords.txt to use TAB instead of SPACE in order to recognize correctly the keywords.
@SuGlider SuGlider added the Type: Example Issue is related to specific example. label Sep 5, 2024
@SuGlider SuGlider added this to the 3.0.5 milestone Sep 5, 2024
@SuGlider SuGlider self-assigned this Sep 5, 2024
Copy link
Contributor

github-actions bot commented Sep 5, 2024

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "feat(openthread): create cj.json file":
    • summary looks too short
  • the commit message "feat(openthread): improve the example":
    • summary looks too short
  • the commit message "feat(openthread): improve the example":
    • summary looks too short

Please fix these commit messages - here are some basic tips:

  • follow Conventional Commits style
  • correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue
  • allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test
  • sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter
  • avoid Jira references in commit messages (unavailable/irrelevant for our customers)

TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

⚠️ Please consider squashing your 13 commits (simplifying branch history).

👋 Hello SuGlider, we appreciate your contribution to this project!


Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 52b3cb7

Copy link
Contributor

github-actions bot commented Sep 5, 2024

Test Results

 56 files   56 suites   4m 50s ⏱️
 21 tests  21 ✅ 0 💤 0 ❌
135 runs  135 ✅ 0 💤 0 ❌

Results for commit 52b3cb7.

♻️ This comment has been updated with latest results.

Changed ExtendedRoterNode to ExtendedRouterNode - Typo error.
Delete libraries/OpenThread/examples/SimpleThreadNetwork/ExtendedRoterNode directory
Copy link
Contributor

github-actions bot commented Sep 6, 2024

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

MemoryFLASH [bytes]FLASH [%]RAM [bytes]RAM [%]
TargetDECINCDECINCDECINCDECINC
ESP32C60⚠️ +8260.00⚠️ +0.09000.000.00
ESP32H20⚠️ +9340.00⚠️ +0.10000.000.00
Click to expand the detailed deltas report [usage change in BYTES]
TargetESP32C6ESP32H2
ExampleFLASHRAMFLASHRAM
OpenThread/examples/SimpleThreadNetwork/ExtendedRouterNode----
OpenThread/examples/SimpleThreadNetwork/LeaderNode⚠️ +8140⚠️ +9200
OpenThread/examples/SimpleThreadNetwork/RouterNode⚠️ +8260⚠️ +9340

Copy link
Member

@P-R-O-C-H-Y P-R-O-C-H-Y left a comment

Choose a reason for hiding this comment

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

Just a typo to fix :) esle LGTM

@SuGlider
Copy link
Collaborator Author

SuGlider commented Sep 6, 2024

Typos are automatically detected by CI. It may find other places and then I'll fix them all together.

@@ -31,10 +31,10 @@ peek KEYWORD2
flush KEYWORD2
otGetDeviceRole KEYWORD2
otGetStringDeviceRole KEYWORD2
otGetRespCmd KEYWORD2
otGetRespCmd KEYWORD2
Copy link
Member

Choose a reason for hiding this comment

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

I can't tell from the diff, but it's very important to remember that name and type need to be separated by TAB and not spaces. Is this here true?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes. It was separated by spaces and I have fixed it to use TABs.
I noticed it when I was writing the example and the keywords were not highlighted.

@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Sep 9, 2024
@SuGlider SuGlider mentioned this pull request Sep 9, 2024
18 tasks
@me-no-dev me-no-dev merged commit cbe0f2f into master Sep 9, 2024
43 checks passed
@me-no-dev me-no-dev deleted the new_openthread_example branch September 9, 2024 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged Type: Example Issue is related to specific example.
Projects
3 participants