Wi-Fi Combo Forum Discussions
Hi All
Not able to get SNTP Response, It giving up after trying two times with attached logs.
/* Bringup the network interface */
wiced_network_up( WICED_STA_INTERFACE,WICED_USE_EXTERNAL_DHCP_SERVER, NULL );
logs:
Starting WICED v3.1.2
Platform BCM9WCDPLUS114 initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp1
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : FC:4D:D4:FF:C3:7A
WLAN Firmware : wl0: Nov 7 2014 16:03:45 version 5.90.230.12 FWID 01-4b73cbac
Starting WICED Bluetooth
Bluetooth MAC Address : FC:4D:D4:ED:0D:30
Bluetooth Firmware : BCM20702B0_002.001.014.0487.0000_Generic_UART_Class1_20MHz.hcd
Initialising WICED SmartBridge ...
Joining : SMART
Successfully joined : SMART
Obtaining IPv4 address via DHCP
Setting IPv6 link-local address
IPv4 network ready IP: 10.100.10.64
Getting NTP time...
failed, trying again...
failed, trying again...
failed, trying again...
Give up getting NTP time
Show LessI found this file factory_reset_dct.c file in temp_control demo example, but I do not see it being used anywhere, nor is it included anywhere. So I was wondering what is the use of it and why it exists there.
Show LessWhen I use SN8200xx as WICED_USE_EXTERNAL_DHCP_SERVER, I get synct to SNTP server.
When I use SB8200xx as static IP WICED_USE_STATIC_IP, I can not get any data from the SNTP server.
The connection my network is OK in both cases.
I work with version wiced sdk ver 2.4.1
Example:
static const wiced_ip_setting_t MNap_ip_settings =
{
INITIALISER_IPV4_ADDRESS( .ip_address, MAKE_IPV4_ADDRESS( 10,0,0,9)),
INITIALISER_IPV4_ADDRESS( .netmask, MAKE_IPV4_ADDRESS( 255,0,0,0)),
INITIALISER_IPV4_ADDRESS( .gateway, MAKE_IPV4_ADDRESS( 10,0,0,138)),
};
//=============================================================================================
void application_start(void)
{
/* Initialise the device and WICED framework */
wiced_init( );
/* Bring up the network interface */
//Work
// wiced_network_up( WICED_STA_INTERFACE, WICED_USE_EXTERNAL_DHCP_SERVER, NULL );
//Do not work
wiced_network_up( WICED_STA_INTERFACE, WICED_USE_STATIC_IP, &MNap_ip_settings);
sntp_start_auto_time_sync( 1 * DAYS );
Why SNTP server do not response while I use Static IP ?
thanks
Show LessHi,
I was wondering if it would be possible to have more than one ( in my case, two ) pass phrases for the WPA authentication on the soft ap.
( or the p2p ).
I'm exploring the option of having two pass-phrases:
one would be a default hard-coded pass-phrase ( which would be a long random set of characters printed on the back of the device ), and the other is user-configurable.
I was thinking about adding a button for that purpose, but that has some additional remifications ( pcb layout, usability, cost, etc ).
btw : in 3.3.1 you've done a great job with extracting the function wwd_wifi_set_passphrase outside.. but you could get an extra bonus by using it in wiced_p2p.c:610.
Tsachi
Show LessI've optimized the dns_redirect component that is provided with the SDK.
Before:
DNS_Redirect_Daemon | 371 | 0 |
After:
DNS_Redirect_Daemon | 315 | 0 |
Also, since it's *doing* less now, it would also run slightly faster.
Attached is the source code; the header file doesn't change.
Tsachi
Show LessHi,
I just found the size of Gedday seems double in SDK-3.3.1.
$ make snip_service_discovery-FreeRTOS-LwIP-BCM943362WCD4
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
Gedday | 4452 | 204 | (SDK-3.1.2)
Gedday | 7124 | 1400 | (SDK-3.3.1)
$ make snip.service_discovery-FreeRTOS-LwIP-BCM94390WCD2
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
Gedday | 0 | 4656 | (SDK-3.1.2)
Gedday | 0 | 8523 | (SDK-3.3.1)
In additional, the Gedday is supposed to be a simple protocol,
why the image size is so big (compare to other daemons)?
Show LessHi
I am currently trying to load images to SB-WM-N03-SEVB board (rev 2.0) which includes BCM4390. I was told to use this board is to use the platform name as BCM94390WCD2. But I have below failures.
Should I use the correct platform info instead of BCM94390WCD2? If so, where can I get the correct platform info?
Creating Filesystem
Downloading Bootloader ...
platforms/BCM94390WCD2/BCM94390WCD2_targets.mk:111: recipe for target 'download_bootloader' failed
make.exe[1]: *** [download_bootloader] Error 1
make.exe[1]: *** Waiting for unfinished jobs....
Thanks
Won
Show LessHi Guys,
I am working on WICED 3.3.1.
I want to debug and download bin into MCU.
My MCU is STM32F207. Below are steps I tried:
1) HW: Connect JLINK to STM32F207 via JTAG directly, not via FTDI.
2) SW: For make targets, i tried but failed with following:
snip.scan-BCM943362WCD4-debug download
snip.scan-BCM943362WCD4-debug download JTAG = jlink
3) it always tell me :
"**** 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. ****"
4) My driver can be seen in attachment.
Anyone has idea on this.
Many thanks.
Show LessI have a problem with the SDK (3.1.2) behavior regarding the use of a soft ap and a udp socket as it breaks the wiced_scan_wifi_networks functionality. So I enabled WPRINT_ENABLE_WWD_DEBUG to see what is happening and rebuilt my app.
This breaks the ability of the soft ap to even start. The following error is reported on the UART
Could not turn on APSTA
This is generated by the wwd_management_wifi_on() function, and it does not lie, the AP does not start. Simply undefining the WPRINT_ENABLE_WWD_DEBUG lets the AP start.
Seems simple enough to enable this definition so the internal prints would work, but there must be someplace in the code that the macro expansion breaks something critical.
Has anyone see this and know how to fix it?
Show LessHi,
In SDK-3.3.1, the http server uses different threads to handle receive and
connect/disconnet.
wiced_http_server_connect_callback sends asynchronous event to HTTPserver
thread when got CONNECT packet.
It sends asynchronous event to HTTPserver thread when got DISCONNECT packet.
It sends asynchronous event to deferred worker thread when got RECEIVE packet.
Since the HTTPserver is running in WICED_DEFAULT_LIBRARY_PRIORITY which has
higher priority than the defered worker thread (WICED_APPLICATION_PRIORITY),
How do you ensure the http_server_deferred_receive_callback is called before
the DISCONNECT is handled? If DISCONNECT is handled by HTTPserver first, the
receive packet is lost.
I'd appreciate if someone can explain the changes in http server implementation.
Show Less