Regarding mouse HID example code

RE: Regarding mouse HID example code

Hung Bui — Mon, 06 Jan 2025 09:22:55 GMT

That's the 32Mhz crystal. You need to show us what you use on the 32kHz crystal. If you don't have the crystal, you need to set the clock source to RC. Please set NRF_SDH_CLOCK_LF_SRC ,CLOCK_CONFIG_LF_SRC and NRFX_CLOCK_CONFIG_LF_SRC to 0.

NRF_SDH_CLOCK_LF_ACCURACY should be 500ppm.

RE: Regarding mouse HID example code

k.hema sundar — Fri, 03 Jan 2025 13:55:38 GMT

Yes i have a crystal oscillator on my board with 32.000MHZ

RE: Regarding mouse HID example code

Hung Bui — Fri, 03 Jan 2025 13:17:17 GMT

Hi,
You need to check the crystal on your board. Please try to test with a 2nd board to verify if there is any problem with that particular board.
Please provide the schematic and the BOM.

RE: Regarding mouse HID example code

k.hema sundar — Fri, 03 Jan 2025 13:09:11 GMT

yes it is configured to <7=> NRF_CLOCK_LF_ACCURACY_20_PPM

RE: Regarding mouse HID example code

k.hema sundar — Fri, 03 Jan 2025 13:03:30 GMT

ok I'll try and let you know what happen thank you.

RE: Regarding mouse HID example code

Hung Bui — Fri, 03 Jan 2025 12:57:25 GMT

Since it's your custom board, please double check the 32kHz crystal to see if you have selected the correct one. THe ppm should be 20ppm, otherwise you need to reconfigure the code to match your actual ppm.

RE: Regarding mouse HID example code

Hung Bui — Fri, 03 Jan 2025 12:35:27 GMT

Hi Hema,

The SDK has not been changed for 5 years and it has been intensively tested on all the boards so I am quite certain it's not the issue with the DK.
Please make sure you erased bond on the phone (Forget the device in Bluetooth testing)
Please use the nRF Connect app on the phone to test, if you have another phone it worth to try on another phone.

Regarding the sniffer you need to have a DK to use as a sniffer.

RE: Regarding mouse HID example code

k.hema sundar — Fri, 03 Jan 2025 04:58:56 GMT

Hi Hung Bui,
I've tried with ble_app_uart example but still not working. And for sniffer is there any chance to get the sniffer data via USB, because, has i said i don't have UART support for my j-link. If it is possible to get via USB please guide me how to do it then, i'll get the sniffer data to you.
if your have nrf52833 DK can you please try the ble_hids_mouse or any other examples and tell me weather it is working or not.

RE: Regarding mouse HID example code

Hung Bui — Thu, 02 Jan 2025 16:44:47 GMT

Hi Hema,
Please try to get hold of a nRF52840 DK. It will help you a lot on development and save you a lot of time. You can use it as the sniffer.

Please try to test with ble_app_uart , it has PCA10100 supported.

Disconnected reason 0x3e means BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED. It's hard to tell what exactly went wrong without the sniffer.

RE: Regarding mouse HID example code

k.hema sundar — Thu, 02 Jan 2025 12:11:54 GMT

it is giving that p_ble_evt->gap_evt.disconnected.reason=0x3e
by the by you said that use another example code like ble_app_blink but in that pca10100 example is not there. So how could i use that code for pca10100 it has limited examples. And i have tried with ble_hid_keyboard too but same problem is facing.
And you said that remove the device in bluetooth setting i've tried that but no change is there.
And as u said refer the sniffer trace but for sniffer trace i dont have UART option on my j-link to detect the port, i am using j-link EDU mini for my board, so i cant use the sniffer trace, that's the reason i am using printf function insted of using APP_ERROR_CHECK.
please help me on my problem.

RE: Regarding mouse HID example code

Hung Bui — Thu, 02 Jan 2025 12:10:58 GMT

Hi,
From the log you showed, it seems that it get connected then disconnected immediately after that.
Please try to print the p_ble_evt->gap_evt.disconnected.reason when you have the ble_event_id=17 (BLE_GAP_EVT_DISCONNECTED)

My suspicion is that there were bonding information on the central device that has not been removed. So when you connect the board to the device it will try to re-pair with the older bond information. This will not succeed and it will terminate the connection.
Make sure you erase all bond information on the phone (Forget/remove the device in Bluetooth setting)

Please try to test using other sample for example ble_app_blinky
If the issue persist please try to capture a sniffer trace. You can learn how to use it here.