Wi-Fi Combo Forum Discussions
Hi,
Hi, i am using wiced sdk 3.5.2 and in this mainly the Bluetooth part.
Similarly one of my colleague also is using the same.
(both being BCM4343 modules)
What i have observed is, even though we change the name of the bluetooth device in each of our firmwares, the bd address (local address) of both the modules are the same.
And because of this, we are not able to work in the same area. (mobiles are getting paired to the other person's module)
So can you please help in this matter?
Is there a way to change the local address (bd addr)?
Thanks in Advance,
Sindhu
Show LessHi there,
We have tested BLE using the BCM43438 (A1) chip and SDK 3.5.2, the BLE power consumption is still very high, we cannot say it is Low Energy.
We want to know how to use BT_HOST_WAKE and BT_DEV_WAKE pins? Are they used for powering down the chip?
Thanks in advance for any input.
Show LessHi,
I'm working with EMW3165 and now I've created my own IRQ handler for USART using the libraries of the MCU (stm32f4xx).
I've added the following definition in platform.c
WWD_RTOS_DEFINE_ISR(juanpi_USART6_IRQHandler)
{
USART6_IRQHandler();
}
WWD_RTOS_MAP_ISR(juanpi_USART6_IRQHandler, USART1_irq)
The definition of USART6_IRQHandler() is in the files
apps/Juanpi_UART_test/drivers/juanpi_ISR.c
apps/Juanpi_UART_test/drivers/juanpi_ISR.h
I've include the header file in the platform.c (#include "juanpi_ISR.h"),
and also add a path to the project to the apps/Juanpi_UART_test/drivers folder but doesn't work:
MAKEFILE MAKECMDGOALS=Juanpi_UART_test-EMW3165 OTA2_SUPPORT is disabled
Building Bootloader
platforms/EMW3165/platform.c:12:24: fatal error: juanpi_ISR.h: No such file or directory
#include "juanpi_ISR.h"
Where is the problem ? I have to edit any .mk file ? How ?
Thanks,
Juan Pablo
Show LessDownloading 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. ****"
Resetting target
tools/makefiles/standard_platform_targets.mk:108: recipe for target 'run' failed
make.exe[1]: *** [run] Error 1
Makefile:220: recipe for target 'main_app' failed
make: *** [main_app] Error 2
13:42:38 Build Finished (took 33s.10ms)
Show LessCan anyone tell me the best way to get a Broadcom EVAL board connected to Azure?
AMQP doesn't appear to be ready for prime time.
What is the fastest way to send data to Azure via HTTP(s)?
has anyone ported the MicroSoft SDK API the the WICED environment?
Thanks
Show LessI'd like to do performance testing with simultaneous Bluetooth and WiFi. Is there a suggested setup or demo app that can help me on this, or do I need to create my own?
Ideally, I'd like a WiFi loopback running simultaneously with a Bluetooth and BLE loopbacks (create servers for each).
I get lost crawling through the SDK; is there a set of documentation on all of the samples and applications in it? NOOB question, I know...
Thanks!
Bill
Show LessHi,
I am using WICED 3.4.0 on EMW3165 platform, i know this is not yet officially supported WICED platform...
I intend to use SPI5 with DMA as a slave.. Can anybody throw light as how i can do this easily?? somewhere i read SPI4 and SPI5 are not supported by WICED platform itself...
Any information, example codes on the same would be really appreciated.
Thanks,
Raghu
Show LessPorting a board platform from 3.0.1 to 3.5.2 and wiced_init returns 2 WIFI init issue?
The call path is:
wiced_init()
wiced_wlan_connectivity_init()
wwd_management_wifi_on()
wwd_management_wifi_platform_init()
wwd_bus_init()
and it appears that the problem is occuring in wwd_bus_init()
and the return value if wiced_init() is 2 which is TIMEOUT which implies that some sort of handshake is not occurring properly between the STM32F411 and the 943362.
All the pins look correctly in wifi_spi_pins and none of that was changed.
I don't think the bootstrap pins are connected per a schematic and I tried various combinations of changing the existing
#define WICED_WIFI_USE_GPIO_FOR_BOOTSTRAP
to
#define WICED_WIFI_USE_GPIO_FOR_BOOTSTRAP_0
#define WICED_WIFI_USE_GPIO_FOR_BOOTSTRAP_1
with no good result.
The bootstrap pins are defined, but I think that's a legacy stamp copy as they don't appear to be connected to anything.
I didn't change anything in the wifi_nvram_image.h file. and even did try substituting the slightly different values in 3 places from BCM943362WCD6
and that didn't get rid of the TIMEOUT either.
Any thoughts of what else I should look at when porting a board platform from 3.0.1 to 3.5.2?
And is that the correct terminology "board platform" so as to distinguish it from a "MCU platform"?
Show LessHi.
I tested the snip.link_status.
Link_up the first event does not occur even though the connection to the AP during boot-up.
However, when off the AP, link_down event is generated.
When the AP on in this state, link_up event does not occur.
Why link_up events do not occur?
Attach the log below.
Starting WICED v3.3.1
Platform MurataTypeYD initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp2
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : FC:DB:B3:7D:E1:01
WLAN Firmware : wl0: Nov 7 2014 16:03:45 version 5.90.230.12 FWID 01-0
Joining : samwoo_R&D
Successfully joined : samwoo_R&D
Obtaining IPv4 address via DHCP
DHCP CLIENT hostname WICED IP
IPv4 network ready IP: 192.168.0.135
Setting IPv6 link-local address
IPv6 network ready IP: FE80:0000:0000:0000:FEDB:B3FF:FE7D:E101
Switch your AP off
Network connection is down.
Switch on your AP and wait until the connection is up.
Show Less