Issue with custom service after adding DFU service

RE: Issue with custom service after adding DFU service

Tosa — Mon, 22 May 2017 16:19:26 GMT

I used the same UUID as NUS in my service, so that's the issue.

RE: Issue with custom service after adding DFU service

Hung Bui — Mon, 22 May 2017 07:34:55 GMT

Which characteristic did you use ? If you use UART service (NUS) then nRFConnect won't allow to write hexa. But if you change the UUID to an proprietary one, it should give you option. If you changed and it still doesn't work, please take a screenshot and update it to the question.

RE: Issue with custom service after adding DFU service

Tosa — Sat, 20 May 2017 02:21:10 GMT

Yes, it was cached on Android. I saw some threads on how to force it to do service discovery. I'm using nRFConnect on Android, but don't see the hex selection. Where do I select it?

RE: Issue with custom service after adding DFU service

Hung Bui — Wed, 10 May 2017 09:28:51 GMT

Hi Tosa,

Have you included Service Changed characteristic in your application ? Have you sent Service changed indication after you do DFU update ? (if your attribute table is changed after DFU).

How do you declare your characteristic ? With fixed length or variable length ?

I suspect that it was the cached attribute table caused the issue. On nRFConnect we do a refresh of the table every time we disconnect from the device. So that service discovery will be performed every time you connect.

To write raw byte in nRFConnect, please select HEX when you write.