45907 Discussions
22779 Members
26510 Solved
Hello,
I am trying to include the 'CyAPI.lib' from the x64 Cypress library folder and trying to build in C++ 10.4 Builder for the multi target platform. But, I am facing problem with a linker error like "[ilink64 Error] Error: Unresolved external 'CCyUSBDevice::CCyUSBDevice(void*, _GUID, int)..................' while trying to build. Please find the attached snapshot for more details.
Any guidance on the matter would be greatly appreciated !!
Thanks,
Aditya
Hello everyone,
i need a clarification on a detail regarding VCCIO=1V8 of CY7C65213.
As seen on the datasheet, the VCCD pin is the OUTPUT of the internal regulator for 1V8 and it cannot drive external loads.
Additionaly, on the datasheet it is mentioned that when VCCIO is less than 2V, VCCD must be connected to VCCIO.
In this scenario, can the device be damaged during startup considering that the default configuration stored in its Flash doesn't disable the internal regulator (as shown on Table 2 in the datasheet)?
Lastly, always from Table 2 of the datasheet, it is hinted that CTS and DSR signals have an internal pull up. What about DCD and RI Signals? Do they have some internal pull up or pull down as well?
Thanks in advance.
Show LessHi
I have a custom board with CYUSB3014-BZXC interfaced with Xilinx ultrascale fpga for which I am facing some issue with gpif interface. I have the a working gpif inteface on a previous board in which CYUSB3014-BZXC is interfaced with Xilinx artix fpga. In the new board with ultrascale , i am reusing the fx3 image and the fpga code ( fx3 interface part is same). However when I do a slave read with GPIF interface , I see that the FX3 is not receiving the data from the FPGA. I have probed on the data lines and pclock signals. Clock is fine at 100MHz and data is also coming out of the FPGA. Other signals like SLCS, SLWR,SLRD,address , pktend etc are also in their expected state. I am doing a 16384 length transfer and the watermark is kept at 16380. However i note that both FlagA and FlagB are staying high throughout and not going to 0. I have a doubt that the Fx3 fifo pointer is not getting incremented or the GPIF state machine is somehow stuck. I do not have access to UART pins. They are connected to the FPGA. Any pointers as what might be happening will be really helpful.
Thanks and regards
Nithin
Show LessHello,
I installed WICED-Studio-6.6 for mac (Big Sur, 11.1) to run my CYW920706WCDEVAL Evaluation Kit.
Despite of successful installation, I can not see the 20706-A2_Bluetooth folder in WICED-Studio-6.6 under Documents. But I can see 43xxx_Wi-Fi folder instead.
tried also reinstallation but there is still no 20706-A2_Bluetooth folder.
am i doing something incorrectly? or is there anything to do more during installation?
Regards,
Eunsung
Show LessHello.
I write this code.
#include "wiced.h"
static wiced_thread_t xt;
static void x(uint args);
static void x(uint args)
{
WPRINT_APP_INFO( ("[x] running\n") );
}
void application_start(void)
{
UINT status;
/* Initializes the WICED system */
wiced_init ( );
for(int m = 0;m<10;m++)
{
WPRINT_APP_INFO( ("\nCreate thread #%d ...\n", m) );
status = wiced_rtos_create_thread ( &xt, WICED_APPLICATION_PRIORITY, "x", (wiced_thread_function_t)&x, 1024, NULL );
if ( status != WICED_SUCCESS )
{
WPRINT_APP_INFO( ("wiced_rtos_create_thread 'x' failed, status = %d\n", status) );
}
wiced_rtos_delay_milliseconds ( 1000 );
}
}
The first iteration of the "for" cycle creates thread successfully.
The subsequents iterations returns "wiced_rtos_create_thread 'x' failed, status = 1031"
1031 is THREAD_CREATE_FAILED.
I dont' understand ... I believe that in 1 seconds the 'x' thread finished because it has only to PRINT a simple string, so duration is less than 1 seconds. So I believe that ThreadX can create new thread with the same "static wiced_thread_t xt;".
Show Less
Hi Team,
1) Does the CYW43455 chip support ad-hoc mode in WIFI?
2) Is there any procedure/command-line tools available to set up an ad-hoc network using the WIFI interface?
Thanks,
Ajith.
Show LessDear community,
I have to implement a virtual COM with the FX3 as an alternative to the UART module for the cyfx3s_fatfs example; so I need a set of API similar to CyU3PUartReceiveBytes and CyU3PUartTransmitBytes and the possibility to write buffer with DMA (as in cyfx3s_fatfs) but working through an USB Virtual COM.
I started working with UsbUart example by modifing the DMA configuration and sockets (in attached) to use the "void CyFxUartSendBuffer(uint8_t *Buffer_Print,uint8_t cnt_read)" function, but without results.
Please, someone could give me some ideas or code example?
Consider that is my first time with this MCU, this architecture and in general with the USB.
Many thanks in advance, regards,
Corrado90
Hi,
We are using Cypress 43455 (murrata 1MW) with NXP MCU with Wiced SDK. We are trying to connect wifi module with a wifi router configured in AC only mode but are not able to do so. We are able to scan the router but join attempts to the router always fails. We have observed that if we set the country code as USA on the module side we are able to connect to router.
We have tried to make sure that the country selection on router and module match but we don't see any success. We are able to use all the other modes (N, A, mixed etc) with other country code but not AC.
What could be the solution for this? We want to set the country code as UK and run AC mode. What are we missing here?
Firmware and CLM blob information:
WLAN Firmware | : wl0: May 2 2019 02:46:20 version 7.45.189 (r714228 CY) FWID 01-105ab14e |
WLAN CLM | : API: 12.2 Data: 9.10.136 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2019-05-02 02:31:24 |
Regards
Show LessDear Yatheesh,
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" ?
BR
Steven.
Show LessEsteemed Contributor II
Esteemed Contributor
Employee
Employee
Honored Contributor II
Employee
Honored Contributor
Honored Contributor
Employee