PSoC™ 4 Forum Discussions
We have a design where there are beads feeding each of the supplies from a signal switching regulator (buck). For a particular customer we need to power several bright LED's from the VDDD bead because there is no connector on the board that has the direct regulator output. This will cause additional drop across the VDDD bead when the LED's turn on, so VDDD will be at a slightly lower voltage than VDDA and VDDR. What is the maximum voltage differential between the three supplies? We have a nominal 3.3 volt supply so is the differential basically the drop to the dropout level of the internal on-chip regulators?
Blair
Show LessWe are using the Cypress project UART_to_BLE_peripheral as a UART Bridge for the EZ-BLE PRoC module CYBLE-022001-00. I have added some code to read the BLE name from a host processor and use that name to advertise, also I write the FW version to the host processor and control an IO pin. This all works fine, but we want the host processor to have more control of the module. So during my search I found EZ-Serial. This has the API we need to do what I was doing manually and the control over settings that we need. I thought that maybe the UART_to_BLE_peripheral FW was built on top of the EZ-Serial, but I didn’t see the API commands in the UART_to_BLE_peripheral code.
Can you please clear this up for me? What is UART_to_BLE_peripheral built on? Does UART_to_BLE_peripheral give me the ability to control and change settings on the module? Is there a UART Bridge that is built on EZ-Serial?
Another question, is there a serial port bootloader that will work with a 128k part?
Thanks for your help!
Show LessHi.
I am using android phone & Psoc 4 Ble Pinoeer kit
In cysmart tm mobile app ,It is discovering Ble device
But when I clicked on it to connect it is showing NO service found.(service discovery status failed with error code :129)
Even in the Cysmart 1.2 windows pc app
It is connecting with BLE device , and discovering all the attributes
But when I try to read or write attributes it is showing, Read characteristic value timed out.
Please help me to find out the problem.
Show LessWhen a pin is set to Open-Drain, Drives Low, does this mean that when you use PIN_Write(1), the pin goes low, and high when you use PIN_Write(0)? The concept of the drive mode is very confusing to me and I cannot seem to get this information from the datasheet for the pins.
I am also trying to use the TM1637 with PSoC 4 (bit banging) and have had no success. If you could clarify this for me, it would help a lot.
Thanks,
Julian
Show LessHi,
I want to create a windows application using the cy dongle api. I'm able to detect the port, do a scan and connect to the BLE device.
But I try to do a write without response to the gatt alert me characteristic (0x2A06). But the BLE device does not reveice a alertme.
Best regards
Martin
Show LessQ1)
Could you please let us know recommended series resistance of Capsense SPI interface?
Is it 330ohm?
Q2)
Should series register be added to all SPI interface(miso, mosi, sclk, ss)?
Best Regards.
Show LessHello,
I'm working on a CY8C4247, and this is the first time I use a Cypress microcontroller.
I'm trying to set up a I2C communication where my micro is the slave. I have found only examples where the interrupt aren't used (the code use polling).
I need to have the code as faster as possible, so I have enabled the interrupt, but as explained on your application note the callback is triggered every time one of the several I2C event happen.
I want to be able to understand which event triggered the interrupt, so I need to know more about the I2C registers.
I have tried to find a complete datasheet, but I have found only a brief datasheet (around 50 pages without register description).
Is it possible to find the information I need about the I2C somewhere ? Can someone send me the link for a complete datasheet and an example of code that use the I2C interrupt, if it exist ?
Thank you
Riccardo
Show LessHello, there
I have a CapSense project using CY8C4025AXI-S412 to calculate absolute capacitances value from the raw counts. When I set the total number of sensor more than 8, the raw count reading from the RAM always gives a fixed value.
Here is the function where I read the raw counts, and I put all the sensors under button0 widget, even I split the sensors into two widgets, still read a fixed value when I set the total sensor more than 8.
void ProcessAllSensors(sensor_data* p_sensor_data)
{
interruptState = CyEnterCriticalSection();
for(uint8 snsId = CSD_BUTTON0_SNS0_ID; snsId < CSD_TOTAL_SENSORS; snsId++)
{
p_sensor_data[snsId].rawCounts = CSD_dsRam.snsList.button0[snsId].raw[0];
p_sensor_data[snsId].capacitance = CalculateCapacitance(p_sensor_data[snsId].rawCounts);
}
/* Enable interrupts for servicing ISR */
CyExitCriticalSection(interruptState);
}
When I adapt all project into the CY8CKIT-048 kit and keep all the settings and code the same, it works fine with CY8C4A45LQI-483.
My question is what difference between CY8C4A45LQI-483 and CY8C4025AXI-S412 cause this issue?
How can I exceed the total number of sensor more than 8 on CY8C4025AXI-S412?
Here I have attached a small test project for that issue tracking.
Show LessHello,
I have a prototype board with a CY8CMBR3106S-LQXI that I am trying to configure. I have two dev boards, CY3280-MBR3 and CY8CKIT-145 (see attachment for image).
First, can I use the CY3280-MBR3 with EZ-click to configure the registers for my prototype? What jumpers do I connect to and how do I make EZ-click recognize my new device? (I think this option is simpler than option two, but let me know).
Second, if the CY3280-MBR3 cannot configure my board, can the CY8CKIT-145 be used? The board can be separated at the J4 header pins and the I2C header J6 I thought could be used for configuring. Gong this route, I assume I have to use PSoC Creator. I can connect to the 4000s using single wire, but it does not switch to I2C in port settings (see Capture1). Let me know if EZ-Click or PSoC is the correct software to be using for configuring the CY8CMBR3106S-LQXI and which dev kit.
Thanks!
Show Less