PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
A new PSoC4 series chip, the default value of SFlash storage is 0x00?
We've inherited a few thousand source code lines within a greater Project. The source code happens to be managed with PSoc Creator 4.2. The Project is a Bootloader Project for OTA update of a sensor. Below the Bootloader Project, we find a number of projects which are in my understanding completely independent.
We have to make some minor changes to 1 specific project and want to debug it using the SWD Interface. The SWD interface works completly fine because we are able to debug the Bootloader itself easily.
Just to verify the correct function of the changes we made, we want to debug the altered project stand alone - means as a normal project without OTA or bootloading
How can we modify the project to be a "Normal project" and not a Bootloadable
Best Regards
Hans
Show LessIs there a part number naming convention for the PSoC 4 ?
Does Infineon maintain a copy of uC/Probe for PSoC on Windows?
If Micrium's uC/Probe is no longer supported for PSoC, is there a preferred method to visualize the performance of the Liquid Level Capacitive Sensors?
I was NOT able to find the code to run the Micrium uC/probe on Windows for the PSoC based Liquid Level Sense example associated with CY8CKIT-02 = CE202479.
Since SiLabs acquired Micrium, they don’t appear to be supporting applications on any MCUs other than their own.
There is one version of Micrium's uC/Probe customized for XMC, that doesn't appear to work with PSoC, on Infineon's site @ https://infineoncommunity.com/uC-Probe-XMC-software-download_ID712?_ga=2.156290555.1967986941.1647260790-1920778277.1636735556
I found uC/probe target code on github. I did not find code to run uC/probe for PSoC on Windows.
References:
- Code for uc/proble on Github @ https://github.com/weston-embedded/uC-Probe-Target#:~:text=readme.md-,uC%2FProbe%20Target%20Code,just%20a%20few%20mouse%20clicks.
- Documentation for uc/probe on Atlassian @ https://micrium.atlassian.net/wiki/spaces/ucprobedoc/overview
- How can Capsense Tuner be added to CE02479, Liquid Level Sense CY8CKIT-022 code? @ https://community.infineon.com/t5/PSoC-4/How-can-Capsense-Tuner-be-added-to-CE02479-Liquid-Level-Sense/m-p/340123#M42126
Dear Receiver,
I study the CY8CKIT-037 user manual and try to know how PSOC 4 generates SVPWM waveform to control motor.
But in the manual, I can't get a very detailed information about how to generates SVPWM.
( I know this manual is for a general overview purpose )
Do you have other documentations that can explain how PSOC 4 generates SVPWM waveform ?!
Thank you so much.
Show LessHi Experts ,
Please confirm the below the two markings are same and ok to use .
Seems like date code is printed in third line . Kindly confirm this is normal printing issue.
MPN : CY8C4125AZI-S423
Need your support on this.
Show LessPSoC4100S+ 系列MCU,系统需要实现deepsleep,且在deepsleep下需要周期性唤醒和休眠;
通过WDT0可以实现休眠态下的计时,但使用WDT0后,再 调用WDT看门狗时,编译器就报错;
请问,如果WDT看门狗和WDT-timer0是否不能同时使用,换言之休眠态下的计时或看门狗功能只能二选一?
期待解答,谢谢~~
Show Less
I understand the main steps to enable the Capsense Tuner as found in the "Using the Tuner GUI" section of the CapSense_CSD data sheet.
However, I'm having difficulty getting the EZI2C component to fit in the CY8CKIT-042. If I attempt to connect the added EZI2C component signals scl and sda to the KitProg I2C by using Port P3[0] and P3[1], the project won't compile without errors. It will compile if I use P4[0] and P4[1] then jumper those signals on the kit. What other options are available to add tuner functionality to a CY8CKIT-042 without external jumpers?
Following are the modifications I made to the CE202479 code example, along with the modified code attached.
Main steps:
1) Enable Tune Helper
2) Add EZI2C component
3) Add code to Main.c
{
CyGlobalIntEnable; /* Enable global interrupts. */
CapSense_CSD_TunerStart();
/* All widgets are enabled by default except proximity widgets.
* Proximity widgets must be manually enabled by calling
* CapSense_1_EnableWidget() API, as their long scan time is
* incompatible with the fast response required of other widget
* types.
*/
while(1)
{
CapSense_CSD_TunerComm();
}
}
4) Build and Program
5) Start CapSense Tuner
Note: The EZI2C component will connect by default to P4[0] for scl and P4[1] for sda
The I2C on the KitProg (PSoC 5 on the kit) is connected to port P3[0] for scl and P3[1] for sda.
Attempting to route the EZI2C to Port 3 (P3[0] and P3[1]) causes fit problems.
As an alternative, the two ports can be connected externally using jumper wiresl
6) Add jumper wire for scl between P3[0] and P4[0] via J3-4 to J3-10
7) Add jumper wire for sda between P3[1] and P4[1] via J3-5 to J3-9
Show LessHi all,
apologies if this is too simple a post. I've a PSoC 4 project with a CYBLE-222014-01 that I'm trying to run in the Central role. It successfully scans for other BLE devices nearby but it always fails to connect to whatever it finds. In short I think I've followed the API instructions yet I think I'm missing something critical;
When I detect the CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT event I call the CyBle_GapcStopScan() function & save the bdaddr.
When I then get CYBLE_EVT_GAPC_SCAN_START_STOP I call the CyBle_GapcConnectDevice() function with the saved bdaddr & get the CYBLE_ERROR_OK return value.
After that I never get CYBLE_EVT_GATT_CONNECT_IND or similar, instead I find I'm getting CYBLE_EVT_TIMEOUT & the reason is CYBLE_GENERIC_TO.
Any ideas what I'm not getting right?
Show LessTrying to use the RTC component, seconds advance appx 1/5th speed.
I routed the clock to a pin to scope it, the signal bounces between 4 and 7 kHz, and definitely isn't square. I expected some distortion from lengthening the wires, but this is excessive.
I even loaded a blank project, with just the clock and pin, no change.
From what I can find, the in internal crystal is either enabled or not, I cant find any adjustments.
Suggestions on where to shagle voojio look?
Show Less