Very long discover time connect with hfclk request

[Vlad Mokhnachov]

Hi!

I am using SDK15.3.0, PCA10056 and Windows10.

I am notice, that if it will be hfclk request before usb launching and WFE in main loop, time for discover usb device by system increase from less second to 5 second.(I mean time after reset, not first launch)

It can be reproduced with usbd_hid_generic example and NRF52840 DK board(in attachment modified example).

Also, it shouldn't use usb event queue.(APP_USBD_CONFIG_EVENT_QUEUE_ENABLE 0)

You can comment:

574: nrf_drv_clock_hfclk_request(NULL);

or:

621: __WFE();

usbd_hid_generic.zip

It will make fast connect.

[AndreasF]

Hi.

It is an internal ticket, so you have to ask info about it here by submitting that ID.

I've talked a bit more with the development team, and the person responsible for USB related stuff is on vacation until Monday.

Best regards,

Andreas

[Vlad Mokhnachov]

Hi!

Is it some progress with ticket NRFFOETT-2347?

[AndreasF]

Hi.

I've looked at the ticket and asked the development team if they had any updates, they did not have any now unfortunately. However, they are looking into the issue.

Best regards,

Andreas

[Vlad Mokhnachov]

Hi!

Was NRFFOETT-2347 ticket resolved?

[Håkon Alseth]

Hi,

 

Unfortunately, the issue is not resolved, as it is a fundamental issue with how the library handles two specific events.

Please see this response for more details:

https://devzone.nordicsemi.com/f/nordic-q-a/59738/usb-device-suspend-resume-issue-when-requesting-hfclk/251427#251427

 

The workaround is to use the event queue (APP_USBD_CONFIG_EVENT_QUEUE_ENABLE 1) to ensure that the above mentioned events are handled in correct order.

 

Kind regards,

Håkon