PSoC™ 4 Forum Discussions

Hey all, I saw a post noting that the PWM could only be used in Sleep mode (not Deep Sleep) - I'm hoping there is a workaround for that, but maybe not.

But how about the iDAC? When I go into deep sleep, it just shuts off, and in regular sleep mode (which is still pretty high consumption), it stays awake. 

Is there any way to get the iDAC to output full time even in Deep Sleep mode?

Thanks.

i found this example project on website. i show PIDAC in this attached file.

whether its working on psoc-4 for higher resolution??

I want to design matrix key pad of 48 keys. Currently I am using only One Matrix Button. Is it recommended  to use two Matrix button? If I  use two matrix button then there is any disadvantages there or not?

I am using two PWM modules both driven by the same clock.

PWM1 period = 99

PWM2 period = 9

Therefore in each cycle of PWM1, there are 10 cycles of PWM2. Everything works just perfect till here and the oscilloscope shows perfectly alligned outputs as expected.

Now, when I prescale PWM1 by 2x in the initial property window, PWM2 should complete 20 cycles in each one cycle of PWM1. It indeed does, BUT there is a phase shift of one clock period between PWM1 and PWM2. It doesn't end here. Instead of setting the prescaler to 2x in the initialization window, if I use the SetPrescaler() function in the code, the phase shift disappears!

In short, the PWM module works differently depending upon whether the Prescaler value has been set in the components initialization window  or whether it is set through programming.

Why is this happening?

Thank you...

Hey all, I was digging into the RTC component (v1.10) because I managed to freeze my app by passing in a bad unix time (I flipped little and big endian, and I basically was stuck in a while loop until I gave up.

While breakpointing in for the problem, I saw that it was caused here:

void RTC_SetUnixTime(uint64 unixTime)
{
    RTC_DATE_TIME tmpDateTime;

    RTC_unixTime = unixTime;
    RTC_UnixToDateTime(&tmpDateTime, unixTime, (uint32)RTC_24_HOURS_FORMAT);
...
}

So, since it seems to be that the unixTime is the internal accumulator, and the important public GET methods first call RTC_UnixToDateTime anyways, why are also running it in here? It seems a bit inefficient, as the UnixToDateTime is internally a ton of while loops - when this could just be a 1 line assignement. 

For example, RTC_UnixToDateTime is internally called by the following methods:

RTC_GetTime, RTC_GetDate, RTC_GetDateAndTime, RTC_SetUnixTime

​Disclaimer: I am nicely cheaping out by using only set and get UnixTime in my app 🙂

Hello,

I try to connect an PSOC 4200 ( CY8CKIT-049-42XX) as slave via I2C to an Raspberry Pi 2 as master.

With 3.3V on 4200 from Raspberry, all works fine, with 5V over USB on kit nothing happens on SDA and SCL.

SDA is stays at 3.3V, but SCL is about 5V ? No signal to see on scope or LA.

I thought I2C should work with both voltages on one line.

Where do 5V come from ? 4200 I2C lines should open drain high side or ?

Then 5V can only come over high impedance, whereas Raspberry has 1.8K to 3.3V,

which should result in about 3.3V ?

What is the high threshold of both lines in this mode ? I find different CMOS and LVTTL in datasheet.

I am trying to enter the PSoC 4 CY8CKit-049 4xxx Prototyping Kit as a part in my Eagle library. Where can I find the connector location dimensions? Especially the bootloader connector.

Thanks,

Doug