PSoC™ 4 Forum Discussions

I would like to know how to recognize the chips or boards that support IDAC7 and IDAC8. The one I used is not available, but there are several more that are hard to recognize.

I always used the CY8CKIT-059 but now is out of stock. What else can I use. Does the CY8CKIT-146 contain IDAC's? or the CY8CKIT-149? The release notes and manuals don't seem to explain. Only the CY8C58LP family datasheet mentions it, but it doesn't say which references belong to this family.

Thanks!

Dear all,

I use PSoC Creator 4.2 and the project that I inherited have a CapSense component released at V7.0 and developed by PSoC Creator 4.2 too but I do not know its settings.

My PSoC Creator SW alert me about the CapSense Component: "Cannot find v 7.0 of component CapSense_P4". I tried to update the component by the option "Update Components" but I can able only to "downgrade" the component to V5.0.

I have found this discussion https://community.infineon.com/t5/PSoC-Creator-Designer/Is-PSoC-v4-2-is-not-compatible-with-CapSense-v7-0/td-p/281511 but this procedure does not work: after the downgrading of CapSense component to V5.0 and the restarting the PSoC Creator SW, the highest available version of CapSense is V5.0 still.

How can I get CapSense V7.0 with PSoC Creator 4.2?

Thanks in advance.

This device must output, using IDAC, a biharmonic signal with two different central frequencies (100 and 200 Hz), the frequency of the second harmonic is equal to the frequency of the central frequencies / 3.

At first there should be a clean oscillation (sine wave), then after pressing the button a parasitic harmonic oscillation appears and lasts for 2 seconds, then the signal returns to the initial value.

Before and after:

during: 

During the test, I used a different frequency ratio of parasitic to normal oscillation for the second mode (not 3, but 2). Only to monitor the correctness of the mode change.

Based on the fact that the frequency changes (100 or 200 Hz), it is necessary to change the period of the output of the signal counts using interruptions (Period Timer).

It is also obvious that the call period will vary from the sampling frequency (the number of counts per period).

As a result, the formula for calculating the call step looks like this: 

As can be seen from the above attached figure, the period is set to 24000 (1ms). The device works according to its described functionality (changing the waveform according to the mode) but with one problem, I could not change the timer period (Timer_Samples).

I tried to find something similar, but using the solutions given there, I could not get it to work. I also want to emphasize that it not only did not change, but in general stopped outputting anything when changing the mode (for the first time, everything worked, but probably most likely using the uncalculated value of "Step" in Timer_WritePeriod() and what was entered into the timer, namely 24000 (1ms ).

I will be grateful for your help, I am also attaching an archive with the project.

P.S. I did that, but the period still doesn't seem to change:

Dear Sirs and Madams,

We are looking at configuring CapSense using PSoC4S.

I'm thinking of using a guard sensor so that it doesn't react to water. Do you have any sample code with ModusToolbox?

We have never used the guard sensor, but would like to know the best way to disable only a specific electrode when the guard sensor responds.

Unlike PSoC Creator, I think that ModusToolbox has less explanation of APIs that are suitable for CapSense.

Is it documented anywhere other than the CAT2 Peripheral Driver Library?

Regards,

Hi so I'm using CY8C4248LQI-583 MCU to my custom board. Normally, it works fine but sometimes it goes to hardfault and every function is pause. So I decide to add WDT reset so it can automaticaliy reset the system(1 hour term).  My device must to be keep on, it must not be turned off.

So my question is same as title. Does constant resetting device hurt system? Also, is there recommended reset time for the system?

Best regards, BK.

I’m adding a bootloader to my PSOC4 project in PSOC creator, Seem to have the bootloader working and able to program the bootloadable application via the UART using the bootloader host in PSCO creator.

Application runs as expected until I power down the device, it then seems to get stuck in the bootloader and doesn’t jump to the application after the set timeout (wait for command time is set to 2000 in Bootloader component).

Any ideas what might be the issue?  This is what I’m doing:

1. Program PSOC with Bootloader application
2. Unload Bootloadable Application via UART (using bootloader host in PSCO creator)
3. Application is running fine
4. Turn device off and on
5. Device remains in bootloader and doesn’t switch to application.

Hello,

I am using PSoC 4500 S to estimate the execution time of algorithms. For this purpose, I started to measure different arithmetic operations with the Systick-Timer (microbenchmarks).

However, especially floating point operations show a non-linear progression of execution time depending on the input data. For example cosf varies between 79000 us and 1051020 us (each for 1000 iterations). This missing determinsim makes it difficult to extract a tight bound from the microbecnhmarks for execution time estimation.

I attached a little overview of the min and max measurements as an excel sheet. It is also noticeable that floating point division highly depends on the  input data and the order of the operations (denominator and numerator). For validation I measured the times with code optimization (O3) and without code optimization (Debug). Furthermore, I analyzed the assembler code to gain further information - without success. 

Here a code snippet how I measure the cosf function. The entire measurement routine is validated and can be excluded as a source of error:

////////////////////////////////////////////////////////////////////////////////////////////

int num_points;
float sortedArray[2000];

for(i = 0; i < 2000; i++)
{
 sortedArray[i] = i*3.1415;
}

for (num_points = 0; num_points <= 2000; num_points++)

{
START_TIME = SysTick->VAL // Start timer

// Microbenchmark: cos

for( i = 0; i < 1000; i++)
{
result1 = cosf(sortedArray[num_points]);
}

STOP_TIME = SysTick->VAL; // Stop timer

}

////////////////////////////////////////////////////////////////////////////////////////////

On the second sheet of the excel file you find the measurements for the first 100 number of points (num_points) for cosf-microbenchmark . Here is mean the metric of interest.

How is this non-determinsim in arithmetic operations explainable?

I expected approximately equal execution times for each class of arithmetic operations (fDiv, fMul, fcos,...).

Best Regards

Jannik 

Hi guys!

I've been trying to find where to download the Hex File Parser but I can't seem to find it any where in the website. 

Can anyone provide me a link for it? 

I'm using PSoC 4.4 - CY8C4146LQI-S433

Kind regards.