Someone at Cypress can help us to solve the problem?
Thanks to all!!
2 of 2 people found this helpful
Is this periodic interference reproducible in other WLAN projects that use the wiced wifi stack? Can you attach the wireshark logs for analysis? This will help us in isolating the cause.
My opinion, that bad board layout or schematic, shielding. Analog part do not must interference with wifi part.
You want analog problems resolve with software. Maybe you have in nearest range radio thermometer? Try check your device in other place.
2 of 3 people found this helpful
Once link has been establish you need to execute the following command:
wl phy_watchdog 0
If still issues you need to include the following in the nvram:
# delay onchip calibration from 120s
# Wifi Adaptivity
Hi and thanks for your tips.
Unfortunately this is our first project that involve the WICED wifi stack. We have tried to use the system with different WiFi connection device (home router, company network, mobile phone in tethering). The results is the same in all different conditions.
At the moment we have configured our system single copy for work around the problem but we'll build other systems soon and we'll try for wireshark logs analysis.
We'll send info asap!
We are conscious that this is an EMI problem. In addition i can tell you that maybe we have also problems with insufficient power supply for our complete system. Otherwise we have restricted time for system testing and delivery, so we're trying to work around the problem to go on with other program planned task such as software testing, cloud tool definitions etc...
We have also testes the system to isolate the causes and we are sure that the problems is the two system (analog board and photon board) connection or closeness.
Thank you very much for your answer. It seems to be the one that helps us to work around our problem.
First of all we're developing using the Photon IDE (Atom). With this IDE we have a restricted access to the system resources and configurations. We only can write our application code in C\C++.
Just few questions about your answer:
- the command that you indicate is a command that we can locate in our application code? Can we define this variable and init to 0 value (wl pay_watchdog(0) in C++)?
- if necessary where we have to locate the nvram configuration for correct setting?
Hiemna_2260626, could you point us to documentation of those parameters:
if you happen to know where to look for that? Web search does not seem to bring anything up that helps.