Wi-Fi Combo Forum Discussions

Hello,

I purchased the cypress WiFi wiced dev kit for iot development.  The CY943907 development kit. 

https://www.cypress.com/documentation/development-kitsboards/cyw954907aeval1f-evaluation-kit

There is some application within our organization for remote monitoring of some tools I would like to develop.  I had intended to do this via amazon web services, however company policy is to avoid 3rd party cloud services at the moment.

Instead of AWS or other cloud streaming, I would like to try to use the kit for writing to a local server.  As a first step, I would like to use the weather station tutorial and log json data onto a local server that can be accessed on demand.  We can parse the JSON data for plotting on needed basis.  I was not sure how to transition this however.  I am working on this using an XAMP server for example, and would just like to write a JSON file to the localhost.

I am very new to this area, and I am having a hard time locating such kind of instruction as most tutorial are about iot streaming applications.  I think perhaps my application is more simple, and would appreciate any support you can provide.   This would include how to modify existing Scripts from ww01 git hub repository to meet this requirement.  I would then tailor our application to the needs of our engineering team, and eventually layout the pcb board for defining this product.

Thanks for any input, and I would be glad to answer any questions you might have.

Hello,

     We are using BCM43242 USB interface wireless chipset. BCM P2P library (Sample App) used for the Wi-Fi Direct (P2P).

Wireless Chipset firmware version: wl0: Feb 26 2020 07:46:16 version 6.20.224.37 (r724556) FWID 01-32bd010f

In 2.4Ghz & 5Ghz frequency, 40Mhz bandwidth, things are working fine, like station connection and p2p connection. But in 5Ghz frequency, 40Mhz bandwidth, P2P is failing to UP. I have collected the logs for both success(5Ghz,20Mhz BW) and failure(5Ghz,40Mhz BW) cases and shared them here.

It looks like the WLC_E_IF event is not received during create bss.

Does anybody know the reason for this?

**********WORKING LOG FOR 5GHz frequency and 20MHz Bandwidth**********

p2papi_osl_create_bss: P2P ch=81:10

---wl p2p_ifadd 86:25:19:ad:b2:85 go 10

p2pwl_iovar_setbuf_bss: iovar=p2p_ifadd, bssidx=0

Receive Event --> Primary through call

event fwd : ret=79

Drop an event

p2papi_rx_wl_event: rx WLC_E_IF 54 bsscfgidx=1() stat=0x0 reas=0x0 auth=0 data_len=5

p2papi_rx_wl_event: event data: 5

  01 01 00 01 03

WLC_E_IF: cbcaw=1 flags=0x0 ifname=wl0.1

...saving conn bsscfg ifname

p2posl_save_bssname: usage=2 ifname=wl0.1

p2papi_osl_connection_mode_ifup: ifname=wl0.1

p2papi_linux_ifup: ifconfig wl0 up

**********NOT WORKING LOG FOR 5GHz frequency and 40MHz Bandwidth**********

p2posl_sem_wait: timed out, cnt=0

p2posl_sem_wait: exit, ret=39 cnt=0 time=505.210000

p2papi_osl_create_bss: sem_wait failed with 2

---wl p2p_ifdel 86:25:19:ad:b2:85

p2pwl_iovar_setbuf_bss: iovar=p2p_ifdel, bssidx=0

p2papi_group_cancel: poll for cancel confirm...

wl_ioctl: WLC ioctl 263 returned error -30

sock=158 buf=0x37beb10 len=16 set=1 wl=0x95c3bc4, ret=-30

pri/dis/con ifidx=0/0/0 ifnames=eth1//, ioctl ifname=eth1

WLC_SET_VAR p2p_ifdel

P2PAPI: set bss 0 iovar p2p_ifdel failed (-2)

'wl p2p_ifdel' error -2

p2papi_osl_create_bss: create bss failed, ret=2

p2papi_create_ap_bss: osl_create_bss failed

p2papi_create_ap_bss: exit, ret=2 conn-bssidx=0

p2p_group_create_core: softap_enable failed

p2papi_group_create_core: cleanup, cancel=1 status=-17

