PSoC™ 6 Forum Discussions
Which motion sensor chip is on the E-ink display shield coming with the PSoC 6 BLE Pioneer Kit?
Is an example project available for this motion sensor yet? (-> https://community.cypress.com/thread/31304: "example project for the motion sensor will be available end of November")
Thanks!
Show LessHi, I'm rather new to the PSoC ecosystem so I am running through some of the examples listed for the PSoC® 6 BLE Pioneer Kit but am having an issue programming the CE219431 PSoC 6 MCU PDM-to-PCM Example to the Pioneer Kit.
This was downloaded from:
http://www.cypress.com/documentation/code-examples/psoc-6-mcu-code-examples
Initially I had to change the Peripheral Driver Library location which was causing build errors due to it being set to:
"C:\Program Files (x86)\Cypress\PDL\3.0.1"
I am using a 32-bit system so I do not have a Program Files (x86) location.
After this, the code ran through the build process without issue, but when I tried to load the code to the board, no device was highlighted to load to. If I select one of the devices despite this I get the following errors:
"C:\Program Files\Cypress\PDL\3.0.1\tools\win\elf\cymcuelftool.exe" -A L:\Cypress\PSoC_6\CE219431\CE219431_PDM_PCM.cydsn\CortexM4\ARM_GCC_541\Debug\CE219431_PDM_PCM.elf
code:18888 sram:2444
--------------- Build Succeeded: 02/17/2018 21:06:08 ---------------
Error: dbg.M0033: The selected debug target 'CY8C6347BZI-BLD53' is not compatible with the project's selected device 'CY8C6247BZI-D54'.
Error: dbg.M0033: The selected debug target 'CYBL11573-56LQXI' is not compatible with the project's selected device 'CY8C6247BZI-D54'.
Error: dbg.M0033: The selected debug target 'CY8C6347BZI-BLD53' is not compatible with the project's selected device 'CY8C6247BZI-D54'.
Error: dbg.M0033: The selected debug target 'CY8C6347BZI-BLD53' is not compatible with the project's selected device 'CY8C6247BZI-D54'.
Error: dbg.M0033: The selected debug target 'CYBL11573-56LQXI' is not compatible with the project's selected device 'CY8C6247BZI-D54'.
Error: dbg.M0033: The selected debug target 'CYBL11573-56LQXI' is not compatible with the project's selected device 'CY8C6247BZI-D54'.
This is what I am seeing:
Is there something that I am missing with building this examples?
Cheers, Jon
Show LessHello. Is there a list of the PSoC 6 101: tutorial video lesson links in order? The website generated suggested lists skip around and jump randomly from PSoc 101 to PSoC 6 101. At the moment I am searching fruitlessly for PSoC 6 101 Lesson 1-3, which I used last week but now am having difficulty in finding..
Show LessI wanted to learn more about using the RTC component, so decided to download two of the code examples "RTC Basics" and "CE220186 RTC CTS".
However, when I click on the "generate application" button with either example, it throws up this error:
Clock Error: (Clock must be enabled. Hardware does not support disable.).
Error location: Clk_PumpPeri
Type: Design-wide
I'm looking for advice on how to fix.
Thanks.
Show LessIs it possible I have the wrong PDL version for AN210781
Dear all,
I am facing a problem while implementing ADC in PSoC. The use of "uint32 ADC_IsEndConversion(uint32 retMode)" gives an error while inserting retMode i.e., ADC_RETRUN_STATUS or ADC_WAIT_FOR_RESULT.
The only way forward is to insert "0" as retMode but still, the ADC results are wrong. I am using the following code:
#include "project.h"
#include "math.h"
#include "stdio.h"
float Is;
int main(void)
{
Is=0;
__enable_irq(); /* Enable global interrupts. */
ADC_Start();
for(;;)
{
ADC_StartConvert();
if(ADC_IsEndConversion(0))
{
Is=ADC_CountsTo_Volts(0, ADC_GetResult32(0));
if (Is<1) //A simple check for the ADC values
Cy_GPIO_Inv(test_PORT,test_NUM);
}
ADC_StopConvert();
}
}
Show Less
Hello, members.
I would like to implement I / O logic as shown in the attached file using AMuxHw, but I don't know.
Please tell me how to make it.
※In the attached file, Input_ 0 is output when Selection Input is 0, and Input_ 1 is output when Selection Input is 1, but the reverse is okay.
Best Regards
Show LessI'm still working on my frequency counter, and noticed some strange issues with the TCPWM counter. It seems I cannot start / stop it properly via signals coming from the UDB cells (I'm using DFFs there). I also had problems gating the count signal via an AND gate.
See the attached project - it is basically self-contained, but needs a a Nokia 5110 connected (but it could be replaced by sending the results via a serial port).
This implements a reciprocal frequency counter. It uses two similar counters (with 24 bit period). They are started with the first falling edge of the input signal, and the the counter waits until the reference counter overflows for the first time. When this happens, the next falling edge of the input signal stops both counters. Then one can use the count values of the reference and the input counter to calculate the input frequency.
To start a measurement cycly, a control register is used which resets the DFFs and reloads the counters (by a '1' pulse).
Since the TCPWMs of PSoC6 do not have an enable signal (as there was in the PSoC4), I'm using the start and stop inputs. A rising flank on the enable signal (which comes from the 3-input AND) starts the counters, and the falling edge stops the counters. Also, the falling edge captures the current counter values.
What I observe is:
- even though the counters are stopped, they seem to count further - reading the current counter value, and comparing them with the captured value show differences (which should not be since the counters are stopped)
- I tried to counter that by gating the path from inclk to count of the input counter with an AND gate (using the enable signal). When doing so, the counter does not count at all.
- at certain low input frequencies, the input counter does not reload, but keeps its current value (which can be seen because the display shows the actual counter values, and input value just
- at other low input frequencies, the input counter overflows as soon as its started (which the code displays as 'frequency too high')
The last one is probably caused by the third one - but issues one to three are very puzzling. Especially number 2 - this is so simple that I think one cannot do anything wrong, yet it does not work.
I observer this behaviour regardless of the core the code is running. I have one version of that running on the M0, one with the M4 and one where the code is split. The latter one seems to be the worst, from what I have found out during debugging this seems to be because the delay between finishing one measurement and starting the next is the shortest here.
I also tried to reset the counters by using the _SetCounter() function, but this seems to completely break them.
Any idea what I'm doing wrong here?
Thanks,
hli
Show Lessi am working with capsense board and i have communicated my development board with capsense board .
i did all the connection and i have written capsense slave address into my code also set clock frequency at 100kHz.
but capsense board does not given any ACK from their side. i have also check SDA and SCL data on oscilloscope. it is right but still board not giving any ACK
please guide me if you have any suggestion.
Show LessIn the early video I see that WIFI might be build in, which is perfect fot IOT applications.
Will the PSoC 6 also have wired ethernet? For example with the use of Universal Building Blocks.
WIFI is great, but in some applications a wired connection is needed.
Show Less