I want to configure the DS-1 port of CY611 EZ-USB HX3PD EVK to supply 12V. But when I try to configure using EZ-USB HX3PD configuration Utility - PD Controller- Port 1, it shows me error - Atleast one 5V PDO should be enabled in Source PDO. But if add another source PDO of 5V, it does not save the configuration.
Can anyone help please ?
I have to find a good and stable 4-port(at least now, in future maybe more ports will be necessary) USB HUB solution. I have payed attention to Cypress products, because development boards are available and it is possible to "play", before making PCB. The HUB should support LED indicators for downstream ports(LED should be on, when device is connected and active).
So, 48-TQFP devices support LED indicators. But what about 28-QFN devices? I have not found information in datasheets. But what confuses me - circuits for CY4608/CY4608M boards show some LEDs, but LEDs are not soldered to boards (See pictures).
So, my question is: If I need LED support, can I use 28-QFN devices, or only 48-TQFP devices can be used?
I have a custom FX3 board with S25FS064S. I programmed the spi flash via control center. I changed the PMODE[0:2] 11F to 1F0 to enable boot from spi flash. When i program a new flash, FX3 can boot from the flash. But when i want to change the img file in the flash, FX3 can't be programmed anymore. I tested the img files with a evaluation board and it worked well with both of the img files. What could be the problem?
Best RegardsShow Less
FX2LP control endpoint 0 is able to transfer more than 64 bytes. How that could be explained?. The control center device info shows 64 bytes for the control endpoint 0. Is it the hardware versus software limitation?.
Sorry to bother you again.
After the last /RD signal problem was solved, no more underrun error.
But recently, all system combined test, I received error "No error : 18" from CY3014 uart port ,then, Xfer to FPGA failed.
Please kindly advise what is "No error : 18" ?
I am testing the AnyCloud TCP Server example project for CY8CPROTO-062-4343W. Inside the tcp_receive_msg_handler(cy_socket_t socket_handle, void *arg) function (I pasted it below), I found that there was about <1s delay when calling the API cy_socket_recv(). I toggled the user LED right before and after calling this API and I found that the delay of calling this function was quite significant. The tcp_receive_msg_handler is called whenever it receives some messages from the TCP client. I tried different message lengths from the client but the delay was quite consistent.
API cy_socket_recv() should just read the buffer and I am wondering why it took that long.
I am working on an application which requires the device (uses the same PSoC6 MCU and the same Wi-Fi/BT chip) to use Wi-Fi communication and act as a TCP server. So I used the AnyCloud TCP Server example project as the basic code structure. The device needs to read something from the client and then take some action as quickly as possible. The long delay of calling cy_socket_recv() is not acceptable for my application.
Any idea how to get rid of the delay? Maybe there is another API which is better in terms of response time?
From AnyCloud TCP Server example project:
static cy_rslt_t tcp_receive_msg_handler(cy_socket_t socket_handle, void *arg)
/* Variable to store number of bytes received from TCP client. */
uint32_t bytes_received = 0;
result = cy_socket_recv(socket_handle, message_buffer, MAX_TCP_RECV_BUFFER_SIZE,
CY_SOCKET_FLAGS_NONE, &bytes_received); // Long delay when calling this
if(result == CY_RSLT_SUCCESS)
/* Terminate the received string with '\0'. */
message_buffer[bytes_received] = '\0';
printf("\r\nAcknowledgement from TCP Client: %s\n", message_buffer);
/* Set the LED state based on the acknowledgement received from the TCP client. */
if(strcmp(message_buffer, "LED ON ACK") == 0)
led_state = CYBSP_LED_STATE_ON;
led_state = CYBSP_LED_STATE_OFF;
printf("Failed to receive acknowledgement from the TCP client. Error: 0x%08"PRIx32"\n",
if(result == CY_RSLT_MODULE_SECURE_SOCKETS_CLOSED)
/* Disconnect the socket. */
printf("Press the user button to send LED ON/OFF command to the TCP client\n");
I have a server tcp socket connected to a client.
I want to get ip address of the client.
Here the code.
status = wiced_tcp_create_socket ( &tcp_socket_msg, WICED_AP_INTERFACE );
if ( status != WICED_SUCCESS )
WPRINT_APP_INFO( ("wiced_tcp_create_socket failed, status = %d\n", status) );
status = wiced_tcp_listen ( &tcp_socket_msg, 50002 );
if ( status != WICED_SUCCESS )
WPRINT_APP_INFO( ("wiced_tcp_listen failed, status = %d\n", status) );
wiced_tcp_delete_socket ( &tcp_socket_msg );
status = wiced_tcp_accept ( &tcp_socket_msg );
if ( status == WICED_SUCCESS )
WPRINT_APP_INFO( ("wiced_tcp_accept ok!\n") );
WPRINT_APP_INFO( ("wiced_tcp_accept failed, status = %d\n", status) );
} while ( status == WICED_TCPIP_SOCKET_CLOSED );
HOW GET TCP CLIENT ADDRESS FROM tcp_socket_msg ???
I am new to development on the PSoC platform and I am attempting to configure UART on this device. It is a PSOC5LP - 050 board. I'm unable to configure the COM port I am supposed to read it on, because it does not show anything on device manager about which virtual COM port I should connect.
I am able to program other components and I have already worked on a few applications which are working fine. Sending a screenshot of my device manager. On PSOC programmer also, the Upgrade firmware option is 'greyed-out'. Any advice is appreciated.
EDIT: I have checked the example documentation and connected the RS-232 with the related Pinouts to the Rx and Tx pin and still nothing appears on my COM port.Show Less
Our FPGA may send variable length data(4B~16kB, integral multiple of 4Bytes) to FX3 in which firmware runs as slave FIFO mode, host app invoke XferData() to initiate a BULKIN transfer for reading data stored in FX3.
At each BULKIN event initiated by host, a certain len parameter must be passed into XferData() refer to Cypress CyAPI Programmer's Reference, for example 16384, if actual length of packet which sent by FX3 is shorter than 16384(ie partial packet), will XferData() receive the short length packet and return ture or return false for time-out? if this function can receive short packet, where can i get the actual length after the XferData() executed ?Show Less
Here`s a strange problem, XferData() may failed when slave endpoint sent a short packet with a particular length.
we`re trying to transfer data from FPGA to PC host by FX3, FX3 runs with a slave FIFO firmware, EP2 IN(0x82) is initiated in FX3 for BULK IN transferring, in each transfer test, firstly, PC host invoke XferData() to generate a BULKIN transfer(bufLen is always set 16384, pktMode is set TRUE) and waiting for a packet from FX3, then our FPGA send a short packet to FX3, at each test,packet length is different, short packet is ended by asserted the PKT_END pin .
XferData() return TRUE in most of tests, but failed at several test, after research of these failed tests, we found that if FPGA send packet with length of 2048,4096 or 8192, XferData() retrun FALSE and timed out happened, such a werid thing. any body can help me ?
BTW, these two results may help you:
1.XferData() can be successful when actual length is 8191 or 8193, but if FPGA send 8192 bytes to FX3, XferData() must be failed.
2.if we set 8192 to bufLen parameter, XferData() return TRUE when FPGA send 8192 bytes to FX3.
here`s main part of BULKIN transfer code at PC host side(VS2013):