1 Reply Latest reply on Dec 19, 2016 3:36 AM by AjayB_76

    SDK-3.7.0-7: Device network is unreachable once init bt stack

    AxLi_1746341

      Hi KausikS_86

       

      I hit a more critical issue while testing sdk-3.7.0-7.

      It seems once ble start scaning, the device's wifi network becomes unreachable.

       

      My test application does below steps:

      1) device join AP and start a tcp server ( you can copy the code from snip.tcp_server )

      2) do delay 20 seconds (on purpose... I can see ping ok during this period)

      3) wiced_bt_stack_init()...

         then wiced_bt_ble_observe() or wiced_bt_ble_scan() in bt_init callback.

      4) ping no longer response after got the first ble scan result

      Note, I also try comment out wiced_bt_ble_observe() or wiced_bt_ble_scan() call

      I still got ping unreachable after calling wiced_bt_stack_init() for 1 or 2 seconds.

      So I think the most easy way for you to test is to modify snip.tcp_server and adding wiced_bt_stack_init().

       

      I use ping device the check network status:

       

      [16:16:40:408] Starting WICED v3.7.0-7␍␊

      [16:16:40:416] Joining : LAB␍␊

      [16:16:43:299] Successfully joined : LAB␍␊

      [16:16:43:322] Obtaining IP address via DHCP␍␊

      [16:16:47:185] Network ready IP: 192.168.1.100␍␊                                << ping 192.168.1.100 ok

      [16:16:47:188] Creating tcp server thread ␍␊                                    << I did 20 seconds delay on purpose ( ping still ok in this period )

      [16:17:07:190] 00:00:29.032000 GKI_create_task func=0x8021b65  id=1  name=BTU  stack=0x0  stackSize=6144␍␍␊

      [16:17:07:198] 00:00:29.040000 GKI_create_task func=0x8023085  id=0  name=HCISU  stack=0x0  stackSize=4096␍␍␊

      [16:17:12:975] [App] 442C058065EB,-98,RAW(15) 0201060B0954455354424C45414456␍␊   << At this point ping 192.168.1.100 don't response and latter becomes Destination Host Unreachable

      ....

       

      PS. I use FreeRTOS+Lwip build but I also notice exactly the same issue on ThreadX+NetX build.

        • 1. Re: SDK-3.7.0-7: Device network is unreachable once init bt stack
          AjayB_76

          Hi Alex,

           

          we tested the same on the WICED 4.0.1 and looks like its working.

          Can you try the same with WICED 4.0.1 and post the logs for the same?

           

          Below are the logs we got:

           

          ============== Logs for Restful Smart Server on BCM943438WCD1 =============

           

          Starting WICED v3.3.DEVELOPMENT

           

          Platform BCM943438WCD1 initialised

           

          Started ThreadX v5.6

           

          Initialising NetX_Duo v5.7_sp2

           

          Creating Packet pools

           

          WWD SPI interface initialised

           

          WLAN MAC Address : 02:0A:F7:1A:E2:6D

           

           

          WLAN Firmware    : wl0: Oct  7 2016 07:13:23 version 7.45.98.4 (r662286) FWID 01-dddf319a

           

           

          Joining : WICED_VikasAP

           

          Successfully joined : WICED_VikasAP

           

          Obtaining IPv4 address via DHCP

           

          DHCP CLIENT hostname WICED IP

           

          IPv4 network ready IP: 192.168.1.20

           

          Setting IPv6 link-local address

           

          IPv6 network ready IP: FE80:0000:0000:0000:000A:F7FF:FE1A:E26D

           

          00:00:08.046392 GKI_create_task func=0x8023079 id=1  name=BTU  stack=0x0  stackSize=6144

           

           

          00:00:08.054392 GKI_create_task func=0x80248ed id=0  name=HCISU  stack=0x0  stackSize=4096

           

           

          Stack requests for local security keys

           

          Bluetooth Internet Gateway initialised. BD address : 43:43:A1:12:6C:66

           

           

          Store local keys in non-volatile memory

           

          Store local keys in non-volatile memory

           

           

           

           

          ============== Logs for Pinging ==================

           

           

          C:\Users\aaaa>ping 192.168.1.20

           

          Pinging 192.168.1.20 with 32 bytes of data:

          Reply from 192.168.1.20: bytes=32 time=276ms TTL=128

          Reply from 192.168.1.20: bytes=32 time=48ms TTL=128

          Reply from 192.168.1.20: bytes=32 time=15ms TTL=128

          Reply from 192.168.1.20: bytes=32 time=2ms TTL=128

           

          Ping statistics for 192.168.1.20:

              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

          Approximate round trip times in milli-seconds:

              Minimum = 2ms, Maximum = 276ms, Average = 85ms

          1 of 1 people found this helpful