Wi-Fi Combo Forum Discussions

Hello.

I write this code.

#include "wiced.h"

static wiced_thread_t xt;
static void x(uint args);

static void x(uint args)
{
          WPRINT_APP_INFO( ("[x] running\n") );
}

void application_start(void)
{
          UINT status;

          /* Initializes the WICED system */
          wiced_init ( );

          for(int m = 0;m<10;m++)
          {
                  WPRINT_APP_INFO( ("\nCreate thread #%d ...\n", m) );

                  status = wiced_rtos_create_thread ( &xt, WICED_APPLICATION_PRIORITY, "x", (wiced_thread_function_t)&x, 1024, NULL );

                  if ( status != WICED_SUCCESS )
                  {
                          WPRINT_APP_INFO( ("wiced_rtos_create_thread 'x' failed, status = %d\n", status) );
                  }

                  wiced_rtos_delay_milliseconds ( 1000 );
          }
}

The first iteration of the "for" cycle creates thread successfully.

The subsequents iterations returns "wiced_rtos_create_thread 'x' failed, status = 1031"

1031 is THREAD_CREATE_FAILED.

I dont' understand ... I believe that in 1 seconds the 'x' thread finished because it has only to PRINT a simple string, so duration is less than 1 seconds. So I believe that ThreadX can create new thread with the same "static wiced_thread_t xt;".

Hi,

I'm using Wiced 6.6.

The structure type 'wiced_ip_address_t' is defined in 'wiced_tcip.h', but this file include 'wiced_network.h', in which,  'wiced_ip_address_t' is defined again. 😅 This will trigger the type redifination under C99.

So, if you include 'wiced_network.h', and forward delclare 'wiced_ip_address_t' in it, why 'typedef' it again in 'wiced_tcpip.h‘????

Who provides a “Host Subsystem” QDID for Infineon based WiFi/BT modules that run a WICED stack?

A “Host Subsystem” QDID is required to complement the “Controller Subsystem” QDID that is provided by Murata for their 1DX module.  Infineon appears to only provide a “Component” QDID for the WICED software stack.(2) (3)

Bluetooth Certification requires either a single "End Product” QDID or combined “Controller Subsystem” and “Host Subsystem” QDIDs.(1).

CYW4343x = QDID:   134532 – Component @ https://launchstudio.bluetooth.com/ListingDetails/89357

Murrata 1DX = QDID 140301 - Controller Subsystem @ https://launchstudio.bluetooth.com/ListingDetails/96389

WICED Stack =  QDID 115853 – Component @ https://launchstudio.bluetooth.com/ListingDetails/65279

References:

1. Bluetooth Module Vendor Qualification Guide @ https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/module-vendor/
2. QDID: 115853 is Component (Tested) per “WICED Studio and ModusToolbox Bluetooth Stack QDID” @ https://community.cypress.com/t5/ModusToolbox-Bluetooth-SDK/WICED-Studio-and-ModusToolbox-Bluetooth-Stack-QDID/m-p/95384
3. QDID:160340 is Component (Tested) per “Can WICED use new QDID ?” @ https://community.cypress.com/t5/WICED-Studio-Wi-Fi-Combo/Can-WICED-use-new-QDID/m-p/165516

    

A similar question is posted on Murata’s website:

https://community.murata.com/s/question/0D55F00009G8DXmSAN/is-there-a-bt-qdid-or-qdids-available-for-complete-bt-implementation-using-wiced-bt-stack-with-1dx-nxp-rt-series-freertos

Greg

Hi , I am testing the function of apsta - sta mode.

At first, I can join to AP well,  but I find the device name is "Unnamed device" in the device list of AP,

Does there have any method to change the device name?  

Thanks

Best regards

This is a confirmation of the behavior of the CYW43438 + STM32F412 when making a BLE connection to a smartphone.
The CYW43438 supports Bluetooth 5.1 and I thought that Channel Selection Algorithm #2 would be applied during the connection.
However, when I checked the sniffer, I found that Channel Selection Algorithm #1 was applied.
In CYW43438, would it be Channel Selection Algorithm #1?

Hi,

In continuation to this post...

What's the correct way to preserve DCT content (mainly WiFi and Security credentials) when JTAG (re)programming the device?

I'm using SDK6.4 on STM32F412 based platform.

Thanks

Hi there. I'm working on bidirectional audio streaming application with the CYW954907AEVAL1F evaluation board and MAX98091 audio codec. I've already used this codec in another project, and have working driver to set up it. Also I'm able to communicate with this codec over I2C0 on the evaluation board. But at the moment I2S setup is unclear for me. I can't find any example in the WICED SDK 6.6.0. Could you please share any instructions or examples, how to setup I2S line on the CYW954907AEVAL1F?

I want to be able to transfer large blocks of data to and from my host processor.

I was reading that the NETX FTP functionality needs a file system to work, but the posts are from 5 years ago.

If my host processor is connected to the WICED device (Murata Type1LD) with SPI, can I tell the WICED application that my "file system" is on the other side of the SPI? - I could write firmware on the host processor to behave like a virtual serial EEPROM.

Is this doable? or is there a better way to get blocks of data to and from my host? Should I not be using FTP? I have an AWS based server.

I currently have a cellular modem connected to my host via a UART, and that supports FTP, so I wanted to do something similar with my WiFi channel.

Thanks in advance for any advice.

Ed.

When using OTA, the allocation of data (LUT, FR_APP...) to external Flash is done automatically, is it possible to make it a user-specified placement?