CC2640: Connection issue for a specific device.

Hi,

I have assigned a relevant expert to help with this query. In the meantime. Could you attach the sniffer file itself as a reply to this message, so that we can look into it more closely. Is the application based on any of our example code? Is the device operating in peripheral or central mode?

Best Regards,

Jan

7563.sniffer.zip

Sorrry for forget to upload sniffer log,

 there are 2 logs success and fail, in success log, you could follow the bookmark to find the success case.

thanks a lot for your support.

Hi Aichi,

Thank you for posting on the E2E forums! For clarification, the iPhone is connecting to the remote health device fine, but the CC2640 is failing to connect?

Best,

Nima 

Hi Nima,

The customer report SmartPhone is ok. The Nordic solution also has some fail rate as well.

So the customer is asking if we can improve the fail rate, no need to complete fix it by some work around, it will be great.

Hi Aichi,

Thank you for your patience! I'm still looking into this. I'll update you when I have more information.

Best,

Nima Behmanesh

Hi Aichi,

I have some questions that could help us debug this issue:

1. What are the scanning parameters for the CC2640?

2. If possible, what are the advertising parameters of the health device?

3. Do you have control over the code of the health device?

4. What is the distance between the devices?

5. Is this a launchpad or custom hardware?

Best,

Nima 

CC2640 acts as the peripheral role and the “health device monitor” acts as the central role.    CC2640 does advertise and “health device monitor” connects to CC2640.

So to Q1~Q3,

The cc2640 is peripherial mode, remote health device is central mode. CC240 advertising parameters are default value. We dont have code for the remote.

To Q4, around 30 cm. and we are using custom HW.

We use N-Company device as reference device, attached is N-company sniffer log for your reference.

BTW,  the customer find out that the T_IFS could be the root cause that the “health device monitor” cannot correctly receive the packet by comparing both CC2640(NG) and nordic(OK) OTA.

The T_IFS is around 149us and the good sample(Nordic) is 149.5us.    How can we tune the parameter to close to 150us ?  We try to tune the 32.768K clock but it doesn’t help.

For more information, please check the OTA which has bookmakers in attached..

nordic_shield.zipti_2640_shield_bookmaker.zip

Hi Aichi,

Thank you for the information. I will take a look at the log and get back to you.

Best,

Nima

Hi Aichi,

Still looking into this, but I may need some more information.

1. For clarification, is this the CC2640 or the CC2640R2?

2. Can you reproduce this issue on a launchpad?

3. Are you operating in 32-kHz crystalless mode?

Best,

Nima

We are working on CC2640F128, not 32-kHz crystalless mode. Not sure the customer have launchpad could test,...

Hi Aichi,

I will ask the hardware team about this issue and get back to you.

Best,

Nima