Wi-Fi Combo Forum Discussions
I build pwm from 101 tutorial. All other programs worked, event PuTTY up to this point. Attached is error, .mk and .c.
Error
10:24:51 **** Build of configuration Default for project 43xxx_Wi-Fi ****
"C:\\Users\\Al\\Documents\\WICED-Studio-6.2\\43xxx_Wi-Fi\\make.exe" ww101.02.09_pwm-CYW94343WWCD1_EVB download
MAKEFILE MAKECMDGOALS=ww101.02.09_pwm-CYW94343WWCD1_EVB download OTA2_SUPPORT is disabled
Building Bootloader
Building Serial Flash Loader App
MAKEFILE MAKECMDGOALS=waf.sflash_write-NoOS-CYW94343WWCD1_EVB-SDIO OTA2_SUPPORT is disabled
Finished Building Bootloader
- waf.sflash_write-NoOS-CYW94343WWCD1_EVB-SDIO
----------------------------------|---------|
| Static |
Module | RAM |
----------------------------------+---------|
App | 21130 |
Host MCU-family library | 11604 |
Interrupt Vectors | 388 |
libc | 556 |
platform | 1104 |
Ring_Buffer | 40 |
SPI_Flash_Library_CYW94343WWCD1_EV| 936 |
Startup Stack & Link Script fill | 486 |
WWD | 188 |
----------------------------------+---------|
TOTAL (bytes) | 36432 |
----------------------------------|---------|
Compiling apps_ww101_02_09_pwm
Build complete
Finished Building Serial Flash Loader App
apps/ww101/02/09_pwm/09_pwm.c: In function 'application_start':
apps/ww101/02/09_pwm/09_pwm.c:11:27: error: 'PWM_PIN' undeclared (first use in this function)
wiced_pwm_init(PWM_PIN, 1000, duty_cycle);
^~~~~~~
apps/ww101/02/09_pwm/09_pwm.c:11:27: note: each undeclared identifier is reported only once for each function it appears in
tools/makefiles/wiced_elf.mk:232: recipe for target 'build/ww101.02.09_pwm-CYW94343WWCD1_EVB/Modules/apps/ww101/02/09_pwm/09_pwm.o' failed
- make.exe[1]: *** [build/ww101.02.09_pwm-CYW94343WWCD1_EVB/Modules/apps/ww101/02/09_pwm/09_pwm.o] Error 1
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2
10:24:53 Build Finished (took 2s.184ms)
09_pwm.mk
NAME := apps_ww101_02_09_pwm
$(NAME)_SOURCES := 09_pwm.c
09_pwm.c
#include "wiced.h"
void application_start( )
{
float duty_cycle = 50.0;
wiced_init( );
wiced_gpio_deinit( WICED_LED1 );
while(1)
{
wiced_pwm_init(PWM_PIN, 1000, duty_cycle);
wiced_pwm_start(PWM_PIN);
duty_cycle += 1.0;
if(duty_cycle > 100.0)
{
duty_cycle = 0.0;
}
wiced_rtos_delay_milliseconds( 10);
}
}
Show LessPer this thread that has not been updated: Not able to install sdk-6.2 on Linux64
I still have the same issue on 6.2.1. Did I miss the fix?
Show LessNot able to install it on linux-64.
I'm sure I have enough free space , but it keep shows below dialog.
I have 8.4GB free space, but the dialog shows I have 879BM?
BTW, what is "BM"??
ps. I have no problem to install older SDKs on the same PC, no idea why it does not work with sdk-6.2.
Show Less
Hello,
we're developing a standalone PcB to monitor WiFi devices based on the management frames they are sending out (Probe Requests mainly).
We currently using the BCM943362WCD4_EVB Dev Board (BCM943362 chip) with WICED Studio Version 6.2.1.2.
We're initiating monitor mode on the board and print the output as suggested in the sample application snip/packet_filter.
Here is a piece of the code:
static const wiced_packet_filter_t anti_beacon = {
.id = 1,
.rule = WICED_PACKET_FILTER_RULE_NEGATIVE_MATCHING, // Negative match
.offset = 0,
.mask_size = 1, // 2
.mask = (uint8_t*)"\xff",
.pattern = (uint8_t*)"\x80",
};
char filter_list[] = {1};
void application_start() {
wiced_init();
wwd_wifi_select_antenna (WICED_ANTENNA_1);
/* Mission Complete, disable & uninstall filters */
pktfilter_disable(filter_list, sizeof(filter_list));
pktfilter_remove(filter_list, sizeof(filter_list));
/* Filter settings */
wiced_wifi_set_packet_filter_mode( WICED_PACKET_FILTER_MODE_FORWARD );
wiced_wifi_add_packet_filter( &anti_beacon );
/* Register callback for packets that match filters */
wwd_wifi_set_raw_packet_processor(raw_packet_callback);
memset(&workspace->sniff_complete, 0, sizeof(workspace->sniff_complete));
wiced_rtos_init_semaphore(&workspace->sniff_complete);
/* Enable Filters */
pktfilter_enable(filter_list, sizeof(filter_list));
/* Display current filter settings */
print_packet_filter_list();
/* Demonstrate filters are all zeros to start. */
pktfilter_stats(filter_list, sizeof(filter_list));
/* Enable monitor mode so we will recieve the packets */
wwd_wifi_set_channel( WICED_STA_INTERFACE, 6); //
wwd_wifi_enable_monitor_mode();
// /* Collect packets for 5 seconds. */
wiced_rtos_get_semaphore(&workspace->sniff_complete, 50 * 1000);
//
// /* Done sniffing. Disable monitor mode */
wwd_wifi_disable_monitor_mode();
//
// /* Show number of hits. Note that even without monitor mode the stats will still show number of matches. */
pktfilter_stats(filter_list, sizeof(filter_list));
//
// /* Deregister our callback routine */
wwd_wifi_set_raw_packet_processor( NULL);
//
// /* Mission Complete, disable & uninstall filters */
pktfilter_disable(filter_list, sizeof(filter_list));
pktfilter_remove(filter_list, sizeof(filter_list));
//
wiced_rtos_deinit_semaphore(&workspace->sniff_complete);
}
We're receiving beacon frames, probe responses and other frames just fine, but we're not getting any Probe Requests sent to the broadcast address (receiver address and bssid set to ff:ff:ff:ff:ff:ff). Probe requests sent to any other Destination/BSSID are being received and displayed correctly.
Specifically, any frames with a receiver address starting with 'ff' (e.g. 'ff:aa:aa:aa:aa:aa) seem to be discarded and are not passed to the callback function. Probe requests sent to any other Receiver Address (e.g. 'fa:aa:aa:aa:aa:aa') are being received and displayed correctly.
We also try to get this working, without any packet filter on a less frequented channel, there where also no or less Probe Request Frames.
At the next point, we compare the output of the Dev Board Chip with an ESP6288 with a filter on probe requests - the ESP collect all of them.
Is there a configuration option/flag we have to set to receive Probe Requests sent to broadcast addresses (the VAST majority of probe requests), is this a limitation inposed by WICED or could this be a limitation from the chipset?
Thanks in advance for any help.
Show Lesswhen I use then mode ---WWD_DIRECT_RESOURCES-- ,how can I confirm the address of firmware ?
could you tell Me the difference about the tow mode(download firmware )?
Show LessHi,
I'm new to WICED sdk. I tried to update my SDK from 3.6 to 6.2. I have installed the 6.2 IDE. imported my 3.6 code.
I tried to build the code and i'm getting below error message. Please any one help me to understand and resolve this problem.
I know it is showing "pers_dct.h" is not included. but it present in the code.
May i know is there any update is needed in make file? and which mk file I need to update.
13:40:17 **** Build of configuration Default for project 43xxx_Wi-Fi ****
"C:\\Projects\\MHB3.0\\CodeDoc\\OTA\\FOTA2.0branch_unchanged\\WICED\\43xxx_Wi-Fi\\make.exe" snip.pers-BCM943909WCD1_3.B1-ThreadX-NetX_Duo-debug ota2_download
MAKEFILE MAKECMDGOALS=snip.pers-BCM943909WCD1_3.B1-ThreadX-NetX_Duo-debug ota2_download OTA2_SUPPORT is enabled
Updating ota2 bootloader version...
Updating application version...
Building Bootloader waf.ota2_bootloader-NoOS-NoNS-BCM943909WCD1_3.B1-SoC.43909
Building Serial Flash Loader App
Finished Building Serial Flash Loader App
apps/waf/ota2_bootloader/./ota2_bootloader.c:59:22: fatal error: pers_dct.h: No such file or directory
#include "pers_dct.h"
^
compilation terminated.
make.exe[3]: *** [build/waf.ota2_bootloader-NoOS-NoNS-BCM943909WCD1_3.B1-SoC.43909/Modules/apps/waf/ota2_bootloader/./ota2_bootloader.o] Error 1
make.exe[3]: *** Waiting for unfinished jobs....
make.exe[2]: *** [main_app] Error 2
make.exe[1]: *** [bootloader] Error 2
WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:256: recipe for target 'bootloader' failed
Makefile:354: recipe for target 'main_app' failed
make: *** [main_app] Error 2
Thanks and regards,
Basava
Show LessIn creating a new platform for an STM32F429 with a Murrata 1DX target board, I have questions on how to find the right label to add for new ISRs handler mapping that aren't defined in the example.
This is the example that I started with
/******************************************************
* Interrupt Handlers Mapping
******************************************************/
/* These DMA assignments can be found STM32F4xx datasheet DMA section */
WWD_RTOS_MAP_ISR( usart1_irq , USART1_irq )
WWD_RTOS_MAP_ISR( usart2_irq , USART2_irq )
WWD_RTOS_MAP_ISR( usart3_irq , USART3_irq )
WWD_RTOS_MAP_ISR( uart7_irq , UART7_irq )
WWD_RTOS_MAP_ISR( usart3_rx_uart7_tx_dma_irq, DMA1_Stream1_irq )
WWD_RTOS_MAP_ISR( uart7_rx_dma_irq , DMA1_Stream3_irq )
WWD_RTOS_MAP_ISR( usart3_tx_uart4_tx_dma_irq, DMA1_Stream4_irq )
WWD_RTOS_MAP_ISR( usart1_rx_dma_irq , DMA2_Stream2_irq )
WWD_RTOS_MAP_ISR( usart2_rx_dma_irq , DMA1_Stream5_irq )
WWD_RTOS_MAP_ISR( usart2_tx_dma_irq , DMA1_Stream6_irq )
WWD_RTOS_MAP_ISR( usart1_tx_dma_irq , DMA2_Stream7_irq )
I would like to add I2C, SPI and 5 GPIO interrupts . This is what I think they might be, but how do it checkj. Where is the values in the example come from.
/* These DMA assignments can be found STM32F4xx datasheet DMA section */
WWD_RTOS_MAP_ISR( usart1_irq , USART1_irq )
WWD_RTOS_MAP_ISR( usart3_irq , USART3_irq )
WWD_RTOS_MAP_ISR( uart7_irq , UART7_irq )
WWD_RTOS_MAP_ISR( uart7_rx_dma_irq , DMA1_Stream3_irq )
WWD_RTOS_MAP_ISR( usart3_rx_uart7_tx_dma_irq, DMA1_Stream1_irq )
WWD_RTOS_MAP_ISR( usart1_rx_dma_irq , DMA2_Stream2_irq )
WWD_RTOS_MAP_ISR( usart1_tx_dma_irq , DMA2_Stream7_irq )
/*
WWD_RTOS_MAP_ISR( i2c1_irq , I2C1_ER_irq )
WWD_RTOS_MAP_ISR( i2c1_tx_dma_irq , DMA1_Stream7_irq )
WWD_RTOS_MAP_ISR( i2c1_rx_dma_irq , DMA1_Stream0_irq )
WWD_RTOS_MAP_ISR( spi2_irq , SPI2_irq )
WWD_RTOS_MAP_ISR( spi2_tx_dma_irq , DMA1_Stream4_irq )
WWD_RTOS_MAP_ISR( spi4_tx_dma_irq , DMA2_Stream1_irq )
WWD_RTOS_MAP_ISR( spi4_rx_dma_irq , DMA2_Stream0_irq )
WWD_RTOS_MAP_ISR( spi5_tx_dma_irq , DMA2_Stream4_irq )
WWD_RTOS_MAP_ISR( spi5_rx_dma_irq , DMA2_Stream5_irq )
WWD_RTOS_MAP_ISR( gpio_irq , EXTI0_irq )
WWD_RTOS_MAP_ISR( gpio_irq , EXTI1_irq )
WWD_RTOS_MAP_ISR( gpio_irq , EXTI3_irq )
WWD_RTOS_MAP_ISR( gpio_irq , EXTI4_irq )
WWD_RTOS_MAP_ISR( gpio_irq , EXTI9_5_irq )
Show LessHello,
we were discussing HW host interface and discovered, that there used to be SPI interface supported on CYW43364 side, but it has been removed from the datasheet in revision D. Can you help us understand if there is possible to use SPI or only SDIO?
Thanks,
J.
Show LessI have a new target board with STM32F429 and 1DX module and will need to download code. I have a J-Link programmer / debugger and want to program with a hex file. I can't find a hex file, only elf and bin in the build folder. How do I get a hex file?
Show Less