I am very new to WICED Studio and downloaded WICED Studio 6.1.
Q.1 I want  memory footprint for entire stack for al connectivity ( wifi+ BT + BLE)?

Q.2 Where can i get examples for cloud connectivity over Wi- Fi

Can anyone please help me on this?

Hello,

I'm currently integrating the BCM4343W, integrated in the Type 1DX, with a STM32L4A6. I'm trying to validate the Bluetooth Low Energy interface on our board. Note that I've done this test using a Nucleo board and the Type 1DX dev kit successfully before, now the objective is to get it to work on our custom board.

I'm getting the following error when running ble_hello_sensor or ble_hello_client:

Started ThreadX v5.8

WICED_core Initialized

Hello Sensor Start

00:00:00.004000 GKI_create_task func=0x80159a5  id=1  name=BTU  stack=0x0  stackSize=4096

00:00:00.008000 GKI_create_task func=0x80170dd  id=0  name=HCISU  stack=0x0  stackSize=3072

00:01:00.111000 GKI_exception(): Task State Table

00:01:00.113000 GKI_exception 65524 getbuf: out of buffers

Note that I've been able to use the WiFi successfully on this custom board.

I have been probing the BLE UART interface between the STM32 and the Type 1DX, and I've noticed that the STM32 asserts its RTS but the Type 1DX doesn't reply with CTS, which sounds like a part of the problem.

Could the fact that the Type 1DX doesn't assert the CTS line lead to having the logs shown above or is it another issue?

Thanks in advance

The QA at https://community.cypress.com/thread/51967 answers how to reduce the WPS timeout from 2 minutes.

Is there a function to kill the waiting state instead of changing the time?

Hello.

How do I create a factory reset image of an executable application and download it to an external SFlash?

The contents I tried are as follows.

Executable applications are built and run in the following ways:

make <App>-<Platform>-ThreadX-NetX_Duo download run

Created a factory reset image of the external flash according to the usage described in the Makefile.

make <App>-<Platform> -ThreadX-NetX_Duo SFLASH=app-dct-download

Note: There is no OTA-APP.

At this time, among the generated files, the size of build/<App>-<Platform>-ThreadX-NetX_Duo/DCT.stripped.elf is very large, and an error exceeding the size occurs.

DCT.elf               ...             24,416Bytes

DCT.stripped.elf ... 1,179,403,647Bytes

Q1. How to specify correct make to download Factory Reset Image to external sflash?

Q2. Are the images stored in the external sflash FR_APP and APP0 stored by Factory Reset the same format?

It is unclear whether FR_DCT is included in FR_APP or stored in DCT_IMAGE separately from FR_APP.

Q3. Is there a tool to access external flash from PC?

Thanks.

When CYW54907 is in AP mode, it will be in transmit and then receive and then again in transmit mode and so on. We are looking for a method, through which inside WICED we can know, the Rf is in transmit or in receive side. By default the transmit beacon we can get in every 100msec. We are trying to trigger some other equipment ( to perform other measurements) with this transmit as trigger.

So our objective is get to know when RF is in transmit mode and switch a GPIO, which will send trigger signal to external equipment.

<English>

Repeated calls to the MQTT API have resulted in memory leaks.

"◆ MQTT API processing procedure" is as follows.

The processing procedure starts from "Referenced sample code".

In the developed application, there is no process to dynamically generate the heap area such as the malloc function, so I don't think it is a problem in the application.

I think the "wiced_aws_create_endpoint" function is the problem.

In the "wiced_aws_create_endpoint" function, the aws_internal_mqtt_init function is called, but there is no place where the aws_internal_mqtt_deinit function is called, and it is thought that there is a memory leak.

Refer to "◆Wiced_aws_create_endpoint function, Malloc, queue, create_thread function"

The size of the memory leak is "8,672" bytes, but the total of the three functions of "◆Wiced_aws_create_endpoint function, Malloc, queue, create_thread function" is "8,626" bytes, which is an approximate value. Is out.

Please let me know if the "◆ MQTT API processing procedure" is bad or if there are any other countermeasures.

◆ MQTT API processing procedure

・ Wiced_aws_init

・ Wiced_aws_create_endpoint ★

・ Wiced_aws_connect

