Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. d4rkr3b3l
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by d4rkr3b3l

    • d4rkr3b3l

      [Solved] Non-healing !TSM:MSG:LEN error hours into run
      Troubleshooting • • d4rkr3b3l  

      8
      0
      Votes
      8
      Posts
      3761
      Views

      Yveaux

      @d4rkr3b3l Good to hear you solved it! And thanks for reporting back how you solved it
    • d4rkr3b3l

      [Solved] PVER Mismatch with MY_DEBUG
      Troubleshooting • • d4rkr3b3l  

      4
      0
      Votes
      4
      Posts
      1410
      Views

      d4rkr3b3l

      Just as an update to anyone that may be interested... My issue was in fact due to RAM usage. I switched from using the GOFi2cOLED library to the u8glib library to drive my OLED display and my ram usage dropped from 91% to 45%. Most OLED libraries (including ADAFRUIT which is the base code for GOFi2cOLED) are going to store the display buffer in ram which makes them a memory hog. Using a 128x64 display means you will consume 8192 bytes just for the display buffer @ 1 byte per pixel, add on top of that all the operational code. The u8glib "pages" the display buffer meaning it can essentially make the buffer as small as you need at the cost of slowing down the refresh rate. For just plain text its not an issue and the paging is not visible on the screen.