PSoC™ 4 Forum Discussions

Hi,

We have done lots of research in AC phase cut dimming application, but still getting flickering issue.

Our project file & block diagram is attached here. We want to switch to interrupt enable software, please support us if anyone have done this.

I am attempting to drive the Nokia 5110 LCD using an adapted version of the example from Element14 - https://www.element14.com/community/message/288978/l/re-psoc-4-pioneer-kit-community-project061-nokia-5110-lcd-interface… https://www.element14.com/community/message/288978/l/re-psoc-4-pioneer-kit-community-project061-nokia-5110-lcd-interface#288978

The display doesn't show anything at all. I have tried 'scoping the signals and it all looks reasonable to my eyes. Is there anyone out there who has succeeded with the same or similar hardware setup?

I need some help please, I cannot seem to find a complete answer in any of the documentation, what is the parameters and use case cmos1.8V gpio selection, does is set the gpio level to be ready for a 1.8V logic signal?  Can it be used if the process is running at 3.3 volts?

I have a peripheral that needs to have the lower voltage signaling, and I cannot implement any additional hardware.

Will CMOS 1.8V allow me to see logic 1 at 2V and 0 at .5V?

I am trying to read the status of an MCP73831 LiPo charge controller. The data sheet gives the following table for its three states (shutdown, charging, and complete):

I would like to be able to identify each condition as it occurs. My hardware has already been designed for me, and we are trying to avoid another round of revisions. A solution I came up with was to configure the controller's status pin (see table above) to an analog input on my PSoC 4 (CY8C4127LQI-BL453) configured with internal pull up and pull down resistors. This would allow for me to detect when the charge controller's status pin goes high (Vdd), low (GND), or Hi-Z (Vdd / 2).

But, I'm having trouble getting the results I expect. I found this recent thread and followed it directly (only with both pull up and pull down chosen):

https://community.cypress.com/thread/43322?q=Configuring%20pull%20up%20and%20pull%20down%20resistors%20on%20an%20analog

However, even when assigning this configuration to an unused pin, which I would expect to act as my Hi-Z (Vdd / 2) state, I am reading Vdd.

Below is my configuration:

And code:

Any obvious suggestions? Is what I'm attempting even possible?

Hi,

I'm developing an electronic board with CY8C4126AZI-S455. I would use Watchdog to generate an interrupt every 10ms witch will used as tick for a time scheduler.

In past i have used this code https://community.cypress.com/message/145533 for a BLE module but it doesn't work for this microcontroller.

Can someone help me to generate a 10ms interrupt through Watchdog Timer for CY8C4126AZI-S455 microcontroller?

Thanks in advance

Gianluca

Hello everyone,

I'm working on a project, and I want to know what is the difference between PSoC 4200M and PSoC 4200L?

Thank you in advance

Hello.

Below is description of CapSense application note(AN64846) about proximity sensor.

=============================================

Wire:

A single length of wire works well as a proximity sensor.

The proximity distance achieved with a wire loop sensor is higher compared to a PCB trace.

But using a wire sensor is not an optimal solution for mass production because of manufacturing cost and complexity.

=============================================

Why is the proximity distance of wire method higher than PCB trace method?

Does not wire method’s noise become larger than PCB trace?

Because wire method can not have both GND/Shield mesh pattern and GND loop around proximity sensor.

Best Regards.

Yutaka Matsubara

Hi,

We are using CY8C4025LQI-S412.

We are using PWM for controlling  backlight LED Intensity but for 100%  and 0% duty cycle we STOP PWM and using GPIO to control LED ON OFF state.

we are putting CPU in sleep mode in between capsense scan in active mode for 30ms using CySysPmSleep(); when LED PWM is running and if LED PWM not running we are using CySysPmDeepSleep() to put device in deepsleep mode for 30ms.

if put in sleep, capsense touch response is not good I have to put finger on button for little more time. But in case we used deepsleep capsense sensing of button working very smooth and responsive.

Can any one review code and suggest possible reason behind it.

complete workspace code is attached in post,

                    if(false == isPWMRunning)

                    {

                        /* Put the device to deep sleep after each CapSense scan */

                        EnterDeepSleepMode();    

                    }

                    else

                    {

                        /* Put the device to sleep after each CapSense scan */

                        EnterSleepMode();    

                    }

Regards,

Hardik Harpal