PSoC™ 4 Forum Discussions
Hello,
I am using a PSoC 4 Character LCD component to display some characters on a 16x2 LCD.
My design is low power, so I am powering the whole LCD from one of the PSoC pins and shut down the power when not needed.
However, I suspect there is a current leak on a control and/or data pins from the LCD port during the time the Vdd to LCD is cut off.
What is the best way to switch all the control and data pins (on PSoC side) of the LCD port to active low or high impedance mode?
The pins are tied to the component so I guess I can't define them one more time in the main.c
Thank you,
David
Show Lesscan I use DEBUG PINS for UART (TxRx) ? Or i have to use anther pins for UART ?
Should I assign it separately in .cydwr ? Or it will be assigned automatically ?
Show LessI am using CY8C3866AXI-040 IC, can I use XRES pin of this IC as analog input ? and how ?
We are using CY5670 cypress usb dongle and connecting some ble sensor, we can want to update some GAP layer parameters like Connection Interval,Slave latency and Supervision time, We are able to do it in Cysmart UI application and we have also have integrated cysmart application using C# API's in our source code. But in C# API's we are not able set the values to the required connection interval, slave latency and supervision timeout. Please help us in setting the values according to proper format
Show LessThe characteristics of Vcompliance is described in the IDAC data sheet of PSoC 4.
It is 0.8 V (min) even under sink / source conditions or 300 uA / 600 uA condition.
Does this mean that a voltage drop of 0.8 V will always be observed on the pin voltage when set to maximum current?
600 uA sink/source, 0.8 V Vcompliance(Drop voltage), The resistance value at that time corresponds to the translation 1333 Ohm.
300 uA sink/source, 0.8 V Vcompliance(Drop voltage), The resistance value at that time corresponds to the translation 2667 Ohm.
Do the above resistance component is affecting?
Please tell us the meaning of this spec.
Show LessAre there any limitations on the processor core when using the emulated EEPROM component. Does the CPU stop while the Flash is being written to for example?
Show LessI have some Cypress Bluetooth modules, part number CYBLE-212023-10, and I'd like to upgrade from the default EZ-Serial firmware to the latest revision.
I can't see the part number listed on the EZ-Serial page: http://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform
Which image should I use?
Show Lesshi every body,
i am using CY8C4245AXI-483 device. i have taken all protections and filtering as per given in datasheet(fig. 9) and trm.
i saw when power fluctuates or smps is toggled on and off and on. all flash gets corrupt/erased?
please tell me the solution. flash program is in un protected mode.
Show LessWe are looking into using a PSoC 4 BLE device in our designs. We would like to place the PSoC 4 chip directly onto our own PCB. Of course, we'd like to avoid having to qualify our design as a new design to Bluetooth SIG - we'd rather just use the relevant QDID, like those listed here: https://community.cypress.com/docs/DOC-13885
However, the documentation that talks about when you can use another QDID or if you have to get your own is somewhat unclear. Of course, for a fully qualified module, it is clear that you can simply use the module's QDID. But when using a "silicon" solution and then providing your own circuit board/antenna, the documents are full of non-committal wording such as "may have to test" or "if the changes are minor", etc, etc. So my question is - who determines the answer to these questions? Do we self-certify that we followed the qualified design guidelines (if such guidelines even exist), and then just apply for a declaration and listing? Or do we submit the design to some authority?
For example, the document "Process for Qualifying a Bluetooth Product" (https://community.cypress.com/docs/DOC-9293) almost answers my question in paragraph 1.2, Scenario 1, where it states (bold red emphasis mine):
Scenario 1 – Using the silicon and referencing Cypress’s End Product QDID for silicon
In this case, you do one or more of the following:
- Using the BLE modules supplied with Cypress’s BLE Pioneer Kit in your product.
- Referencing the schematics and layout provided for the BLE modules supplied with Cypress’s BLE pioneer Kit.
- Making minor changes to the electrical circuit with the assessment confirming that the changes do not change the compliance status of the design, or making changes to the electrical circuit and confirming that the compliance is not impacted by running the RF/PHY tests at a BQTF.
So, who is confirming this assessment? Clearly, we have due diligence to perform our own design assessment, but surely there must be some way to demonstrate that this has been accepted by the certifying authority.
In general, can we just use the required silicon device, follow design guidance (such as http://www.cypress.com/documentation/application-notes/an91445-antenna-design-and-rf-layout-guidelines), and place the rest of our circuitry on the PCB located sufficiently far away from the RF section?
We are trying to plan our design cycle for incorporating bluetooth, and for space constraint reasons we would like to avoid purchasing an additional module, but want to avoid extensive testing time and fees.
I apologize if this has been asked and answered, but in all my searching on this website I haven't found anything definitive.
Show LessI have my PSoC 4 Pioneer Board wired to bring the PSoC Rx/Tx lines over to the the PSoC 5LP in an attempt to use the PSoC 5 LP as a USB-UART Bridge. This, in fact, works as expected with PuTTY and MS Windows.
However, plugging that cable into a machine with a recent version of Linux, does not yield the same success.
The USB core code is able to query the Cypress KitProg, but, cdc_acm fails to probe the device.
[2851710.658221] usb 3-1: New USB device found, idVendor=04b4, idProduct=f139
[2851710.658229] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=128
[2851710.658233] usb 3-1: Product: Cypress KitProg
[2851710.658235] usb 3-1: Manufacturer: Cypress Semiconductor
[2851710.658238] usb 3-1: SerialNumber: 191E022A021C2400
[2851710.660871] hid-generic 0003:04B4:F139.0014: hiddev0,hidraw3: USB HID v1.11 Device [Cypress Semiconductor Cypress KitProg] on usb-0000:00:14.0-1/input0
[2851710.661603] cdc_acm 3-1:1.2: This device cannot do calls on its own. It is not a modem.
[2851710.661614] cdc_acm: probe of 3-1:1.2 failed with error -22
I have scoured all through these forums and all through Google and have turned up no remedies.