All Forums

Hello All,

I'm working with a team of students and we are developing a prototype using a PSoC 5LP. A question I have is, when applying power to the PSoC 5LP, is it required to  to have separate supplies (We are using LDO's) for VDDA, and VDDD? Also, we are not planning on using an of the analog peripherals.  Any help would be appreciated.

Hello,

I am using PSOC4100S MCU CY8C4147AZI-S445 with PSOC Creator 4.2.

I want to switch Pins(P3.0(RX) and P3.1(TX))  from UART SCB to Input pins. 

I followed this link.

In this Uart port is stopped, but In Uart tx pin, it reads value 0, but on the it is 3.3V (tested with multimeter). I used following code:

temp = CY_GET_REG32 (CYREG_HSIOM_PORT_SEL3);

        // Configure UART_Rx pin to be controlled in firmware

        CY_SET_REG32 (CYREG_HSIOM_PORT_SEL3, CY_GET_REG32 (CYREG_HSIOM_PORT_SEL3) & 0xFFFFFF00);

        // Set the drive mode of UART Rx pin

        UART_1_tx_SetDriveMode(UART_1_tx_DM_RES_UP);
        //CY_SET_REG32 (CYREG_HSIOM_PORT_SEL3, temp);

Please help me for this issue.

Thank You 

Hello
Just trying to get a simple setup to work.
Both have 9600 baud rate (76k/8) = approx 9600

The PSOC1 microprocessor that send data TX use port 1.3 to send data. I did measure a good signal with my oscilloscope, matching (if using pin 1.5 as TX) so they have the same output on oscilloscope.

I use putchar to send TX data and cgetchar on the other PSOC microprocessor to read data from RX.
I have connected TX to RX and vice versa.

So I am pretty sure I send correct data. When using cGetChar I just wait and wait for data to be received in RX, so the program stall because I apparently never receive anything acceptable.

If I use cReadChar it gives me back a zero as an error condition. So for some reason I dont receive what I am supposed to, or read it wrong.
I disabled interrupt´s  on RX at the receiving end.

I start both unist with none parity.

Where do I do wrong?
Please if you refer to examples, then refer to an example that actually is an example of similar problem.

Thanks in advance

Hello Infineon Experts,

We use a CX3 and one or two related image sensors on our board, and we are facing a CY_U3P_ERROR_FAILURE value returned by the CyU3PMipicsiSetSensorControl() API. This behavior is random, but the error rate is over 20 %.

We probed the I2C bus and some other significant signals (CX3_RESET*, CX3_XRESET and CX3_XSHUTDOWN), to look what’s happen (see attached pictures):

• On successful execution, a first reading of Register 0x0012 (CY_U3P_MIPICSI_REG_GPIOIN) is done, bits [2:1] of this value are set to ‘1’ to drive High XRESET and XSHUTDOWN pins, the changed value is written to Register 0x0014 (CX3_CSI_SENSOR_SIG_VAL) and a second reading of Register 0x0012 is performed to be sure that Register 0x0014 is correctly written. So, reserved bits of Register 0x0014 are preserved as requested to section 1.10.7 of CX3 TRM.
• On fail execution, the second reading of register 0x0012 doesn’t match the writing to Register 0x0014 and the CyU3PMipicsiSetSensorControl() API returns CY_U3P_ERROR_FAILURE. The difference concerns the reserved bit 0.

Do you have an explanation for this error CY_U3P_ERROR_FAILURE?

For your information, both SDA and SCL signals are pulled high with 2kΩ resistors, and the I2C block is initialized (by calling CyU3PMipicsiInitializeI2c() API) before initializing the MIPI-CSI-2 block (i.e. before calling CyU3PMipicsiInit() API).

Best Regards,

Eric.