・ Wiced_aws_publish / wiced_aws_subscribe

・ Wiced_aws_disconnect

・ Wiced_aws_deinit

◆ Referenced sample code

・ WICED-Studio-6.4 \ 43xxx_Wi-Fi \ apps \ demo \ aws \ iot \ pub_sub \ publisher \ publisher.c

・ WICED-Studio-6.4 \ 43xxx_Wi-Fi \ apps \ demo \ aws \ iot \ pub_sub \ subscriber \ subscriber.c

◆ Environment

・ Version: WICED SDK with PSoC 6 Support 6.4.0

・ Project: 43xxx_Wi-Fi

◆ Wiced_aws_create_endpoint function, Malloc, queue, create_thread function

・ Aws_internal_mqtt_init: 1864 Byte

・ Wiced_rtos_init_queue: 640 Byte

・ Mqtt_core_init: 6122 Byte

◆ aws_internal_mqtt_deinit function Grep result

・ WICED-Studio-6.4 \ 43xxx_Wi-Fi \ libraries \ protocols \ AWS \ aws_mqtt.c (345,16) [SJIS]: wiced_result_t aws_internal_mqtt_deinit (wiced_aws_internal_handle_t * aws)

・ WICED-Studio-6.4 \ 43xxx_Wi-Fi \ libraries \ protocols \ AWS \ aws_internal.h (132,16) [SJIS]: wiced_result_t aws_internal_mqtt_deinit (wiced_aws_internal_handle_t * aws);

>> No function is called

<Japanese>

MQTT APIを繰り返しコールすると、メモリリークの現象が発生する

MQTT APIを繰り返しコールすると、メモリリークの現象が発生しています。

「◆MQTT APIの処理手順」は、以下のとおりです。

「参考にしたサンプルコード」からの処理手順になります。

開発したアプリケーションでは、malloc関数などのヒープ領域を動的に生成する処理がないため、アプリケーションでの問題ではないと思っています。

wiced_aws_create_endpoint関数が、問題だと思っています。

wiced_aws_create_endpoint関数内で、aws_internal_mqtt_init関数がコールされていますが、aws_internal_mqtt_deinit関数をコールしている箇所がなく、メモリリークしていると考えています。

「◆wiced_aws_create_endpoint関数で、Malloc、queue、create_threadをしている関数」参照

メモリリークしていると思うサイズが、「8,672」バイトですが、「◆wiced_aws_create_endpoint関数で、Malloc、queue、create_threadをしている関数」の3関数のトータルが、「8,626」バイトであり、近似値がでています。

「◆MQTT APIの処理手順」が悪いのか、他に対応策がありましたら、教えてください。

◆MQTT APIの処理手順

・wiced_aws_init

・wiced_aws_create_endpoint  ★

・wiced_aws_connect

・wiced_aws_publish/wiced_aws_subscribe

・wiced_aws_disconnect

・wiced_aws_deinit

◆参考にしたサンプルコード

・WICED-Studio-6.4\43xxx_Wi-Fi\apps\demo\aws\iot\pub_sub\publisher\publisher.c

・WICED-Studio-6.4\43xxx_Wi-Fi\apps\demo\aws\iot\pub_sub\subscriber\subscriber.c

◆環境

・Version：WICED SDK with PSoC 6 Support 6.4.0

・Project：43xxx_Wi-Fi

◆wiced_aws_create_endpoint関数で、Malloc、queue、create_threadをしている関数

・aws_internal_mqtt_init：1864 Byte

・wiced_rtos_init_queue：640 Byte

・mqtt_core_init：6122 Byte

◆aws_internal_mqtt_deinit関数 Grep結果

・WICED-Studio-6.4\43xxx_Wi-Fi\libraries\protocols\AWS\aws_mqtt.c(345,16)  [SJIS]: wiced_result_t aws_internal_mqtt_deinit( wiced_aws_internal_handle_t* aws )

・WICED-Studio-6.4\43xxx_Wi-Fi\libraries\protocols\AWS\aws_internal.h(132,16)  [SJIS]: wiced_result_t aws_internal_mqtt_deinit( wiced_aws_internal_handle_t* aws );

＞＞コールしている関数がない