PSoC™ 4 Forum Discussions

We think about using the touch controller “CY8CMBR3102-SX1IT” as an standby button for our product. I tested the touch button with the evaluation board and it performs very good.

Now I am wondering if the touch controller has enough immunity versus environmental factors(EMC).

Do you have practical experiences with the touch used in other projects as standby button? Are there any test results with IEC/EN 61000-4-6 (10V rms)?

best regards

I have CY8CKIT-145-40XX with me, I ported  CE210290_CapSense_P4_Ganged_Sensor example to CY8CKIT-145-40XX just changed slider GPIO  and also enabled Software UART Tx for LOG data to PC using CY8CKIT-145-40XX's UART-USB capabilities. all code is same as it was in example.

If comment out EnterDeepSleepMode(); everything works fine and when uncommented  CapSense_IsWidgetActive(CapSense_GANGED_SENSOR_WDGT_ID); never returns active and touch is not working.

I am attaching code for the same.

Same logic for Look for touch and Active mode of scan we need in our product but same problem faced in that code also so I retested with this example code so anyone from cypress can help me with kit and this example code

Hello MoTa_728816

,

I am using CY8CKIT-042 PSoC® 4 Pioneer Kit for connecting 10 Cap sense buttons and 2 Cap sense sliders (each consisting of 6 sensors).

As I have shortage of pins on PSoC kit, I used P3_1 and P3_0 pins for CSD component in right slider.

From the datasheet, I came to know that these P3[0] & P3[1] pins are multi purpose pins s below,

We have used the same pins for I2C for tuning. And after tuning when we want to use the same pins as CSD pins there is some instability. and these 2 pins are not sensing as CapSense inputs. One thing noted is, after reset of pins, it's sensing. So assuming after reset the default selection is GPIO for these pins.

So, can we know after disabling the tuner/i2c component how can we configure these 2 pins for CSD function always?

We couldn't find any reference to configure these 2 pins as CSD pins as described in the data sheet. Please help.

We need piece of code/configuration to configure these P3[0] & P3[1] as CSD pins always.

Hi,

     I am using CY8CKIT-042 PSoC® 4 Pioneer Kit for connecting 10 Cap sense buttons and 2 Cap sense sliders (each consisting of 6 sensors). As i am lagging with GPIO pins on the PSoC kit i used P3_1 and P3_0 pins for taking input from two sensors of one slider.

Actually these pins(P3_1 and P3_0) are used for the I2C communication of the Cap sense tuner. But for this project we need tuner also, so for now i am enabling tuner by connecting P3_1 and P3_0 pins to SDA and SCL pins respectively for noting down the signal values (when Cap sense module is being touched) and after that i am disconnecting P3_1 and P3_0 pins from tuner and assigning back to the Slider sensors.

when i am following the above mentioned procedure i am unable to get the signal from the sensors connected to P3_1 and P3_0 pins(2 sensor pins of slider) and if i Reset the PSoC kit (with the help of the Reset button on PSoC board)then i am able to get the signal from both the pins (P3_1 and P3_0).

My queries are:

1. Can i know about the issue regarding above mentioned query?

2. I have attached the pin assignment of my project. Kindly help me if i can use any other pins instead of P3_1 and P3_0 for the sensors of slider.

3. I tried to use P12_6 and P12_7 pins on J8 header, but in the PSoC creator under Pin assignment in am not getting any option of P12_6 and P12_7 pins. Is that possible to use P12_6 and P12_7 pins. If yes, Kindly suggest me how to use it.

Please let me know asap as it a serious and urgent issue.

Thanks in advance.

In the PSoC4 SCB manual I find a particular statment

Would this mean that 2 communication modes can be enabled simultaneously on a single SCB?

I mean is it possible to enable I2C and SPI on a single SCB block? If so, how would the pins be configured for the same?

Hi

1. Design with PSoC 4100S. XRES pull-up resistor is 4.7k, capacitor to GND is 0.1uF. No pull-up or series resistor on SWDIO and SWDCLK. System power should be 5V.

2. Miniprog3 can program PSoC at 3.3V, cannot program PSoC at 5V no matter programmer powered or external powered.

    While using PSoC Creator, powered at 5V, we found IC part number could be detected, "Programming" was shown in the output window but couldn't move on and then failed.

3. Miniprog4 cannot program no matter powered at 5V or 3.3V. It failed at detecting IC.

Could you give some suggestions on how to fix the problem ? Thanks.

BR

Grace

Hi,

I am using CY8CKIT-042 PSoC® 4 Pioneer Kit. I am using it for the CapSense design with 10 buttons and 2 sliders.

I can see that, this kit has an in-built CapSense slider with 5 sensors.

Due to shortage of pins which are required for my project, I tried using the above in-built capsense pins I,e P1_1, P1_2, P1_3, P1_4 and P1_5 for my external custom CapSense.

But I couldn't get the capsense input sensed through these pins from external capsense.

Please suggest if there is any workaround.

Hi,

I need suggestion and a little clarification regarding the central -peripheral example PSoC-4-BLE/100_Projects_in_100_Days/Day012_Central_Peripheral/Central and Peripheral/Central and Peripheral.cydsn at mas…

I would like to know if there is any  flow chart also how do i put the code in the ble stack handler with respect to events without the commands through COM port.

Implementing the same as in example without the Com port commands.

Thanks,

Uma

I am using CY8C4248LQI-BL483. I have a bootable stack and application. I am bonding to the device. I'm using em_EEPROM V2.2

When I write to a secure BLE characteristic from my phone and then some time later in the main context call Em_EEPROM_1_Erase(), when the firmware next reaches CyBle_ProcessEvents(); it all hangs. I don't receive any error messages from CyBle_ProcessEvents(); nor from Em_EEPROM_1_Erase();

I can increase the amount of time after writing a secure BLE characteristic before calling Em_EEPROM_1_Erase() and the code will still hang when it reaches CyBle_ProcessEvents();

I can write and read and erase from the EEPROM as long as I do not write to a characteristic.

Is there a known bad interaction with Bonding or BLE and the Emulated EEPROM? Is there a workaround for this?

This does not appear related to KBA228069 as the device does not need to be powered down for this interaction to occur.