E2Studio GUIX - Raw Image is Noisy When Rendered

Hello everyone!

In my application, I use GUIX and a TFT display.

To extract the current image of the display, I am using the Memory Monitor of E2Studio.

I configure it to show the g_display_fb_background variable as a Raw Image with the following configuration.

I am using breakpoint before making a capture to make sure the image is "static".

However, the images rendered are noisy and "line distorted" (not one or the other, both at the same time on the same image).

Here are two fragments of the whole image showing the problem:

1) Line Distortion: 

2) Noisy background (it should be a single color, without these dots) 

I need them to be clear.

Any ideas what is causing this?

ps: g_display_fb_background[1] is just as noisy

Thanks a lot!!

Parents Reply
  • Hello!

    I still have the problem and need help with it.

    Thanks for both topics you mentioned, but they are related to the LCD rendering.

    My LCD rendering is fine (without line glitches or noisy pixels). 

    Sorry if my first post isn't clear enough. I'm talking about rendering the image the LCD is displaying (which, again, is displaying fine) in E2Studio, like the image below:

    ps: regardless, I tried disabling "Enable 2D Drawing Engine" (according to the first topic) and it didn't help.

  • Hi Lil' Joe,

    Thanks for your patience!  JB brought this to my attention and I was able to ask some advice from one of our applications engineers.  Here are his thoughts:

    I think that the issue may be either a hardware interface (signal quality) from the MCU to the panel or related to the r_glcd settings. I would make sure that the GLCD timing parameters in the settings match the panel requirements. For example, if the panel uses data enable signaling they need to select the correct polarity for the signal. Likewise the sync edge can be set to either rising or falling edge. I’ve seen display glitches on customer panels due to the incorrect edge being used – it looks like it works except for the occasional artifacts on the screen. The pixel clock should also match the requirements of the panel for proper operation.

    So, in summary, let's make sure that our signal integrity is high on the hardware side and then check those GLCD timing parameters on the software side.  Let us know how it goes!


    If this response, or one provided by another user, answers your question, please verify the answer. Thank you!
    Renesas Engineering Community Moderator