Peripheral doe not terminate according to spec

[knisbet]

I'm writing test code to verify the softdevice operation according to the spec.

The goes like this:

 The central sends the feature exchange command, when the feature exchange response is received, the central sends a terminate command with a NACK response. 

The expected response is the peripheral sould terminate the connection and not send another exchange response.

The actual response is the peripheral sends another feature exchange response after receiving the terminate command.

Any ideas?

[Kenneth]

Do you have an on-air sniffer log to share? What SDK and SD is this? Any error code when calling sd_ble_gap_disconnect()?

[knisbet]

I have an Ellisys log attached. Using SDK 16.0.0 with the included SD for the Nrf52840 pca10056.

'm modifying the code on a Zephyr central to perform the test. The central sends the feature exchange command, when the feature exchange response is received, the central sends a terminate command with a NACK response.  The peripheral sends another feature exchange response after receiving the terminate command

[Kenneth]

The sniffer log is missing here. From your screenshot is may seem as the peripheral is also using Zephyr? So not sure what device (central or peripheral) is actually using nRF5 SDKv16?

[knisbet]

Sorry for the dropout, I got diverted to another project.

I mistakenly sent the wrong screenshot. Here's the correct one along with an Ellisys .btt fileFeature Exchange Termination Nordic.btt

[Susheel Nuguru]

Hi Kim,

In the screenshot you attached

The actual response is the peripheral sends another feature exchange response after receiving the terminate command.

Where is the second feature exchange response in the log after the termination request? 

[knisbet]

Hi Susheel,

That statements applies to the Zephyr screenshot that I first provided. The Nordic behavior is different but it stills seems incorrect. After receiving a Termination message the slave should not continue to send the ATT Notification correct?

[Susheel Nuguru]

No, after the termination request on the connection is received, then it does not make sense to keep sending ATT notifications. We have some regression tests just to test this scenario and must have passed , else there would have been no release. 

Can you help me reproduce the behavior on my desk. Can you share your application project or hex file that i can use with the given softdevice to reproduce this .

[knisbet]

Here's the .hex file that I used for the central. I use a 52840 board connected to a USB port. You need to use tera term or equivalent set up to connect to the virtual comm port of the nrf board. Settings are 115200 N,8,1 no parity.  When the interface comes up 3681.zephyr.hexand the central and peripheral are connected, type "test terminate featureExchange. This will run the test.

[Susheel Nuguru]

So this is related to Zephyr RTOS?

The first question Kenneth asked was requested you the SDK and Softdevice version.

You should then ask this question in Zephyr forums as we are not ready officially supporting nRF52 on Zephyr yet. 

[knisbet]

No it is not related Zephyr. I am using a Zephyr stack as a central so that I can modify the code to get the behavior I want for the test. The test target is a Nordic using the softdevice from SDK16.0.0.

[Susheel Nuguru]

Sorry for coming back late. It was a bit bad time with health.

I tried to run your zephyr central and make it connected with Nordic_HRM peripheral.

But the problem is that the test command does not do anything and you application just does not respond

Sniffing the packets shows that there is absolutely no activity but the devices stay connected.

[knisbet]

I modified the test code a little, see if this works better for you. I should have warned you that the mods to the stack to implement this test are not very robust. The test works most times but not always and the code does not return gracefully from the test so you have to power cycle between tests.8551.zephyr.hex