PSoC 4 MCU

Hello, 

I have a PSOC 4 MCU with BLE 4.1

I would like to understand if there is a way to verify a write response was actually sent to a write request?

Today, I use this API function provided by cypress: 

CyBle_GattsWriteRsp(cyBle_connHandle)

The function is said to return the following options:

* \return
*  CYBLE_API_RESULT_T : Return value indicates if the function succeeded or
*  failed. Following are the possible error codes.
*
*  Errors codes                          | Description
*  ------------                          | -----------
*   CYBLE_ERROR_OK                       | On successful operation
*   CYBLE_ERROR_INVALID_PARAMETER        | 'connHandle' value does not represent any existing entry in the Stack
*   CYBLE_ERROR_INVALID_OPERATION        | This operation is not permitted
*   CYBLE_ERROR_MEMORY_ALLOCATION_FAILED | Memory allocation failed

So even if I get CYBLE_ERROR_OK returned, it doesn't necessarily mean that the response was sent yet. I understand that it just means that the request to send a response has been received successfully by the stack and it will now take care of it asynchronously. This is a problem for us because we need to reset the MCU immediately after receiving a specific write request. But we need to send a response before the reset, otherwise, it will cause a problem in the device that had sent the write request.

So we need to be able to know that the response has actually been sent. How can we know this?

Thanks,

Eyal

I have a large project which I am trying to add a new characteristic to an existing service. I am using the CY8C4248LQI-BL583 chip and I can't seem to get the BLE APIs to properly generate. I keep getting an error when referencing the characteristic's handle. Note that this project is configured for OTA updates so I have a bootloader and a bootloadable projects. 

Steps taken so far:

1. Go to the bootloader project, open the BLE 4.2 component, navigate to profiles, and add my new "custom glows" characteristic under the LED service. I set the read / write properties and the UUID of the characteristic. 

2. I delete the automatically generated custom descriptor and add a CCCD, as instructed by the documentation. 

3. Click OK, then clean / build the bootloader project. 

4. I clean / build the bootloadable project. 

5. I navigate to my bleCallback.c file in the bootloadable project and try to reference the newly added characteristic handle (as such: CYBLE_LEDS_GLOWS_CONTROL_CHAR_HANDLE) and it throws an error that I'm using an undeclared identifier. 

The strange thing is if I navigate to the CyBle_custom.h file in the bootloader project, I see my CYBLE_LEDS_CUSTOM_GLOWS_CHAR_HANDLE value defined. I just can't reference it in my bootloadable project. 

Also, my newly defined characteristic handle does not show up in the cyapicallbacks.h file of my bootloadable project. But, this file does contain all of the handles for my previously defined custom characteristics. 

Does anyone have any thoughts as to what I'm doing wrong here? 

I should note that I have recently migrated from a CY8C4148LQI-BL453 to the CY8C4248LQI-BL583 I'm using currently. This is my first time manipulating the BLE stack on this new MCU. 

Hi All,

I  tried to implement I2C communication between Cy8C4025AZI-S412( Slave ) and Pic Microcontroller(Master). The speed is 100kbps and used polling method. When button not pressed then it will sent 0xFF. The polling time is 100msec by PIC controller.

The issue is, 

1) Sometimes acknowledge not given by Slave.(need to sent data 3 to 4 times  or delay of 30ms  then it gives ack ).

I used one example code to develop I2C.

My code is below,

#include <project.h>

/* Macro Declaration */
#define BUFFER_SIZE (1u)
#define PACKET_SIZE (BUFFER_SIZE)

/* The I2C Slave read and write buffers */
uint8 i2cReadBuffer [BUFFER_SIZE] = {0};
uint8 i2cWriteBuffer[BUFFER_SIZE]= {0};

uint8_t flag1=0;

uint8_t flag3=0;

void Received_Data_From_Master1();

