CC256x / MSP430F5438A unable to pair SPPDemo

Hi,

I hope you have applied the CC256xB patch http://processors.wiki.ti.com/index.php/CC256x_MSP430_Bluetopia_Basic_Demo_APPS#CC256XB_Information

By default the discoverability mode is enabled. You can just scan for the CC256X, from the remote and pair.
SPPLE Demo see below.

SPP+LE>Server

SPP+LE>Open 1
Server Opened: Server Port 1, Serial Port ID 1.
Server Port Context Stored.

SPP+LE>
atPINCodeRequest: 0x10683F59E8A1
Respond with: PINCodeResponse

SPP+LE>PINCodeResponse 0000
GAP_Authentication_Response(), Pin Code Response Success.

SPP+LE>
atLinkKeyCreation: 0x10683F59E8A1
Link Key Stored.

SPP+LE>
SPP Open Indication, ID: 0x0001, Board: 0x10683F59E8A1.

If you want to change the pairability mode to SSP, then you can do the below. Please have a look at the code for better understanding.

SPP+LE>Server

SPP+LE>SETCBPAIRABILITYMODE 2
Pairability Mode Changed to pmPairableMode_EnableSecureSimplePairing.
LE: I/O Capabilities: No Input/Output, MITM: TRUE.
BR/EDR: I/O Capabilities: Display Yes/No, MITM: TRUE.

SPP+LE>Open 1
Server Opened: Server Port 1, Serial Port ID 1.
Server Port Context Stored.

SPP+LE>SETCBDISCOVERABILITYMODE 2
Discoverability: General.

SPP+LE>
atIOCapabilityResponse: 0x10683F59E8A1
Capabilities: Display Yes/No, MITM

SPP+LE>
atIOCapabilityRequest: 0x10683F59E8A1
Auth success.

SPP+LE>
atUserConfirmationRequest: 0x10683F59E8A1
User Confirmation: 429267
Respond with: UserConfirmationResponse

SPP+LE>UserConfirmationResponse 1
User Confirmation Response success.

SPP+LE>Un-handled Auth. Event.

SPP+LE>
atLinkKeyCreation: 0x10683F59E8A1
Link Key Stored.

SPP+LE>
SPP Open Indication, ID: 0x0001, Board: 0x10683F59E8A1.

SPP+LE>

I have even tried the SPPSemo without any issue.

Hi Sundeep,

I have indeed done as described on the wiki ... I added to BTPSVEND.c  "#define __SUPPORT_CC256XB_PATCH__"

just in front of the conditional...

#ifndef __SUPPORT_CC256XB_PATCH__

#include "CC256X.h"

#else

#include "CC256XB.h"

#endif

I've also verified the existence of the CC256x.h header file, and i'ts really there in the project folder ...

I also tried setting pairabilitymode as you described, but I get following error :

SPP+LE>SETCBPAIRABILITYMODE 2
GAP_Set_Pairability_Mode Failed: -14.
Function Error.

The board is however found when scanning bluetooth devices on my smartphone ... this in contradiction to when running the SPPDemo :

In SPPDemo, this same "-14" shows when I try to set certain options :

Server>SetDiscoverabilityMode 2

GAP_Set_Discoverability_Mode Failed: -14.
Function Error.

And so when booted in SPPDemo the device isn't even discoverable on my smartphone...

