PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
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 LessHi,
I am using CY8C4014SXI-421 [16 PIN SOIC]. The IC does not come up with an XRES pin. I have kept programing header having SWD [P3.0], CLK [P3.1], VDD, GND.
I am using KitProg that comes readily with CY8CKIT-043. I have updated the mini prog firmware. After the upgrade, it shows KirProg Version 2.21. Since the IC does not support XRES pin, I have set up RESET mode as POWER CYCLE in debug/programmer setting. Under KitProg2 voltage, the source setting is kept at 3.3V. Acquire mode is RESET.
Below wiring of KitProg to CY8C4014SXI-421
SWD [P3.0] -> SWDIO
CLK [P3.1] -> SWDCLK
VDD -> VTARGET
GND -> GND
Unconnected ->RST
With the above setup, I am unable to program the MCU. However, when a brand new MCU is soldered it gets programmed somehow. But after 1st successful flashing, the MCU never gets detected again. It shows an unknown device.
I have attached reference images for quick understanding.
Show Less
Whenever I power my chip it ramps up to 8mA before dropping towards the 4~1 mA range. Is there a way for me to lower that current consumption ? I tried reducing the transmission dB power on my antenna from 0dB to -14dB but I learned that nothing I do on the PSoC creator affects the boot-up consumption.
I am using the:https://github.com/Infineon/PSoC-4-BLE/blob/master/100_Projects_in_100_Days/Day005_Health_Thermometer/Health%20Thermometer.pdf
in the demonstration.
Is there anything I can do in this case to lower my hardware or software boot-up current consumption?
Show Less
Unfortunately, CYBLE-014008-00 is failing the EN 300 328 limits of -47 dBm at 4802 MHz by more than 2 dB. This was performed only with the standalone module (not mounted on any additional circuitry)
We performed the measurements on CYBLE-014008-00 with the oscillator set to 24 MHz instead of 48 MHz. We did not observe any improvement as the device is still failing at around 4GHz for the RX mode.
We reviewed the "RF Regulatory Certifications for CYBLE-014008-00" and we couldn't find any measurements under the CE test report for Receiver spurious emissions.
Any ideas on where we can find the ETSI EN 300 328 V2.2.2 Receiver spurious emission complete measurements for CYBLE-014008-00
Thank you
Show Less
Hello,
I've had a sudden problem while working with KITProg 3 of a CY8CKIT-149.
Suddenly Kitprog is not found while USB UART functionality continues working regularly.
I've checked on Device manager comparing with another kit that works, but i couldn't find any difference.
Can You please Help?
Thanks,
Alfonso
Show LessCapSense Slider can a Slider be implemented on a single layer, looking for application notes
Will the chip be damaged?