PSoC™ 4 Forum Discussions
Hi,
I would like to use the PSoC® 4 PIN configured as analog PWM.
It all works very well until it goes to sleep. When the board wakes up from sleep, the PWM pin doesn’t works.
I have tried to re initialized the PWM pin with PWM2_Wakeup function (defined in the board library) but without success.
Any idea?
Thanks
Is it possible to successfully run CY8C4125AXI-483 code on a CY8C4245AXI-483 chip? I don't have the set up yet to test this myself but am being asked by a board vendor due to parts shortage.
Show LessHow to make the CapSense PSoC4 wakes up from sleep when the finger touch us detected?
Hello,
I have a product need to achieve LIN UDS bootloader,mcu is CY8C4146-S433.
I found that when MCU is busy with CySysFlashWriteRow() after receiving an earse memory cmd, mcu will cost aroud 4 mins to finish earsing the whole flash memory of the bootable area;
according to ISO 14229-2 ,if mcu is busy with the previous cmd, it should response an NRC with 0x78,
but during the 4 mins described above, now MCU can't response anything.
I have found there is a "Response Pending" part in LIN_V5_0.pdf,but I don't know how to use it, or this will be helpful to my case?
Hi ~ all,
I would like to create example codes from PSoC Creator 4.4 IDE -> start page -> Find example code.
But the message always show: "Your selected code example is available in the Web Content Store. Click the install button to the left of the item to download it." Finally, no example codes can be created.
Does someone know what's the reason !? Could you please tell me how to use find example code function ?!
Thank you so much.
Show Less
I have a touch button scheme , which uses cy8c4025azi-s413 .
I did not connect the 21 pin(Vddd) when designing the hardware. At present, the project has been mass produced.
inquired about the impact of this design problem on the scheme.
1 does the design have to be changed?
2 what is the impact on the design?
3 if there is a risk, what is the risk and why?
4 PINS 21 and 39 are the same power pins. Are they directly connected internally?
Dear All,
Refer to below HW setup.
Target MCU - CY8C4014SXI-421 ( Custom Board )
KitProg from CY8CKIT-043
Interface - SWD ( used 74HC04 as an interface for power cycle programming )
We are using Proximity_Distance_040 from AN92239 - Proximity Example Project.
To enable cap sense tuner we tried the below connection
UART
TX( P3.0) of Target MCU is connected to CY8CKIT-042 TX (P1.5)
Tried connecting TX( P3.0) of Target MCUto CY8CKIT-042 RX (P1.4) as well
I2C
SCL( P1.2) of Target MCU is connected to CY8CKIT-042 SCL (P3.5)
SDA( P1.3) of Target MCU is connected to CY8CKIT-042 SCL (P3.4)
We tried Capsense_CSD Tuner 2_60
In all the options, we get READ OPERATION FAILED
kindly suggest a corrcet way to use the tuner.
A screenshot of the error message & reference project archive is attached.
Show Less
below are our findings:
- Most of the time it was found that OTA failed due to the below-mentioned error:
- Failed due to error code 0x03
- Failed due to error code 0x04
- Failed due to error code 0x0D
- command_1 for Entering DFU = {0x01, 0x38, 0x00,0x00,0xC7 ,0xFF ,0x17}
- command_2 for Application OTA = {0x01, 0x32, 0x01,0x00, 0x01, 0xCB ,0xFF ,0x17}
- command_3 for Golden copy OTA = {0x01, 0x32, 0x01,0x00, 0xCC ,0xFF ,0x17}
- Why 0x03, 0x04 and 0x0D error occur?
- What is the time interval after which the bootloader mode command can be sent to the module once the discovery process is completed?
- While sending commands in bootloader mode, we are sending two commands (command_1 and command_2 or command_3 depending upon application OTA or Golden copy OTA). What should be the time interval between two commands so that the module can accept the command comfortably without error.
- After sending both the command what should be the minimum time interval after which transfer of the OTA packet should take place.
Hello,
We are trying to develop a cap sense proximity-based sensor for human detection. We want to detect the presence of the human body at a distance of 40mm. Our hardware contains a plastic frame which is covering a lot of metal components ( all are grounded ). We are keeping a gap of 20mm in between the proximity sensor PCB attached to the plastic cover & the metallic frame which is carrying metallic components.
Now, when we reduce down the area of proximity sensor PCB our sensing range drops down to almost 1-2mm but there is not back sensing of metal objects. But this is not useful to us as we need a minimum of 40mm of sensing range.
Now, if we increase the sensor area, then there is continuous detection of back-side placed metal objects.
We cant remove the metallic objects as it's the primary hardware. We cant increase the gap between sensor & metal objects due to mechanical constraints.
Please suggest what care can be taken to get rid of this issue. Also, suggest the best configuration of cap sense proximity to achieve the goal.
I have added a video clip that shows the problem.
Show Less
Hi, my customer came across a question on mismatching between DC on the moisture barrier bag and the physical components for Cypress PSoC 4 MCU part CY8C4246AZI-L445. Details see below:
MBB showed DC 1813 while physical parts showed DC 1807
Is there a reason on why such differences occur between label and parts? or if it is related any DC policy from Cypress?
Please kindly explain. Thanks in advance.
Thanks,
Miranda
Show Less