Wi-Fi Combo Forum Discussions
Hi,
We are using Cypress 43455 (murrata 1MW) with NXP MCU with Wiced SDK. We are trying to connect wifi module with a wifi router configured in AC only mode but are not able to do so. We are able to scan the router but join attempts to the router always fails. We have observed that if we set the country code as USA on the module side we are able to connect to router.
We have tried to make sure that the country selection on router and module match but we don't see any success. We are able to use all the other modes (N, A, mixed etc) with other country code but not AC.
What could be the solution for this? We want to set the country code as UK and run AC mode. What are we missing here?
Firmware and CLM blob information:
WLAN Firmware | : wl0: May 2 2019 02:46:20 version 7.45.189 (r714228 CY) FWID 01-105ab14e |
WLAN CLM | : API: 12.2 Data: 9.10.136 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2019-05-02 02:31:24 |
Regards
Show LessHello.
I've bought CYW943907AEVAL1F and I developed a firmware that use WiFi and USB as CDC-ACM.
I create some threads using 1024 as stack size.
I observe that WICED resets when I send a particular TCP packet to one of my thread that is waiting for TCP packet.
Today I launch debugger and I notice that there is a "threadx stack overflow". So I decide to increase this thread stack size progressively. This problems disappears when I set thread stack size to 2048.
I observe this problem in another thread , so I have to increase "thread stack size" for this other thread.
My question is : it is possibile that I have to use so large stack size ?
Show LessHello.
I've bought CYW943907EVAL1F board and I've developed simple firmware that configure SPI.
I want to use DMA for the SPI in order to unload CPU work.
I configure spi in this way
spi_fpga.port = WICED_SPI_1;
spi_fpga.chip_select = WICED_GPIO_NONE;
spi_fpga.speed = 5e6;
spi_fpga.mode = SPI_CLOCK_RISING_EDGE | SPI_CLOCK_IDLE_HIGH | SPI_USE_DMA | SPI_MSB_FIRST | SPI_CS_ACTIVE_LOW; /* see Document Number 002-14829 Rev. *K page 22 */
spi_fpga.bits = 8;
/* init 'spi_fpga' spi */
status = wiced_spi_init ( &spi_fpga );
Today I launch debugger but I observe this strange assert:
The problemi is that "( config->mode & SPI_USE_DMA ) == 0" is not true and so the assertion fail.
What I'm wrong ?
I have to not use DMA ?
Show LessHello,
I am using CYW954907AEVAL1F dev board and want to connect to MQTT via web socket.
I see that the current WICED SDK only supports native MQTT, and in AWS there is an option for MQTT via web socket, but no implementation yet.
Is there any API in WICED SDK or any available MQTT lib for connecting MQTT via web socket with my board, or I have to implement it on my own?
Show LessHello,
I read datasheet (Document Number: 002-14829 Rev. *L) at page 38
PWM_0 seems to be an output
Also on MURATA datasheet (SP-UZ1GC-S) at page 10
On demo board PWM_0 is used as input (USD_DETECT)
And in the firmware WICED I read on platform.h
|---------------+-----+--------------+-----+-------------------------+--------------------------+--------+--------------+-------------------------------|------------------|
| WICED_GPIO_13 | 185 | PWM_0 | C10 | PWM_0 | PWM_0 | N/C | PWM, GPIO | uSD Connector/Slot Detect | |
|---------------+-----+--------------+-----+-------------------------+--------------------------+--------+--------------+-------------------------------|------------------|
And in the EVM PWM_0 can be configured as input and it works correctly.
Show LessHello,
I've bought CYW943907AEVAL1F board.
I develop a firmware that manipulate a mutex (wiced_rtos_lock_mutex) and manipulate a queue (wiced_rtos_push_to_queue) in a ISR (interrupt service routine) but each API calls get me errors:
wiced_rtos_lock_mutex returns 4 (WICED_ERROR)
wiced_rtos_push_to_queue returns 1032 (WICED_QUEUE_ERROR)
I suspect that I can't manipulate mutex or queue in a ISR (interrupt service routine) ...
can you confirm this ?
Thankyou.
Show Less
Hello,
It seems that CYW94343WWCD1_EVB platform has been removed from WICED Studio 6.6.0.9.
Any reason why?
How to evaluate WICED 6.6 on this platform?
Show Less
On an STM32F4 based board...
When hitting ota2_bootloader.c::ota2_failsafe_app_load() the entry point is a flash address 0x800c3e5 but it hasn't been loaded into internal flash from SFlash. I see ota2_failsafe_app_load() erasing (internal?) flash:
/* Erase the application area */
result = ota2_failsafe_app_area_erase( flash_location, &header );
Then reading into RAM from flash:
result = ota2_failsafe_app_read( flash_location, (uint8_t*)prog_header.physical_address, prog_header.data_offset, prog_header.data_size_in_file );
But danged if it's obvious how internal flash get's written! It is quite clear in wiced_waf_common.c::wiced_waf_app_load():
result = platform_load_app_chunk( app_header_location, offset, (void*) prog_header.physical_address, prog_header.data_size_in_file );
Thanks!
Geoff
Show Less