Device doesn't work after upgrade from SDK 15.0.0 to SDK 17.1.0

[Mykhaylo]

Hello,

Our project based on nRF52840 doesn't work on MacOS after update from SDK 15.0.0 to SDK 17.1.0.

We can't transfer packets over USB because of changes in SDK 17.1.0 (app_usbd_hid_generic.c):

If we remove this line device works on MacOS again.

Why was this checking added here? If the report has changed, it should be transfered immediately even when idle is enabled.

[Sigurd]

Hi,

It was added in SDK 15.2, as part of this change mentioned in the release notes:

 - Redesigned the idle report mechanism in HID. It now allows a callback function and handles multiple report IDs.

[Mykhaylo]

Hi Sigurd

Are there any results or thoughts?

Do you get the same behavior?

[Sigurd]

Mykhaylo said:

Does it work on your side?

Yes, it's working here. Pressing and releasing button 4(P0.25) printed letter G.

[Mykhaylo]

Hi

Strangely why this doesn't work for us. Are there any thoughts?

[Sigurd]

Sigurd said:

E.g. Pressing button 1 moved the mouse.

Does this work for you? or is it only button 4 and print keyboard "g" letter" that fails?

[Mykhaylo]

We have tested this example on another host. It's a MacBook Pro 2015 13", running macOS Monterey. The example also works for us.

So next week I'm going to retest the example with the first host - MacBook Pro, running macOS Big Sur. I will report results here.

[Mykhaylo]

Hi,

We have checked the usbd_hid_composite_pca10056.hex on our hosts again. There are no problems when we use the example from sdk 15.0.0 (with Win and Mac) or sdk 17.1.0 with Win.

The example from sdk 17.1.0 doesn't work stable when we use Mac. Sometimes it works (pressing and releasing button 4 print letter G), but sometimes it doesn't work after USB cable plug in. Also if we press button 1 mouse movement begins and stops at once and then we can't print letter G anymore by pressing and releasing button 4.

[Sigurd]

Hi,

Mykhaylo said:

The example from sdk 17.1.0 doesn't work stable when we use Mac.

Again, do you see this issue on nRF52840 DK, or only your custom board?

Mykhaylo said:

It's a MacBook Pro 2015 13", running macOS Monterey

Mykhaylo said:

I'm going to retest the example with the first host - MacBook Pro, running macOS Big Sur.

Are you seeing the issue on both macOS Monterey and macOS Big Sur?

[Mykhaylo]

Hi,

Now we test and see the issue on nRF52840 DK (0.9.3). Yes, we have the same behavior on 2 different hosts:
1) MacBook Pro, macOS Monterey
2) MacBook Pro, macOS Big Sur.

[Sigurd]

Hi,

Mykhaylo said:

Now we test and see the issue on nRF52840 DK (0.9.3). Yes, we have the same behavior on 2 different hosts:

This board uses the Engineering A version of nRF52840. https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52840/COMP/nrf52840/nRF52840_ic_rev_comp_with_dev_hw.html

This version is not supported in recent SDK versions, and it's not recommend to use this version anymore. https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52840/COMP/nrf52840/nRF52840_ic_rev_sdk_sd_comp_matrix.html

If you are able to get hold of a newer version of the nRF52840-DK, it would have been interesting to know if it happened on that as well.