Jump to content

Search the Community

Showing results for tags 'oled'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Calendars

  • Community Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. While preparing a tutorial I came across an issue with all Digilent IP associated with the 128x32 Monochrome OLED display module that appear on numerous Digilent products. There are numerous versions of VHDL and Verilog source code to demonstrate how to use the OLED display that have been posted over the years that the display has appeared on Digilent products. Unfortunately, none of them function properly. The most concerning is the manipulation of the Vbatt and Vdd FET control signals. Digilent acknowledges that not observing a recommended power-on and power-off can have deleterious effects on the display hardware over time. From the PmodOLED Reference Manual: "The PmodOLED has a particular power-on/power-off sequence that must be followed to prolong the life of the display." From the vivado-library PmodOLED_V1_0 README.md file: "To make sure that the Pmod OLED isn't damaged, make sure to safely quit the demo." I haven't checked this version as it only supports ZYNQ or MicroBlaze designs and the source is in the form of a pre-compiled netlist. As for the Verilog and VHDL code versions, none of them actually work as advertised. Specifically, there is no power-off activity on the control pins. In the case of the latest published Verilog code the OLEDCtrl.v code has major flaws that prevent if from being suitable for any of the demos. When there is a possibility of damaging hardware it is vital that the designer actually verify that the design works as intended. I did this using an oscilloscope and by simulation. Obviously, no one at Digilent, including the many coders who've massaged the design, have bothered to do either of those verification steps. I hacked the OLEDCtrl.v to at least manipulate the display power controls properly, and over repeated power-on and power-off cycles; but the code is so overly complicated and badly structured that I don't have the time to correct it's deficiencies. It's not my responsibility to do this for Digilent IP even if I were so inclined. I thought about writing my own OLED controller but it's beyond the scope of my tutorial. I suggest having someone completely re-write the OLED controller from a fresh start. Since it requires absolute timing it should work with any input clock. This can be done with generic or parameter specifications. Make it simpler so that whoever designs it, or modifies it, can understand what the heck is going on. Verifiy that the code does what it claims to be doing with a proper testbench simulation Verify control pin behavior with an oscilloscope. Given the severity and number of products involved, I'd expect that Digilent would want to address this issue ASAP
  2. Hi, I want to connect the pmod oled display to my raspberry pi, but I'm not really getting the hang of how I should wire it. If someone can explain where to plug in each pin and how to code it that would be great. Thank you.
  3. Hi, I use uC 32 and Basic I/O shield in my microcontroller programming class. I am using utility functions provided in class to display strings on the OLED, but it is not working. I am not sure whether it is me that made mistake or the OLED is broken. All other things (SW, BTN, ADC, and LED's) are working fine with the utility functions provided to control them. I tried to get help from TA, but with remote class and all, it is rather difficult. Can someone share a easy way to check if the OLED is functional? I am using Pickit3 to program uC32. Let me know if you need any more information.
  4. Hi, I'm a newbie trying to learn about the Genesys 2 board and would like to program the onboard OLED as an exercise. I'm following this tutorial. There is a prominent warning that says "Important! Make sure to turn off the OLED display before shutting down or reprogramming your board." Why? What will happen if I don't turn off the OLED display and simply turn off the power switch? Will it get damaged? This makes me very nervous to try my own programs since I will probably mess up at some point. Can someone reassure me that I won't do any permanent damage? Thanks!
×
×
  • Create New...