nrf52832 NUS UUID problem

RE: nrf52832 NUS UUID problem

Simonr — Wed, 24 Mar 2021 13:48:43 GMT

BLE_UUID_TYPE_BLE indicates that the UUID is a Bluetooth SIG UUID, while BLE_UUID_TYPE_VENDOR_BEGIN specifies that it will be a Vendor UUID type.

Best regards,

Simon

RE: nrf52832 NUS UUID problem

joe — Wed, 24 Mar 2021 09:23:50 GMT

Thank you for your reply. I have solved this problem.

#define NUS_SERVICE_UUID_TYPE BLE_UUID_TYPE_BLE // BLE_UUID_TYPE_VENDOR_BEGIN /**< UUID type for the Nordic UART Service (vendor specific). */

After changing BLE_UUID_TYPE_VENDOR_BEGIN to BLE_UUID_TYPE_BLE, it can run normally. Although I don't know why.

Thanks!

Best regards,

RE: nrf52832 NUS UUID problem

Simonr — Tue, 23 Mar 2021 14:05:33 GMT

I need some more details to help you out here. What kind of device are you flashing this application onto, an nRF52 DK or a custom board? What function is it that returns this 0x4001 error? Does it occur when you leave the NUS_BASE_UUID as is? If not, please control that the length of your UUID is the same as NUS_BASE_UUID.

As a side note, if you modify yhe NUS UUID (NUS_BASE_UUID) to your own UUID (any other value) the nRFConnect application won't recognize it as a UART service just so you know.

Best regards,

Simon