I'm trying to workaround the Anomaly #4 in the PAN for nrf8001 cx:
The workaround comprises the three following requirements:
All 16-bit Service declarations must be placed first within the database, followed by all 128-bit
Service declarations.
All 128-bit Characteristic declarations must be placed first within a Service declaration.
The number of 16-bit Service declarations divided by three must not be equal to an integer number.
I have a 128-bit sevice definition and two 16-bit services I want to implement.
The nrfgo is not really very helpful because the database layout always starts
with the two 16-bit services GAP and GATT and then nrfgo always
place the 128-bit service and after that the 16-bit declaration last thus breaking point 1 in the workaround.
And the problem with corrupted Read by Group Type responses is still there.
I hva tried to edit the xml-file manually but it made no difference in the generated layout.
So I try to assemble a service layout manually. I have figured out most of the setup layout but
have not managed get it to work properly yet. The crc calculation works fine and the setup is
accepted by the chip but it does not repond to a connect command so something is not right...
I would definitely recommend that you get the latest D version chip instead. Notice that the Cx is an old engineering sample so I do not see any reason to go through all that trouble for this chip...
I reverse engineered the format and wrote a infinitely superior setup generator in python :)
Now the discovery process works like a charm on Android also.
Some parts of the setup format are documented in the attached word doc. Its not complete and we will work to complete it soon. (not a good time commitment but that's the best we can do now).
