Wi-Fi Combo Forum Discussions
Where can I download WICED 3.4 or 3.5?
Struggling to modify the xively code because some of the libraries are not accessible/available in the SDK files via the eclipse IDE.
Am I missing something?
I'd like to re-jig for phant.io but can't find any suitable code and unable to modify the existing hidden code.
Show LessHello,
for building OpenOCD, i was running './build_all.sh' script using MINGW, Msys, Git. tools in 32-bit Windows System,
but below build error message is printed.
maybe, 'just_libusb.sh' script is built, this error message is printed.
---------------------------------------------------------------
../../libusb-1.0.19/libusb/os/windows_usb.c: In function 'get_windows_version':
../../libusb-1.0.19/libusb/os/windows_usb.c:850:4: error: implicit declaration o
f function 'VerSetConditionMask' [-Werror=implicit-function-declaration]
major_equal = VerSetConditionMask(0, VER_MAJORVERSION, VER_EQUAL);
^
../../libusb-1.0.19/libusb/os/windows_usb.c:850:41: error: 'VER_MAJORVERSION' un
declared (first use in this function)
major_equal = VerSetConditionMask(0, VER_MAJORVERSION, VER_EQUAL);
^
../../libusb-1.0.19/libusb/os/windows_usb.c:850:41: note: each undeclared identi
fier is reported only once for each function it appears in
../../libusb-1.0.19/libusb/os/windows_usb.c:850:59: error: 'VER_EQUAL' undeclare
d (first use in this function)
major_equal = VerSetConditionMask(0, VER_MAJORVERSION, VER_EQUAL);
^
../../libusb-1.0.19/libusb/os/windows_usb.c:860:42: error: 'VER_MINORVERSION' un
declared (first use in this function)
minor_equal = VerSetConditionMask(0, VER_MINORVERSION, VER_EQUAL);
^
cc1.exe: some warnings being treated as errors
make[1]: *** [os/libusb_1_0_la-windows_usb.lo] Error 1
make[1]: Leaving directory `/home/Ssery/source/libusb-build/libusb'
make: *** [install-recursive] Error 1
------------------------------------------------
how can I resolve this build error?
Thank you.
Show LessMy company is starting development work on a new product and we are considering using a Broadcom radio. We plan to use Micrium uC/OS-III RTOS and uC/TCP-IP networking stack. In discussions with Micrium, they indicated that it would be easy to integrate their RTOS and network stack into the WICED SDK to provide a complete WI-FI solution. I have been looking at radio options that are supported by the WICED SDK. The BCM4343W radio is mentioned on the WICED web page as being supported, but when you download the SDK, the readme file does not mention that the BCM4343W is supported. Can someone confirm that this radio is currently supported? If not, will it be in the future?
Another product in our company is using the BCM4354 radio, it would be a better choice for us to re-use this radio if it can or will be supported by the WICED SDK. As with the BCM4343W, the BCM4354 radio is mentioned on the WICED web page, but noted as a Linux Only Solution and is not mentioned in the SDK readme as supported. Can someone confirm whether this radio is supported by the WICED SDK? What does a Linux Only Solution mean and would that make it difficult to use Micrium uC/OS-III and uC/TCP-IP?
Show LessI have already added a UART to the bootloader, which I am modifying. The SDK is great because this was rather easy to do!
However, we need to load the WiFi firmware into the external flash manually via a UART in the bootloader instead of using the FTDI. This is for a board used for production testing of modules and we do have the ability to bootload the ST processor, but not the external flash. Furthermore, we are out of internal memory to store the WiFi firmware image internally.
Any thoughts on how this can be done?
Thanks,
Ben
Show LessIs there any standalone board with BCM4343W chip on it, that is a development board with BCM4343W wifi chip with SDIO interface and it should not have controller on it.
We already have a controller board which we want to interface with BCM4343W chip over SDIO interface, so we need a standalone BCM4343W board.
Show LessWe are facing a very serious issue of AP interface going down momentarily when the STA interface is started on WICED 3.1.2 My platform is BCM9WCDPLUS114 and the module is WM-N-BM-14
Our Observation:-
1.The mobile phone was connected to WICED's AP ,as soon as the board connected to the router and started the STA interface, we noticed that the mobile got disconnected i.e the board's AP was down for a while ,it got reconnected after around 10 seconds.
2. This problem is also noticed when the STA interface is already up and we try to connect to an external network.
3.I even tried with security disabled on both STA and AP interfaces of WICED,but the problem still exists.
4.If any device is connected to the AP mode of wiced, we can see that it has disconnected from the network for few seconds and then connects back. We lose any UDP packets that were sent during this period.seyhangangiabirjepatil@
Show Lessin the code in ble_proximity_reporter, I see in the serial logs that tx_power is returned as 4:
WPRINT_BT_APP_INFO( ("Local TX power: %i\n", p_tx_power->tx_power) );
proximity_tx_power_level = p_tx_power->tx_power;
However, looking through the code I was unable to find where this gets set .. seems like its somewhere within the library:
Bluetooth_Low_Energy_Proximity_Reporter_Application
1. Can I change the power level ?
2. Where is the source code for Bluetooth_Low_Energy_Proximity_Reporter_Application ?
Sajid
Show LessHi.
I am noticing BLE connection problems with the BLE Proximity Reporter application running on ISM43341 hardware with WICED SDK 3.5.1 and LightBlue on iOS 9.2.
Starting WICED v3.5.1
Platform ISM43341_M4G_L44 initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp2
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : C4:7F:51:80:25:6F
WLAN Firmware : wl0: Oct 13 2014 15:25:13 version 6.10.190.51 (r507746) FWID 01-60cadeb3
00000363 GKI_create_task func=0x8016e29 id=1 name=BTU stack=0x0 stackSize=6144
00000370 GKI_create_task func=0x80182a9 id=0 name=HCISU stack=0x0 stackSize=4096
Unhandled Bluetooth Management Event: 0x15
Bluetooth enabled (success)
Local Bluetooth Address: [43:34:1B:00:1F:AC]
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
GATT connection to [6E:1C:87:98:71:E9] established.
---->>> New ADV state: 0
Local TX power: 4
GATT connection to [6E:1C:87:98:71:E9] released.
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
GATT connection to [6E:1C:87:98:71:E9] established.
---->>> New ADV state: 0
Local TX power: 4
GATT connection to [6E:1C:87:98:71:E9] released.
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
GATT connection to [6E:1C:87:98:71:E9] established.
---->>> New ADV state: 0
Local TX power: 4
GATT connection to [6E:1C:87:98:71:E9] released.
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
GATT connection to [6E:1C:87:98:71:E9] established.
---->>> New ADV state: 0
Local TX power: 4
GATT connection to [6E:1C:87:98:71:E9] released.
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
---->>> New ADV state: 4
---->>> New ADV state: 0
Just wanted to verify if this is a known problem and if there is a workaround.
Show Less