Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    New firmware release 1.7.5.b2

    Scheduled Pinned Locked Moved Announcements & News
    firmware
    14 Posts 6 Posters 4.3k Views 6 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L Offline
      livius @daniel
      last edited by livius

      @daniel
      Hi is there something changed in the init of Wifi AP?
      now my working previously code

      wlan = WLAN(mode=WLAN.STA_AP)
      

      give me an error:
      ValueError: AP SSID not given

      UPDATE
      i see that now it is not optional

      wlan = WLAN(mode=WLAN.STA_AP,ssid='wipy-pytrack')
      

      and i see in sources

      if (mode != WIFI_MODE_STA) {
       -        wlan_setup_ap (ssid, ssid_len, auth, key, key_len, channel, add_mac);		 
      

      and now

      +        if (ssid == NULL) {
       +            nlr_raise(mp_obj_new_exception_msg(&mp_type_ValueError, "AP SSID not given"));
       +        }
       +        if (auth == WIFI_AUTH_WPA2_ENTERPRISE) {
       +            nlr_raise(mp_obj_new_exception_msg(&mp_type_ValueError, "WPA2_ENT not supported in AP mode"));
       +        }
       +        wlan_setup_ap (ssid, auth, key, channel, add_mac);
            }		      }

      think about people first, then computers

      robert-hhR 1 Reply Last reply Reply Quote 2
      • robert-hhR Offline
        robert-hh @livius
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • S Offline
          ssmith
          last edited by

          This is completely unacceptable for a company at the stage of pycom. You cannot do an update that breaks backward compatibility without serious thought and warnings that updating to this version can brick every unit you touch. This is the kind of behavior that forces me to look for other vendors for my products. Now that I have 25 bricks on my desk, how can I downgrade the FW to version 1.7.4?

          L 1 Reply Last reply Reply Quote 0
          • D Offline
            daniel
            last edited by

            @ssmith what do you mean by saying that your units are bricked? What part has broken backwards incompatibility?

            1 Reply Last reply Reply Quote 0
            • D Offline
              daniel
              last edited by

              @livius the fact that it was optional before was a bug. If the module is going to be setup as an AP, the SSID must be specified.

              S L 2 Replies Last reply Reply Quote 0
              • S Offline
                ssmith @daniel
                last edited by

                @daniel It may have been a bug but it was how the product worked. Now all SW has to be changed that relied on this 'bug'.

                1 Reply Last reply Reply Quote 0
                • L Offline
                  livius @daniel
                  last edited by

                  @daniel
                  Previously ssid was equal to system default like wipy-wlan-a8be if not specified.

                  think about people first, then computers

                  1 Reply Last reply Reply Quote 0
                  • L Offline
                    livius @ssmith
                    last edited by livius

                    @ssmith
                    As hint. You can work without downgrade
                    You must connect to wipy/lopy... by UART and send from hand

                    from network import WLAN
                    wlan = WLAN(mode=WLAN.AP, ssid='wipy-test')
                    

                    then you can connect to board normally by ftp and change your config

                    problematic but work

                    think about people first, then computers

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      ssmith @livius
                      last edited by

                      @livius There's a difference between using these devices on my desk as a developer and using them in a completed product. I can make anything work as a developer. Making it work as a product is a completely different situation. I don't have the luxury of connecting a USB cable to products that are packaged up in an enclosure. I have to work with the tools available in that situation. The system was designed to allow anything to be updated (except FW which is a different issue that needs to be addressed) remotely over the internet. In order to do that, the internet needs to work. When updating FW breaks what was previously working, that is a huge issue.

                      L 1 Reply Last reply Reply Quote 1
                      • L Offline
                        livius @ssmith
                        last edited by

                        @ssmith
                        This was only hint. I understand you completly i am also affected.
                        But fortunately, I have a series of unit tests, although in this case, the test was shrouded at very beginning ;-)

                        think about people first, then computers

                        S 1 Reply Last reply Reply Quote 0
                        • S Offline
                          ssmith @livius
                          last edited by

                          @livius Thank you for posting the issue so quickly. That kept me from a much bigger hole when I saw you mention it. I am chasing some other WiFi issue right now that may be related to this update but not sure yet..

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dbrgn
                            last edited by

                            @ssmith said in New firmware release 1.7.5.b2:

                            When updating FW breaks what was previously working, that is a huge issue.

                            Especially if a breaking change is not listed in any changelog, as far as I can tell :)

                            1 Reply Last reply Reply Quote 3
                            • ledbelly2142L Offline
                              ledbelly2142
                              last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0

                              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                              With your input, this post could be even better 💗

                              Register Login
                              • 1 / 1
                              • First post
                                Last post

                              Pycom on Twitter

                              Pycom