service discovery failed with master control panel

[kirt]

hi

i have written a  service and added 3 characteristics .In master controll panel i am trying to discover services.i see these logs . Device gets disconnected while discovering services .

can anyone suggest where to look for solution 

[11:22:19.6] Received Read Response, handle: 0x000D, value (0x): 00-00

[11:22:19.6] Received Read Response, handle: 0x000E, value (0x): 9E-CA-DC-24-0E-E5-A9-E0-93-F3-A3-B5-01-00-40-6E

[11:22:19.7] Received Read Response, handle: 0x000F, value (0x): 10-10-00-9E-CA-DC-24-0E-E5-A9-E0-93-F3-A3-B5-04-00-40-6E

[11:22:19.8] Received Read Response, handle: 0x0010, value (0x): 18

[11:22:19.9] Received Read Response, handle: 0x0011, value (0x): 00-00

[11:22:19.9] Received Read Response, handle: 0x0012, value (0x): 0C-13-00-9E-CA-DC-24-0E-E5-A9-E0-93-F3-A3-B5-03-00-40-6E

[11:22:20.0] Received Read Response, handle: 0x0013, value (0x): 82

[11:22:20.0] Received Read Response, handle: 0x0014, value (0x): 0C-15-00-9E-CA-DC-24-0E-E5-A9-E0-93-F3-A3-B5-0A-00-40-6E

[11:22:30.6] No response received for ReadRequest on handle 0x0015. Disconnecting..

[11:22:30.6] Lost connection to device. Reason: BTLE_LOCAL_HOST_TERMINATED_CONNECTION

[11:22:30.6] Service discovery aborted, connection terminated.

[11:22:30.7] SERVER: Received packet <HciEvent: eventCode=0x0A> - <HciEvent: eventCode=0x0A>

[11:22:30.7] SERVER: Received Link Loss

thank you 

[tesc]

Hi,

Can you try with nRF Connect for desktop as well?

What characteristics (with what attributes, permissions, etc.) have you added?

Regards,
Terje

[kirt]

i am trying with nRF connect for windows ,I get this error

2018-04-21T06:29:53.127Z ERROR Failed to get device info: Error occured when get device info. Errorcode: CouldNotCallFunction (0x9)
Lowlevel error: NOT_AVAILABLE_BECAUSE_PROTECTION (ffffffa6)

i am using PCA10040

softdevice :s132 

sdk14.2 as reference 

i have seen this thread.

[tesc]

Hi,

That error means the current flash contents of the connectivity device is readback protected. (I.e. on the device that you use from nRF Connect in order to communicate.) Erase the flash, either by "nrfjprog -e" from the command line or by the erase button in nRFgo Studio. Then nRF Connect should be able to program the required connectivity firmware, which is needed on the connectivity device.

(See also this thread.)

Regards,
Terje

[kirt]

hi,

yes ,i have erased flash ,i can discover devices and connect .i have added these characteristics 

#define BLE_UUID_MPU_TX1_CHARACTERISTIC 0x0A
#define BLE_UUID_MPU_TX_CHARACTERISTIC 0x03 /**< The UUID of the RX Characteristic. */
#define BLE_UUID_MPU_RX_CHARACTERISTIC 0x04 /**< The UUID of the TX Characteristic. */

i am writting to 0x04 characteristics and need to get data on 0x03 characteristics.

here is logs i get 

:46:12.0760

Attribute value changed, handle: 0x10, value (0x): FF-F7-24-06-C8-40-1C-3B-FF-D4-00-07-00-00-00-FF

16:46:12.1020

Attribute value changed, handle: 0x10, value (0x): FF-F7-24-06-C8-40-1C-3B-FF-D4-00-07-00-00-00-FF

16:46:12.1050

Attribute value changed, handle: 0x10, value (0x): FF-F7-6C-06-F0-40-08-39-FF-D3-00-06-00-00-00-FF

16:46:12.1300

Attribute value changed, handle: 0x10, value (0x): FF-F7-6C-06-F0-40-08-39-FF-D3-00-06-00-00-00-FF

16:46:12.1590

Attribute value written, handle: 0x13, value (0x): AA-00-66-AA

16:46:12.1640

Attribute value changed, handle: 0x10, value (0x): FF-F7-C0-06-C4-40-28-3B-FF-D4-00-07-00-00-00-FF

16:46:12.2310

Attribute value changed, handle: 0x10, value (0x): FF-F7-C0-06-C4-40-28-3B-FF-D4-00-07-00-00-00-FF

16:46:12.2320

Attribute value changed, handle: 0x10, value (0x): FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF

i disconnect device and try to connect again .it doesnot get cconnected untill i dont reprogram the device

please help with this

[tesc]

Hi,

Does it not work even if turning the device off and on again?

What SoC and board are you using? (nRF51422, nRF52832, etc? Custom board, DK from us, third party module, etc?)

What SDK version and SoftDevice?

Can you enable logging on the nRF device, either over RTT or over UART, in order to trace what happens on the nRF device?

Do you have another DK or dongle, so that you can use the nRF Sniffer to get a log of everything that is sent over the air?

You can also do a debug session for the nRF device, in order to figure out where it hangs.

Regards,
Terje