Wi-Fi Combo Forum Discussions

Hello.

I want to get the SSID list in order of signal strength by referring to the file(ThreadX_NetX_Duo_Scan.c).

(1) How long does it take to get one list? (time per outer while)
     When I tried, it was around 1.0 second.
(2) If there are many access points around, does this time increase?
(3)Will access points with strong signal strength be added to the list preferentially?

Thank you.

Hi.

I want to stream video from external MCU to WiFi via SDIO.

CYW43907 datasheet said, that CYW43907 can operate as SDIO host and as a device.

There is huge amount of SDIO host examples, but no SDIO slave projects.

I`ve seen API at:

WICED/platform/MCU/BCM4390x/peripherals/platform_sdio_host.c,platform_sdio.h,

WICED/platform/MCU/BCM4390x/peripherals/sdio_host/*

WICED/platform/MCU/BCM4390x/peripherals/include/sdio.h sdioh.h sdiovar.h

WICED/WWD/internal/bus_protocols/SDIO

I have CYW943907AEVAL1F board connected with SDIO host via headers and resolder R141 to pulldown.

All info about SDIO device is addresses of SDIOD registers. Is anyone can help me with some examples of initialisation and data transfers?

Thanks very much for help!

Hello.

After connecting to AWS, subscribe,
We will publish, etc.
While waiting for publishing from the AWS server,
The MQTT session may be disconnected.

The calling sequence from the receive callback function is
It is as follows,

mqtt_thread_main ()
Mqtt_process_tcp_receive ()
  Wiced_tcp_receive ()
   Wiced_tls_receive_packet ()
    Mbedtls_ssl_read ()

Since the return value of mbedtls_ssl_read () is an error,
"TCP receive error" log is output by mqtt_process_tcp_receive ().

What is the cause of the error?
Was access denied from the AWS server?

Thank you.

Hello.

I want to change the settings of the keep alive timer of MQTT,

Should I change the defined value of "WICED_AWS_MQTT_KEEP_ALIVE_TIMEOUT" in "aws_common.h"?

Is there a setting value range?

I want to set it to 600 seconds, but it will be disconnected 600 seconds after the last access.

Is there a solution?

Thank you.

Hi All,

I understood that "chunked encoding response" is not implemented by the following thread.
https://community.cypress.com/message/223831#223831

       Doesn't it support whole Chunked Transfer Encoding ?
       Or Does it support the request ?

Best Regards,
       Sakagami

Hi,

I have an issue during wiced_init() => "Could not set Country code"

I get retval = WWD_WLAN_BADARG while calling " retval = wwd_sdpcm_send_iovar( SDPCM_SET, buffer, 0, WWD_STA_INTERFACE );",

Below a description of my software & Hardware and a Log

Hardware :

- Custom board with an BL6212 and an STM32F412ZG
- Wifi chip is connected through SDIO, without "WL_HOST_WAKE / WL_IRQ / OOB" connected on "WWD_PIN_SDIO_OOB_IRQ / RC6" .

=> "#define WICED_DISABLE_MCU_POWERSAVE" is  Uncomment.

Note : I am not sure if "WICED_DISABLE_MCU_POWERSAVE" is supported because in Wiced Eclipse IDE Version 6.4 if I uncomment "#define WICED_DISABLE_MCU_POWERSAVE" in "wiced_defaults.h / L246" and I try to compile : "snip.scan-BCM943438WCD1" => I got compilation errors.

Sofware

- Wiced SDK 6.4

- IAR  (I have migrate the code to IAR, so my issue can also come from that).

Below a Log,

Notes :

- WWD_LOG is active, so we have trace of SDIO transfert.

- The "return retval" after "WPRINT_WWD_ERROR(("Could not set Country code\n"));" is commented, so the firmware continue even if SET country failed.

- I ove log wwd_sdpcm_send_ioctl() retval on errors :

-------------------- START LOG --------------------

Starting WICED Unknown

Platform Unknown initialised

Started FreeRTOS Unknown

WICED_core Initialized

Initialising LwIP Unknown

............!Ce·....................................................................................................................................................................................................................................................................................................................................................................................DHCP CLIENT hostname WICED IP

Started Wiced Thread

Wcd:< Rcvd pkt 0x20015194

credit update =16

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =17

Wcd:< Procd pkt 0x20015194: IOCTL Response (43 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =18

Wcd:< Procd pkt 0x20015194: IOCTL Response (38 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =19

Wcd:< Procd pkt 0x20015194: IOCTL Response (47 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =20

Wcd:< Procd pkt 0x20015194: IOCTL Response (43 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =21

Wcd:< Procd pkt 0x20015194: IOCTL Response (48 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =22

Wcd:< Procd pkt 0x20015194: IOCTL Response (48 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

--> WARN:  wwd_sdpcm_send_ioctl L#1030 wwd_sdpcm_send_ioctl() FAILED, retval=2002

--> WARN:  wwd_management_wifi_on L#314 Could not set Country code

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =23

Wcd:< Procd pkt 0x20015194: IOCTL Response (58 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =24

Wcd:< Procd pkt 0x20015194: IOCTL Response (28 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =25

Wcd:< Procd pkt 0x20015194: IOCTL Response (32 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =26

Wcd:< Procd pkt 0x20015194: IOCTL Response (37 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

--> WARN:  wwd_sdpcm_send_ioctl L#1030 wwd_sdpcm_send_ioctl() FAILED, retval=2023

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =27

Wcd:< Procd pkt 0x20015194: IOCTL Response (48 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

WLAN MAC Address : 60:23:A4:04:36:75

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =28

Wcd:< Procd pkt 0x20015194: IOCTL Response (232 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

WLAN Firmware    : wl0: May  2 2019 02:39:20 version 7.45.98.83 (r714225 CY) FWID 01-476cc09d

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =29

Wcd:< Procd pkt 0x20015194: IOCTL Response (235 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

WLAN CLM         : API: 12.2 Data: 9.10.39 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2019-05-02 02:30:04

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =30

Wcd:< Procd pkt 0x20015194: IOCTL Response (36 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =31

Wcd:< Procd pkt 0x20015194: IOCTL Response (36 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =32

Wcd:< Procd pkt 0x20015194: IOCTL Response (32 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Init took ~1342 ms

Waiting for scan results...

  # Type  BSSID              RSSI Rate Chan Security               SSID                            CCode    Flag

------------------------------------------------------------------------------------------------------------------

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =33

Wcd:< Procd pkt 0x20015194: IOCTL Response (32 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =34

Wcd:< Procd pkt 0x20015194: IOCTL Response (69 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:> Sending pkt 0x200124B8

Wiced Thread: Woke

Wiced Thread: Woke

Wcd:< Rcvd pkt 0x20015194

credit update =35

Wcd:< Procd pkt 0x20015194: IOCTL Response (106 bytes)

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

Wiced Thread: Woke

--> WARN:  wwd_sdpcm_send_ioctl L#1030 wwd_sdpcm_send_ioctl() FAILED, retval=2004

Wiced Thread: Woke

-------------- TASK  MONITOR --------------

monitor                         X       9       95      6

IDLE                            R       0       40      9

temperature_probe_to_display    B       16      97      2

button_driver                   B       16      33      5

display_driver                  B       24      43      4

mbr_driver                      B       24      61      3

console                         B       8       111     7

tcpip_thread                    B       7       977     13

defaultTask                     B       24      97      1

worker thread                   B       50      91      11

worker thread                   B       52      1755    12

wifi                            B       24      247     8

WWD                             B       55      576     14

Tmr Svc                         B       16      101     10

FreeRTOS Free Heap : 39520 now - 39008 min

-------------------------------------------

Heap Memory : used 8008 / 65536

My system is an STM32F411RE interfaced to the Murata 1DX (based on the Cypress CYW4343W.) The Future Nebula board was the basis for our design and platform.

While I know how to put the STM32F411 into standby and sleep modes, it isn't clear to me what the proper method for putting the WIFI and BLE stacks to sleep is. Is there an SDK call that I should make prior to putting the STM32F411 to sleep? After going into this deep sleep mode, I would like to wake up using the STM32's WKUP pin.

I ran into an error in my application where I received err 2 from wwd_wifi_leave api that corresponds to timeout error. Can you provide feedback on how this can occur and how to overcome this error, as I kept getting this error on every subsequent leave call.

If we used a pre-certified Cypress Wi-Fi modules, do we still need to go thought the  FCC radiator test ?
Or we only need to go through FCC un-intentional radiator  product test only.

And does it  works similar  for CE and other certifications ?

We are using HTTPS for sending ~1K Byte data blocks from STM32F4 over WIFI. Everything works, but occasionally

we see this assert in memp.c    in function:  do_memp_free_pool(),    line 435:

#if defined( LWIP_DEBUG ) && (! defined( LWIP_NOASSERT ) )

  {

      /* Check if the buffer is already in the free list */

      struct memp * tmp_memp = *desc->tab;

      while ( tmp_memp != NULL )

      {

          LWIP_ASSERT( Freeing a buffer that is already freed, tmp_memp != memp );

          tmp_memp = tmp_memp->next;

      }

  }

#endif /* if defined( LWIP_DEBUG ) && (! defined( LWIP_NOASSERT ) ) */

How can we get rid of this assert without interrupting the transfer - our large data file is critical to get to the destination.

We also noticed that this assert is enabled with:  LWIP_DEBUG enabled and LWIP_NOASSERT disabled !

Would it be safe to simply disable this assert ? Appreciate answers from those who have seen this memory leak issue.

--

Thanks, BM