Skip to content

boards: shields: add mchp_rnbd451_bt#98043

Open
JamesLiu-Microchip wants to merge 4 commits intozephyrproject-rtos:mainfrom
Zephyr4Microchip:shield_rnbd451_bt_upstream
Open

boards: shields: add mchp_rnbd451_bt#98043
JamesLiu-Microchip wants to merge 4 commits intozephyrproject-rtos:mainfrom
Zephyr4Microchip:shield_rnbd451_bt_upstream

Conversation

@JamesLiu-Microchip
Copy link

Add board support for the Microchip RNBD451 shield. This shield is compatible with a development board that includes a mikroBUS socket. This shield is intended to enable Bluetooth Low Energy functionality.

@github-actions
Copy link

Hello @JamesLiu-Microchip, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

@NhMchp
Copy link
Contributor

NhMchp commented Oct 22, 2025

@JamesLiu-Microchip , fix compliance issues

@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch from e09cf21 to 05b00d6 Compare November 5, 2025 07:54
@nandojve nandojve added this to the v4.4.0 milestone Nov 9, 2025
@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch from 05b00d6 to 0291576 Compare November 10, 2025 06:56
Comment on lines 117 to 149
Navigate to the project root directory. For example, if the Zephyr workspace was setup
following the Application Development section in the Zephyr Project Documentation,
use the following command.

``cd zephyrproject``

Append the above mentioned ``prj.conf`` configurations to each ``prj.conf`` in Example #1~#5.
Build the applications located in ``zephyr/samples/bluetooth`` using the following commands:

+----+---------------------+------------------------------------------------------------------------------------------------------------+
| No | Example name | Build command |
+====+=====================+============================================================================================================+
| 1 | Peripheral | west build -p always -b sam_e54_xpro --shield mchp_rnbd451_bt zephyr/samples/bluetooth/peripheral |
+----+---------------------+------------------------------------------------------------------------------------------------------------+
| 2 | HID Peripheral | west build -p always -b sam_e54_xpro --shield mchp_rnbd451_bt zephyr/samples/bluetooth/peripheral_hids |
+----+---------------------+------------------------------------------------------------------------------------------------------------+
| 3 | Peripheral Identity | west build -p always -b sam_e54_xpro --shield mchp_rnbd451_bt zephyr/samples/bluetooth/peripheral_identity |
+----+---------------------+------------------------------------------------------------------------------------------------------------+
| 4 | Central Multilink | west build -p always -b sam_e54_xpro --shield mchp_rnbd451_bt zephyr/samples/bluetooth/central_multilink |
+----+---------------------+------------------------------------------------------------------------------------------------------------+
| 5 | Central/Gatt Write | west build -p always -b sam_e54_xpro --shield mchp_rnbd451_bt zephyr/samples/bluetooth/central_gatt_write |
+----+---------------------+------------------------------------------------------------------------------------------------------------+


For more information on building the applications, refer to the `Building
<https://docs.zephyrproject.org/latest/develop/west/build-flash-debug.html#building-west-build>`_
section.

Flash the Applications
**********************
To flash the built application, use the following command:

``west flash``
Copy link
Contributor

Choose a reason for hiding this comment

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

Just give one example of building one sample application, for a given board. No need for more

See for example https://docs.zephyrproject.org/latest/boards/shields/adafruit_aht20/doc/index.html#programming

Copy link
Author

Choose a reason for hiding this comment

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

Hi @kartben , Document was revised according to your review. could you please help to confirm again? Thank you.

Copy link
Member

@nandojve nandojve left a comment

Choose a reason for hiding this comment

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

Hi @JamesLiu-Microchip ,

Thank you for the newer changes.

I found a few minor things, overall, LGTM!

Make sure you rebase before push.

@kartben ,

Is it possible to create vendor folder in shields ?
I see that it is starting to get a little messy for some vendors and I would like to avoid it.

@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch from a342382 to 343ebf7 Compare December 16, 2025 02:31
@nandojve
Copy link
Member

needs rebase

@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch from 343ebf7 to 481fb8c Compare December 19, 2025 02:00
@nandojve
Copy link
Member

Hi @JamesLiu-Microchip ,
Needs rebase : )

@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch from 19fb0e2 to fa9f6a4 Compare January 19, 2026 06:27
Copy link
Member

@nandojve nandojve left a comment

Choose a reason for hiding this comment

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

LGTM!

The PR need rebase to solve new conflicts.

@kartben , could you take another look?

