[Solved] Trying to build Prospector dongle but west build failed

[crimson crystal]

https://github.com/kaihchang/zmk-simply-adept-dongle-combo/actions/runs/21989523439/job/63532495754#step:13:414

⁨⁨error: 'CONFIG_BT_MAX_PAIRED' undeclared here (not in a function) 19 | #define ZMK_BLE_PROFILE_COUNT CONFIG_BT_MAX_PAIRED | ^~~~~~~~~~~~~~~~~~~~ /tmp/zmk-config/zmk/app/include/zmk/ble.h:19:31: note: in definition of macro 'ZMK_BLE_PROFILE_COUNT' 19 | #define ZMK_BLE_PROFILE_COUNT CONFIG_BT_MAX_PAIRED | ^~~~~~~~~~~~~~~~~~~~⁩⁩

But ⁨CONFIG_BT_MAX_PAIRED⁩ is declared here in simply_adept.conf:
https://github.com/kaihchang/zmk-simply-adept-dongle-combo/blob/main/config/simply_adept.conf#L20

I'm super confused now 😅

[worn totem]

https://github.com/kaihchang/zmk-simply-adept-dongle-combo/actions/runs/21989523439/job/63532495754#step:13:70

warning: BT_MAX_PAIRED (defined at /tmp/zmk-config/zmk/app/src/split/bluetooth/Kconfig:93, /tmp/zmk-
config/zmk/app/src/split/bluetooth/Kconfig.defaults:19, /tmp/zmk-
config/zmk/app/src/split/bluetooth/Kconfig.defaults:32, subsys/bluetooth/host/Kconfig:762) was
assigned the value '6' but got the value ''. Check these unsatisfied dependencies:
((!ZMK_SPLIT_ROLE_CENTRAL && ZMK_SPLIT && ZMK_SPLIT_BLE) || (ZMK_SPLIT_ROLE_CENTRAL && ZMK_SPLIT_BLE
&& ZMK_BLE) || (!ZMK_SPLIT_BLE && ZMK_BLE) || (BT_CONN && BT_HCI_HOST && BT_HCI && BT)) (=n).

[crimson crystal]

Hmmm. I added those bc previously build threw me this error message: ⁨error: 'CONFIG_BT_MAX_PAIRED' undeclared here (not in a function)⁩
https://github.com/kaihchang/zmk-simply-adept-dongle-combo/actions/runs/21988791695/job/63529902875#step:13:390

Also throws ⁨error: 'ZMK_SPLIT_BLE_PERIPHERAL_COUNT' undeclared here (not in a function)⁩ when I get rid of them.
https://github.com/kaihchang/zmk-simply-adept-dongle-combo/actions/runs/21990235994/job/63535065309#step:13:378

[crimson crystal]

Found something interesting. My old push that built successfully few days ago failed as well when I hit re-build. I guess something has changed within the mods I use.

[crimson crystal]

I saw carrefinho used zmkfirmware v0.3 in his main branch build, so I also tried that. Build failed as well but seems like for another reason.

devicetree error: /chosen: undefined node label 'st7789'

https://github.com/kaihchang/zmk-simply-adept-dongle-combo/actions/runs/22008958447/job/63598800947#step:13:41

[lone pollen]

You were building off zmk main, see #announcements message

Pin your version to v0.3

[crimson crystal]

I tried
- name: zmk remote: zmkfirmware revision: v0.3 import: app/west.yml
in my comment at 10:25, it gave that node label error.

I don't know what else to try, so I switched back to zmk main for now and see if I can spot something.

I'm using the correct board ID in build.yaml right...? nice_nano and xiao_ble?

[crimson crystal]

Can't build with nice_nano//zmk and xiao_ble//zmk as board ID in build.yaml as well.

[flat ibex]

for v0.3 is nice_nano_v2 and seeeduino_xiao_ble

this one worked for me with the main version https://github.com/carrefinho/prospector-zmk-module/tree/feat/new-status-screens

[crimson crystal]

yeah zmk main isn't working properly now, or maybe I should just wait while I play with v0.3

That said, I don't get why only the dongle build keeps failing, saying my ZMK_SPLIT_BLE_PERIPHERAL_COUNT is undeclared.

[flat ibex]

here is my config file for a working dongle using that version https://github.com/felixJR123/Melior_V2/blob/main/boards/shields/melior/melior_central_prospector.conf, you can also browse around that is a working build

[crimson crystal]

Seems like the same old node error when I use v0.3 with board IDs like nice_nano_v2 & seeeduino_xiao_ble.
devicetree error: /chosen: undefined node label 'st7789'

https://github.com/kaihchang/zmk-simply-adept-dongle-combo/actions/runs/22010678102/job/63603691218#step:13:42

[flat ibex]

with the zmk v3 you should not use this version of the dongle revision: feat/new-status-screens, this is for the main branch

the undefied node I think is because the driver for the screen st7789 is different from v3 to main

I think if you keep zmk v3 and change the dongle revision to main it may fix the error according tho this https://github.com/carrefinho/prospector-zmk-module the main revision of the dongle is still for zmk v3

[crimson crystal]

Oh wow, it passed!
I thought I've tried that before. I have memory of a gold fish...

[flat ibex]

Nice!

[crimson crystal]

Hey! I think they updated st7789v's driver for zephyr 4.1! I didn't change a thing and my zmkfirmware main version built successfully and is working now!