• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 300 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

RTOS/CC2640: Reject L2CAP connection

RTOS/CC2642R: We need OOB with SC on CC2642

user4615084
Prodigy 30 points
Part Number: CC2642R
Other Parts Discussed in Thread: CC2640

Tool/software: TI-RTOS

Hi

On the CC2640 we used “GAPBondMgr_SetParameter“ to set GAPBOND_REMOTE_OOB_SC_ENABLED. On the CC2642 5.0 SDK, We found this function but GAP Bond Manager Parameters not have GAPBOND_REMOTE_OOB_SC_ENABLED.

We try the parameter GAPBOND_OOB_ENABLED, it is not OK, And also we try the parameter GAPBOND_SECURE_CONNECTION and GAPBOND_OOB_ENABLED, but it is also not OK, We need OOB with SC on CC2642.

We have consulted on this question before, please check the link before. https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/p/747850/2762759#2762759

Please help check why CC2642 not have this function?

We want to confirm why CC2642 does not support this SC OOB function? If it is certain, we can do it directly with CC2640. But now we just can't explain this to our customers or internally. After all, CC2642 is positioned on top of CC2640. Unless you give us a strong persuasion, such as: CC2642 hardware design, the original did not consider this function, so do not support, will not support this function in the future.

Thanks for your great support!    

 

Best Regards

Kevin