Wi-Fi Combo Forum Discussions

hello

i am try to test LBEE5KL1DX (https://wireless.murata.com/type-1dx.html ) using stm32F429ZI NUCLEO board.

we notice NEB1DX-02 (https://www.futureelectronics.com/p/development-tools--development-tool-hardware/neb1dx-02-future-electronics-dev-tools-5094171  ) has same stm32F429ZI  chip with LBEE5KL1DX wifi+BT  module

so i am try to test LBEE5KL1DX with my nucleo-F429ZI ("https://www.st.com/en/evaluation-tools/nucleo-f429zi.html ") using WICED studio

i am use NEB1DX-02 firmware,

i am try to download NEB1DX-02 example into nucleo-F429ZI

i am use "scan" example of NEB1DX-02.

i am update directly "scan" example's  ".bin" file using ST-LINK but its not working

so i am try to add ST-LINK support in WICED​ using this ​​ link (Adding ST-Link support in WICED  )

but it will generate  error like

Merge all bin files into a single bin for MSD upload

Downloading Bootloader ...

build\waf.bootloader-NoOS-NEB1DX_02\binary\waf.bootloader-NoOS-NEB1DX_02_PAD.bin

build\NABULA.scan2-NEB1DX_02\DCT.bin_PAD.bin

build\NABULA.scan2-NEB1DX_02\binary\NABULA.scan2-NEB1DX_02.bin

        1 file(s) copied.

Location: build/NABULA.scan2-NEB1DX_02/binary/NABULA.scan2-NEB1DX_02.bin_MSD.bin

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

Downloading DCT ...

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

Downloading Application ...

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

Resetting target

tools/makefiles/standard_platform_targets.mk:226: recipe for target 'run' failed

make.exe[1]: *** [run] Error 1

Makefile:351: recipe for target 'main_app' failed

make: *** [main_app] Error 2

please suggest me way to test LBEE5KL1DX using nucleo-F429ZI.

my only goal is to test LBEE5KL1DX

with WICAD studio or without WICAD studio

with nucleo-F429ZI or nucleo-F429ZI

All suggestion are welcome

thank you

I have three CY8CKIT-062-WiFi-BT. Out of the box all kits are able to be programmed with wiced examples.

I have done the following with two of the three kits:

I used fw-loader to upgrade to KitProg3 so I could try modus.

I used fw-loader to downgrade to KitProg2 so I could go back to wiced.

Since I went back to KitProg2 I have not been able to program with wiced. See error below.

According to the documentation I should be able to use fw-loader to switch between KitProg2 and KitProg3. This does not work for me.

I have tried every possible led configuration

The board with original kitprog2 works fine.

The two boards that went to kitprog3 and then back to kitprog2 do not work.

Thoughts?

Error:

Downloading Bootloader ...

Building apps lookup table

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

Downloading DCT ...

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

Downloading resources filesystem ... build/ww101.02.04_button-CY8CKIT_062/filesystem.bin at sector 1  size 104...

tools/makefiles/wiced_apps.mk:335: recipe for target 'FILESYSTEM_IMAGE_DOWNLOAD' failed

make.exe[1]: *** [FILESYSTEM_IMAGE_DOWNLOAD] Error 1

make: *** [main_app] Error 2

Makefile:351: recipe for target 'main_app' failed

I am using BCM943909WCD1_3 wiced controller.

Wiced studio version : 6.4.0.61

In ota2_bootloader.c I am trying to use UART communication with another controller to get new wiced image and write in to the staging area.

In ota2_bootloader right now uart drivers not exposed/available. Facing issues in uart drivers implementation and access.

Need assistance in uart communication establish in bootloader level.

I found that a new QDID had been registered on Bluetooth Sig.

QDID:160340 - Component (Tested)

        CY-WICED 4.1 BLUETOOTH Host Stack, 4.1

We have BLE project with CYW4343W(1DX) and WICED(6.4.0).

Can I use this QDID for BT SIG certification ? Should we update WICED to 6.6.0 ?

Hi Sir，

我目前打算搭建环境测试同一个AP下两个STA之间TCP收发包时间及丢包率，数据包会自定义大小，不考虑使用第三方工具如iperf，使用的是psoc6+43438。

我在wiced里面有找到demo：tcp_client比较适合，目前有两个问题，比较疑惑，请帮忙解答下，谢谢。

1.wifi_config_dct.h这个文件在该demo里面没有找到，是在哪里配置SSID等信息，default_wifi_config_dct.h下面有相关的宏，是在这里修改吗，还是说需要自己新建？

2.demo发送的数据是Hello from WICED，tx_data这个数据最大可以配置为多少？

Hi,

I'm using 4343W with WICED Studio SDK Version: Wiced_006.004.000.0061

I am writing a custom application to run a BLE Client. I can see the Server advertisements in the scan callback. Then, I stop the scan and try to make the intial connection as follows:

wiced_result_t status;
status = wiced_bt_ble_scan(BTM_BLE_SCAN_TYPE_NONE,
                               WICED_TRUE,
                               ble_scan_result_cback);
if (WICED_BT_SUCCESS != status)
{
    LOG_ERROR("Scan error: %u", (uint16_t)status);
}
if (false == wiced_bt_gatt_le_connect( p_scan_result->remote_bd_addr, p_scan_result->ble_addr_type, BLE_CONN_MODE_HIGH_DUTY, TRUE ) )
{
    LOG_DEBUG("GAP Conn fail!");
}

This results in the scan callback being called with a NULL scan result pointer, as expected.
This is immediately followed by a call to the management callback with the BTM_PAIRED_DEVICE_LINK_KEYS_REQUEST_EVT event.

There is no GATT_CONNECTION_STATUS_EVT event happening. I would expect this to come first, but this event does not occur.

Is the above a valid scenario? If so, how should I handle the link keys request? There has been no prior connection or pairing and no calls to any security functions such as wiced_bt_dev_sec_bond() at this stage.

Hello,

Does Ethernet module of Cypress WiFi MCUs support MAC (RMII) to MAC (RMII) connection without Ethernet PHYs?

As I want to use Ethernet for onboard communication with FPGA, I want to avoid extra chips on the PCB.

Thank you in advance.

Hello.

I'm using connection_manager library to configure my WICED as P2P GC.

In file "connection_manager.c" rows 122...158 I see the structure besl_p2p_device_detail_t.

Can someone explain me what is listen_channel, operating_channel, channel_list ?

Listen channel is the channel where WICED listen probe requests ?

Operating_channel is the channel where WICED works upon connection established ?

But if I configure WICED as Group Client is the Group Owner that establish working channel, right ?

I don't understand the purpose of "p2p_channel_list_table" : they are the channels where WICED works ?