Re: [PATCH v7 00/24] usb: dwc3: part 2, make the resynced code work

Anshul Dalal <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <178765097973.1498018.5668901885485543636.b4-review@b4>
On Mon, 24 Aug 2026 17:41:09 +0200, Anders Roxell <[email protected]> wrote:
> [...]
> dwc2 with and without DM_USB_GADGET, at91_udc, atmel_usba_udc, ci_udc,
> musb-new and mtu3. 17 boards in total.
> 
> DFU is tested on hardware on BeagleBoard-X15, and on BeaglePlay by
> Anshul. ci_udc is tested on an i.MX93 board with ums. The rest is build
> tested only.

Hi Anders,

Thanks for reworking the series, I was able to get DFU boot to work properly
and the usb devices are being discovered properly too.

Though I ran into an issue while using ums with your patches as the host isn't
able to detect the connected device. With default logs I only see a
'\dwc3-generic-peripheral usb@31000000: unknown endpoint event 0'.

Further debug logs are below on TI's AM62p EVM:

@    => ums mmc 1
@    UMS: LUN 0, dev mmc 1, hwpart 0, sector 0x0, count 0x3b72400
@    g_dnl_register: g_dnl_driver.name = usb_dnl_ums
@    g_dnl_bind: gadget: 0x00000000fde7fb68 cdev: 0x00000000fde5cdd0
@    usb_add_config: adding config #1 'usb_dnload'/00000000fde83cc0
@    g_dnl_do_config: configuration: 0x00000000fde83cc0 composite dev: 0x00000000fde5cdd0
@    adding 'Mass Storage Function'/00000000fde5c110 to config 'usb_dnload'/00000000fde83cc0
@    cfg 1/00000000fde83cc0 speeds: high full
@    usb_add_config: interface 0 = Mass Storage Function/00000000fde5c110
@    g_dnl_bind: calling usb_gadget_connect for controller 'dwc3-gadget'
@    usb_dnl_ums: ready
@    -dwc3-generic-peripheral usb@31000000: unknown endpoint event 0
@    |set_config: high speed config #1: usb_dnload
@    \non-core control reqa1.fe v0000 i0000 l1

I observed a similar issue on the beagleplay too. Regards!

Anshul

-- 
Anshul Dalal <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.