I am working with CY8CKIT-059 and need help discerning the differences between my custom project and one of the projects provided under "Find code example..." dialogue. 

I have a device that is acting as an I2C Master and is connected to the CY8CKIT-059 acting as an I2C slave. 

If I use the sample project: "DelSig_I2CS" I can  successfully perform a Write operation from the external device and the CY8CKIT-059 running the sample project can successfully ACK the address and receive the 2 bytes being written to it.  No issues here, I2C slave is working as expected. 

However when I generate a new project, and reuse the code from the sample I2C project and set up the I2C peripheral in the same way the sample project has it configured, the CY8CKIT-059 NACKs the address and no data is received. 

Perhaps I am not setting up the custom project in the same way, but I think I have checked everything. 

What are some probable causes as to why the CY8CKIT-059 would NACK when being addressed?

I will attach both projects: DelSig_I2CS is working just fine with no issues and "Roadrunner2_Eval which I believe is setup in the same way. 

In general, both projects have the same code:

At this point Delays are being used to have a line of code to attach breakpoints to. 

I2CS_Start();

/* Set up slave read data buffer */
I2CS_SlaveInitReadBuf((uint8 *) sample_segment, RD_BUFFER_SIZE);
I2CS_SlaveInitWriteBuf((uint8 *) sample_segment, RD_BUFFER_SIZE);

/* Enable global interrupts - needed for I2C operation */
CyGlobalIntEnable;

Enter Main Loop:

/* Check if the slave buffer has been Written */
if(I2CM_SlaveStatus() & I2CM_SSTAT_WR_CMPLT)
{
     byteCount = I2CM_SlaveGetWriteBufSize();
     I2CM_SlaveClearWriteStatus();
     I2CM_SlaveClearWriteBuf();

/* If both bytes of the read buffer have been read */
if(byteCount == I2C_BUFFER_SIZE)
{
     CyDelay(1);
     return 1;
}
else /* Wrong number of bytes read - place error handling code here */
{
     CyDelay(1);
}


/* Check if the slave buffer has been read */
if(I2CM_SlaveStatus() & I2CM_SSTAT_RD_CMPLT)
{
     byteCount = I2CM_SlaveGetReadBufSize();
     I2CM_SlaveClearReadStatus();
     I2CM_SlaveClearReadBuf();

/* If both bytes of the read buffer have been read */
if(byteCount == I2C_BUFFER_SIZE)
{
     CyDelay(1);
     return 1;
}
else /* Wrong number of bytes read - place error handling code here */
{
     CyDelay(1);
}

 

Show Less

Dear supporter

I want to translate the following KBA, Please confirm to my work.

Creating PSoC® 6 UART project without UART component- KBA233876

Regards,

Nino

Show Less

The Universal Serial Interface Channel module (USIC) is a flexible interface module covering several serial communication protocols. A USIC module contains two independent
communication channels named USICx_CH0 and USICx_CH1.

Each USIC channel can be individually configured to match the application needs. The following protocols are supported:
• UART (ASC, asynchronous serial channel)
• LIN Support by hardware (Local Interconnect Network)
• SSC/SPI (synchronous serial channel with or without slave select lines)
• IIC (Inter-IC Bus)
• IIS (infotainment audio bus) Show Less

I am looking for a simple demo for using the ETH module in a Aurix TC265D using the Infineon Low Level Drivers (iLLD).  Any help in getting started would be greatly appreciated as I have never worked with Ethernet in a microcontroller.  I am using a TriBoard TC265 V2.0

 

Show Less

Hi, All and Infineon employee

I think Aurix TC237 iLLD code has had error about Qspi communication.

I’m using the TFT LCD operating code which is extracted from the TC237 app-kit application demo project file. Of course, I’m using TC237 app-kit and The app-kit application demo project file has been uploaded on Myicp.
I changed from old iLLD v1.0.0.8.0 which is included the demo project file to latest iLLD v1.0.1.12.0.
And then, I did import the project file on the Aurix Development Studio v1.5.2 and built it successfully.
But, My TC237 app-kit TFT LCD wasn’t worked. My TFT LCD was displayed continuous thin vertical black lines like below.

So, I analyzed Qspi parts of iLLD because TFT LCD have been using Qspi function.
Finally, I found that TFT LCD was worked well when using iLLD v1.0.1.8.0 and its previous version, but TFT LCD was not worked when using iLLD v1.0.1.9.0 and its later version.
Plus, I found that if some code in Qspi iLLD is swapped between (A) and (B) showed below picture, TFT LCD is worked well when using iLLD v1.0.1.9.0 and its later version.

So,,,, I have a few questions about this problem and situation.

1. What do Code (A) and (B) do for Qspi communication?
   (The codes are line no.198~199 in IfxQspi.c which is included TC23A iLLD v1.0.1.12.0.)
2. I think the codes have had error about Qspi communication. Is it right?

I’m using the IDE program named Aurix Development Studio v1.5.2 and using iLLD v1.0.1.12.0.
(This iLLD is latest version).
Also, Complete workspace file which is not working is uploaded on this posting by attached file.
This file is complete workspace for TFT LCD operating which is extracted from the TC237 app-kit demo.

Please Answer me ASAP!!

Show Less

Hi,

I am trying to port a PSoC 6 project from creator to modustoolbox and the last thing I need is to port to do is port our BLE OTA. The OTA is almost identical to the example project CE220960. I've added DFU into modus and changed the necessary  function and variable names but I'm struggling with the linker scripts since as far as I can tell, there doesn't seem to be any examples for a BLE upgradable stack bootloader for modus. Basically what I'm looking for is any help with getting the linker files working for this port for the 3 projects (main app, launcher, stack). I put this project aside and just came back to it so apologies if I missed any information. Thank you in advance.

Show Less