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, version 1.6.4.b1

    Scheduled Pinned Locked Moved Announcements & News
    lopywipyfirmwaresipy
    26 Posts 9 Posters 10.5k Views 9 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
      lars
      last edited by

      I just updated my newly bought WiPy 2.0 to this firmware version with the Pycom updater. After reset I get a boot loop with the following messages via serial connection:[0_1488012601074_core_dump.txt](Uploading 100%)

      Resetting the firmware via safe mode does not work. Also trying to reinstall the firmware update leads to the same result. Any help?

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

        @lars
        did you removed wire (G23-GND) after sucesfull upgrade?

        think about people first, then computers

        L 1 Reply Last reply Reply Quote 0
        • J Offline
          jmarcelino @zmrzli
          last edited by

          @zmrzli
          Your BLE advertising data is invalid according to the Bluetooth spec. The first octet is 1 so you're specifying you are sending one byte for that unit. That's exactly what you're getting :-)
          Let's move this discussion to your original post https://forum.pycom.io/topic/723/bluetooth-advertising-data

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

            @livius yes I removed the G23-GND wire. I tried serveral disconnects to power and only 3v3 and GND plus plus P0,P1 for UART were connected. Even without uart there is no wifi AP available any more, as was before the update.
            For safe mode I tried 3v3-p12 for as long as the most rapid flashing of the orange led.

            J 1 Reply Last reply Reply Quote 0
            • J Offline
              jmarcelino @lars
              last edited by

              @lars
              could you post the serial connection messages again, either pasting here or somewhere like pastebin.com. It seems they didn't show on your other post

              L 1 Reply Last reply Reply Quote 0
              • L Offline
                lars @jmarcelino
                last edited by

                @jmarcelino You are right of course. There was a message, that I didn't have the rights to upload a file here. Here is the pastbin: http://pastebin.com/3RaMdeJ2

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

                  @lars it might be that there's a conflict with the NV storage area on your WiPy and the current firmware. I have just updated the firmware package online in order to erase that area before applying the new firmware. Could you please try the update again and let me know? Thanks!

                  Cheers,
                  Daniel

                  L 1 Reply Last reply Reply Quote 0
                  • P Offline
                    Pete
                    last edited by Pete

                    By the way, I do want to thank whoever fixed the OSX GUI firmware updater so that it 1) shows some of the output from the underlying tools, and more importantly 2) knows about pycom.io's TLS certificate. That made my messing about above that little bit easier :-)

                    Pete

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

                      @daniel although pycom does still report the same version number 1.6.4.b1 on update I hope, that I got the new version. The behavior is similar but the serial output is slightly different: http://pastebin.com/EN30c4Nk
                      Thank you all very much for your quick responses!

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        rdixey
                        last edited by rdixey

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • L Offline
                          livius @daniel
                          last edited by

                          @daniel
                          I see that some timings/stability improved in pin.
                          Now i am able read samsung tv codes without any problem from python code without need of C function as previously :)
                          I tested this i suppose in many previous versions (last tested lower than 1.5) and it was not stable enought but now it work :)

                          think about people first, then computers

                          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
                          • 2
                          • 2 / 2
                          • First post
                            Last post

                          Pycom on Twitter

                          Pycom