PSoC™ 4 Forum Discussions

Just wanted to run a scenario by you that is causing me some grief. I have a brd with a cy8c4247lqi-bl453 talking to an accelerometer (MMA8451) through I2C. The circuit is powered from a coin cell (CR2032) and the cypress chip is the master. I am using P1.4 and P1.5 for I2C. If I program the chip from the miniprog the I2C will start as soon as the chip is done programming and will run fine as verified by my scope. As soon as I try to run the device from battery with the miniprog disconnected the I2C locks up, both SCLK and Data go high. The chip is running because I am toggling one of the cypress pins and it is cycling. For some reason the I2C is getting hung up under battery supply. BTW, I also replaced the battery with my bench supply and had the same issue so I don’t think it is a supply issue because the chip is running. Any ideas?

Hi everybody,

I would like to use two CSD modules in same project. But i took error message about Resource limit end of the building operation like attached. 4100M datasheet says : 

"Each CSD block has two IDACs which can be used for general
purposes if CapSense is not being used.(both IDACs are
available in that case) or if CapSense is used without water
tolerance (one IDAC is available). The PSoC 4100M has two
CSD blocks which can be used independently; one for
CapSense and the other for IDACs.
The two CapSense blocks are referred to as CSD0 and CSD1.
Capacitance sensing inputs on Ports 0, 1, 2, 3, 4, 6, and 7 are
sensed by CSD0. Capacitance sensing inputs on Port 5 are
sensed by CSD1."
 

Do you have any IDEA ? Also, i have another dramatic information : when i try to same operation with CY8C4127AZI-M485, it can work without any error. There is a table at page 30 of datasheet. The table gives some information about IDAC and CSD capabilities. But i can not comment table and above information at same time.

Thanks in advance for your valuable comments. 

Hi all,

We have created a 5 x 5 touchpad project using PSoC 4000.We are using CY8CKIT-043 programmer interfaced(EZI2C) with our remote board(CY8C4014LQI-422) as tuner.We are successfully able to load the program but the issue is "unable to launch the tuner due to "read operation failed! check I2C bus connection(SDA:P3.0,SCL:P3.1).

Project files uploaded for your reference.

Regards

Pankaj

Hi,

I am trying to achieve very simple task. I want to get public address of the BLE device which I have set as 00A055-000124 in BLE component's setting with silicon option unchecked. But if I follow the below code I am getting some random values like FF4922190091 inside the localAddr.bdAddr

CYBLE_GAP_BD_ADDR_T localAddr;
localAddr.type = 0u;
CyBle_GetDeviceAddress(&localAddr);

I called the above code after the CyBle_Start(AppCallBack) call.

Could you please tell if I am doing something wrong here? or missing something?

Thanks in advance

Kind Regards,

Jitender

Hi, i bought one weak ago the PSOC 4M - CY8CKIT-044, and i have a trouble with the LCD and other functions like the PWM, in 5V, and the system is configure to work in 5V, software and hardware, in 3.3V i doesn't have any problem all the functions works fine, only in 5V the PSOC start to work with some problems, and one change i made to the board is change the current measurement jumper J14, to 1-2 and the PSOC (default is in 3-4)
work fine but when i use the ADC to read a voltage measurement i have a big difference with the multi meter, like 0,3V, and when i back to 3.3V and the jumper in 3-4 the read is the same that the multi meter. another test i was doing is in 5V and the jumper in other configurations and all start to lock the PSOC.

So any have the same problem? or a solution.

Thanks

PD: sorry for my english, is no my  language.
 

Hi,

Can someone please walk me through debugging and manual tuning steps?

We are using 8C4014 for trackpad application. The issue which we are facing is that if we click left 10 times and immediately click down button then it is still taken as left. With enough pause between clicking left and down is given then we dont see this issues. As are our reading capsense is reporting that finger is still on left area of track pad and hence we take it as left. I am sure that this problem is due to capsense.

So, please answer the following question:

1. How to debug this further?

2. What debugger is required? I know old PSOC will give all the data is we ground the cap sense pin, can i still use that?

3. How to manually tune the device?

Regards

Pankaj Katiyar