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.

Is MSP430F5438 Experiment board connected with PAN1323ETU detectable by a mobile with android?

Other Parts Discussed in Thread: MSP430F5438

Hi there,

I've connected MSP430F5438 Exp board with a PAN1323ETU board and flashed the image of example code (SPPDemo to be specific) and I'm not able to detect the board from my mobile (running android), but by using the Inquiry command from MSP board I'm able to see device address on my Tera Term console.

I've followed the steps as mentioned in the link: http://processors.wiki.ti.com/index.php/CC256x_MSP430_Bluetopia_Basic_SPPDemo_APP

Also I've downloaded Blue Term, but as I was never connected to my board before, I'm not able to search even using my mobile phone settings.

Any help would be appreciated.

Do we have a application which needs no intervention like in SPPDemo which waits for the commands?

  • Hi,

    Sorry for the delay, some how missed this post.

    are you searching from the blue term app? Procedure to connect from blue term app is mentioned here
    http://processors.wiki.ti.com/index.php/CC256x_MSP430_TI's_Bluetooth_Stack_Basic_SPPDemo_APP#Example_connection_using_Blueterm
  • Hi There,

                    Yeah, I'm trying to connect from Blue Term, from the same link you've mentioned. Search is showing only paired devices, So I've tried to search from my mobile "settings" options. So how can I search for the msp board?, but I'm able to set name from command prompt also I'm able to search the devices with proximity with their BD_ADDR (displaying on hyperterm).

  • Hi,

    That is strange.

    For san and pairing from MSP+ CC256x, try the below

    ******************************************************************
    * Command Options: Server, Client, Help *
    ******************************************************************

    Choose Mode>Server

    ******************************************************************
    * Command Options: Inquiry, DisplayInquiryList, Pair, *
    * EndPairing, PINCodeResponse, PassKeyResponse, *
    * UserConfirmationResponse, *
    * SetDiscoverabilityMode, SetConnectabilityMode,*
    * SetPairabilityMode, *
    * ChangeSimplePairingParameters, *
    * GetLocalAddress, GetLocalName, SetLocalName, *
    * GetClassOfDevice, SetClassOfDevice, *
    * GetRemoteName, SniffMode, ExitSniffMode, *
    * Open, Close, Read, Write, *
    * GetConfigParams, SetConfigParams, *
    * GetQueueParams, SetQueueParams, *
    * Loopback, DisplayRawModeData, *
    * AutomaticReadMode, SetBaudRate, Send *
    * Help, Quit *
    ******************************************************************

    Server>Open 1
    Server Opened: 1.

    Server>SetLocalName spp
    Local Device Name: spp.

    Server>SetDiscoverabilityMode 2
    Discoverability: General.

    Server>SetConnectabilityMode 1
    Connectability Mode: Connectable.

    Server>Inquiry

    Server>
    Inquiry Entry: 0xB4B67673923F.

    Server>
    Inquiry Entry: 0x10683F59E8A1.

    Server>
    Inquiry Entry: 0xC4850885EDEF.

    Server>
    Result: 1,0xB4B67673923F.
    Result: 2,0x10683F59E8A1.
    Result: 3,0xC4850885EDEF.

    Server>Pair 2
    GAP_Initiate_Bonding(Dedicated): Success.

    Server>
    atLinkKeyRequest: 0x10683F59E8A1

    GAP_Authentication_Response success.

    Server>
    atPINCodeRequest: 0x10683F59E8A1
    Respond with: PINCodeResponse

    Server>PINCodeResponse 0000
    GAP_Authentication_Response(), Pin Code Response Success.

    Server>
    atLinkKeyCreation: 0x10683F59E8A1
    Link Key Stored.

    Server>
    atAuthenticationStatus: 0 for 0x10683F59E8A1

    Server>
    atLinkKeyRequest: 0x10683F59E8A1

    GAP_Authentication_Response success.

    Server>

    Now enter the same pin from your phone side and after the pairing is successful. Go to the Blueterm and initiate the connection. 

  • Thanks,
    Will try the sequence you've mentioned
  • Hi,

    Server>OpenStack().

    Bluetooth Stack ID: 1

    Device Chipset: 4.0

    BD_ADDR: 0x0017E9D3566E

    ******************************************************************

    * Command Options: Server, Client, Help                          *

    ******************************************************************

    Choose Mode>Server

    ******************************************************************

    * Command Options: Inquiry, DisplayInquiryList, Pair,            *

    *                  EndPairing, PINCodeResponse, PassKeyResponse, *

    *                  UserConfirmationResponse,                     *

    *                  SetDiscoverabilityMode, SetConnectabilityMode,*

    *                  SetPairabilityMode,                           *

    *                  ChangeSimplePairingParameters,                *

    *                  GetLocalAddress, GetLocalName, SetLocalName,  *

    *                  GetClassOfDevice, SetClassOfDevice,           *

    *                  GetRemoteName, SniffMode, ExitSniffMode,      *

    *                  Open, Close, Read, Write,                     *

    *                  GetConfigParams, SetConfigParams,             *

    *                  GetQueueParams, SetQueueParams,               *

    *                  Loopback, DisplayRawModeData,                 *

    *                  AutomaticReadMode, SetBaudRate, Send          *

    *                  Help, Quit                                    *

    ******************************************************************

    Server>Open 1

    Server Opened: 1.

    Server>SetLocalName spp

    Local Device Name: spp.

    Server>SetDiscoverabilityMode 2

    Discoverability: General.

    Server>SetConnectabilityMode 1

    Connectability Mode: Connectable.

    Server>Inquiry

    Server>

    Inquiry Entry: 0xE440E29FBCAC.

    Server>

    Result: 1,0xE440E29FBCAC.

    Server>Inquiry

    Server>

    Inquiry Entry: 0x34BB26E0C2A5.

    Server>

    Inquiry Entry: 0xE440E29FBCAC.

    Server>

    Result: 1,0x34BB26E0C2A5.

    Result: 2,0xE440E29FBCAC.

    Server>Pair 1

    GAP_Initiate_Bonding(Dedicated): Success.

    Server>

    atAuthenticationStatus: 4 for 0x34BB26E0C2A5

    I'm getting the following responses, which is deviating from yours @the step Pair . So, can I know what the atAuthenticationStatus: 4 means and how can I overcome it and initiate a pairing request with my mobile phone?

    Thanks

  • Hi,

    The error you are getting is page time out, which mean we have not received any response from the remote device in the the maximum time the
    local Link Manager shall wait for a baseband page response from the remote device
  • Hi Sundeep,
    I've tried with 4 different mobiles but I'm facing the same problem, one more thing is that now the SPP Demo loaded msp430f5438 exp board isn't mostly able to find the near by devices, don't know why, followed all the steps mentioned in the link http://processors.wiki.ti.com/index.php/CC256X_MSP:EXP430F5438 and also the command sequence from your previous response.

    Any jumpers have to be changed apart from what are mentioned in the above link?

    Can you guide me to reference where I can find all the steps of bringing up the msp430exp5438 + pan1323 with bluetooth solution would be grateful

    Thanks

  • Just to add apart from SPP Demo, other examples I've tried SPPLEDemo, SPPLEDemo_Lite, HIDDemo &  ANPDemo are giving me  BSC_Initialize Failed: -4. But I've followed the steps mentioned in the TI's link for RF3 connector and plugged in the PAN1323ETU module in to MSP430EXP5438, Is it any possible H/w configuration issue?

    Because I'm using the example code provided by TI as is, I don't think any S/w issue, if I'm not wrong.

    Thanks in Advance

  • Hi Sai,

    Do you mean you don't have the R3 connector?

    But you were able to turn on BT and scan for devices, and are you able to scan for the DUT, from your phone?
    Did you try scanning from the Blue term app on your phone and initiate connection from the phone?
  • Hi Sundeep,

    1. No, I don't have the RF3 connector, So I've shorted it according to the section "RF3 Connector" in the link, http://processors.wiki.ti.com/index.php/CC256X_MSP:EXP430F5438 , I think this is fine

    2. Yes, I'm able to scan for devices from MSP board, whose address I'm able to see on tera term [which we can see from the log I've pasted in my previous posts]. No, I'm not able to see DUT, from my phone. One more thing is that I'm not able to get the remote name using the GetRemoteName command, which is a success but responding me back with a dot, "."

    3. Blue term is only showing the list of connected devices, So the only left out option is to initiate the connection from phone's settings

    Thanks

  • Hi Sai,

    I think It should be fine. see http://e2e.ti.com/support/wireless_connectivity/f/660/p/382440/1363508#pi239031348=1 where they were discussing about the RF3 connector.

    2. As you are using PAN1323ETU, I hope you have not changed any thing in the demo (i.e., not even defining __SUPPORT_CC256XB_PATCH__, this flag should not be defined for the device you are using).

    3. How may paired devices do you have (make sure that they are less than 8), and in blueterm app after select the option "connected devices", you will see the list of paired devices and "Scan for devices" option to scan for devices. all I have done is "Open 1" after initializing the server and was able to scan for the DUT from the Blueterm app.
  • Hi Sundeep,

    Sundeep Mandava said:

    I think It should be fine. see http://e2e.ti.com/support/wireless_connectivity/f/660/p/382440/1363508#pi239031348=1 where they were discussing about the RF3 connector.

    1. I've gone through the link and have verified my msp and pan modules for continuity check, they are passing, no issues [in continuity perspective]

    2. I didn't change anything in the demo [ I've also checked for " __SUPPORT_CC256XB_PATCH__ " in my example project, but it is not present]

    3. I've done what you've said and tried to scan but I'm not able to scan the DUT from the Blueterm app, it is showing, no devices.

    What else can be done?

    Thanks

  • Hi,

    what is the version of Bluetopia SDK you are using?  Can you provide me the complete terminal output? As i don't see the logs highlighted below from what you have provided

    OpenStack().

    HCI_VS_InitializeAfterHCIReset

    HCI_VS_InitializeAfterHCIReset Success

    Bluetooth Stack ID: 1

    Device Chipset: 4.0

    BD_ADDR: 0x0017E7FF41A8

    ******************************************************************

    * Command Options: Server, Client, Help                          *

    ******************************************************************

    Choose Mode>

    Also provided me the Image of your hardware setup.

  • Hi Sundeep,
    1. v1.5 R2 is the version of Bluetopia I'm using
    2. I'm not getting any output as highlighted by you, the log I've uploaded in previous reply is what I'm getting, So can I know what is the version that you're using so that I can try with that

    Or do I need to do anything in the S/w to get that in the log

    Thanks
  • Hi,

    I am also using version 1.5 R2 SDK, SPPDemo on MSP430F5438 Experiment board with PAN1323ETU.
    It is strange that it is not working for you and the behavior is also different.
  • Hi Sundeep,

    Are you using the R3 Connector or did you short the wires from TI's link?
    I think that's the only point where I may be different from you, as the version of Bluetopia is same and other connections are just plugging in the PAN1323ETU board directly on to the MSP430F5438 Exp board.

    Note: I'm using TI's MSP-FET430UIF for flashing my code to the Exp board

    Thanks
  • Hi,

    I am using the jumper block came along with the PAN1323ETU.
  • Hi Sundeep,

    I didn't get any jumper block with my PAN1323ETU. Does it has anything apart from shorting the pins as shown in the TI's link?
  • Hi All,

                             Now I'm able to connect using the msp430f5438 exp board + pan1323etu to a mobile phone now. The main issue is that "the pan1326 module is  present in the PAN1323ETU REV2.3 board (which we have), this I confirmed by reading device LMP Subversion - 0x1b90". So, by including the CC256XB.h instead of CC256X.h served the purpose.

    So, anyone facing this kind of problem can try by changing the header included to CC256XB.h instead of CC256X.h, this can be accomplished by adding #define __SUPPORT_CC256XB_PATCH__ in the BTPSVEND.c before the line #ifndef __SUPPORT_CC256XB_PATCH__ which will include the CC256XB.h