Skip to content

boot: zephyr: board: Add M5stack Unit C6L overlay - #2829

Closed
marekmatej wants to merge 1 commit into
mcu-tools:mainfrom
marekmatej:bugfix/unitc6l_overlay
Closed

boot: zephyr: board: Add M5stack Unit C6L overlay#2829
marekmatej wants to merge 1 commit into
mcu-tools:mainfrom
marekmatej:bugfix/unitc6l_overlay

Conversation

@marekmatej

@marekmatej marekmatej commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

The PI4IOE5V6408 expander driver selects I2C, overriding MCUboot CONFIG_I2C=n, and its polling work queue fails to link without multithreading. Disable the expander node, and the unused I2C buses with it. Related board PR zephyrproject-rtos/zephyr#113221

The PI4IOE5V6408 expander driver selects I2C, overriding
MCUboot CONFIG_I2C=n, and its polling work queue fails to
link without multithreading. Disable the expander node, and
the unused I2C buses with it.

Signed-off-by: Marek Matej <marek.matej@espressif.com>

@nordicjm nordicjm left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

whilst the changes are OK, bit puzzled why they are needed since I2C should not be enabled, so why would any of the others?

@marekmatej

marekmatej commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

whilst the changes are OK, bit puzzled why they are needed since I2C should not be enabled, so why would any of the others?

The GPIO expander, which is enabled by default, is pulling the I2C. But I agree with you, but I didn't find a better solution to the linker error (if sysbuild is used) than doing what the other M5stack board m5stack_cores3 does.
Anyway, I added a link to the board PR in question to the description.

@nordicjm

Copy link
Copy Markdown
Collaborator

whilst the changes are OK, bit puzzled why they are needed since I2C should not be enabled, so why would any of the others?

The GPIO expander, which is enabled by default, is pulling the I2C. But I agree with you, but I didn't find a better solution to the linker error (if sysbuild is used) than doing what the other M5stack board m5stack_cores3 does. Anyway, I added a link to the board PR in question to the description.

why is the GPIO port expander enabled by default?

@marekmatej

Copy link
Copy Markdown
Contributor Author

why is the GPIO port expander enabled by default?

It is used to connect the radio.

@nordicjm

Copy link
Copy Markdown
Collaborator

why is the GPIO port expander enabled by default?

It is used to connect the radio.

right but MCUboot does not need a radio :) is it just because CONFIG_GPIO is on which enables it and the other thing selects CONFIG_I2C?

@marekmatej

Copy link
Copy Markdown
Contributor Author

why is the GPIO port expander enabled by default?

It is used to connect the radio.

right but MCUboot does not need a radio :) is it just because CONFIG_GPIO is on which enables it and the other thing selects CONFIG_I2C?

You're right, this doesn't belong to MCUboot. Will fix dependencies and remove this PR.

@marekmatej

Copy link
Copy Markdown
Contributor Author

Closing as solved on a board level.

@marekmatej marekmatej closed this Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants