NUS central and DFU using Serialization

[TS Gowtham]

Hi,

I'm using 2 nRF52832s in my project. One of them is connected to a PC serially and has NUS central running on it and the other nRF52 connects to this central. I was able to get the HRM example running with the connectivity firmware on the nRF52 which is connected serially to the PC.

1. Similar to the Serialized HRM example, are there any examples of NUS central which I can use with the HCI BLE connectivity firmware?

2. I would also like to use the nRF52 which will be running the connectivity firmware as an intermediary to perform a DFU on the peripheral nRF52. Is this possible?

Thanks

[Vidar Berg]

Hi,

1. Unfortunately, but the HRM example should be a good starting point for creating a NUS central. Just remember to add the 128-bit base UUID. Should look something like this if you're using the python wrapper:  

    BASE_UUID = BLEUUIDBase([0xXX, 0xXX, ..,])

    NUS_RX_CHR  = BLEUUID(0xXXXX, BASE_UUID)

    NUS_TX_CHR  = BLEUUID(0xXXXX, BASE_UUID)

2. Yes, nrfutil uses the connectivity firmware as an intermediary to perform DFU. Source code is available here: https://github.com/NordicSemiconductor/pc-nrfutil/blob/master/nordicsemi/dfu/dfu_transport_ble.py 

 

 

[TS Gowtham]

For 1, I have switched from using the python wrapper to the C library. So how do I add the 128 bit address in C? Also, by adding the address am I correct in assuming that you are referring to adding the vendor ID to the BLE stack table done by calling the  'sd_ble_uuid_vs_add'?