NUS Service: sdk-zephyr implementation vs sdk-nrf implementation

[longo92]

Hi,

I’m evaluating the NUS (Nordic UART Service) as a way to stream and receive byte arrays.

I’ve noticed that there are two different implementations of the NUS service:

1. zephyr-sdk implementation
   https://github.com/nrfconnect/sdk-zephyr/blob/ncs-v3.2.0/subsys/bluetooth/services/nus/nus.c
   (with the corresponding nus.h and Kconfig files)

2. nrf-sdk implementation
   https://github.com/nrfconnect/sdk-nrf/blob/v3.2.0/subsys/bluetooth/services/nus.c
   (with its own nus.h and Kconfig files)

Which implementation should be used?
What are the differences between the two?

Thanks,

Alessandro

[Benjamin]

Hi Alessandro,

It is the same BLE service and UUIDs, implemented in two different ways. The difference is in how they are implemented. The Zephyr version comes from upstream Zephyr and is more generic and vendor independent. The nRF version is maintained by Nordic and is the one typically recommended.

Regards,
Benjamin

[longo92]

Thank you!

I will use the nordic implementation!