Skip to content

example usb/cdc_acm coredump on board STMicroelectronics nucleo_h563zi when use "usbd_next_prj.conf" #76250

@MY201314MY

Description

@MY201314MY

Describe the bug
when I enable the CONFIG_USB_DEVICE_STACK=y, the usb/cdc_acm can work well.
But when I enable CONFIG_USB_DEVICE_STACK_NEXT=y, the system will coredump.

To Reproduce
Steps to reproduce the behavior:

  1. check zephyr version
commit 099209b7d563886b23ddcbb1d59f06fdd9e66ab1 (HEAD -> mini-h562-usb-1.1.0, origin/main, origin/HEAD, main)
Author: Johan Hedberg <[email protected]>
Date:   Mon Jul 22 12:43:46 2024 +0300

    doc: release-notes-3.7: Add more details for Bluetooth HCI drivers
    
    Make sure all added (and removed) HCI drivers are mentioned, and also
    provide a reference to the new HCI driver API.
    
    Signed-off-by: Johan Hedberg <[email protected]>

2.build

west build samples/subsys/usb/cdc_acm -b nucleo_h563zi -p -- -DCONF_FILE:STRING="usbd_next_prj.conf"

3.west flash and inset the usb cable to PC
4. See error
the third parameter buf is NULL , which caused the system to crash.
I don't know how to fix it.
image

Expected behavior
usb cdc_acm can run normal when CONFIG_USB_DEVICE_STACK_NEXT=y is enabled.

Impact

Logs and console output

*** Booting Zephyr OS build v3.7.0-rc3-102-g099209b7d563 ***
[00:00:00.000,000] <inf> cdc_acm_echo: USB device support enabled
[00:00:00.000,000] <inf> cdc_acm_echo: Wait for DTR
[00:00:00.003,000] <inf> cdc_acm_echo: USBD message: Device suspended
[00:00:04.955,000] <inf> cdc_acm_echo: USBD message: Device resumed
[00:00:04.958,000] <inf> cdc_acm_echo: USBD message: Device suspended
[00:00:05.099,000] <inf> cdc_acm_echo: USBD message: Device resumed
[00:00:05.156,000] <inf> cdc_acm_echo: USBD message: Bus reset
[00:00:05.284,000] <inf> cdc_acm_echo: USBD message: Bus reset
[00:00:05.383,000] <err> os: ***** BUS FAULT *****
[00:00:05.383,000] <err> os:   Precise data bus error
[00:00:05.383,000] <err> os:   BFAR Address: 0x0
[00:00:05.383,000] <err> os: r0/a1:  0x20000544  r1/a2:  0x00000000  r2/a3:  0x0800e4d8
[00:00:05.383,000] <err> os: r3/a4:  0x200000e8 r12/ip:  0x20002484 r14/lr:  0x080033b9
[00:00:05.383,000] <err> os:  xpsr:  0x61000000
[00:00:05.383,000] <err> os: Faulting instruction address (r15/pc): 0x080046b0
[00:00:05.383,000] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:00:05.383,000] <err> os: Current thread: 0x20000aa0 (unknown)

Metadata

Metadata

Labels

area: USBUniversal Serial BusbugThe issue is a bug, or the PR is fixing a bugplatform: STM32ST Micro STM32priority: lowLow impact/importance bug

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions