CC2640R2F: Porting ANCS to CC2640R2，no advisting after disconnect from iphone.urgent

teddy

Prodigy 210 points

Part Number: CC2640R2F
Other Parts Discussed in Thread: BLE-STACK

Hi, Ti team menber

I follow ancs porting guider form ti wiki,Poring the ANCS to CC2640R2, it‘s running ok. can recive the

information from iphone,like MissedCall,IncomingCall,Social Apps,But stress testing,there are three issues:

1) social apps information about per 2 sencode.CC2640R2 will not recieve the information from iphone

2) Alternately turn on or off Bluetooth setting. CC2640R2 will can not bonded sucess with iphone.

3) Alternately turn on or off Bluetooth setting. CC2640R2 will not advisting.

4) Delete the bond snv message. iphone keep the ltk information. when turn on the bluetooth setting.

May occur many diffrent issue:1, CC2640R2 CRASH 2,CC2640R2 no advisting ever untill reset.3,keep connect with iphone,but no notify.

Can Stack tell app error LTK event ? the app can reject the connect request then advisting again.

ps: i test iphone 7plus,iphone 6,iphone 6s iphone 5s.ipad mini. ios version 10.2.1 and 10.3.1

my project seting as below:

#define DEFAULT_DESIRED_MIN_CONN_INTERVAL 160

#define DEFAULT_DESIRED_MAX_CONN_INTERVAL 240

#define DEFAULT_DESIRED_SLAVE_LATENCY 4//

#define DEFAULT_DESIRED_CONN_TIMEOUT 600 //1000

#define DEFAULT_ENABLE_UPDATE_REQUEST GAPROLE_LINK_PARAM_UPDATE_INITIATE_BOTH_PARAMS/

uint32_t passkey = DEFAULT_PASSCODE; // passkey "000000"
uint8_t pairMode = GAPBOND_PAIRING_MODE_WAIT_FOR_REQ;
uint8_t mitm = TRUE;
uint8_t ioCap = GAPBOND_IO_CAP_NO_INPUT_NO_OUTPUT;
uint8_t bonding = TRUE;

over 8 years ago

0 JXS over 8 years ago

TI__Guru** 105180 points

Hello teddy,

Which BLE-Stack or CC2640R2 SDK version are you using?

Can you provide a representative code sample that can reproduce this problem on a CC2640R2 LaunchPad?

Best wishes

0 teddy over 8 years ago in reply to JXS

Prodigy 210 points

Hi JXS,

I use the simplelink_cc2640r2_sdk_1_30_00_25 version. i send you the source code.

please unzip to to :

ti\simplelink_cc2640r2_sdk_1_30_00_25\examples\rtos\CC2640R2_LAUNCHXL\blestack\simple_peripheral\src.

then open the porject,add file path:$PROJ_DIR$\..\..\..\src/app/ancssrc.zip

0 sdf chris over 8 years ago in reply to teddy

Expert 1250 points

Have this issue been solved?

0 JXS over 8 years ago in reply to sdf chris

TI__Guru** 105180 points

Hello,

We received your code and are still looking into it.

Best wishes

0 teddy over 8 years ago in reply to JXS

Prodigy 210 points

it's long time ago,no guys give suggusetion,so I close the issue.

JXS please think about the ram of the cc2640r2.you will find the rootcause.

0 sdf chris over 8 years ago in reply to teddy

Expert 1250 points

teddy, can you point out which ram setting need to be changed?

0 sdf chris over 8 years ago in reply to JXS

Expert 1250 points

JXS, Do you have any progress about this problem?

0 Mark Schuster over 8 years ago in reply to teddy

TI__Prodigy 50 points

Hey Teddy,

I apologize for the delay in response. I have been working on a ANCS example for the CC2640r2, starting from the previously released example as you did. I have encountered the connectivity bugs you mentioned, but I found most were caused by poor placement of discovery event posts when converting from the use of ICall_Semaphores. As for the limited reception of the notification data, I experienced a similar problem with the state machine for handling notification attributes not reaching past the first or second state. The loss of data was quite inconsistent, but I found increasing the connection interval to 80 (100ms) gave enough time for the CC2640r2 to "catch up" which seemed to solve the problem. Could you please give more details on how you encountered these bugs while testing?

Best Regards,

-Mark

0 Mark Schuster over 8 years ago in reply to Mark Schuster

TI__Prodigy 50 points

Hello again,

As a quick update, as I continued debugging, I believe I have found the main cause of the limited reception of the notification data. As I further tested the application, I noted that the variable responsible for holding the length of the data to contained in the Data Source's notification encounters an overflow, resulting in the application to continue to wait for the rest of the notification packets indefinitely. A simple fix to include an else if to check if the variable's value has experienced an overflow (excerpt from ancs_client.c):

Please let me know if this has been of any help.

Best Regards,

-Mark

0 teddy over 8 years ago in reply to Mark Schuster

Prodigy 210 points

hello Mark，

Thank you. i think this bug caused by RAM used up .

from your code, i think you find cc2640r2 cannot recieve message correctly sometimes.

Bluetooth®︎

Bluetooth forum

CC2640R2F: Porting ANCS to CC2640R2，no advisting after disconnect from iphone.urgent