7 Replies Latest reply on Nov 10, 2016 5:56 PM by ielec

    SDK 3.7 Config_mode not work

    sharnlin_1740926

      Hi

      I tried both SDK 3.7.0 and 3.7.0_3

      test condition

      - clean SDK without any modification

      - target board is BCM94343WWCD1

       

      issue

      build snip.config_mode download download_apps run to target board, the Config mode AP is working, PC can connect and ping to the board, but can't access the config webserver (http://192.168.0.1)

      if change SDK to 3.5.2, no trouble found.

       

       

      Thanks,

      Sharn

        • 1. Re: SDK 3.7 Config_mode not work
          rash

          I have tested with 3.7.0 and found the same issue. I have contacted with our experts team and found that this is a bug in 3.7.0 SDKs. We will correct this in the next release.

           

          If you are stuck in you development let us know we can escalate this as per the priority.

          1 of 2 people found this helpful
          • 2. Re: SDK 3.7 Config_mode not work
            sharnlin_1740926

            just report the bug, not urgent to me.

             

            Thanks,

            Sharn

            • 3. Re: SDK 3.7 Config_mode not work
              fx2016

              rash

              I have the same problem with SDK 3.7.0. After debugging I find out, that the function http_server_process_packet() delivers the wrong url string. The correct url string should be "config/device_settings.html", but if I write

               

              192.168.0.1/config/device_settings.html in Firefox, the function http_server_process_packet() delivers the following string

              "/ HTTP/1.1\r\nHost: 192.168.0.1\r\nUser-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0\r\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8\r\nAccept..."

               

              In internet explorer this function delivers the following string

              "/config/device_settings.html HTTP/1.1\r\nAccept: text/html, application/xhtml+xml, */*\r\nAccept-Language: de-DE\r\nUser-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko\r\nAcce..."

               

              That's why the server never accept the request from the browser. This case is for me very urgent, because I want to demonstrate our customer how a shock sensor data can be transferred to a web client through WIFI.  I know the application appliance is more suitable for my case, but this app config_mode is the first step to do it.

               

              Additionally, instead of clicking button, I want to use appliance to ask the shock sensor for data, and this data should be displayed in a text box in the web page. How can I implement the text box in the web page? Thanks

              1 of 1 people found this helpful
              • 4. Re: SDK 3.7 Config_mode not work
                fx2016

                Hi Rash, any update to this issue ? It would be nice if you can give me a workaround as soon as possible. Thanks

                • 5. Re: SDK 3.7 Config_mode not work
                  ch@broadcom

                  had the same issue!!!

                  these are my changes i did to the 3.7.0 WICED-SDK\libraries\daemons\simple_HTTP_server\simple_http_server.c

                  file:

                  Unbenannt.png

                  it's mostly the old SDK3.5.2 file but i think not completly so it's a mixture of the SDK3.5.2 and 3.7.0 file.

                   

                  edit: attached file

                  2 of 2 people found this helpful
                  • 6. Re: SDK 3.7 Config_mode not work
                    fx2016

                    Hi

                    1 of 1 people found this helpful
                    • 7. Re: SDK 3.7 Config_mode not work
                      ielec

                      @rash The snip.config_mode example in WICED Studio 4 doesn't work still, neither using the original simple_http_server.c nor the one attached here.

                       

                      Hope the WICED team figure it out ASAP.

                       

                      Kind regards.