-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
example usb/cdc_acm coredump on board STMicroelectronics nucleo_h563zi when use "usbd_next_prj.conf" #76250
Comments
Also seen with stm32h573 disco kit, when plugging the USB cable. The function usbd_cdc_acm_ctd of the ./subsys/usb/device_next/class/usbd_cdc_acm causing a crash at memcpy because next_buf->data is 0 after
Log before crashing reports
|
@loicpoulain or @jfischer-no please, could you help During the udc_stm32 ep_enable, the HAL_PCDEx_PMAConfig is called for EP 0x0, 0x80,0x81, 0x82, 0x1 but never called for EP 0x2 |
An issue is also seen with the b_g474e_dpow1 (USB FS)
|
To be tested with #80820. |
Test done but issue always here. |
I am seeing the below error message when running the HID sample on RT1060 EVK board. However the test seems to be working as I see a HID-mouse device on my Windows machine.
|
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:
2.build
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.
Expected behavior
usb cdc_acm can run normal when CONFIG_USB_DEVICE_STACK_NEXT=y is enabled.
Impact
Logs and console output
The text was updated successfully, but these errors were encountered: