PSoC™ 4 Forum Discussions

I'm working with the CYBLE Pioneer Kit.  I'm trying to switch between two different connection intervals.  The purpose is to change modes, between high throughput and low power modes. 

Mode 1 is fast and responsive, at the expense of battery power.  

Mode 2 is the low power mode.  It is too slow for user-interface activity, but it's just enough to keep the connection alive.

In the final product, the device will idle in Mode 2 for low power.  When the user pushes a button, it will switch to Mode 1 for a while, and then revert to low power mode after a timeout.

To test this, I modified the code example Day019_Connection_Parameters, so there are two sets of connection parameters:

 

 

CYBLE_GAP_CONN_UPDATE_PARAM_T connectionParameters_1 = 
{
    12,                /* Minimum connection interval - 12 x 1.25 = 15 ms */
    24,                /* Maximum connection interval - 24 x 1.25 = 30 ms */
    0,                  /* Slave latency - 1 */
    500                 /* Supervision timeout - 500 x 10 = 5000 ms */
};

CYBLE_GAP_CONN_UPDATE_PARAM_T connectionParameters_2 = 
{
    160,                /* Minimum connection interval - 160 x 1.25 = 200 ms */
    160,                /* Maximum connection interval - 160 x 1.25 = 200 ms */
    29,                  /* Slave latency - 1 */
    1800                 /* Supervision timeout - 1800 x 10 = 18000 ms */
};

 

 

 

To toggle between them, I just test one of the LEDs that toggle when the user button on the Pioneer Kit is pushed:

 

 

if (Led_Green_Read() == 1)

    CyBle_L2capLeConnectionParamUpdateRequest(cyBle_connHandle.bdHandle, &connectionParameters_1);

else    

    CyBle_L2capLeConnectionParamUpdateRequest(cyBle_connHandle.bdHandle, &connectionParameters_2);

 

 

 

The behaviour is almost exactly as expected, toggling between the two modes whenever the user button is pressed.  When the device is in Mode 1 (fast mode) and the button is pressed, Mode 2 activates within a few seconds. 

However, to go back to Mode 1, there is a very long lag time (between 30-60 seconds).   This is what I would like to understand.

The peripheral (the CYBLE) is acting quickly.  However, the central (CySmart) is very slow to respond.  This is shown by the  two BLE stack events:

• CYBLE_EVT_L2CAP_CONN_PARAM_UPDATE_RSP shows that CySmart receives and accepts the request very quickly in each case.  Then (I presume) CySmart must process the request and modify the central's BLE connection settings.  When this is complete, it announces the next stack event, which (eventually) arrives at the peripheral as:
• CYBLE_EVT_GAPC_CONNECTION_UPDATE_COMPLETE.

The long delay occurs between these two stack events.  In Windows CySmart, this delay varies between 45-60 seconds.  Android CySmart is a little better, at about 30 seconds.

Questions:

1. Is this delay something peculiar to CySmart, or is this expected from all BLE devices and apps? 
2. Why does it vary across BLE platforms (Android, iOS, Windows)? 
3. Is there a programming trick that would allow the central device to process the Connection Parameter Update Request more quickly?

Thanks for your collective knowledge.

 

Show Less

 when we try lock the debug port. We found that the chip can not be changed to Kill mode from Open mode. the error is shown as attached file.

‘Transition ‘protection OPEN’ – ‘protection KILL’  is not supported’

But when we change it to protected mode from open mode. it was successfully changed. Is there other setting for kill mode?

Show Less

Designing a product using the CY8C4014LQI-421, which does not have XRES on this MCU, and using the on-board programmer on the CY8CKIT-042 to connect to SWDIOSWCLK for debugging, I found that it could not be connected, and that the device could not be discovered by CREATOR. What other device can I use to debug it?

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-4/CY8C4014LQI-421%E7%BC%96%E7%A8%8B%E8%B0%83%E8%AF%95%E8%BF%9E%E6%8E%A5%E5%A4%B1%E8%B4%A5%E7%9A%84%E5%8E%9F%E5%9B%A0-%E6%80%8E%E4%B9%88%E8%A7%A3%E5%86%B3/td-p/735447

Show Less