Forums

1 & 2 :

If BT_spp_send() is failing frequently, it typically points to incorrect handling of RTS. The BT controller is unable to send anything back to the MSP430 leading to memory allocation failures since the application is still trying to pump data to the controller. As part of the demo application, RTS is enabled only as part of the Idle hook and is disabled elsewhere.

You can try the following:

a. Check if RTS is being handled correctly as part of the application customizations

b. Try to increase the number of allocated BT buffers as part of heap_bt.c to see if this makes any difference. However, note that this should not be required since we have validated the SDK behavior with 110 bytes of payload.

3:

SPP_ERR_INVALID_STATE is returned for the following conditions:

a. If BT_spp_start() is called without required initialization

b. If BT_spp_connect() is called without required initialization

c. If BT_spp_disconnect() is called without required initialization

d. If BT_spp_send() is called without required initialization

Please initialize SPP and then call the required SPP API functions.

UCHAR data Signifies byte information and payload could be anything, but it needs to be encoded before transmission and decoded after receives.

ex. To transmit short int data(X = 0x1234)

 in transmission,

data[0] = X / 0x100; /* MSB of variable 'X' */

data[1] = X % 0x100; /* LSB of variable 'X' */

in Receiver,

Y = (int)(data[0] * 0x100) + data[1];

So application data signals needs to be encoded and decoded based on the application data range.

Regards