Good morning,

how you can see on attached file, I would to pilot 10 7-segment displays with LED_Driver block.

I can't use a second LED_Driver because the 7-segment are commons and Creator give me an error.

Is there a way to use LED_Driver block with 10 commons?

Thanks for all your helps.
Mattia Scricciolo

Hi All.

Our customer going to make Audio device through CYBT-343026-01.
Can i embody A2DP in the Non-OS through CYBT-343026-01?
And Can distribute with Firmware form possible?

Please check this question.

Thank you.

Hi 

I am use CYW20706A2. and I want to connect special central device(BLE)

special central device prefer use LE 2M. 

so it send LL_PHY_REQ after device connected. But CYW20706A2 don't send LL_PHY_RSP

(my SDK is wiced studio6.4 and modus2.2(BTSDK2.8))

According to "BT Core Doccument",  if device receive LL_PDU_REQ, device have to send LL_PDU_RSP

But CYW20706A2 don't send it and LE data packet for connection. 

so device is disconnected.  why don't send LL_PHY_RSP on CYW20706A2??

Hello

"AN65974.zip"-> "FX3 Firmware"-> "Slave Fifo Sync"

→ There is the following description on line 892 of "cyfx slfifosync"

io_cfg.gpioSimpleEn [0] = 0;
io_cfg.gpioSimpleEn [1] = 0x08000000; / * GPIO 59 * /
io_cfg.gpioComplexEn [0] = 0;
io_cfg.gpioComplexEn [1] = 0;

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?

Please answer each  question mentioned above?

Best Regards

Arai

Cx3 has a camera, and other devices can preview images by UVC connection . The customer want to add the time stamp on the image.Can cx3 realize this function?Or is there a corresponding interface？

I am following "Snippet 2: PDM/PCM Asynchronous Receive" from the link below:

https://cypresssemiconductorco.github.io/psoc6hal/html/group__group__hal__pdmpcm.html

The pdm_pcm_event_handler never gets called but when I comment out the line below it starts working.

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.

Hi，

    将USB CDC code example工程修改，将工程下载到自定义的使用CY8C624AAZI-S2D44芯片的板子中，将usb连接到电脑端，可以识别到一个设备：CDC Code Example，但是显示没有安装驱动，从例程文件目录下的win_drv安装驱动，提示安装驱动时出现错误，请问这种情况应如何处理？需要如何才能获得正确的驱动文件？工程请参考附件。

Hyperflash is not responding to any commands except status register read. I tried word programming , buffer programming, sector erase, Chip erase, DeviceID reading but none of this worked. Everytime status register value remains 0x80.

Can someone tell me what could be the issue.?