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.

CC2564MODNEM: CC2564 Bluetopia SPP Information & Status Indications Issue

Part Number: CC2564MODNEM

1st: Why etPort_Send_Port_Information_Indication event of the SPP_Event_Callback function can't sense the change of SPP_Event_Data->Event_Data.SPP_Send_Port_Information_Indication_Data->SPPPortInformation.Parity property. I mean it sense it, but the property has always 0 value (No parity), even the remote side opens the port with Even or Odd parity.

2nd: The SPPPortInformation.PortInformationMask can't signal when the remote side wants to change the flow control. I mean there is no way the  SPP_PORT_INFORMATION_FLOW_CONTROL_BIT to be set if a remote side wants a specific flow control. Will the SPP_Event_Data->Event_Data.SPP_Send_Port_Information_Indication_Data->SPPPortInformation.FlowControlMask property be correctly set if SPP_PORT_INFORMATION_FLOW_CONTROL_BIT working correctly.

3th: The SPPPortInformation.DataBits -> 6 & 7 are swapped. When the remote side opens port with 6 data bits the server say that someone wants to open port with 7 data bits. If remote wants 7 data bits, the server says: client wants 6 data bits?

4th: The etPort_Status_Indication event cannot be sensed if the remote side sends Break through a terminal.

Еxperimental arrangement:
The Bluetopia dual mode stack is running on discovery STM32F411VE and the radio is CC2564MODNEM evaluation board through CC256XEM-STADAPT adapter board. The application is modified SPPDemo which opens Server on port 1 and try to configure the hardware USART of the STM32F4 according to the remote side open port request settings. The Client is any PC's Bluetooth running random terminal application.

Any suggestions haw to deal with all of this?

  • Hi,

    This query has been assigned to a relevant expert. We will get back to you soon.

    Best regards,
    Vihang
  • It seems Microsoft are getting sloppier & sloppier. After purchasing a second DiscoveryF4 with adapter board & CC2564MODNEM module, and configuring as a client, there is no trace of the previously observed issues. The problem is the implementation of the BT stack in wins 7, 8 & 10. In XP there is some appropriate behavior, but again the flow control is uncontrollable (which is some kind of workaround for no flow control connection) Well it seems I should live with that & have to find some unconventional way to tell the server how to set the physical UART.