Wi-Fi Combo Forum Discussions
Hi
I have one of the BCM943907AEVAL1F-2 boards, running wiced 5.0.1
I am trying to test the ping.deepsleep function.
It appears to work as an app, ping every 3 cycles.
However the measured current consumption seems high.
Measuring the voltage on the test points (10V=1A) test point, the Voltage appears to be 0.89V which to my mind translates to 89mA.
This seems high. Could you advise what the measurement should be?
Thanks
Graham
Show LessI have my "Dcuments" folder on my windows 10 machine redirected to point to a documents folder on my Google stream drive(g:)
The Wiced installer didn't seem to honour my documents folder redurect, and instead installed the sdk by default in:
Windows/user/<me>/documents...
Which is a redundant folder in my system.
I uninstalled, and reinstalled specifying my Google drive documents folder for the SDK. This appeared to work in the sense that the SDK appeared to be installed in the correct place, but the target builds (e.g. Hello sensor) don't seem to work with this configuration. I uninstalled again and reinstalled with default configuration and builds all work again. It appears to me that some of the build paths might not be correctly set up to honour a non-default SDK installation. Can you shed any light on this problem? I would prefer to keep my development files on my Google Drive rather than my local hard drive, if possible. Any advice appreciated.
Show LessHello,
I have a board of BCM94343WWCD1 and want to test the button and LED example in snip.gpio app, I try to create target and double click it : snip.gpio-BCM94343WWCD1 download run , the code can be found download to the target board but the LED not light when I push button.
I open the gpio.c file and put mouse arrow on the character of 'WICED_LED1', it pop up a hint of : Symbol 'WICED_GPIO_15' could not be resolved, then I open the /platforms/BCM94343WWCD1/platform.h file and fine a line: #define WICED_LED1 ( WICED_GPIO_11 ), which gpio definition is right following the schematics.
So, I wonder why and where 'WICED_LED1' has been defined as 'WICED_GPIO_15', and why the right definition of 'WICED_GPIO_11' was not available even I try to
add #include "platform.h" in the gpio.c file, any obvious step I missed ?
Chris
Show Lesswhat is the easiest way to compile the WICED SDK with it's minial configuration to support STA and AP mode as a library which can be linked against our own existing project ?
Show LessI notice on sdk-6.1, a printf("#"); in ble scan result callback can cause hang.
Remove the printf then it works.
It's pretty common to do such printf for debug purpose.
On sdk-6.0.1:
00:00:02.624000 GKI_create_task func=0x80182d5 id=1 name=BTU stack=0x0 stackSize=6144
00:00:02.632000 GKI_create_task func=0x80197f5 id=0 name=HCISU stack=0x0 stackSize=4096
On sdk-6.1:
00:00:01.066000 GKI_create_task func=0x8017d1d id=1 name=BTU stack=0x0 stackSize=4096
00:00:01.074000 GKI_create_task func=0x801954d id=0 name=HCISU stack=0x0 stackSize=3072
I believe other users may find the existing application fails due to this stack size change.
Would you consider change the stack size back?
Or alternatively provide user an argument to override default settings.
Show LessIn my hardware, I am using antenna "1" from the point of view of the wl tool, or WICED_ANTENNA_2 in the WWD enum parlance.
I need to run the test.bt_mfg_test app to do wireless certification. I am using a 4343W radio.
How can I set the antenna selection from the mbt tool to choose the correct antenna?
Also, I have seen some references to "BlueTool" software from Cypress that might be able start/stop the same tests that mbt does. Is that tool available for download anywhere?
Show LessI am having an issue with running bt_mfg_test on a 4343W radio.
I can build and flash the `bt_mfg_test` project, and invoke the control commands, but I cannot get the `set_tx_frequency_arm` mode to work.
For example, the `le_transmitter_test` does work, and I see "Received HCI event" at the command line, and I can see output on a spectrum analyzer.
Same for the simple commands, like `reset`.
But: when I run the `set_tx_frequency_arm` command, I the mbt.exe tool just returns without reporting even "Sending HCI command".
Note: I did have to make a patch to the BT mfg_test library to get the application to start correctly:
In bt_firmware_download, There is the code:
/* TODO : Eventually we will be using the patchram_download_baudrate variable from the platform file. */
/* update BT and host to switch to 3mbps */
if ( bt_host_update_baudrate( BAUDRATE_3MPBS ) == WICED_BT_SUCCESS )
{
fast_download = WICED_TRUE;
}
I made this change because I was observing a breakpoint on failure to load BT firmware. Commenting that baud rate change out (and leaving it at 115200) solved that error.
Show LessHi. I use the websocket library in WICED SDK 4.1.1, and I tried to use it to read larger websocket data(>=1447 bytes). Unfortunately, it failed to read the larger data.
I tried to trace the library code, and I found that there is a "tls_get_next_record_failed" in wiced_tls_receive_packet(wiced_tls.c).
Do you have any suggestions for this issue?
Show LessLooking for a component to create a very simple WiFi based solution.
Problem Description: Monitor if a device is powered on by monitoring its IP address, communicated over the local WiFi network
Possible Solution Scenario:
- When a device power source is "present"/"on", a simple WiFi module will turn on and connect to a predefined WiFi SSID.
- The WiFi module will have an IP address (either pre-set or received via DHCP).
- One can ping WiFi module IP address to conclude if the device is on or off
The WiFi component shall be as simple as posible. No much programming, no commercial monthly fees for wireless < -- > cloud services
I just don't know enough about the product line to find the simplest device that fits the requirements
Thank you in advance
Show LessIn the 43xxx_Wi-Fi folder, there is only one directory (tools).
My search for files normally found in other releases came up empty.
The files do appear to be in the Windows release of 6.2.1
Show Less