I'm working on CY8C4245AXI-483 MCU. I want to write a code to toggle LED through capsense touch button. it means, initially LED is OFF. now when i touch button it should be ON. and remains ON untill i touched it 2nd time. after touching 2nd time it should be in OFF condition and remains in OFF untill i touched it 3rd time and so on.
i found code for same, somewhere on internet. is this correct or i need to change something? Please give me your valuable suggestions.
Thanks & Regards,
/*code starts from here*/
uint fingerpresent_0 = 0;
uint8 wdgt_active = 0;
In my application Psoc4 has to serve a device that could be configured in SPI or parallel mode during runtime. In SPI mode pin named D0 has to be configured as MTSR, D1 has to be configured as SS, D2 has to be configured as SCLK and D3 has to be configured as MRST. In parallel mode D0...D3 are part of the parallel IO (D0...D7) offering bidirectional IO. How to implement this switch on the fly?Show Less
I have a pin colection (number of pin= 😎 forming a 8 bit port on P0.0 to P.7. For this port is used as to interface my device in a byte way in one mode. My device also allow to run with an SPI in serial mode. Here I have to configure the port each pin differently (input/output) to be able to connect as SPI. Each pin configuration needs 3 bit so for 8 bits this will end up in a uint32_t for configuration.
If I use each pin seperatly (number of pin =1 eight times), I will lose the possibility to write all 8 bits in one cycle... I have to generate a bif if / else construct for each bit of the byte, slowing down my write cycle.
I want to have a fast byte access and a fast bit access of each pin / port and I want to assign aome pins
case 1 to the SPI module and sone single control lines
case2 to 8 port bidirectional
and diong this in runtime.
Please tell me the name and the access posibility of this 32bit register. It would be great if you will publish all the information you are hiding how the peripheral exactly look (structure and register/flags names), how the register are named so I can use the controller bejond the methods you are offering in your API.Show Less
Hello sir, I have kitprog cy8ckit-059. Kitprog is successfully detected by PSoC programmer and PSoC creator 4.2. I have attached MCU cy8c4245axi-483. I have debug code in MCU through kitprog. But after one time connect now I'm getting error like Error dbg.m0039 there was an error running port acquire. Can not acquire SWD device!
Can any one give me any suggestion?
Prem KBShow Less
I want to use the iDAC in the CYBLE-222014 and was wondering if the Vref supplies the iDAC. If so,
1) is it okay to supply Vref/iDAC with 5.5V and VDD/VDDR with 2.8V?
2) Also, is it okay to leave Vref disconnected when I am not using any analog blocks?Show Less
In KBA210620 you say that 22Ohm resistors should be placed in series with the D+ and D- USB data line but the technical reference manual specifically says that the silicon has 22Ohm resistors internal to the chip:
The PSoC USB has these features:
■ Integrated 22 USB termination resistors on D+ and D– lines, and 1.5-k pull-up resistor on the D+ line
Do I need external 22Ohm resistors as well?
KBA210620 also says that 0.1uF should be connected between VBUS and GND. Is this necessary even if VBUS is just used to sense the presence of the host, and enable the USB drivers? There is no reference to this in the trm.
I am having problems getting the USB to work reliably. It works as long as there is at least one USB hub between the PSOC and host controller on the PC, but not if the PSOC is connected directly to the host controller, either USB3 or USB2. Error message is : "USB device not recognised, the last device connected to this computer malfunctioned and windows does not recognise it" with device manager saying "Windows has stopped this device because it has reported problems. (Code 43). A request for the USB device descriptor failed."
Traces on the PCB between USB connector and PSOC are about 5mm in length, matched to about 0.5mm, and reasonably matched to 100 Ohms. PSOC is self powered.
I am using the CYBLE-214015-01 chip to transmit x & y positional data of a trackpad to an application. In this application, I determined the time stamp when the notifications were collected. From this time stamp, I determined the frequency between consecutive notifications. In plotting the frequency spectrum, I noticed that there is a large range (between 50-1000Hz) of frequency values. I am curious if there is a logical explanation as to why the frequency between consecutive notifications is so variable.
Thank you,Show Less
in my application, I have a lithium battery.
the system is powered when USB is pluging in and a specific IC charge the battery?
the IC charger has two differents set up: 1: limit the current at USB specifications (100 mA and 500mA after enumeration) and 2 :boost current more than 500mA (max 1800mA) when the USB cable is connect to a wall adapter.
I need to kown, when this two different stage happen
_ when enumeration is ok and USB port can send 500mA
_when the USB cable is connect to a wall adapter.
is there fonctions in the API of the USBFS component that can handle that.Show Less
in my application the charger IC always feed the system and "disconnect" the battery when the charging process is finish.( ofr keeping a long life battery with less cycle)
So for my understanding, when a USB cable is plug into my device, my system is ALWAY bus powered.
Do I have to set my USB device as a self powered device, and just after the configured state, change into bus powered device ? or directly as a bus powere device ?
What about the hardawe configuration ? do i need external resistance for pull up or I just use the internal pull up resistance on D- and d+
We have a product that uses the CYBLE-012011-00 with EZ-Serial 1.1.1 that is experiencing issues when sending data over CYSPP.
We are seeing an intermittent issue where it seems the module stops forwarding the data sent to it over UART while in CYSPP mode when connected to an Android Phone (OnePlus 7T Android 10). Usually, the first 2 or 3 packets sent over UART after sent over BLE but after that, there are no more packets. The module is not completely non-responsive, when the phone doesn't respond to the CYPSS packets, we enter API mode to disconnect which works and then we reenter CYSPP mode awaiting connections. Following connection attempts from the phone do not work either. I have verified that we are sending the same data over UART for the working and failing cases.
I have captured Wireshark logs a successful connection attempt and failing attempt and nothing stood out to me, an example of both is attached taken using the nRF sniffer firmware. See attached images (couldn't attach pcapng)
We do not see this issue when an nRF product connects to our Cypress module. Sometimes after the nRF product has connected, sent data and disconnected, the following phone connection works.
Is this issue related to 274727 mentioned here?
We are in the process of testing this on other Phones.Show Less