PSoC™ 4 Forum Discussions
Can non-Automotive PSOC4 support touch screens, and what is the maximum size or resolution that can be supported? Gen6 and Gen7 are not adopted due to their high prices。
Show Less
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-4/mtb-v3-0-CY8CKIT-145-40XX-%E4%B8%8B%E8%BD%BD%E7%A8%8B%E5%BA%8F%E5%87%BA%E7%8E%B0%E9%97%AE%E9%A2%98-%E6%80%8E%E6%A0%B7%E5%8D%87%E7%BA%A7%E5%91%A2/td-p/481044
Show LessHi Infineon.
This thread is additional question regarding the content of the link below.
Could you please let us know about “IMO AC specifications” of table 32 in PSoC 4100S Max DS?
Both SID223 and SID223B values are ±2.0%.
Case1)
SID223 temperature range is from -40deg to 85deg.
In other words, IMO accuracy at -40deg can be considered to be ±2.0%.
Case2)
SID223B temperature range is from -30deg to 105deg.
In other words, IMO accuracy at 105deg can be considered to be ±2.0%.
In other words, when considering Case1) and Case2) together, IMO accuracy can be considered to be ±2.0% in the range of -40deg to 105deg.
However, IMO accuracy of SID223A with the same temperature range(-40deg to 105deg) is ±2.5%.
Even though the temperature range is the same, there is discordance in the spec value.
What should I think about this?
Because the word "parts" is purposely used in datasheet, device parts with a temperature range of SID223A cannot be referenced to values in other specifications(for example, SID223C, SID223D etc), even if the temperature range during actual use is narrower than the product specification.
=========================================================
At 0°C to 85°C, for enhanced IMO extended industrial temperature range parts
=========================================================
Is the above understanding more correct than the previous Infineon’s answer(below link)?
(When asked about IMO accuracy of device parts with temperature range of -40deg to 105deg(SID223A), the only answer is “IMO accuracy is ±2.5%.”, regardless of the actual temperature conditions?)
Best Regards.
YuMa
Show LessHello. I have an IRQ for my serial device that looks similar this:
CY_ISR(uart_isr) {
if (h_UART_CHECK_INTR_RX_MASKED(h_UART_INTR_RX_NOT_EMPTY))
{
uint32_t data = h_UART_UartGetByte();
uint8_t byte = data & 0xFF;
// Ignore any errors.
if ((data & 0xFFFFFF00) != 0) {
return;
}
queue_data(&queue, byte);
h_UART_ClearRxInterruptSource(h_UART_INTR_RX_NOT_EMPTY);
}
}
But I get an issue where I will occasionally get an underflow error. Which is to say on the `((data & 0xFFFFFF00) != 0` will be true. It is not a framing or parity error, but the underflow error. But I don't understand how that could happen since I am specifically checking for the FIFO not being empty. Alright, so I made an alternative.
CY_ISR(uart_isr) {
if (h_UART_CHECK_INTR_RX_MASKED(h_UART_INTR_RX_NOT_EMPTY))
{
for (uint32_t count = h_UART_SpiUartGetRxBufferSize; count > 0; count--) {
uint32_t data = h_UART_UartGetByte();
uint8_t byte = data & 0xFF;
// Skip errors
if ((data & 0xFFFFFF00) != 0) {
continue;
}
queue_data(&queue, byte);
}
h_UART_ClearRxInterruptSource(h_UART_INTR_RX_NOT_EMPTY);
}
}
And this ends up being even worse somehow. Count will be a positive number, but then it will skip each byte received.
Basically what I'm asking if, how can it be possible for
h_UART_CHECK_INTR_RX_MASKED(h_UART_INTR_RX_NOT_EMPTY)
to be true, but then there be an underflow error in the byte read? I did a test and every error it received was an underflow. If I inspect the values that get received upon this underflow, some are actual data sent (aka not an underflow) and some are just junk.
This has been a thorn in my side for months but so far my solution has been "about one in fifty messages fail for some reason," but that is getting old.
Show LessFor PSOC4,we will design touch buttons.
As for the touch button, we are thinking of using transparent electrodes such asITOfilm to pass light.
We believe that it will be a one-sided pattern design from the viewpoint of cost.
If you look at the manufacturer's materials,
└ 3.8.15 CAPSENSEsystem design for single-layer printed circuit boards
Please contact us for details.
Regarding the above, could you send us any design guidelines for touch switches on single-layer boards?
Show LessHi everyone, I have a touch door handle issue on my end:
Question: Why is the base line value of the power-on detection in normal mode (non-rainy condition) and in rainy condition the same?
Due to the above problem, the original value obtained in normal mode can be recognized normally when touching (greater than the finger threshold), while the original value obtained after touching in the rainy state changes very little (much less than the finger threshold), resulting in invalid touch.
The above uses the same door handle. May I ask why the baseline values obtained are the same in both modes? Anyone who knows give some advice, thanks!
Note: If you turn on the power in a non-rainy state and then turn on the shower to get wet, the original value obtained at this time is changed, no problem.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-4/%E5%85%B3%E4%BA%8ECypress-4025-MCU%E8%A7%A6%E6%91%B8%E9%97%A8%E6%8A%8A%E6%89%8B%E4%B8%8D%E5%90%8C%E7%8E%AF%E5%A2%83%E4%B8%8B%E8%8E%B7%E5%8F%96%E5%9F%BA%E7%BA%BF%E5%80%BC%E4%B8%80%E6%A0%B7%E7%9A%84%E9%97%AE%E9%A2%98/td-p/468299
Show LessPlease help provide cy8c4014lqs-s422 and CG9107AM errata document, thanks.
hello, we develop a project with CY8C 4149 and project go very well, we switch the chip cy8c4149 to cy8c4148 and program cyc84148, it got failure. we understand the cy8c4148 has flash memory of 256kb, our firmware size is 235kb, it should allow to be programmed in cy8c4148. following image is the programmer programming result.
Could you help me out to successfully program in cy8c4148
Thank you
Show LessThe PSoC is configured as USB cdc device. On my board, there is USB hub. The up stream is connected to PC with Windows 11. I connected 1 of the down stream with usb thumb drive and from the Windows device Manager, I can see a generic USB hub as well as USB mass storage device.
Another downstream port is connected to the USB of PSoC. Unfortunately, there is no detection seen in Device Manager. I have installed the PSOC programmer as well as PSoC create 4.4. so I suppose the Windows cdc driver for Cypress PSOC 4 is installed. If I connected the MiniPROG3 debug port, then I can see the MiniProg3 decive.
Please advice and help.
Show LessI've been using 4.4 for a couple of years. At some point, my setup got corrupted, and it started complaining about being unable to find certain component versions. They are:
- cy_isr: have 1.70, need 1.71
- cy_boot: have 6.0, need 6.10
- LIN_Dynamic: have 5.0, need 6.0
- ADC_SAR_SEQ_P4: have 2.50, need 2.60
I uninstalled PSoC Creator 4.4, did a fresh download (which is identical to the one I downloaded two years ago), did a fresh install, and they're still not there. It looks like these install files don't contain the latest components. However, the Component Installer shows no components whatsoever, even if I set the device to "all" and turn off the "Show only newer" checkbox. It's behaving like you've completely removed the component library from your website, so now all that's available is a two year old installer. My company buys thousands of these PSoCs, and now I can't do my work. I'm stuck.
If you can't fix what's wrong at your end, can you at least provide me with the four components mentioned above, for individual download?