Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
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...
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).
I need to achieve low standby power consumption in a system with an FX3 and a Xilinx FPGA. This system primarily remains in a low power idle state fo...
I need to achieve low standby power consumption in a system with an FX3 and a Xilinx FPGA. This system primarily remains in a low power idle state for 99% of the time where neither the FX3 or FPGA is being used.
Referring to the block diagram below, the PSoC is powered continuously through the LDO. The PSoC controls switching regulators that power a USB host, the FX3 and the Xilinx. The PSoC also performs aggressive power management to maximize battery life.
The PSoC turns on power to the FX3 and the Xilinx FPGA. All of the FX3's core VDD(x) and IO VIO(x) supplies are powered. The FPGA's IO banks connected to the FX3 are powered as well to avoid the FX3 driving an unpowered FPGA or vice versa.
Later, the PSoC will apply power to the USB Host system which in turn powers VBUS on the USB connector. VBUS is used to hold the FX3 in RESET (using an RC network) until VBUS is stable.
1. Will this method of powering the FX3 work?
2. I'm confused about the use of VBATT versus VBUS FX3 signals. The Super Speed Explorer connects VBUS on the USB connector to the FX3's VBUS signal. The FX3's VBAT signal is not connected on the SSE. The FX3 DVK connects a select-able power supply(+5V,+3.3,+2.5) voltage or a battery through a diode OR to the FX3's VBAT signal. VBUS from the USB connector is connected to the FX3's VBUS signal. Other FX3 based boards connect the VBUS line from the USB connector to both VBAT and VBUS on the FX3. I'm not sure what is the correct usage for my application. Please explain.
3. I have other H/S USB devices that would share one USB Gen 3 connector. It is possible to insert a CY7C65642 USB hub on the D+ and D- signals?
I'm debugging a camera firmware which is developped based on this: https://www.cypress.com/documentation/application-notes/an75779-how-implement-image-sensor-interface-using-ez-usb-fx3-usb...
The cypress camera works fine except that seldomly during video streaming the camera somehow stops and when I check usb desctiption with lsusb -v, I saw that its descriptor is corrupted. And in dmesg I saw:
[ 8720.318320] usb 1-1.4: new high-speed USB device number 28 using xhci-hcd
[ 8720.419525] usb 1-1.4: config 1 contains an unexpected descriptor of type 0x1, skipping
[ 8720.419534] usb 1-1.4: config 1 has an invalid descriptor of length 1, skipping remainder of the config
[ 8720.419540] usb 1-1.4: config 1 has 1 interface, different from the descriptor's value: 2
[ 8720.419548] usb 1-1.4: config 1 interface 0 altsetting 0 has 0 endpoint descriptors, different from the interface descriptor's value: 1
[ 8720.420738] usb 1-1.4: config 1 has an invalid descriptor of length 1, skipping remainder of the config
[ 8720.420747] usb 1-1.4: config 1 has 0 interfaces, different from the descriptor's value: 2
[ 8720.423854] uvcvideo: Found UVC 1.00 device _v1.4.0 (04b4:00f8)
[ 8720.423873] uvcvideo: No valid video chain found.
[ 8720.423919] usb 1-1.4: Unsupported device
I'm using ADC component of CYBLE-416045-02 MCU. I have 4 analog pins which needs to be attached on 4 separate ADC channels but its showing me anal...
I'm using ADC component of CYBLE-416045-02 MCU. I have 4 analog pins which needs to be attached on 4 separate ADC channels but its showing me analog internal routing error. For the time being I'm using an internal mux like shown in the picture, but i want to use 4 different channels of the ADC and not through internal mux.Please help.
Q1) What will happen to the terminal state when all gpioSimpleEn are set to 0 (disabled)? Q2-1) I think that the GPIO_SIMPLE register setting described on P.590 of FX3 TRM corresponds to the terminal setting in this case. Is this correct? if so, would like to know the terminal status and necessary terminal processing in that case. Q2-2) I think that DRIVE_HI_EN: 0 is a tri-state output if the initial value of the register. Is this correct? Q2-3) Is it okay if external terminal processing is not required in the case of tri-state?