Wi-Fi Combo Forum Discussions
Hi,
Actually I bought CYW954907AEVAL1F_Evaluation_Kit to test the RF parameters .I am new to WLAN testing .Could you please suggest me to understand and testing/measure the RF parameters.
Thanks,
harshini
Show LessHi,
i'm using Type1LD Evaluation Board and followed the process mentioned in the Type1LD Evaluation Board Quick Start Guide used the WICED-SDK
to compile the application by creating a separate make file but, i'm getting an error as
tools/makefiles/standard_platform_targets.mk:205: recipe for target 'run' failed
make.exe[1]: *** [run] Error 1
make: *** [main_app] Error 2
Makefile:349: recipe for target 'main_app' failed
Show LessWe recently upgraded the firmware for our 4343W-based product from WiCED sdk v4.0 to 5.2 on the way to 6.2. There were some hurdles to jump through to get things building and running because of the resource changes (e.g.. the clm_blob), but we passed a quick verification of our system performance as we continued our upgrades onto v6.2.
But we recently noticed a sharp drop in the reliability of BLE scanning and pairing when trying to connect to the 4343W from our mobile apps. We traced to the change between v4.0 and 5.2 version. Specifically on the same hardware and same antenna, our apps (both iOS and Android) scan and pair reliably with our 4.0 firmware build and struggle to find our hardware or maintain pairing with it for more than a few 10's of seconds with the 5.2 build.
The 5.2 release notes do not mention any changes in the BLE firmware or API.
So before we dive in and try to figure this out, wanted to see if anyone else has run into anything similar.
Show LessI set up my target ssid and password in the DCT then called wiced_network_up. Since my target ssid won't be up 100% during my application. I saw the wiced_network_up tried to join the target ssid three times and then declared the "failed to join : target ssid"
I would like to have it keep try to connect to the ssid, instead of stooping after only 3 tries. How could I achieve this?
In other API I used before, I can set the something like wifi,config,auto_connection to true. then the wifi API will keep trying to connect to the ssid provided. Is there anything similar in wiced?
Show LessOn ThreadX build:
WICED_TLS_MINOR_VERSION_MIN=0 && WICED_TLS_MINOR_VERSION_MAX=0 works
WICED_TLS_MINOR_VERSION_MIN=0 && WICED_TLS_MINOR_VERSION_MAX=1 works
WICED_TLS_MINOR_VERSION_MIN=0 && WICED_TLS_MINOR_VERSION_MAX=2 fails
On FreeRTOS build
WICED_TLS_MINOR_VERSION_MIN=0 && WICED_TLS_MINOR_VERSION_MAX=0/1/2 all fails
For the failure case, sometimes I got join result 1007, and sometimes it just hang.
grsr
The test result is similar to the PEAP test.
So the enterprise security does not work for FreeRTOS+LwIP build at all.
Show LessHello,
I want to make an application which uses wifi continuously on with BT/BLE switching for Voice and Data communications. So, I want Combo module of wifi with Dual mode Bluetooth BLE5 so that i can achieve the same in my product as i am unable to find this kind of module as of now so I would like to request all that if you have seen or using this kind of module then please suggest us.
I have found one solution CYW43438 but its BLE 4.2 so i want the same with BLE 5 . Also please share the link for the same to buy as i didnt find the way to buy this modules.
Tell me if you need more info.
Thanks & Regards,
Irfan
Show LessWhen I place breakpoints, they are not 'loaded' if I'm not running the firmware, i.e., there's no tick placed next to the breakpoint in the IDE.
When I run the firmware and place a breakpoint, then it is properly loaded and the firmware will break as intended.
This is annoying, because I have to reload breakpoints on every run!
Is there a solution to this?
Show LessWe have been trying to debug multicast dropouts. This has occurred on ALL versions of WICED and is currently being experienced on WICED 6.0.1
The devices join the multicast group immediately after going online, the same time they set up a UDP socket to receive CoAP messages.
In the system we are transmitting multicast messages to groups of devices to get responses on various states and to notify them of actions occurring on other devices in the group.
We have noticed at times that the messages are not received by some of the devices. They seem to loose the ability to recv multicast messages.
Apply the following filter to the wireshark capture file: coap&&((ip.addr==10.6.0.8)||(ip.addr==10.6.0.7))
Device .8 sends a notification of an OTA update. The devices do the update and later the devices are sent a request for status. Record 14188
Only two devices respond. The request is repeated by .8. on a couple of occasions. records 14656, 16492. A unitcast request for the same data is sent to one device from .7 and is responded to immediately record: 22982. the multicast request is sent out again record: 27186. The .7 device sends another unicast to another member of the group and it is also responded to immediately. 28268. Some time later ~9 seconds the .8 device sends another multicast request and all devices respond.....
To try to understand this I dug into the source to see what statistics I could pull from the nx drivers. I found the routine. nx_igmp_info_get. When I called this routine the values of all statistics are 0 regardless of the responsiveness of the multi cast action.
This problem only occurs occasionally but is enough to derail this products operation as the notifications that are sent periodically are critical for the operation of other members of the group.
All units have good RSSI levels and acceptable noise levels. Normal operation is correct. Its just this occasional issue we are having.
How to proceed with debugging this issue?
Show Less