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

    LoPY PIN outs

    Scheduled Pinned Locked Moved LoPy
    4 Posts 3 Posters 2.3k Views 4 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.
    • bmarkusB Offline
      bmarkus
      last edited by

      Hi,

      looking for a documentation describing pin functions of P0...P23, where is I2C, SPI, .etc. assigned to.

      Thanks... Béla

      1 Reply Last reply Reply Quote 0
      • A Offline
        abilio
        last edited by

        Hello markus,

        We are aware that at the present time the documentation related to the pinouts is still incomplete. We apologize for it, but we're running around the clock to release an amended version of it along with a new firmware version that includes improvements and bugfixes. We expect it to be released this Friday, so please stay tuned.

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

          The LoPy has pins numbered in order under the P naming, or in WiPy 1.0 order under the G naming (which is used on the expansion board). Either of these are understood by the machine.Pin class. Internally (in the ESP32 chipset) there are 40 GPIOs, 24 of which are external pins on the LoPy; the exact mapping will likely be documented soon (and can be extracted by observing registers when accessing pins). For one example, P9=G16=ESP32 GPIO 12 in LoPy. Some pads are used internally such as for flash memory, LoRa, and the onboard RGB LED, and others have defaults such as UART 0 (which matches the expansion board, documented at https://github.com/wipy/wipy/blob/master/docs/User_manual_exp_board.pdf ).

          As for peripherals, most signals can be mapped to any IO through the ESP32's GPIO matrix. This means I2C and SPI can in fact be assigned anywhere (unless run at extreme speeds). Sections 4.9 to 4.11 of the ESP32 Technical Reference Manual details what can be connected where in the ESP32; beyond that the questions are which pads reach which pins on the LoPy, and what the MicroPython implementation handles.

          1 Reply Last reply Reply Quote 0
          • bmarkusB Offline
            bmarkus
            last edited by bmarkus

            @LonTech

            thanks, let's see how it will be supported by the machine module.

            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