#Unexpected issue with `__device_dts_ord_DT_CHOSEN_zephyr_console_ORD` issue

1 messages · Page 1 of 1 (latest)

civic zephyr
#

Another what did I miss with the latest ZMK main changes question. Something has triggered an issue with __device_dts_ord_DT_CHOSEN_zephyr_console_ORD

#

My personal layout is in https://github.com/peterjc/zmk-config/tree/main and is also targetting main for ZMK etc. This is building on all except a split Xiao keyboard:

  # Acid (split):
  - board: xiao_ble//zmk
    shield: acid_left
    snippet: studio-rpc-usb-uart
    cmake-args: -DCONFIG_ZMK_STUDIO=y
  - board: xiao_ble//zmk
    shield: acid_right

All that is changed here (in the personal layout, that I can see) is a keymap https://github.com/peterjc/zmk-config/blob/main/config/acid.keymap yet the build for this keyboard is failing at __device_dts_ord_DT_CHOSEN_zephyr_console_ORD

#

This keyboard is my only one using the Xiao BLE, and I am using the NFC pads. That's something that changed since ZMK v0.3

burnt plinth
#

Sorry, didn't get a chance look at the links. But this error might be because CONFIG_SERIAL is not enabled, which'd be needed for wired split

civic zephyr
#

Good guess, but the wired split board is building (used to be working fine too - not tried yet since the //zmk changes).

#

Only one build is failing, my only wireless spilt, and only Xiao BLE board.

#

Again, this used to build fine

burnt plinth
#

Hm, I should have read better, yes

#

My rough guess is you have a .../boards/xiao_ble.overlay somewhere, that needs to be xiao_ble_zmk.overlay

#

But I'll check the build

civic zephyr
burnt plinth
#

You should ignore my comments, yeah

civic zephyr
#

So whatever it is wasn't super obvious. Thanks for trying, even if we only ruled out a few potential mistakes.

burnt plinth
#

I found the root cause but not sure why it's happening

civic zephyr
#

That's odd. I wanted ZMK Studio on the left (primary), but not right (secondary) as per the docs.

#

The build entry is the same on the original keyboard repo (which builds with a simple keymap) as on the personalised repo (with the fancy keymap):

  # Acid (split):
  - board: xiao_ble//zmk
    shield: acid_left
    snippet: studio-rpc-usb-uart
    cmake-args: -DCONFIG_ZMK_STUDIO=y
  - board: xiao_ble//zmk
    shield: acid_right
burnt plinth
#

I am confused, I thought I saw zephyr,console in the file I linked. But it's not there, so it never ends up getting set in your case. But in my local build, it is set in zephyr/boards/common/usb/cdc_acm_serial.dtsi

civic zephyr
#

That's the debugging logging over USB thing?

burnt plinth
#

Yeah, but in this case it's not from ZMK's USB logging snippet. It's just a board property

civic zephyr
#

So possibly activated somewhere by mistake...

burnt plinth
#

This is pretty funky, I also couldn't reproduce locally with your config repo

civic zephyr
#

Something in the GitHub action maybe? It isn't a one off - I have a branch for some RGB experiments (different keyboard), and there too this Xiao fails the same way:

/tmp/zmk-config/zephyr/drivers/console/uart_console.c:42:9: note: in expansion of macro 'DEVICE_DT_GET'
   42 |         DEVICE_DT_GET(DT_CHOSEN(zephyr_console));
      |         ^~~~~~~~~~~~~
compilation terminated due to -Wfatal-errors.
burnt plinth
#

More likely that my setup has a discrepancy, I'll have another look

civic zephyr