USB2CANFDV1 failure with usbd_next

[henrikbrixandersen]

Describe the bug

CANnectivity on the USB2CANFDV1 board fails during driver initialisation when used with the experimental device_next stack.

To Reproduce

Steps to reproduce the behavior:

1. west build -b usb2canfdv1/stm32g0b1xx ../custom/cannectivity/app/ -S rtt-console -- -DFILE_SUFFIX=usbd_next
2. west flash
3. See error below on the RTT console

Expected behavior

No error.

Logs and console output

*** Booting Zephyr OS build v4.0.0-2502-gf786ecc07513 ***
*** CANnectivity firmware v1.0.0-6-gcbbbc9b1b8fa ***
[00:00:00.000,000] <dbg> gs_usb: gs_usb_register_channel: channel 0 features = 0x00002533
[00:00:00.000,000] <dbg> gs_usb: gs_usb_init: initialized class instance 0x20001068, interface number 0
[00:00:00.001,000] <inf> main: CANnectivity firmware initialized with 1 channel

[00:00:00.209,000] <dbg> gs_usb: gs_usb_enable: enabled
[00:00:03.485,000] <err> udc: Failed to allocate net_buf 0
[00:00:03.485,000] <err> gs_usb: unsupported host byte order (0x20004430)

Environment

• Target board: usb2canfdv1
• OS: Ubuntu 22.04, Linux kernel v6.8.0-49
• Toolchain: Zephyr SDK version 0.17.0
• CANnectivity Git commit SHA: cbbbc9b
• Zephyr RTOS Git commit SHA: f786ecc075132297fc409bb1d89e3300de1a95db

Additional context

Known issues with the STM32 device_next driver: zephyrproject-rtos/zephyr#80820