Keyboard build is sucessfull, but doesn't do anything when it has the UF2 file.

[exotic hornet]

Absolutely no inputs whatsoever. not tried BT, only given wired a shot so far. Currently only using the left side as the right side isnt done (ran out of solder, so I'm waiting on that), I haven't a clue what could be going on, I'm new to this. I am using an Nice!Nano knock off and it seems to be working perfectly fine. It could potentially have something to do with my originally attempting to give it support with Studio, but I'm not sure. I would try to fix it, but I haven't a clue what I am doing and would likely make it worse - it is all copied from the official documentation with the changes necessary to make it fit my board. The issue isnt hardware related, unless I want to be using different gpio numbers with it being a Nice!Nano instead of a ProMicro. https://github.com/ThisIsVamp/Ballpadyl

Also, just want to add that I haven't yet added the trackball, trackpad or joysticks so I haven't added anything to include them yet. Thanks.

[bitter anchor]

You're building corne_left..?

Error message from the last failed build is

No shield named 'ballpadyl_left' found

https://github.com/ThisIsVamp/Ballpadyl/actions/runs/14961792050/job/42024867258#step:11:35

Files for a shield should be in boards/shields/<name>

[unkempt gate]

you have the right shield set up twice

[exotic hornet]

I’ve solved these issues (I think). Moved the shield files into a folder (boards/shields/ballpadyl) and fixed the duplicate right shield issue. Still getting the same ‘no shield named ‘ballpadyl_left’ found’ error message. It also seems to be failing to locate a key map file, which I do have. Not sure if this is because it doesn’t like the ballpadyl naming or not.

[bitter anchor]

Revert this change https://github.com/ThisIsVamp/Ballpadyl/commit/0f0b92f1768d6e39bd200eac4a77c5c48020b210

The dot . in board_root: . is important

devicetree error: /__w/Ballpadyl/Ballpadyl/boards/shields/ballpadyl/ballpadyl.keymap:27 (column 264): parse error: expected number or parenthesized expression

In case you haven't found it.. COMM isn't a valid keycode.
https://github.com/ThisIsVamp/Ballpadyl/actions/runs/14969997475/job/42048582552#step:13:1574
https://zmk.dev/docs/troubleshooting/building-issues

[exotic hornet]

Yea I saw it. Chucked an error code into copilot and it seems to have mostly solved the remaining issues (random stuff like not changing &lt to &kp when copying layers but changing the functions). Successful build now so I’ll give it a go and see if it works.

Nope that most definitely did not work. When it rebooted it then opened every application I own, spammed random text in it and when currently typing no inputs are being made, and it’s kind of flickering between 2 applications, as well as repeatedly enabling and disabling caps lock. Any ideas?

[unkempt gate]

I don't know how your keyboard is actually wired, but the diode direction and GPIO flags you've specified are at odds
worth reviewing the kscan docs for those: https://zmk.dev/docs/config/kscan#devicetree-3

[bitter anchor]

I don't have time right now and didn't check your repository, but I would recommend NOT using any kind of LLM for ZMK in general. They mostly hallucinate their output related to ZMK.

[exotic hornet]

Don’t worry I have all the time in the world (this has taken 2 months of attempts before coming here for help so far). What’s an LLM?

[bitter anchor]

Large language model, aka chatgpt and the alike

If you ask copilot "What's LLM? How does LLM work? What are the shortcomings of LLM? Explain the randomness in LLM."
It should give you some pretty reasonable responses.

But anything ZMK related tends to be completely wrong.

[exotic hornet]

Yea I’m being cautious with it, as I did use it way too much one time and it had me adding all sorts of random stuff, so I’m only doing things that I know won’t cause issues. Basically only used it to change key codes to stuff that actually made sense.

[exotic hornet]

Had a look, have tried to change it but it’s giving new errors now. I’m completely lost as what’s going on at this point, but I can say the diodes go down the keyboard, not across it. Is the direction they go matters, the black line on the diode is pointing up.

[unkempt gate]

Slow down, take a breath, and closely review your changes: https://github.com/ThisIsVamp/Ballpadyl/commit/b2b03489cc37cb1a3040028b8c9fa07b11629c82#diff-45628c53f9f8fffcbaf8286619348c9557b025162cc3c795459e9be5070655ef
||Where did your > s go?||

[exotic hornet]

Ok. Sorted that out, and the build came back positive, it’s no longer opening every piece of software imaginable 100 times a second, however I’m not getting any input on any keypress.

[boreal pivot]

Do you have some sort of schematic/drawing of what row/column you wired where?

[exotic hornet]

does this work? the diodes are all facing in the direction that I show in the corner, and are all above each switch.

this is only for the left side, as I haven't wired the right side completely yet.

[unkempt gate]

so you have a row2col matrix

[exotic hornet]

do I need to do anything more than flip that phrase around? when I did it has started opening all my software again..

[boreal pivot]

You need to move the pull down flags from row pins to col pins, like mentioned in docs linked here

[exotic hornet]

ah right. I apologise, I'll have a look.