[SOLVED] No input from board

[violet drum]

you probably want to follow the new shield documentation

[compact vine]

Firmware builds, board doesnt work.

I have literally no idea what I could do wrong anymore. Cheched the PCB, that doesn't seem to be the fault.

https://github.com/siliconsniffer/zmk-config

No input from board

[violet drum]

It doesn't look like you followed the docs.

• build workflow doesn't match the template
• boards/shields folder nested under config, no physical-layout
• looks like you're trying to build for a Xiao BLE, but I'm not actually sure for a few reasons. P0.06 isn't exposed on a Xiao. Better to stick with the &xiao_d nomenclature explained here.
• Your build.yaml indicates you're trying to build two_percent_milk, which is a Pro Micro shield. So not sure whether you're making a Xiao or a Pro Micro shield I can tell you're at least not calling your shield the same thing, which is good, because the version in ZMK always "wins". But you'll want to put your own shield name in.

[compact vine]

I did - at least partly.

boards/shieldsbeing under config doesn't seem to be an issue?

Ah, forgot to push the build.yml.

[violet drum]

it's been deprecated, and the eventual plan is to throw an error about it
the new shield guide doesn't involve moving it there, which is kind of a tell

[compact vine]

Ah, yeah - saw the deprecation warning but would put it in a separate repo once I get it up and running.

&xiao_d instead of the gpio pins, right?

But yes, I am trying to build for the Xiao BLE.

[violet drum]

I don't know what pins you wired to. I'm asking you to look at the image in the docs, read the text below it, and translate that to your wiring.
Much like the middle pins on a nice!nano, which do not exist on most Pro Micro-shaped boards—if you repurposed the NFC pins as GPIO, using &gpio X Y for those is valid because they only exist on the Xiao BLE, not the Xiao RP2040 and Xiao SAMD. You have no choice but to use the nRF-specific pin names. For the rest, &xiao_d mappings exist.

[compact vine]

Haven't soldered them (yet) - so that I can still choose.

[violet drum]

I definitely would not use the NFC pins. Aside from not being usable with other Xiaos, they're more of a soldering hassle.

[compact vine]

Thanks for the info, will remember that!

Should have resolved some of your points in the latest commit.

Holy smokes, thank you so much!

[solved] No input from board

[SOLVED] No input from board

Thanks thanks and thanks! Good night, I will report back tomorrow :D

[compact vine]

@violet drum (I hope you don't mind the ping)
Got the module repo up and running but I am struggling with correctly setting up the physical layout. Could you throw a peak at my setup? Run, file.

[winged light]

https://github.com/siliconsniffer/zmk-keyboard-2x3pad/blob/master/boards/shields/2x3pad/2x3pad.overlay#L28 this layout doesn't have keys

[compact vine]

I have those in 2x3layouts.dtsi, that's how I understood the docs?

Ah, I probably need to include it? Or can I put it directly into the 2x3pad.overlay?

[winged light]

Yes and yes.

Currently the only physical layout included in the build is the one I linked
https://github.com/siliconsniffer/zmk-config/actions/runs/14840098765/job/41660755715#step:13:685

[compact vine]

Okay, might have mixed something up while trying to put it in the .overlay.

#include "2x3pad-layouts.dtsi" and keys = <&2x3pad_physical_layout>;

Eugh, got a syntax error now. This is a step back lol

[compact vine]

I don't get it - what am I doing wrong?

https://github.com/siliconsniffer/zmk-config/actions/runs/14837914542/job/41664882944#step:13:954 Here it does show up

[meager plover]

Your matrix transform is labeled default_transform, not matrix_transform0: https://github.com/siliconsniffer/zmk-config/actions/runs/14837914542/job/41664882944#step:11:39

[compact vine]

    matrix-transform0: keymap_transform_0 {
        compatible = "zmk,matrix-transform";
        rows = <2>;
        columns = <3>;
        map = <RC(0,0) RC(0,1) RC(0,2) RC(1,0) RC(1,1) RC(1,2)>;
    };

Will result in a syntax error.

[meager plover]

You are using -, not _

I'd change what you use in the physical layout instead

Since that's the "new" part

Just change transform = <&matrix_transform0>; to transform = <&default_transform>;

[compact vine]

I suppose its easier to just move physical_layout0 into the .overlay?

[meager plover]

I see this: https://github.com/siliconsniffer/zmk-keyboard-2x3pad/blob/master/boards/shields/2x3pad/2x3pad-layouts.dtsi#L9

[meager plover]

Either way works

[compact vine]

I guess it's little enough to fit in there.

Will push asap.

[meager plover]

You shouldn't have both though

Otherwise it will see two different physical layouts

[compact vine]

Seems to work now. Is it supposed to not display bluetooth actions on the keycaps in zmk.studio?