One more thing, I have simulated the RF3 block with jumper/wires (http://processors.wiki.ti.com/index.php/CC256X_MSP:EXP430F5438)

but I have had to unlink pin11-14 connection, otherwise the board doesn't boot at all.

grtz,

Gert

Hi,

The error you are facing is “BTPS_ERROR_HCI_DRIVER_ERROR(-14)”. Which is defined in “CC256x MSP430 Bluetopia SDK\v1.4\MSP430_Experimentor\Bluetopia\include\BTErrors.h” file.

This seems to be like a UART interface problem. Please make sure that your uart connection is fine. I think it is related to the RF3 connector.  see http://processors.wiki.ti.com/index.php/CC256X_MSP:EXP430F5438#RF3_Connector

Hello,

like I said in my original post, I've had to simulate the RF3-jumperblock as described here : http://processors.wiki.ti.com/index.php/CC256X_MSP:EXP430F5438#RF3_Connector

BUT I have to unlink 11-14 connection, otherwise neither SPP, nor SPPLE can initialize the BTstack, and I get : 

OpenStack().
?
Stack Init Failed: -4.
Unable to open the stack.

So, it might be related to this I guess ... could it be a defunct rf3 header, I've verified with multimeter continuity on pins  ... and i noticed pin7 interconnects pin 10 & 8, when just pin 7 & 10 are interconnected.  Is there some more detailed info about RF3 header, or maybe a more detailed schematic of the RF3-jumperblock ?

grtz,

gert

'lo Miguel,

so if it's possibly a short on the board ... does it mean I can get a replacement board under warranty ?  How should I continue now ?

grtz,

gert

Gert,

Could you check if the short is in the MSP430 baord or the jumper board?

Miguel

Hi Miguel,

jumper board, you mean the RF3-Jumper block ?  I don't have one, it wasn't included in my CC256x-QFN package ... I simulated it with jumpers & wires ...

grtz,

gert

Gert,

Oh, ok. Can you check the MSP430 board without your wires? Could you double check your wiring just to make sure?

Miguel

Hi Miguel,

the MSPEXP board otherwise works fine, I started out with the UserExperience demo, and it worked fine ... I've also loaded the same demo with the wires in place, and also no problems there.

There is not a lot to check regarding the wiring, I've followed the RF3-jumper_block as per this document : http://processors.wiki.ti.com/index.php/CC256X_MSP:EXP430F5438#RF3_Connector

grtz,

gert

Gert,

The user experience demo does not use these pins, so it may run ok even if there is a short.

Could you check continuity on these MSP430 pins when there is no wiring? Also, could you check continuity on pins 7 and 9 in the RF1 connector on the CC256x board?

~Miguel

Hi Miguel,

without any jumper_wires on the RF3 header, there's no continuity on any of the pins ... also without the cc2564em board plugged in, there is no weird continuity on the rf3 header

With the board plugged in :

3-6 : all fine

5-8 : all fine

7-10 : continuity between pins 7-10(obviously), but also between pins 7-13 & 7-2 ... 

as for the RF1 header on the CC2564EM board, there is no continuity between pins 7 & 9

grtz,

gert

Gertz,

In the last part of the analysis above, when you mentioned “With the board plugged in”, I assume that the jumper_wires are not connected on the RF3 header correct? or they are?

Miguel

'lo Miguel,

there is no continuity whatsoever on any of the aforementioned pins when there are no jumper-wires on the RF3 block.

When on RF3, pin3<->pin6 & pin5<->pin8 jumper_wires are placed, there is no continuity on any of the other pins except the ones that have the jumper_wire obviously.

But when I connect pin7<->pin10, all of a sudden there's continuity between pin7<->pin10|pin13|pin2|and more w

How can I continue, I've been developping on a backend part last 2 weeks, for which the MSPEXP is the client_prototype ... I'd really like to have a working setup quite soon. Can I get a replacement/fix/devboard for the cc256x and/or mspexp ?

grtz,
Gert

Hi Gert,
Yes, please contact TI Support (http://www.ti.com/general/docs/contact.tsp) to replace your boards.
Even though this could be related to a HW issue, I would still recommend checking on the SW that no changes have been done which affect these pins.
~Miguel

Hi Miguel,

I contacted TI Support, and they said they were in communication with you about this issue, and that they are awaiting your further analysis before they can ship replacement boards ...

Can you please give some feedback about this process ?

Many thnx,
Gert

Hi Gert,

Yes, they contacted me. They should have come back to you. Could you check with them again?

Regards,

~Miguel

Hi Gert,

I think I have similar issue like you had. It was posted in the thread:
http://e2e.ti.com/support/wireless_connectivity/f/660/p/395364/1398149#1398149
Can you please let me know did you fixed the issue or not? And how you fix it. I am blocked by this problem for so long. Really hope this TI solution can work for me. Thanks a million times!!

Chen-Hsiang Feng

Hi Feng,

Your issue seems different. Your slow clock is out of spec as Sundeep mentioned.

Regards,

Miguel