Mbed-os: STM32F429: "usb_thread could not read dev descr" error in USB host keyboard

[Arjun765]

Description

- Type: Bug

Bug

Target
NUCLEO-STM32F429

Toolchain:
GCC_ARM

Toolchain version:
arm-none-eabi-gcc (15:4.9.3+svn231177-1) 4.9.3 20150529 (prerelease)

mbed-cli version:
1.2.2

mbed-os sha:
caeaa49

mbed's USB host keyboard is not working, i'm getting the following error when i try to use the usb host keyboard

[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_ERR: ../USBHost/USBHost/USBHost.cpp:149]usb_thread could not read dev descr
[USB_INFO: ../USBHost/USBHost/USBHost.cpp:177]New device connected: 0x2000b414 [hub: 0 - port: 1]

[0xc0170]

@ARMmbed/team-st-mcd Please review
[Mirrored to Jira]

[timkrief]

I have the same problem here. I can't connect a keyboard on an usb hub connected to STM32F429I-DISC1 ... The library seams to not work properly.
[Mirrored to Jira]

[jeremydufour]

@adbridge any ideas on this issue ?
[Mirrored to Jira]

[adbridge]

@jeremydufour We are waiting on ST to take a look.
[Mirrored to Jira]

[bcostm]

No idea why it does not work on the NUCLEO_F429ZI, we'll have to look at it.

But concerning the support of USBHost on the DISCO_F429ZI is has not been enabled due to unresolved issue (see PR #5617). No progress since that time on this board.

[Mirrored to Jira]

[Piroro-hs]

I have the same problem with the NUCLEO-F446RE board.
Each time I connect a USB device to the board, I get 10 USB_ERRs and one USB_INFO with address of 0x2000549c.
[Mirrored to Jira]

[jeremydufour]

@bcostm I added support for DISCO-F429ZI. My commit is here 859c607f30bd989ab6acde333980daea791d1827

I need your approval before opening a pull request

[Mirrored to Jira]

[bcostm]

Thanks ! I'll have a look and let you know.
[Mirrored to Jira]

[timkrief]

Thank you @jeremydufour I hope ARMmbed will use this as soon as possible!
[Mirrored to Jira]

[bcostm]

@jeremydufour So, I checked your commit and it is almost the same as I did (and removed) in my commit https://github.com/ARMmbed/mbed-os/pull/5617/commits/c621c688c4777b5bef65ea00d4bfb537d547cf12. Only difference is that in your case you didn't configured the VBUS pin.

Anyway it didn't work for me. I test it using the features\unsupported\tests\usb\host\mouse test.

Can you tell me the board name/version you have ? The state of the solder bridges SB18, SB19 and SB20. And finally can you test the USB Mouse test code ? Thanks.

[Mirrored to Jira]

[jeremydufour]

@bcostm Sorry for the late reply. I have a STM32F429I-DISC1 board. I can't test the solder bridges right now but I keep you updated for the next two weeks. I will try soon the USB Mouse test code as well.
[Mirrored to Jira]

[0xc0170]

@jeremydufour Any update?

@ARMmbed/team-st-mcd What is the status for this issue?
[Mirrored to Jira]

[screamerbg]

@jeremydufour Any update on this?
[Mirrored to Jira]

[jeremydufour]

Hi everyone ! I have been working on the BlueNRG2 SoC recently. I don't have any updates on this issue but I will send updates when I have some time.
[Mirrored to Jira]

[bcostm]

No update also on our side with the actual API.

The goal now is to work on the new USB API (branch https://github.com/ARMmbed/mbed-os/tree/feature-hal-spec-usb-device) only. But nothing done yet on this board AFAIK.

[Mirrored to Jira]

[adbridge]

Internal Jira reference: https://jira.arm.com/browse/IOTPART-5628

[jeromecoutant]

It seems there is no more pending action.
Can we close this old issue ?