@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch from fa9f6a4 to 746bb8d Compare January 26, 2026 01:40
@JamesLiu-Microchip JamesLiu-Microchip force-pushed the shield_rnbd451_bt_upstream branch 2 times, most recently from 705f67f to ddb1d85 Compare February 5, 2026 08:29
nandojve
nandojve previously approved these changes Feb 8, 2026
@nandojve
Copy link
Member

ping @kartben

};
};

sercom5_uart_default: sercom5_uart_default {
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
sercom5_uart_default: sercom5_uart_default {
sercom5_uart_default: sercom5-uart-default {
Copy link
Author

Choose a reason for hiding this comment

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

There are other pin control definitions in this file; I prefer to reserve underscores to keep the style consistent.

Copy link
Contributor

@JarmouniA JarmouniA Feb 25, 2026

Choose a reason for hiding this comment

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

Copy link
Author

Choose a reason for hiding this comment

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

Has committed the change. However, I only revised the node I added and preserved the original underscore style use by others.

Copy link
Author

@JamesLiu-Microchip JamesLiu-Microchip Feb 26, 2026

Choose a reason for hiding this comment

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

This change makes twister-build fail because the "sercom1_uart_default" node is already defined in two overlay files in the tests/drivers/uart folder. The device tree compiler treats both as the same label and reports a duplicate definition. Do you have any suggestions?

Changing the definition in the tests/drivers/uart folder is not a good idea because it would alter definitions by other people and is not related to the original feature that was added.

Copy link
Contributor

@JarmouniA JarmouniA Feb 26, 2026

Choose a reason for hiding this comment

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

It's just 2 instances. Fixing test issues is part of any PR.
https://github.com/search?q=repo%3Azephyrproject-rtos%2Fzephyr%20path%3A%2F%5Etests%5C%2F%2F%20sercom1_uart_default&type=code
If the nodes in the tests represent the same one in the board, just use the node phandle (&sercom1_uart_default {) in the test instead of redefining the node. If it's another node, give the test or board node a different node name.

Comment on lines 18 to 19

**Figure 1: RNBD451 Add-on Board**
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
**Figure 1: RNBD451 Add-on Board**
Copy link
Author

@JamesLiu-Microchip JamesLiu-Microchip Feb 25, 2026

Choose a reason for hiding this comment

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

Has committed the change.

Comment on lines 35 to 36

**Figure 2: ATMBUSADAPTER-XPRO - mikroBUS Adapter**
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
**Figure 2: ATMBUSADAPTER-XPRO - mikroBUS Adapter**
Copy link
Author

@JamesLiu-Microchip JamesLiu-Microchip Feb 25, 2026

Choose a reason for hiding this comment

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

Has committed the change.

Copy link
Contributor

Choose a reason for hiding this comment

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

unused - please drop

Copy link
Author

@JamesLiu-Microchip JamesLiu-Microchip Feb 25, 2026

Choose a reason for hiding this comment

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

Has committed the change.

Copy link
Contributor

@kartben kartben Feb 16, 2026

Choose a reason for hiding this comment

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

this should be named exactly like the shield - mchp_rnbd451_bt_mikrobus.webp

Copy link
Author

Choose a reason for hiding this comment

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

Has committed the change.

kartben
kartben previously approved these changes Feb 25, 2026
@nandojve
Copy link
Member

ping @JarmouniA

nandojve
nandojve previously approved these changes Feb 25, 2026
The Xplained Pro layout provide a standard 20 pin header.  A board
can have one or more headers and can share pins.  The extension
headers are given names EXTn where n ϵ [1…7], n is determined by
which ID pin is connected to the embedded debugger.

Signed-off-by: James Liu <James.Liu2@microchip.com>
Add xprpo-header support in sam_e54_xpro

Signed-off-by: James Liu <James.Liu2@microchip.com>
Expand SERCOM serial ports in the sam_e54_xpro board. This add and
enable sercom0, sercom1 and sercom5 ports which are located in the
xplained pro header. It makes use of the microchip,xpro-header to
easy use with shields.

Signed-off-by: James Liu <James.Liu2@microchip.com>
Add board support for the Microchip RNBD451 shield.
This shield is compatible with a development board that includes a
mikroBUS socket.

Signed-off-by: James Liu <James.Liu2@microchip.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Boards/SoCs area: Devicetree Binding PR modifies or adds a Device Tree binding area: Devicetree Bindings area: GPIO area: Shields Shields (add-on boards) platform: Microchip SAM Microchip SAM Platform (formerly Atmel SAM)

6 participants