Help save net neutrality! Learn more.
Close

Pixel write performance

Anonymous
2011-08-10
2013-04-29
  • Anonymous - 2011-08-10

    Hi there,

    I've been looking at this firmware, and from what I'm understanding, each time a pixel is to be written, the firmware has to ask the LCD for the contents of 8 pixels, then OR that to the new one and then write that data back to the LCD.

    I'm wondering… wouldn't it be faster to just store a local copy of the LCD contents so that it doesn't have to fetch the data all the time? To me it looks like that would most likely improve performance a lot.

    Did you consider this possibility?

     
  • Jennifer Holt

    Jennifer Holt - 2011-08-10

    I did think of this, and it would help the write performance by a factor of 2(As well as lot of other cool effects). However, I wrote the code to be usable on the SparkFun board, and the mega168 does not have enough ram to store an entire frame.  If you build a custom board with a larger processor, this would be a great way to do it.

     
  • Jim M

    Jim M - 2013-03-18

    Now THIS I find very interesting. My Mega644P has scads of room (4K). The entire pixel space would take up 1K. On top of the ~560 bytes its using now, it would even fit in the 324P.

     

Log in to post a comment.