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

    WiPy can`t get started

    Scheduled Pinned Locked Moved WiPy 2&3
    20 Posts 6 Posters 5.5k 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.
    • K Offline
      Knoahlr @Ralph
      last edited by

      @Ralph I got the WiFi and Ftp working, everything else fails. Especially the much needed firmware update.
      Also, when i connect to the board using screen (serial connection), I can only see the output but can`t type and send any commands to the board. Is this a problem with screen or my board.

      L S 2 Replies Last reply Reply Quote 0
      • L Offline
        livius @Knoahlr
        last edited by

        @Knoahlr
        check if you have all jumpers on the expansion board

        think about people first, then computers

        K 1 Reply Last reply Reply Quote 0
        • K Offline
          Knoahlr @livius
          last edited by

          @livius Yes I do.

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

            @Knoahlr
            change usb cable ;-)

            think about people first, then computers

            1 Reply Last reply Reply Quote 0
            • S Offline
              sakis @Knoahlr
              last edited by

              @Knoahlr

              The screen connection stability is improved in every firmware update. Make sure that you are not using any other terminal multiplexers (e.g. tmux or screen inside screen). Open a new terminal window to ensure that there are no such dependencies and use screen /dev/yourdevice 115200.

              It might take some time before the REPL appears. If you still don't get it keep the screen connection open and press the reset button on your board.

              K 1 Reply Last reply Reply Quote 0
              • K Offline
                Knoahlr @sakis
                last edited by

                @sakis Hey, I did this same exact steps a few times and all I was able to see was the output. Also, whenever I was connected to the board using Pymakr and screen at the same time. I could see the exact same output from Pymakr on the screen terminal.

                I tried to upgrade the firmware by ftp(ing) the binary file to /flash/sys but now when I reset the board I see a red light and it doesn`t seem to finish booting up.
                This what I see on my screen terminal

                rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
                configsip: 0, SPIWP:0x00
                clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
                mode:QIO, clock div:2
                load:0x3fff9010,len:8
                load:0x3fff9018,len:312
                load:0x40078000,len:2352
                load:0x4009f000,len:1196
                entry 0x4009f2d8

                Booting in safe mode doesn`t help.

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

                  @Knoahlr
                  i also tried before by ftp but it does not work properly
                  and somwhere in the formu some admin say that it is no longer supported
                  but i am not sure

                  to fix problem flash it by updater tool

                  think about people first, then computers

                  1 Reply Last reply Reply Quote 0
                  • robert-hhR Offline
                    robert-hh
                    last edited by

                    Flashing by uploading appimg.bin to /flash/sys does not work any more since V1.0.0.xxx (or so). You may use the uploader tool, or if you have built you own image, use
                    make flash

                    K 1 Reply Last reply Reply Quote 0
                    • K Offline
                      Knoahlr @robert-hh
                      last edited by

                      @robert-hh @livius I`m getting an error A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header, whenever I try to use the Upgrader tool. Did any of you experience this problem. Do you think this a problem with my WiPy or the expansion board?

                      1 Reply Last reply Reply Quote 0
                      • robert-hhR Offline
                        robert-hh
                        last edited by robert-hh

                        Did you connect GP23 and GND & Reset then? That's needed for upgrading via USB/Serial,

                        K 1 Reply Last reply Reply Quote 0
                        • K Offline
                          Knoahlr @robert-hh
                          last edited by

                          @robert-hh Yes I did.

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

                            @Knoahlr

                            as @rskoniec wrote do the following - i have modified two points :

                            1. Check if you have all jumpers on the expansion board
                            2. Unconnect (USB) WiPy/LoPy board from PC.
                            3. Connect wire G23+GND.
                            4. Connect the board (USB) to PC by shortest usb cable.
                            5. Upgrade but unselect fast connection in upgrade tool.
                            6. after sucessfull update unconnect the board (USB) from PC.
                            7. Remove G23+GND wire.
                            8. Connect the board (USB) to PC.
                            9. Check f/w release with os.uname()

                            you can try also at point 4
                            when you press upgrade button i upgrader tool or really shortly before
                            press reset button on the board - this should 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 / 1
                            • First post
                              Last post

                            Pycom on Twitter

                            Pycom