PSoC™ 4 Forum Discussions
Two questions regarding caps and types:
1.
The Cint caps on the ev-kit for magsense are 470PF 50V C0G 0805
(Samsung, CL21B471KBANNNC)
- are there any reasons for the 50V rating and the 'big' 0805 package?
I have no space so would prefer to go with 0402 instead. not sure if there is some important characteristic I missed out on.
Very little documentation around these caps in the datasheets.
2.
related, the CMOD for capsense is also 50V, 2200PF 5% NP0 0603
(Murata, GRM1885C1H222JA01D), I guess no problems to reduce down to 0402,
- but how important is NP0?
Show LessAre there any example-applications or existing API's to update "application area 1 vs 2" in-app?
i.e. in the bootloadable while the app is running, not by first having to reboot into the bootloader.
Show LessHi Ganesh, may be my reply of last week had some mistakes.... I see "....the discussion is blocked"
In effect I made some errors attaching my project, sorry.
Can we resume from your kind request to send you my project?
Here it is.
Pls notice that I have done many attempts to exit from DEEP SLEEP, having a look from the web, but still I'm stuck!
CPU enters DEEP SLEEP, exits for Advertising, but completely ignores my GPIO transitions!
Please help me.... this job is taking too much time and I am late....
Thanks in advance
Luigi
Show LessHello,
I am working on a project on home automation using CY8C4245AXI-483.
I have achieved basic stuff like led toggle using arduino with wemos d1 mini board and blynk app but don't know how to interface any wifi module (ESP series) using CY8C4245AXI-483.
Also, How many libraries or header files will be needed and where can I find them (since in case of arduino, there are built in examples so we need to select that only I guess).
Is there any android app available or shall I have to create own app?
Kindly help.
Thanks in advance.
Show LessHello Forum!
Our project uses CY8C4248L mcu and we are about to start FCC intentional radiator testing. The Lab we are using is asking for a tool so it will be possible to control channels, power, modes, etc. during the test. What kind of Cypress development sw / tool can we use for that? Third-party dev. tools?
Any advice/link will be greatly appreciated!
Show LessGood morning,
my name is Giulio and I am Italian, so I apologize for the English. I have a problem creating a timer to activate a led. I bought the Psoc 4100s plus Kit but I don't know how to use the timer to activate a led after some time that you have placed your finger on the capacitive button. Somebody can help me?
Thank you
Show LessI am new to Cypress Capsense. We have develop board for CY8C4025LQI-S412 with TRF7970 IC. Can you please do pcb layout review for CY8C4025LQI-S412?
Thanks
kadam
Show LessI'm in the process of implementing OTA in some of our existing BLE products. These are devices that are likely to be out in the field operational for up to 10 years, and I'm guessing early on they'll probably need one or two software upgrades to iron out a few bugs, but beyond that I would think they'll be reasonably stable.
I'm weighing up the pro's and con's of the Fixed Stack v Upgradeable Stack options. As I understand it, if I want to go with the Upgradeable Stack option I'm most likely going to have to go with a 256KB PSOC IC (we're currently using the CY8C4127LQI-BL473 devices), as most of my devices are using up > 50% of available flash. Alternatively, I could go with an external memory chip I guess.
If I stick with the Fixed Stack approach, I know I'll not be able to update my stack and add new services, or make modifications to the existing services. So, I'm limited to only making changes to the Bootloadable code.
What I'm not sure about is the implications of BLE component upgrades within PSOC Creator, and how this will impact my ability to update the firmware on devices already out in the field. For example, I'm currently coding with the V3.66 BLE component. If in 2 years time I need to update the firmware on a device OTA, I am assuming as long as I don't make any changes to the Bootloader code (and not update the BLE component for example), then I can just update the bootloadable code and copy across the new firmware to the device and everything should be OK, correct? So, in theory, as long as V3.66 BLE component remains available, I can continue supporting devices that were originally programmed with a bootloader using that version?
Are there any other issues that I might get caught out by if I go with a Fixed Stack OTA option?
I don't want to upgrade to the 256KB chips unless I really have to, as there is a cost penalty that I'd like to avoid if I can get away with it.
Cheers,
Mike
Show Less