PSoC™ 4 Forum Discussions
I'm working with a customer where we are performing a feasibility study to use the PSoC4 (or maybe 6) as a touch controller for displays with the size around 15 inches. I understand the Multitouch automotive PSoC portfolio, such as the GEN7L could be a fit, but the available flash and RAM for user code doesn't seems enough for the application, so my questions are:
1 - Is it possible to use the capsense solution from the non-auto PSoC part for display touch sensing? (It's a PCAP techology)
Please note that due to the size of the screen, it may be required around 80-100 IO's combined as Tx/Rx to perform the scanning.
I couldn't find any demo board for this purpose, similar to this one CY3290-CYAT8168X. Note this one is, again, automotive part.
In summary, is it possible to use a non-auto PSoC to work similar as the Multitouch devices?
Marcelo - FAE at Neutronics
Some projects need to use an MCU to read the TOUCH coordinates and point status (press, lift, move) information, and then send it to the main control MCU;
Is there any CYAT817AZS61-3A002 documentation on the TOUCH register, similar to the one in the attached picture.
Use official debugging tools, then use a logic analyzer to capture IIC bus data. I don't know the specific meaning of the data;
You need to know the specific meaning before you can debug the MCU driver. If you can't find any relevant documentation, ask for help.
Hello! I am encountering an issue. I want to use the CYBLE-012011-EVAL Bluetooth module with the CY8CKIT-042 kit. However, the kit I purchased does not have a module header for the CYBLE-012011-EVAL Bluetooth module. I would like to inquire about how to use the CYBLE-012011-EVAL with my CY8CKIT-042 kit. I plan to create a project where I connect to the CYBLE-012011-EVAL via Bluetooth using my phone. I want the phone to be able to visualize the Capsense service, similar to the one in this [video] (https://www.youtube.com/watch?v=51uQKbztthg&list=PLIOkqhZiy83F2ZCIpmOIFnnOR2FdWW8JK&index=5&ab_channel=CypressSemiconductor).Show Less
I'm working on an application that needs to communicate using KitProg UART bridge using 115k2 8O1 -- 8 data bits plus odd parity. I configure the port in Windows (10) that way, but what gets sent is 8N1 -- 8 data bits without parity. I'm trying to sort out of this is a KitProg limitation or a W10 limitation. I used a different configuration where I was using a Tripp-Lite USB to serial interface and encountered the same problem. I tried a third configuration using a computer with built in serial port running Windows XP and it worked properly. So I'm trying to sort out between three possible issues: W10 versus W XP Internal serial versus USB serial Different brands of USB serial Does anyone have any experience with this? At no time is any equipment saying, "sorry I can't use those parameters". It just silently ignores the fact that it should be generating a parity bit.
Further checking indicates that other USB serial adapters can do 8O1. W10 can do 8O1. Some terminal programs have issues, such as CRT doing 8O1 with a suitable port when typing but reverting to 8N1 when sending a binary file. Most terminal programs can't send bytes > 127. HTerm is one that reliably can.
But even with HTerm, I could not make KitProg send 8O1. It always dropped the parity bit, making it 8N1. This is surprising, because I assume it is using an SCB and SCBs are capable of 8O1. So it must be a program issue. Hopefully it can be addressed.
I have been away from PSOC4 program for awhile now.
But, now I'm back, but things seem to have changed?
I want a simple program that will send out a UART welcome screen and then allow user command line input.
I have it working now, but I had to compromise, when I run the program the welcome screen does not display (Putty).
UNTIL, I hit any character on the keyboard, then TX seems to work fine.
WIERD!!!, why do I have to RX before I can TX?
This was never a problem when I used PSOC4 code before?
Could it be ARM GCC 5.4 -2016-q2-up toolchain?
Also, my POSC4 UART drives a FT230X device to support USB/comm port (Is the problem here?).
Also, I've tried other PSOC4 code examples and they have the same issue? WEIRD!!!
Anyway, I'm moving on with what I've got working but any help here would be appreciated?
Can you please let me know the storage temperature range for PSoC 4100S Max?
Naoaki MorimotoShow Less
Could you please tell me about the data retention voltage of SRAM array in PSoC 4?
I would like to know the min voltage that the SRAM can retain data while the VDD supply voltage is falling down or rising up.
MPN: PSoC 4100S Max/CY8C4148AZI-S555
Naoaki MorimotoShow Less
Dear Sirs and Madams,
Our customer is considering RS-232C using CY8C4126AXI-S445.
Since it is RS-232, communication uses the SCB's UART component, but there was an inquiry about the setup time and hold time of PSoC4S Plus.
When I confirm for the SCB component datasheet, there is no mention of setup time and hold time for the UART.
(1) Does UART have a concept of setup time and hold time?
(2) I understand that UART depends on the total error between PSoC4 Plus and connected devices.
In the case of RS-232C, does the error include not only clock error but also driver/receiver delay?