Forums - SPPLE demo testing

2 posts / 0 new
Last post
SPPLE demo testing
son
Join Date: 9 Aug 17
Posts: 14
Posted: Thu, 2018-06-14 04:35

Hi

I tried to test Bluetooth SPPLE on demo QCLI. The problem is that although I could  set up the connection between two devices (1 is QCA4020, the other is QCA4024), i could not carry out some SPPLE test commands  (such as SendDataCommand,etc.)

These are command lines I did on 2 devices:

--------------------------------------------------------------------------------------------------------

1. DEVICE 1:

BLE> InitializeBluetooth                                                        
                                                                                
                                                                                
BLE: OpenStack().                                                               
BLE: Bluetooth Stack ID: 1.                                                     
BLE: Device Chipset: 5.0.                                                       
BLE: Number ACL Buffers: 16, ACL Buffer Size: 81                                
BLE: HCI Event Registration Successful.                                         
BLE: ACL Data Callback Registration Successful.                                 
BLE: BD_ADDR: 0x00001D123456                                                    
BLE: Connection Tx Power: 4.                                                    
BLE: Initialized 6LoWPAN layer for BLE.                                         
                                                                                
BLE> spple       
BLE\SPPLE> RegisterSPPLE                                                        
                                                                                
BLE\SPPLE: Successfully registered SPPLE Service, ServiceID = 5. 
BLE\SPPLE> up 
BLE> advertisele 1                                                              
                                                                                
BLE: Advertising Channel Tx Power: 4.                                           
BLE:    The 128-bit SPPLE Service UUID CANNOT fit in the scan response data.    
BLE:    GAP_LE_Advertising_Enable success, Advertising Interval Range: 100 - 20.
 
BLE\SPPLE> ConfigureSPPLE                                                       
                                                                                
BLE\SPPLE: No SPPLE Service discovered on device.                               
                                                                                
BLE\SPPLE> senddatacommand 32                                                   
                                                                                
BLE\SPPLE: SPPLE has not been configured  
 
 

2. DEVICE 2

BLE> InitializeBluetooth                                                        
                                                                                
                                                                                
BLE: OpenStack().                                                               
BLE: Bluetooth Stack ID: 1.                                                     
BLE: Device Chipset: 5.0.                                                       
BLE: Number ACL Buffers: 16, ACL Buffer Size: 81                                
BLE: HCI Event Registration Successful.                                         
BLE: ACL Data Callback Registration Successful.                                 
BLE: BD_ADDR: 0x200200F0FD8C                                                    
BLE: Connection Tx Power: 4.                                                    
BLE: Initialized 6LoWPAN layer for BLE.  
BLE> connectle 0 00001D123456 0                                                 
                                                                                
BLE: Connection Request successful.                                             
BLE: Scan Parameters:       Window 50, Interval 100.                            
BLE: Connection Parameters: Interval Range 50 - 200, Slave Latency 0.           
BLE: Using White List:      No.                                                 
                                                                                
BLE>                                                                            
                                                                                
BLE>                                                                            
                                                                                
BLE> displayremotedevices                                                       
                                                                                
BLE>                                                                            
BLE: etLE_Connection_Complete with size 24.                                     
BLE:    Status:              0x00.                                              
BLE:    Role:                Master.                                            
BLE:    Address Type:        QAPI_BLE_LAT_PUBLIC_E.                             
BLE:    BD_ADDR:             0x00001D123456.                                    
BLE:    Connection Interval: 50.                                                
BLE:    Slave Latency:       0.                                                 
       BLE\SPPLE> senddatacommand 32                                                   
                                                                                
BLE\SPPLE: SPPLE has not been configured                                        
                                                                                
BLE\SPPLE> configurespple                                                       
                                                                                
BLE\SPPLE: No SPPLE Service discovered on device.                           

----------------------------------------------------------------------------------------------

I wonder if SPPLE demo between two devices works OK or not.

and If it works, please let me know how to set up, etc.

Thanks

Son Le

 

  • Up0
  • Down0
Re: SPPLE demo testing Best Answer
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Mon, 2018-06-18 15:51

Hi Son Le,

Please follow the below instructions between two QCA402X devices to test BLE SPPLE demo using QCLI.
Device 1:
> BLE InitializeBluetooth  
> BLE SPPLE RegisterSPPLE
> BLE AdvertiseLE 1
Device 2:
> BLE InitializeBluetooth  
> BLE ConnectLE 0 <BLE_DEV1_ADDR> 0
> BLE DiscoverServices
> BLE SPPLE ConfigureSPPLE
 
Device 1:
> BLE SPPLE SendDataCommand 32
Device 2:
> BLE SPPLE ReadDataCommand
 
Example:
Device 1:
> BLE InitializeBluetooth
BLE: BD_ADDR: 0x00001D123456
BLE: Initialized 6LoWPAN layer for BLE.
> BLE SPPLE RegisterSPPLE
BLE\SPPLE: Successfully registered SPPLE Service, ServiceID = 9.
> BLE AdvertiseLE 1
BLE: Advertising Channel Tx Power: 4.
> BLE SPPLE SendDataCommand 32
BLE\SPPLE: Send Complete, Sent 32.

Device 2:
> BLE InitializeBluetooth  
BLE: BD_ADDR: 0x9401007F0300
BLE: Initialized 6LoWPAN layer for BLE.
> BLE ConnectLE 0 00001D123456 0
BLE: Connection Request successful.
> BLE DiscoverServices
BLE: Valid SPPLE Service Found.
> BLE SPPLE ConfigureSPPLE
BLE\SPPLE: SPPLE Service found on remote device
BLE\SPPLE: Data Indication Event, Connection ID 2, Received 32 bytes.
> BLE SPPLE ReadDataCommand
BLE\SPPLE: Read: 32 bytes.
BLE\SPPLE: Read: Data: 0x7E 0x21

Regards,
Raja Pedada

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.