Wi-Fi Combo Forum Discussions
I am just starting to modify an example project from the "43xxx_Wi-Fi" example projects in WICED Studio 6.4. I would like to use some sort of version control to keep track of the project. So far I've been editing a copy of the original project that exists in the same directory as the original. Ideally I would like to host a repository on BitBucket. If that is not possible, what is the best approach for version control of a WICED project?
Show LessHi,
I'm using Wiced SDK 3.5.2. I'm trying to flash images using stlink-v2(embedded on stm32f4 discovery board.)
Suppose i have blinky code built using keil, I can flash the image using command line as
start /B ./tools/OpenOCD/Win32/openocd-0.8.0.exe -f ./tools/OpenOCD/stlink-v2.cfg -f ./tools/OpenOCD/stm32f4x_stlink.cfg -f ./tools/OpenOCD/stm32f4x-flash-app.cfg -c init targets -c "halt" -c "program ./tools/OpenOCD/Win32/Blinky.hex" -c "reset run" -c "shutdown"
And it works!!
I downloaded the openocd-0.8.0 and performed the following
- uzipped the zip file
- Placed the openocd-0.8.0.exe(from extracted) to the /tools/OpenOCD/Win32/
- Placed the stlink-v2.cfg(from openocd-0.8.0\scripts\interface) to /tools/OpenOCD/
- Placed the stm32f4x_stlink.cfg and stm32_stlink.cfg(openocd-0.8.0\scripts\target) and placed in to /tools/OpenOCD/
Then i tried to figure out the macros "OPENOCD_INTERFACE & OPENOCD_TARGET" but could ,and hence was unable follow the steps further . I just replaced the OPENOCD_FULL_NAME as
- OPENOCD_FULL_NAME := $(OPENOCD_PATH)Win32/openocd-0.8.0.exe
This does not seems to work and I get following errors.
Downloading Bootloader ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading DCT ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading Application ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Build complete
Making .gdbinit
Can you please elaborate to the steps preferable with exact changes in make file with example. Kindly help in this regard.
Waiting for response.
Thanks,
Nishal
Show LessHi:
as we know, we can compile some codes which we add in a project by some macros
for example. in the wiced studio SDK, there are many application project for example mesh_level_client, mesh_onoff_server and so on ! however some codes are the common codes for example device provisioning codes for this projects !
I want to add some codes for the mesh_onoff_server project during device provisoining ,but I don't want to affect other projects
Show LessI'm using a CYW943907AEVAL1F board to evaluate using CYW43907 in an upcoming board design. I'm using the latest release of WICED Studio.
My application needs to transmit and receive raw 802.11 frames including the layer 2 (MAC) header. I have a working example of receiving frames in monitor mode using wwd_wifi_set_raw_packet_processor() and wwd_wifi_enable_monitor_mode(). This is based on the snip.packet_filter example code. Unfortunately, I need a few hooks that I can't find digging through the SDK which may make this part not feasible for this project.
- If I call wwd_wifi_set_channel() before entering monitor mode, will the transceiver stay tuned to the requested channel while monitor mode is active? If so, can I later call wwd_wifi_set_channel() again without exiting monitor mode, so I can capture packets for fixed time intervals on different channels?
- When I'm receiving raw frames in monitor mode, how can I query RSSI for each received frame, or in some way differentiate the receive power of incoming frames?
- This question is not related to monitor mode - it is about raw frame transmission. How can I transmit a raw 802.11 frame that is not data. My application will create a custom 802.11 management frame (providing its own complete and valid 802.11 MAC header) that I need to transmit on a specified channel. This is not a data frame and does not have an Ethernet header, so the wwd_network_send_ethernet_data() function does not seem appropriate.
For what it's worth, I also sent these questions in a direct technical support case and received a terse and discouraging response, "We do not recommend using Monitor mode in CYW43907 as it is not tested." I'm not exactly sure what to make of that.
Finally, if the CYW43907 cannot do what I need, are there any other Wireless MCU parts that you'd recommend for this use case? The application will be RTOS-based or bare-metal. The CYW43907 is a very enticing solution with its Cortex-R application core, plentiful on-chip SRAM, and rich set of I/O peripheral support. Other Wireless MCUs on the market are much less performant.
Thank you,
David
Show LessSupport Gurus:
Where is the best place to add some command line options to the make process in Wiced?
I want to add something like:
objcopy -j .text -j .data -O ihex <input-file.elf> <output-file.hex>
to the "make command file" to generate a Hex file from ELF file, since this feature has not been implemented in the Wiced Studio package.
I have found the “tools / makefiles” folder, but there are so many “mk” files that it is too confusing to figure out which one to use, and which line to modify, or even if that is the correct place. I want the Hex files to be generated ALL THE TIME, no matter what project I am making.
Any help would be appreciated.
Thanks,
Garry Anderson
Show LessHi,
The latest wiced-studio-6.4 supports WPA3 so I'm wondering if the device running latest
sdk has impacted by the vulnerabilities of WPA3.
See below references:
https://www.technadu.com/researchers-five-vulnerabilities-wifi-wpa3-standard/64460/
https://www.technadu.com/two-dragonblood-vulnerabilities-wpa3-wi-fi-standard/75933/
Show LessHi,
I want to change the BCM94343WWCD2 EVB CPU freq (96MHz to 48 MHz)
I change the CPU_CLOCK_HZ (and some PLL paramers) in platform_config.h
But got error msg about watchdog
it seems doesn't define the DBG_WATCHDOG_TIMEOUT_MULTIPLIER in platform_watchdog.c:
#if (CPU_CLOCK_HZ == 120000000)
#define DBG_WATCHDOG_TIMEOUT_MULTIPLIER (2250)
#elif (CPU_CLOCK_HZ == 100000000)
#define DBG_WATCHDOG_TIMEOUT_MULTIPLIER (1875)
#elif (CPU_CLOCK_HZ == 96000000)
#define DBG_WATCHDOG_TIMEOUT_MULTIPLIER (3600)
how should I define the DBG_WATCHDOG_TIMEOUT_MULTIPLIER with CPU_CLOCK_HZ == 48000000?
Thanks.
Randy
Show Less