PSoC™ 4 Forum Discussions

Which PSoC 4 devices support I2C, SPI and UART?

Using the Device Selector in PSoC Creator shows all PSoC 4000 devices have Communication Blocks.  The Device Selector does not clarify what those Communication Blocks support.

I was not previously aware that some PSoC devices have limited support Communication Blocks.

“SPI and UART modes are not available for the selected device” ??

Greg

How can ADC be used separately from CapSense yet concurrently in a 16-QFN PSoC?

I’m looking for a PSoC with CapSense and ADC functionality in a 16-QFN. Options appear to be PSoC 4014 or 4000T.

• The 4014 has an ADC within the Capsense block – can the ADC functionality be shared?
• The 4000T datasheet isn’t released – not sure if it will have ADC capability separate from Capsense

The following Posts reference components that have separate ADC and Capsense blocks.

A Community Post recommends using a Capsense_ADC component. That component doesn’t appear for a PSoC 4014 in PSoC Cretaor 4.4. Reference Cy8C4045AZI CapSense + ADC @ https://community.infineon.com/t5/PSoC-4/Cy8C4045AZI-CapSense-ADC/td-p/325809

A Community Post refers to an ADC tab in Capsense Configurator. Reference CY8CPROTO-063-BLE ADC & CapSense @ https://community.infineon.com/t5/PSoC-6/CY8CPROTO-063-BLE-ADC-amp-CapSense/td-p/322415

Greg

Dear Sirs and Madams,

We are currently looking into using the Bridge Control Panel for proximity sensor tuning.

I'm attaching the project "cce-mtb-psoc4-capsense-proximity.zip", which I developed CY8CKIT-145-40XX with ModusToolbox.

That project has the following:

Therefore, I connected the demo kit CY8CKIT-145-40XX to my computer and checked it, but the array of data read from the Bridge Control Panel was different from the expected value.

Each number is "+" and "p" and ACK is returned normally, but it seems that it is not data corresponding to raw count or baseline.

What steps do I need to take to see raw counts, baselines, etc. in the Bridge Control Panel?

We would like to read raw counts and baselines, diffs and status in the Bridge Control Panel.

If you prepare the original EZI2C register and try to set the following data in the cycfg_capsense.h” file, an error will occur.

#define CY_CAPSENSE_PROXIMITY0_SNS0_RAW0_VALUE (cy_capsense_tuner.sensorContext[0].raw)

#define CY_CAPSENSE_PROXIMITY0_SNS0_BSLN0_VALUE (cy_capsense_tuner.sensorContext[0].bsln)

#define CY_CAPSENSE_PROXIMITY0_SNS0_DIFF0_VALUE (cy_capsense_tuner.sensorContext[0].diff)

#define CY_CAPSENSE_PROXIMITY0_SNS0_STATUS0_VALUE

Regards,

Hello,

Based on this DFU quick start , I want to migrate my project from ModusToolbox 2.4 to 3.1, starting by the DFU. As my project currently works, I have a working bootloader and bootloadable, generated with MDT 2.4.

I use a MiniProg4 to flash my own board, embedding a MCU CY8C4147AZI-S445 and with a UART transport.

This quick start is based on an Hello World example. At the end of it, generated with MDT 3.1 , I have a bootloader which allows transfert through DFU Tool, with no error returned, but the bootloadable never launches itself.

When I use the bootloader generated with MDT 2.4, the bootloadable generated with MDT 3.0 launches itself. There is no difference between linker script in MDT 2.4 and MDT 3.0 projects (except the version at the top of the files).

 I would said that the App is not validated (Cy_DFU_ValidateApp) but with not certainty...

Any support would be appreciate, please.

Jean

Hi Community,

I want to know how can I know the difference between a Real Touch on a CapSense Peripheral and Ghost Touch. I'm facing a lot of issue on my Touch Switches which automatically gets Turned on and Off. 

I didn't put any air gap between the Surface and Touch Pad. 

Hi community ，

我的 Modustoolbox 环境出了点问题，两天前我还正常使用过，今天想要创建新工程的时候出现了很多问题，如截图

我尝试过重装MTB，结果还是一样，看起来貌似是联网的问题，你能告诉我如何解决这个问题吗？