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

    I2C LCD: code inside

    Scheduled Pinned Locked Moved LoPy
    41 Posts 8 Posters 27.8k Views 8 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.
    • R Offline
      rdixey @DVE
      last edited by

      @DVE Hey Dmitrii ...... I see your 128X64 OLED has a SPI CS Pin but when I look at your code it appears that you do not connect it to a GPIO Pin. The Adafruit ssd1306 lib sequences the OLED CS signal high to low to do write operations. How did you eliminate having to do that with your configuration? I ask because I have tried your code using your default pin config (no connection to OLED CS) but it will not turn on for me. On my OLED pcb the CS pin is high (3.3V) by default, did you pull it low all the time on your OLED pcb?

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

        @rdixey Dmitri.....I went ahead and tied my 128X64 OLED CS Pin to ground, and now the code you provided is working for me as SPI Master. I'm now able to write text to the display. Nice Job :) Many Thanks!

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

          Cool :) I didn't connect CS pin at all, maybe ground is really better.

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

            I tried this code on the i2c 128x64 version of this oled. All the characters are missing the top and bottom pixels. They're the correct characters, but are clipped. Example: The capital 'L' in LoPy is just 3 vertical pixels, and the lower case 'o' is just 2 vertical pixels on for each side. Been messing with it all day and haven't found an obvious problem in the code. I don't have another display to try, but don't think the displays the problem. Any ideas?

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

              Finaly I got 128x64 I2C screen from Ebay. No visible problems, all works nice on standard firmware.
              alt text

              And I don't see any cropping, btw.

              @leelive, did you try the last version from my library?

              J 1 Reply Last reply Reply Quote 0
              • J Offline
                Jiemde Pybytes Beta @DVE
                last edited by

                @DVE I have the same result when the WiPy2 have the right main.py, but in my case it's the transfert of the main.py by Pymakr or by FTP who don't work !

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

                  @Jiemde have you tried with the latest firmware (1.5.0.b2)? We have increased the memory available which was the main reason syncing with Pymakr was not working...

                  J 1 Reply Last reply Reply Quote 0
                  • J Offline
                    Jiemde Pybytes Beta @daniel
                    last edited by

                    @daniel Yes it's with that release! but it's also the same with FTP there is modification of the original file like I explain in an other post like "bytearray" who became "dytearray" and some part of the code who are missing
                    Jiemde

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

                      @Jiemde have you tried formatting the file system?

                      import os
                      os.mkfs('/flash')
                      
                      J L 2 Replies Last reply Reply Quote 0
                      • J Offline
                        Jiemde Pybytes Beta @daniel
                        last edited by Jiemde

                        @daniel Just do it, but nothing change!
                        Changed the WiPy with an other and the result is the same!

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

                          @daniel
                          if you look at my post
                          https://forum.pycom.io/post/3254
                          it looks same as @Jiemde problem
                          i have also malformed files - look for line oryginal file in my post

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

                          Pycom on Twitter

                          Pycom