CC2540 Disconnect with Smartphone

ikon

Hi Support,

During development... found that the device will disconnect and go back to broadcasting after several times of osal_snv_write() function call after device successful connected with smartphone.

The disconnect error code is 0x3F(LL_STATUS_ERROR_CONN_TIMING_FAILURE).

Searched for root caused and found that osal_snv_compact() function being called during osal_snv_write(), which leads to the disconnect.

Proceed with osal_snv_write()function during Bluetooth connection. The data each time transmitted is less than 20 bytes.

Do you have any suggestions or solutions for this case?

Thanks.

over 10 years ago

0 Sean2 over 10 years ago

TI__Mastermind 33460 points

Hello,

A page compaction can affect the timing of the stack, which is likely what you are experiencing. Can you please describe the sample application you started from and what modifications you did, especially those pertaining to SNV? This will help us to best resolve your issue.

0 ikon over 10 years ago in reply to Sean2

Genius 5355 points

Hi Sean,

Customer is using SimpleBLEPeripheral for development.

Modification Done: Using osal_snv_write() function to different SNV pages and define different pages by SNV ID.

Thanks.

0 ikon over 10 years ago in reply to ikon

Genius 5355 points

Hi Sean,

Any feedback?

Thanks.

0 ikon over 10 years ago in reply to ikon

Genius 5355 points

Hi Sean,

Need your help to advise the soonest.

Thanks.

0 Sean2 over 10 years ago in reply to ikon

TI__Mastermind 33460 points

Hello,

What stack version are you using and when are you performing an SNV write? Can you give me more details about the system/detailed steps to reproduce the issue?

0 ikon over 10 years ago in reply to Sean2

Genius 5355 points

Hi Sean,

The stack version is BLE-CC254x-1.4.1.43908b. Is this the latest stack from TI?

The disconnect issue happened when the device connect to smart phone and we perform osal_snv_write() function to write some data from smart phone to device several times(less than 10 times) then will disconnect.
The disconnect error code is 0x3F(LL_STATUS_ERROR_CONN_TIMING_FAILURE).

Thanks.

0 ikon over 10 years ago in reply to ikon

Genius 5355 points

Hi Sean,

Any feedback?

Thanks.

0 ikon over 9 years ago in reply to ikon

Genius 5355 points

0 Sean2 over 9 years ago in reply to ikon

TI__Mastermind 33460 points

Hello,

Thanks for following up with more information. What connection interval are you using? The reason for the error you are seeing is that the link layer scheduler is unable to schedule packets to be sent between the phone and our device because the flash write is locking up the system for too long. Using a longer connection interval will greatly reduce the occurrence of this problem. Please let me know if this is an acceptable fix.

0 ikon over 9 years ago in reply to Sean2

Genius 5355 points

Hi Sean,

Customer's connection interval is 25ms. But if they extend the connection interval, this may lead to slow response on App site.

Please advise.

Thanks.

0 Sean2 over 9 years ago in reply to ikon

TI__Mastermind 33460 points

The customer could temporarily increase the connection interval while doing the SNV operation and then move to a faster interval for regular communications. Is this this acceptable?

0 ikon over 9 years ago in reply to Sean2

Genius 5355 points

Hi Sean,
This may lower down the communicate and respond time at App site. Is there any other possible solutions?
Thanks.

0 Sean2 over 9 years ago in reply to ikon

TI__Mastermind 33460 points

Hello,

Again, you can temporarily lower the connection interval while writing to SNV, and then return to the desired connection interval.

This should show minimum latency as the interval is only increased for a short period of time. Is this acceptable?

Bluetooth®︎

Bluetooth forum

CC2540 Disconnect with Smartphone