int main()
{

     /* Eneble Global Interrupt */

      CyGlobalIntEnable;

      CapSense_Start();
      CapSense_ScanAllWidgets();

     /* Start the I2C Slave And I2C Address Setting*/
     I2CS_I2CSlaveInitReadBuf(i2cReadBuffer, BUFFER_SIZE);
     I2CS_I2CSlaveInitWriteBuf(i2cWriteBuffer, BUFFER_SIZE);

       I2CS_I2CSlaveSetAddress(0x08);
       I2CS_Start();

for (;;)
{
    CyDelay(2);
   /* With Respect to Master i.e Checked Whether the Master Write Complted Or Not */
    if (0u != (I2CS_I2CSlaveStatus() & I2CS_I2C_SSTAT_WR_CMPLT))
{
          /* Calling Function to Collect The Data From Master */
          Received_Data_From_Master1();
          /* Enable this above function when we used the data On Switch Function */

            /* Clear the slave write buffer and status */
            I2CS_I2CSlaveClearWriteBuf();
            (void) I2CS_I2CSlaveClearWriteStatus();
}

if(CapSense_NOT_BUSY == CapSense_IsBusy())
{
      /* API For Capsense Update Scanning And Process */
      CapSense_ProcessAllWidgets();           /* Process all widgets */
      CapSense_RunTuner();                            /* To sync with Tuner application */
      /* Checked whether Left Button Active or Not*/
if((flag3==0)&&(CapSense_IsWidgetActive(CapSense_BUTTON2_WDGT_ID)) )
{
      flag3=1;              /* Reseting Left Button Flag */
      i2cReadBuffer[0] = 0x01;
      while (I2CS_I2C_SSTAT_RD_CMPLT!=(I2CS_I2CSlaveStatus()));
      /* Clear the slave read buffer and status */
       I2CS_I2CSlaveClearReadBuf();
      (void) I2CS_I2CSlaveClearReadStatus();
      i2cReadBuffer[0] = 0xFF;
}
else if((flag3==1) && (!(CapSense_IsWidgetActive(CapSense_BUTTON2_WDGT_ID))))
{
       flag3=0; /* Setting Left Button Flag */
       i2cReadBuffer[0] = 0xFF;
}


/* Checking Right Button active or not */
if((flag1==0)&&(CapSense_IsWidgetActive(CapSense_BUTTON0_WDGT_ID)))
{
        flag1=1; /* Reseting the flag*/
         i2cReadBuffer[0] = 0x06;
         while (I2CS_I2C_SSTAT_RD_CMPLT!=(I2CS_I2CSlaveStatus()));
        /* Clear the slave read buffer and status */
        I2CS_I2CSlaveClearReadBuf();
        ( void) I2CS_I2CSlaveClearReadStatus();
         i2cReadBuffer[0] = 0xFF;
}
else if((flag1==1)&& (!(CapSense_IsWidgetActive(CapSense_BUTTON0_WDGT_ID))))
{

          flag1=0; 

}
}

}

}

void Received_Data_From_Master1()
{
switch(i2cWriteBuffer[0])
{
  /* After Receiving 00 touch will be Ready to Work */
  case 0x00:
         i2cReadBuffer[0] = 0x19; /*According to New Document Wants to transmit new data acknowledgement */
         POWER_LED_Write(0);
          break;

}

}

Any Help will be highly appreciated .

Thanks & Regards,

AsDh

ello there,

I created a program in Psoc 4 BLE using uC / OS III, however when I add a task for the button and send it to Psoc and put it to work, the other tasks start normally, but do not do their functions normally, that is , they start and remain the same as they started, without doing their job. Could someone please check my program for me. The problem is in the App_Botao_Pedestre_1_Task task.

To access the project, open Psoc Create and then click on "file-> Open-> Project / workspace" and open the folder "Micrium\Examples\Cypress\CY8CKIT-044\OS3\PSoC\OS3.cywrk"

I like to use this device running an USB - HID profile. According datasheet Pin 13.1 (D-)  13.0(D+) and P13.2 VBUS (5V from USB?). Datasheet of USB tells me that I also have to assign VBUS to P0.0 ..(for 4200L devices). For me this is all not clear how to wire. It would be very great if your datasheet hold a schematics of all possible scenario.. how to connect. Pease assist !!

I like to run it as self powered, Not Bus powered. Please tell me the exact setting in USB configuration, and how to wire... what to connect where and how, Thanks.

Hello

There is the following description in the debug select column of PSoC Creator.

”Controls whether or not to reserve pins for debugging. If any JTAG or SWD option is selected, the debugging features of the chip will be externally accessible. If GPIO is selected the pins are available for general purpose use. When set to GPIO the device can For more information see the device datasheet or Technical Reference Manual (TRM). Still be acquired with SWD / JTAG, and reprogrammed, but not for debugging.”

Where can I specifically refer to TRM for more information on this?

Best Regards

Hayato 

We use the Cypress CY8C4248LQI-BL553 CPU and an Ethernet Controller (ENC28J60).
We need to implement a TCP Stack for this system. Do you have some know-how concerning such a case ?
and can we get some support ?

Hello there,

I implemented code in psoc 4 with uC / OS, where there are tasks and interruptions, but I had a problem with the interruption. The interrupt I created is a button. The interrupt works, but when the interruption comes to an end, the tasks return to where they left off and I would like them to return from the beginning, is there any function of uC / OS III that does this?

To access the project, open Psoc Create and then click on "file-> Open-> Project / workspace" and open the folder "Micrium\Examples\Cypress\CY8CKIT-044\OS3\PSoC\OS3.cywrk"