-
Notifications
You must be signed in to change notification settings - Fork 73
4.0.0 metafiles naming conventions boardname #360
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
base: 4.0.0-pre-release
Are you sure you want to change the base?
4.0.0 metafiles naming conventions boardname #360
Conversation
20c9188
to
03bf5f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And the ci seems to be compile straight away? :)
docs/hw-platforms.rst
Outdated
@@ -47,13 +47,13 @@ The following XMC microcontroller boards are supported by XMC for Arduino: | |||
KIT_XMC11_BOOT_001 | |||
------------------ | |||
|
|||
* Name in Arduino IDE: ``XMC1100 Boot Kit`` | |||
* Legacy name: ``XMC1100 Boot Kit`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we keep the legacy name?
The idea of renaming is to have unify and simplify to one name.
If the user get´s lost, maybe a look up table with legacy name and new name would be convenient? But then keep it in a section decouple from the main doc, so that we have a clean single naming approach across code and docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by decouple? Separate pages of the name LUT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we would be already in 4.x for new users the legacy name is not relevant no?
Then I would maybe put in a different section.
But wait with any changes until we decide how to proceed with all these naming topics :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
@@ -1,5 +1,5 @@ | |||
/* | |||
* Simple DMA example for XMC4700 Relax Kit V1 | |||
* Simple DMA example for KIT_XMC47_RELAX_5V_AD_V1 V1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
V1 not required? already in the board name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are these xmc relax kit products:
KIT_XMC47_RELAX_V1 : https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc47_relax_v1/
KIT_XMC47_RELAX_LITE_V1 : https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc47_relax_lite_v1/
KIT_XMC47_RELAX_5V_AD_V1: https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc47_relax_5v_ad_v1/
If they are all supported by the same core variant... maybe that naming is too restrictive. And even the product website name is not the best but something like KIT_XMC47_RELAX?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
KIT_XMC47_RELAX is taken
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
taken? is there a product named like that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe my reply was too short, what I meant was that I think you have a valid point therefore change all KIT_XMC47_RELAX_5V_AD_V1 to KIT_XMC47_RELAX
The missing thing would be to rename the pinout diagram boards name as well. |
Yes, I also updated the arduino-devops. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR renames board identifiers and updates metafile naming to follow the new convention across code, tests, documentation, and configuration.
- Renamed all board macros (e.g.,
XMC1100_Boot_Kit
→KIT_XMC11_BOOT_001
) in tests and libraries - Updated documentation (
.rst
,README.md
, Markdown) to reference new board names and package indexes - Modified build metadata (
boards.txt
,platform.txt
,package_xmc_index.template.json
, YAML files) to reflect new identifiers and addedboard_variant_old
where needed
Reviewed Changes
Copilot reviewed 35 out of 45 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
tests/manual/tonetest/tonetest.ino | Updated #if defined checks to new board macros |
tests/manual/analogwritetest/analogwritetest.ino | Updated conditional macros for analogWrite across boards |
tests/manual/Servotest/Servotest.ino | Renamed boards in comments and updated PWM pin listings |
tests/manual/PWMtest/PWMtest.ino | Replaced boot‐kit macro in comments |
tests/manual/PCLKTest/PCLKTest.ino | Updated comments and defines for new boot‐kit macro |
tests/hil-unity-checklist.yaml | Lowercased and renamed test suite board keys |
tests/Makefile.test | Updated FQBN values to new board package names |
platform.txt | Added board_variant_old in compile recipes |
package/package_xmc_index.template.json | Lowercased package name and updated board list |
package/config.yml | Changed index-name to match new package index |
libraries/Wire/src/Wire.cpp | Updated #if defined for renamed boards |
libraries/SPI/src/SPI.h | Updated board macro in SD card slot comment |
libraries/RTC/examples/* | Replaced board names in example headers and #error lines |
libraries/OneWire/src/util/OneWireConf.h | Updated hardware‐mapping macros for renamed boards |
libraries/LED/Readme.md | Updated board table to use new names |
libraries/I2S/src/I2S.h/.cpp/README.md | Updated wiring docs and interrupt macros for new boards |
libraries/DeviceControlXMC/examples/* | Replaced board names in example headers |
libraries/DMA/examples/* | Replaced board names in example headers |
libraries/CAN/README.md | Updated hardware setup section with new board names |
extras/arduino-devops | Advanced submodule commit |
docs/*.rst & README.md | Updated links, image references, and board descriptions |
cores/xmc/*.c/.cpp/.h | Updated board macro checks and comments |
ci-matrix-config.yml | Updated FQBN entries to new board package IDs |
boards.txt | Completely replaced old board sections with new identifiers |
Comments suppressed due to low confidence (3)
tests/manual/tonetest/tonetest.ino:77
- The conditional still references
XMC1300_Sense2GoL
; to align with the new naming scheme, either rename that macro or introduce the correspondingKIT_
variant.
#elif defined( XMC1300_Sense2GoL )
tests/manual/analogwritetest/analogwritetest.ino:30
- Inconsistent macro naming:
XMC1300_Sense2GoL
remains in the same check. Consider updating it to aKIT_
version or removing if obsolete.
#if defined ( KIT_XMC11_BOOT_001 ) || defined ( KIT_XMC1400_ARDUINO ) || defined ( XMC1300_Sense2GoL )
package/package_xmc_index.template.json:19
- The
help.online
field is empty; please provide the correct documentation URL or remove the empty entry.
"online": ""
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot really help a lot here.
haha maybe I want to ask you about this as it may affect changing names and paths inside some of the HIL processes, but it will make all the names uniform and clear. Do you think merge this is ok? |
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
24cc450
to
1dfa71c
Compare
Signed-off-by: zhanglinjing <[email protected]>
@ederjc Can you provide the source file for the pinout diagram? |
@@ -34,8 +34,8 @@ The following XMC microcontroller boards are supported by XMC for Arduino: | |||
- :ref:`KIT_XMC_PLT2GO_XMC4400` | |||
- XMC4400 | |||
- Arduino Uno, Shield2Go, mikroBUS | |||
* - .. image:: img/KIT_XMC47_RELAX_5V_AD_V1.jpg | |||
- :ref:`KIT_XMC47_RELAX_5V_AD_V1` | |||
* - .. image:: img/KIT_XMC47_RELAX.jpg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we explicitly add in this table the available XMC4700 boards covered by KIT_XMC47_RELAX?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The workflows are still not running. Let´s fix that before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also we should update the pinout diagrams titles... 👯
This is related to the compilation test issue on the other board. |
If it is easily doable, fine. If not, you can also keep only the boards which PASS, and create tasks for enabling/fixing the other ones? |
Branch for fixing the compilation error: 4.0.0-metafiles-naming-conventions-boardname-fix-compile |
2f57160
to
91ca1fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 nice !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am through, please have a look at the 17 comments.
- Fix comments
- Add overview of the available XMC4700 boards as Juan also requested.
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Signed-off-by: zhanglinjing <[email protected]>
Please provide lists of boards name 😸 |
Signed-off-by: Eder Julian <[email protected]>
Signed-off-by: Eder Julian <[email protected]>
By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---
CONTRIBUTING.md also tells you what to expect in the PR process.
Description
update metafiles naming according the convention: https://confluencewikiprod.intra.infineon.com/spaces/ARDUINO/pages/1951456037/Metafiles+variables+naming+conventions
This PR also change all the name of boards.
Related Issue
https://jirard.intra.infineon.com/browse/DESMAKERS-4121
Context