Wi-Fi Combo Forum Discussions

Hello, we've had some breakthroughs with the configuration of our module CYW43455 on our custom board. We've been able to setup an Access Point on the 5Ghz band and it was possible to connect to it and have traffic to the internet via the wan interface.

But now we need also to setup the 2.4 Ghz band, and the situation here es that we don't see it available on the Openwrt Wireless Overview

Now, our question would be if it is necessary to do something in particular to startup the second radio for the other band, or if it should start automatically, then what could we be missing this time?

Thank you.

Does murata1LD board support Toshiba 4Gb serial nand flash  with part number TC58CVG2S0HRAIJ?
 

Dear Cypress support,

I am running WICED on a custom platform board and I noticed that the WICED application is dependent on a DCT.

In our project we don't want to use the WICED bootloader and also not the DCT. We have our own bootloader and our own standard mechanism of updating applications. We have our own linker scripts and WICED is already customized so it uses our own style of linking.

Currently we have our own bootloader, the wiced bootloader and the wiced application. I noticed that the wiced application creates a default DCT at 0x0800C000, equal to region FLASH_DCT1. Our memory map looks like this

MEMORY {
FLASH_DEVICE (rx) : o = 0x08000000 /* FLASH_ORIGIN */ , l = 1m /* FLASH_SIZE size of flash of device */
FLASH_BL (rx) : o = 0x08000000 /* FLASH_ORIGIN */ , l = 32K /* boot loader size, normal build */
FLASH_DCT1 (rx) : o = 0x08000000 + 32K /* FLASH_ORIGIN + OFFSET_BL */ , l = 16K /* DCT1 size */
FLASH_DCT2 (rx) : o = 0x08000000 + 32K + 16K /* FLASH_ORIGIN + OFFSET_BL + OFFSET_DCT1 */ , l = 16K /* DCT2 size */
FLASH_BL_WICED (rx) : o = 0x08000000 + 32K + 16K + 16K /* FLASH_ORIGIN + OFFSET_BL + OFFSET_DCTS1+2 */ , l = 16K /* WICED bootloader size, normal build */
FLASH_APL (rx) : o = 0x08000000 + 128K /* FLASH_ORIGIN + OFFSET_FW */ , l = 1m - 128K - 0 /* FLASH_SIZE - OFFSET_FW - NVM, normal build */
RAM_DEVICE (rwx) : o = 0x20000000 /* RAM_ORIGIN */ , l = 256K /* RAM_SIZE */
RAM_BL (rwx) : o = 0x20000000 + 256 /* RAM_ORIGIN + MAX_NO_INIT_FW*/ , l = 256K - 256 /* RAM_SIZE - MAX_NO_INIT_FW */

RAM_BL_WICED (rwx) : o = 0x20000000 /* RAM_ORIGIN */ , l = 256K /* 256 bytes reserved for no_init */
RAM_APL (rwx) : o = 0x20000000 /* RAM_ORIGIN */ , l = 256K /* 256 bytes reserved for no_init */
}

We don't use the DCT anywhere in our application.

My questions:

• Is there a compile flag or define for our platform so a DCT is NOT build
• Is there a compile flag to not build the bootloader?
• How can we remove the dependency of the WICED bootloader
• How can we remove the dependency of the DCT
  • If not possible, can you show how to put a DCT inside the wiced application. Perhaps statically allocated so at least the application starts?

Is it really necessary for our application to reserve 32K (two times 16K) of memory for around 405 bytes?

(sizeof(platform_dct_header_t) +  sizeof(platform_dct_version_t) + sizeof( zero_byte ))

Hi,

We are using STM32F412 based platform and running WICED threadx OS based application on it. We wanted to measure the CPU load used by the application. So we tried to use Tracelyzer tool after enabling TX_ENABLE_EVENT_TRACE macro. Then we are getting  the below linking error.

undefined reference to `wiced_tracex_enable'

So where can we get  the definition for `wiced_tracex_enable'? Is it part of a separate library?

Also please let us know if there is any alternate ways for measuring the CPU load.

Regards,

Srinivas

I tried to do everything as instructed.

Here are a few of the installation screenshots:

No icon is created.

No message is shown.

What should I try next?

Hi team I am using murata Type1LD Wifi module - Wiced studio 6.2

I plan to use wifi module internal flash for store around 2KB data of data .

Any one have sample code for internal flash read/write  .

Please help.

Thanks and Regards

Ravi S

Hi All,
I want to randomize the initial value of TCP Sequence number.

[Background]
Currently, the TCP initial sequence number (ISN) always starts from "0" when starting TCP connection  immediately after reseting the wifi-module .
In order to connect to  the Server that supports "Defending Against Sequence Number Attacks",
I want to randomize the initial value of TCP Sequence number.

Software environment:
        - WICED 6.2.1
        - LwIP

Hardware environment:
        - murata type-1LD wifi-module

[Question]
Which part of the source code should I change ?

-----------------------------
I checked the following, but regarding the TCP sequence number,
it doesn't seem to be processed in particular.

/43xxx_Wi-Fi/WICED/network/LwIP/WICED/tcpip.c

Best Regards,
       Sakagami

I am working on WICED secure bootloader.

In wided studio sdk is uEcc is buit-in available?

If yes how to enable and utilize in application code.