Skip to content

fix(boards) fix missing overlay for mikoto v6.3#3232

Open
zhiayang wants to merge 2 commits intozmkfirmware:mainfrom
zhiayang:pr-fix-missing-mikoto-6.3
Open

fix(boards) fix missing overlay for mikoto v6.3#3232
zhiayang wants to merge 2 commits intozmkfirmware:mainfrom
zhiayang:pr-fix-missing-mikoto-6.3

Conversation

@zhiayang
Copy link
Copy Markdown
Contributor

@zhiayang zhiayang commented Feb 12, 2026

PR check-list

Adds a dts for mikoto 6.3, which some people have apparently acquired from somewhere XD

Close #3121

Had to edit some Kconfig things for this to build (was getting dts link errors), not sure if this is necessary or not. Haven't kept up much with ZMK dev.

@zhiayang zhiayang requested a review from a team as a code owner February 12, 2026 15:55
Copy link
Copy Markdown
Contributor

@petejohanson petejohanson left a comment

Choose a reason for hiding this comment

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

Just one question on the Kconfig changes. Thanks for the fixes!

Comment on lines +6 to +8
imply RETAINED_MEM
imply RETENTION
imply RETENTION_BOOT_MODE
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this is ok as is, and is extra safe not to change things if you build the "bare" mikoto board without the /zmk variant. Did you find these conditionals not working for you? Can you share the exact build command you used when testing this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

ohhh, interesting. Am I supposed to specify "mikoto/zmk@6.30" now?

Yeah I built locally with just "mikoto@6.3" and it was giving me DTS errors that I traced to smth about retention, so I tried disabling these configs and it worked.

Im not sure if there's a better way? Haven't been keeping up with the zmk progress lately.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes, see the zephyr 4.1 blog post - recent addition. mikoto//zmk@... I believe

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.

Based on https://docs.zephyrproject.org/latest/hardware/porting/board_porting.html#board-terminology, it should actually be mikoto@6.3//zmk (which I think is a little odd to put the version in the middle)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The blog post for the 4.1 migration has been updated to reflect those new board IDs with the variant included.

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.

Mikoto@6.3.0 undefined node label causes build to fail

4 participants