nrf desktop in ncs SDK cant work when onnect to cmac os

[pipixia_1_1]

When I was developing a keyboard using the nRF52840 with the NCS SDK, I found that the keyboard couldn't type on macOS when connected via USB or BLE. However, it worked perfectly on Windows and Android. I tried modifying the CONFIG_DESKTOP_DEVICE_VID and CONFIG_DESKTOP_DEVICE_PID to Apple's IDs, but it still didn't work. Could you help me solve this problem?

[Priyanka]

Hi,

I am checking this internally and will get back to you.

Regards,

Priyanka 

[pipixia_1_1]

3q for your reply，is there some message now?  

[Priyanka]

Apologies for the delay, but I am still working on this and will get back to you as soon as I get a solid result.

-Priyanka

[pipixia_1_1]

Hello, has there been any progress on this issue? I have a USB case that works on macOS and has been successfully run on the nrf SDK16 here. Is the USB description needed for your reference? I don't know how to modify it to be the same on the NCS SDK. If it's modified to be the same, it should also work on macOS.

[Priyanka]

Hi,

Sorry for the delay but I am discussing this with experts.
Also, why do you change the VID/PID to Apple IDs? I would suggest you to refrain from doing so because you cannot really know if there are some hardcoded quirks based on VID/PID in the host drivers.

pipixia_1_1 said:

I don't know how to modify it to be the same on the NCS SDK.

Modification can be difficult because both are entirely different SDKs. The nRF5SDK is FreeRTOS based and the nRF Connect SDK is Zephyr based. 

Is there any particular sample in the nRF5SDK that you wish to run using the nRF Connect SDK?

-Priyanka

[pipixia_1_1]

because if the PID and VID is not the apples,some key like comsumer key will not work well on mac os, nRF5 SDK v17.1.0: USB HID Composite Example in this example after modify the pid and vid to apples ,mac os can work well.

[Priyanka]

We recommend to try to parse the HID report descriptor with external tools e.g. https://github.com/FFY00/python-hid-parser and see if the parser output matches what was intended

It would be great if you could provide the report descriptor and what reports you send when buttons are pressed and released, ideally a whole sequence of reports that is sent when user types "test" (or any other word) on the keyboard.

Also, I don't think there is a point to point alternative to the sample that you mentioned, but maybe you can take a look at this sample in Zephyr:
https://docs.nordicsemi.com/bundle/ncs-2.6.2/page/zephyr/samples/subsys/usb/cdc_acm_composite/README.html 

-Priyanka