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

    REPL Prompt missing and no response after connection

    Scheduled Pinned Locked Moved Issues & Bugs
    lopy4firmwarerepllora
    3 Posts 2 Posters 973 Views 3 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.
    • B Offline
      brentoon
      last edited by

      I am using LoPy4 on a Pysense board and had it all working. I was using Atom successfully and uploading files no problem. I could also telnet to the device.

      I'm using MacOS 10.13.3
      I should add on first use I updated the Pysense firmware using 'dfu-util -D pysense_0.0.8.dfu' and then updated the LoPy4 firmware - it said it was updating to 1.17.3b1 (I assume this is the latest but can't find a list of release numbers anywhere).

      I have been testing LoRa using the example code in the docs to access LoRaWAN (OTAA) (unsuccessfully so far), and tried some web server examples using MicroWebSrv & MicroDNSSrv.

      At some stage the REPL console stopped responding. On Atom I could initiate a connection, the Atom connection window would say 'Connected' but in the console window, after 'Connecting on /dev/tty.usbmodemPY... there was no '>>>' prompt.

      The same happens with Telnet. I can log in ok, get the 'Help()' message, but no response after that.

      I have tried Ctrl-B, & Ctrl-D, etc with no response. I've tried entering a command (blind) but still no response.

      I have reloaded the firmware a few times.
      I have tried using battery only and connecting via telnet, same result.
      The Blue LED heartbeat flashing continues ok all through this.

      Any suggestions?

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

        @brentoon You could try a safe boot. Connect P12 to 3.3V and push the reset button (next to the RGB LED). Safe boot ignores boot.py and main.py on boot. Similar is trying Ctrl-F in the REPL prompt.
        To avoid all other dependencies with Atom and the pymakr plugin, connect via USB using a simple terminal emulator like screen. That should be available on OS X.

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          brentoon @robert-hh
          last edited by brentoon

          @robert-hh Thanks, that did it!

          I had to do the P12 to 3.3V for the 7-9s to load the factory firmware.
          I retested a firmware update and it went back to the unresponsive mode. So I then reformatted the /flash area by running:

          import os
          os.mkfs('/flash')

          A firmware update then worked ok.
          Thanks again.

          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