WICED Studio Wi-Fi Combo

Hi,

How do I generate checksum in WICED studio? I know in PSoC Creator, the checksum is stored at the address 0x9030 0000. Is there something similar on WICED Studio?

Thanks!

Dear Cypress/Infineon Team,

We are currently using  CYW43455 Single-Chip 5G WiFi IEEE 802.11n/ac MAC/Baseband/ Radio with Integrated Bluetooth 4.2 module for one of our products.

For the DFS, we are using sequence of commands mentioned in Section 4.2.6. from the Regulatory Manual, Here is the sequence,

wl down
wl ap 1
wl mpc 0
wl country DE
wl band a
wl dfs_preism 1

wl spect 1
wl chanspec 100/20
wl up
wl radar 1
wl ssid DFS_AP
wl status
wl dfs_ism_monitor 0
wl chan_info

However, we observed that when we execute all commands one after the other, "DFS_AP" transmission starts before 60 seconds scan is completed.

As the regulatory manual explains, transmission should not start before 60 seconds irrespective of presence of radar signal on the channel.

Channel Availability Check (CAC) :
This test applies to devices that are capable of detecting radar signals. The Channel Availability Check (CAC) test is
where the radio scans a target DFS channel (that it would like to utilize) for radar signals for a period of 60 seconds.
After the 60 second scan, if no radar signals are detected, the radio can transmit on the target DFS channel.

Is there any specific way, CAC test should be performed? Why the transmission starts before 60 seconds?

Thanks and Regards,

Bhushan Pawar

Hi 

I try to connect to AWS woth Sterling-EWB, WICED SDK 6.6.

When I got the certificate or private key from AWS the stop on  wiced_tls_init_identity() function.

/* initialize credentials list to store credential info */
linked_list_init( &identity->credentials );

if ( credential_info != NULL )
{
if ( ( result = tls_load_certificate_key( identity, credential_info, certificate_data, certificate_length, private_key, key_length ) != WICED_SUCCESS ) )
{
WPRINT_SECURITY_ERROR((" Failed to load certificate & private key \n"));
goto ERROR_INIT;
}
}

In WICED code the list of network that store in DCT is 5 due to the define(CONFIG_AP_LIST_SIZE (5))

I can change this number? to be 50 ?

if I want to store a lot of network what is the recomended way to do this? 

Hi,

We are testing mesh gateway firmware from https://github.com/cypresssemiconductorco/mbed-os-example-bluetooth-mesh-gateway. We are facing a compilation issue with the above firmware. Below is the setup details,

1. System: Windows 10 64Bit

2. Python: Python 3.7.9

We are attaching an error screenshot for your reference. We have tried to remove the "-std=gnu++14" flag from JSON files present in the "mbed-os\tools\profiles" directory but it results in other errors.

Please help with this issue.

Hi to all, i have one CYW943907AEVAL1F that isn't being detected by the USB PC  i follow the next steps 

3.3.2 Troubleshooting
If an error occurred during the automatic driver installation process, the driver may be manually installed from the
following directory: WICED-SDK- Drivers- Windows -wiced_uart.
If the CYW943907AEVAL1F EVK does not appear in the Device Manager, verify that the +3V3 LED is turned
ON and check the USB cable.

the +3V3 LED is turned ON an the USB cable is OK  but the issue still happen

i have other 2  CYW943907AEVAL1F that are working fine 

Question: How can i fix the issue with the bad one 

Since the following error occurred when the program was started, the problem has been resolved by taking the action described in [1].

  ************************************************** **

  ** ERROR: WLAN: could not download clm_blob file

  ** FATAL ERROR: system unusable, CLM blob file not found or corrupted.

  ************************************************** **

[1]Details of support

   When the Wi-Fi FW was updated, an error occurred due to an inconsistency between the placement of memory sectors managed by the application and the placement of external Flash.

  "RESOURCES_LOCATION ? = RESOURCES_IN_WICEDFS", the external Flash could not be updated, which resulted in the inconsistency.

   Changed the setting to "RESOURCES_LOCATION ? = By changing the configuration to "RESOURCES_IN_DIRECT_RESOURCES", the error will not occur.

   Because the build error occurred when the above settings were changed, added the following settings so that the LUT can be written to the external Flash.

   -----

   /tools/makefiles/standard_platform_targets.mk

   #ifeq ($(RESOURCES_LOCATION),RESOURCES_IN_WICEDFS)

   download: $(STRIPPED_LINK_OUTPUT_FILE) display_map_summary download_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,download_dct) APPS_LUT_DOWNLOAD

   #else

   #download: $(STRIPPED_LINK_OUTPUT_FILE) display_map_summary download_bootloader $(if $(findstring no_dct,$(MAKECMDGOALS)),,download_dct)

   #endif

   -----

[2] Confirmation

   There is a confirmation of the behavior when the software with "RESOURCES_IN_DIRECT_RESOURCES" is updated against the module with "RESOURCES_IN_WICEDFS" set.

   It works with the current configuration, but I'm not sure how WICED affects it, so I'm asking.

1. If you set "RESOURCES_IN_DIRECT_RESOURCES", the filesystem will be included in the application and no inconsistency will occur?

2. Update "RESOURCES_IN_DIRECT_RESOURCES" software to "RESOURCES_IN_WICEDFS" module.

  If I update the software again in this state, is it correct that "FR_APP" will not be destroyed when updating to APP0 because the LUT of the external flash will not be changed?

Hi,

We have problems setting up debugging. 

We use WICED 6.4.0.61, and our target is STM32F427II on custom HW platform.

We can program target with both Olimex ARM-USB-TINY-H and Segger J-link Ultra+ via Segger driver. RTOS is ThreadX. 

Now we need to be able to debug the application. We are to single step until rtos is startet, then we stop at 

Program received signal SIGTRAP, Trace/breakpoint trap.
0x08046356 in mbedtls_pem_read_buffer (ctx=0x0, header=<optimized out>, footer=<optimized out>, data=<optimized out>, pwd=0xc1 "\004", pwdlen=1414025796, use_len=0x0) at WICED/security/BESL/mbedtls_open/library/pem.c:330
330 return( MBEDTLS_ERR_PEM_ALLOC_FAILED );

Note, when not debugging, the application continue running.

Yours sincerely,

Anton