CC2650MODA: Cause of "Different Transaction Collision"

rei

Part Number: CC2650MODA
Other Parts Discussed in Thread: CC2650

Hi,
My customer is developing on customer's board using CC2650MODA. They designed based on project_zero of CC2650, but when paired with PC, error occurred. Customer confirmed the connection on various PCs using "Bluetooth LE Explorer" (Analyzer). On some computers, pairing error has occurred.

From PC(Master), it was confirmed "different transaction collision". We thought PC was bad and checked with SensorTag. Pairing was successful even on PC what pairing error occurred. Even if the driver of error PC is replace, customer's board can't be paired. I think that something in project_zero is bad.

Do you have any thoughts about what the cause might be?

CC2650MODA
Customer Board
BLE-STACK-2-2-4

Regards, Rei

over 6 years ago

0 IUsedToBeARealPerson (M-W) over 6 years ago

TI__Guru 58425 points

Hi Rei,

I have assigned a subject matter expert to comment on this for you.

0 Marie H over 6 years ago

TI__Guru* 83881 points

Hi Rei,

From the sniffer log you can see that the master device is terminating the connection. There's no pairing process started.

Are they using the CC2650MODA booster pack or a custom board?

Can you point me to the example they use and list any code changes?

0 rei over 6 years ago in reply to Marie H

Mastermind 6155 points

Hi Marie-san,

Thank you for your reply.

Customers can reproduce with a combination of CC2650Launchxl and project_zero. However, when used binary that file I've compiled, they can communicate properly. (inscrutable…)

I'm currently asking them to match CCS and compiler versions, and develop from another sample project. I will keep you updated.

Regards, Rei

Bluetooth®︎

Bluetooth forum

CC2650MODA: Cause of "Different Transaction Collision"