Wi-Fi Combo Forum Discussions

Hello, 

I tried to work on the EWD_Sterling evaluation board, and I want to start from the introducer, but I don't know how to install the ios demo app on my ipad.  The step by step only shows the app (wifiintroduce)location, but it didn't tell how to install it, does any one can help? I never install things to ipad from PC.  Thank you.

Holly

Hello,

I've an issue similar to this post https://community.infineon.com/t5/Wi-Fi-Combo/STM32F769NI-Murata-SN8000-Problem-with-high-throughput-clock/td-p/112986.

I succeed to communicate through SDIO with the module, flash the module without any error but I've the error 

/* If your system times out here, it means that the WLAN firmware is not booting.
         * Check that your WLAN chip matches the 'wifi_image.c' being built - in GNU toolchain, $(CHIP)
         * makefile variable must be correct.
         */
         WPRINT_WWD_ERROR(("Timeout while waiting for high throughput clock\n"));
         /*@-unreachable@*/ /* Reachable after hitting assert */
         return WWD_TIMEOUT;
         /*@+unreachable@*/

The value of the register SDIO_CHIP_CLOCK_CSR is 0x64. One time out of 20 it's working and I've the result 0xC0. (Bit 0x80 is set).

With STM32 Connectivity pack, it's working every times.  I can't use STM32 Connectivity pack because I need Wi-Fi Direct (P2P)

I used the STM32 to output the clock for LPO. This clock is always on at frequency 32.768kHz.

The SDIO clock frequency is both 5MHz with WICED and with STM32 Connectivity pack.

I downloaded WICED parameters files from Laird and adapt it to my board. (wifi_nvram_image.h, platform.c/h, platform_config.h). I tested the same set of parameters (wifi_nvram_image.h, binaries files) with STM32 Connectivity pack and it's working.

I check every signals with oscilloscope and I didn't see any major differences.

I use WICED 6.2 because STM32H753 MCU is already added. I adapted files for STM32H733.

Do you have any solutions?

Thank you

Hello guys!

I have the board CYW954907AEVAL1F and I had an electrical accident the last week. It seems that all was OK but the USB IC (FT2232H) was not. My PC didn't recognize the usual COM port and I was unable to use it for download or debug via WICED STUDIO. After several tests, I realised that the EEPROM associated to FT2232H was broken.

I have replaced it with a new one and the same part  number and now the board is recognized on PC, but there are now two COM PORTS and I can't use WICED Studio to download nor Debug any program.

I have downloaded the FT Prog software from FTDI and, after studying this chip, it could be used as JTAG bridge, but after some test, I can't use the board with Wiced Studio for debugging.

Please, could any one tell me how I can reprogram the FT2232H chip implemented on CYW954907AEVAL1F to use with WICED Studio?

Many thanks in advance!

BR, 

Luis Lopez

Hello

       There are missing files after wiced studio is installed. Please check the missing files and where to get them to complete the vulnerability.

17:54:07 **** Incremental Build of configuration Default for project 43xxx_Wi-Fi ****
"C:\\Users\\Merri\\Documents\\WICED-Studio-6.6\\43xxx_Wi-Fi\\make.exe" Default
MAKEFILE MAKECMDGOALS=Default OTA2_SUPPORT is disabled
Making config file for first time
tools/makefiles/wiced_config.mk:256: platforms//.mk: No such file or directory
tools/makefiles/wiced_config.mk:267: *** Unknown component: Default. Stop.
make: *** No rule to make target 'build/Default/config.mk', needed by 'main_app'. Stop.

17:54:07 Build Finished (took 346ms)

Hi all, new to the community and have just started evaluation of the CYW parts.  I just downloaded the latest WICED Studio (6.6) and was stopped short in the README:

***PLEASE*** read through the WICED Quickstart Guide located
in the <WICED-SDK>/Doc directory before attempting to use any of
the applications in the application sub-directories!

Problem is, the only thing in the  <WICED-SDK>/Doc folder is "WICED-Studio-License-1.0.pdf"

So, where is this WICED Quickstart Guide, which based on this comment appears to be quite useful

Dear Support,

I have a question regarding the procedure for BLE client to pair and bond to a BLE server. I am using 4343W (Murata 1dx module) and WICED Version: Wiced_006.006.000.0009

I am currently using the following API function: 

wiced_result_t wiced_bt_dev_sec_bond (wiced_bt_device_address_t bd_addr, wiced_bt_ble_address_type_t bd_addr_type, wiced_bt_transport_t transport, uint8_t pin_len, uint8_t *p_pin);

Upon initial connection, when I call the above function the result is always WICED_BT_PENDING.
A pairing IO capabilities request event occurs, to which my client sets the parameters in the callback.
The BTM_ENCRYPTION_STATUS_EVT event is called with the WICED_SUCCESS result (link encrypted).
The BTM_PAIRED_DEVICE_LINK_KEYS_UPDATE_EVT event is called and my application saves the link keys.

My question is:
How does my application to re-use the bond and encrypt the link using the saved keys for subsequent connections?

I only see the above API function and another one:

wiced_result_t wiced_bt_dev_set_encryption (wiced_bt_device_address_t bd_addr, wiced_bt_transport_t transport, void *p_ref_data);

The latter always returns 8036 (WICED_BT_WRONG_MODE).
If I call wiced_bt_dev_sec_bond() upon every connection, then it seems a new key exchange occurs as described above.

Please describe the correct process for establishing the encrypted link (pairing) and saving the keys for re-use (bonding) and describe how the application should ensure the bond is re-used (the saved keys are used to encrypt the link on subsequent connections).

Regards,
Rob