52840 usb can't be recognized

RE: 52840 usb can't be recognized

Sigurd — Tue, 14 May 2024 13:36:48 GMT

Hi!

[quote user=""] the usb hub can't recover this 840 usb slave(reboot 840 would not solve this issue), unless reboot usb hub.[/quote]

Overall, this seems to be a weakness with this USB hub. Not seen anything like this before with other hubs.

RE: 52840 usb can't be recognized

William.wei — Wed, 17 Apr 2024 03:05:51 GMT

Hi Sigurd,

i have onsite visit and tested together, it was simlpy plug in and out testing, and it is about "1 of 100 " to "1 of 200" chances that device would not be recognized.

Regards,

William.

RE: 52840 usb can't be recognized

Sigurd — Wed, 10 Apr 2024 21:56:47 GMT

Hi!

[quote user=""] and when they did pressure test,[/quote]

Could you elaborate on this pressure test? How was it done?

RE: 52840 usb can't be recognized

William.wei — Tue, 09 Apr 2024 03:28:06 GMT

Hi Turbo J,

may i ask the where is the source of usb driver, that pc set address of our 840?

i would suggest customer to do usb init first and get address, make sure usb is working normally, then do other task later.

customer is using nrf5 sdk17.1.0

i did see some source code ,but it never runs into here:

Regards,

William.

RE: 52840 usb can't be recognized

William.wei — Sun, 07 Apr 2024 01:45:55 GMT

i mean set_address operation from host:

normally, host will set a new address to usb after 840 reset. But here, host didn't do that action, and engineer from usb hub told me that our D+ D- is not responding correctly.

normally D+ is 3.3v and D- is 0v,after we received C_PORT_RESET command from host，D+ will be 0v and D- will be 800mv as respond.

So,may i ask where is the source code in our driver, that D+ and D- change this status,.

Regards,

William.

RE: 52840 usb can't be recognized

Turbo J — Wed, 03 Apr 2024 05:28:34 GMT

Why do you expect a "set address" operation in the 2nd trace?

Look closer at the "get descriptor" request: It has a valid address already, and its not for the device descriptor but for one of the strings. The host is expected to set the device address after getting the device descriptor.