The EVE series of ICs do not include a frame buffer, they dynamically clock out each computed pixel on the screen. A displays size and what the Pixel Clock is running at will determine the achievable performance.

If we take the example from the following WQVGA settings:
    // WQVGA display parameters
   lcdWidth   = 800;                                                            // Active width of LCD display
   lcdHeight  = 480;                                                            // Active height of LCD display
   lcdHcycle  = 928;                                                            // Total number of clocks per line
   lcdHoffset = 88;                                                             // Start of active line
   lcdHsync0  = 0;                                                               // Start of horizontal sync pulse
   lcdHsync1  = 48;                                                            // End of horizontal sync pulse
   lcdVcycle  = 525;                                                           // Total number of lines per screen
   lcdVoffset = 32;                                                            // Start of active screen
   lcdVsync0  = 0;                                                              // Start of vertical sync pulse
   lcdVsync1  = 3;                                                              // End of vertical sync pulse
   lcdPclk    = 2;                                                                  // Pixel Clock
   lcdSwizzle = 0;                                                              // Define RGB output pins
   lcdPclkpol = 1;                                                              // Define active edge of PCLK
                   

HCYCLE = 928
VCYCLE = 525
VCYCLE * HCYCLE  = 487,200

Note: REG_PCLK is using the value 2 which will divide PCLK down to 30Mhz.

Result = 30,000,000/487,200 = ~ 61 fps
 
 
If there are too many elements (display list items which intersect a given point) to compute for a pixel, this is when you will see corruption. Which is why reducing the PLCK (and thus the frame rate) will remove some errors, essentially you are giving EVE more time to compute what should be on a given line. I would suggest dividing PCLK down further to see if this improves the results.
 
Our new BT81X has a feature that will vary the PLCK allowing for more computational elements if the screen supports this. What EVE IC are you using?

Hello,

The core issue here relates to the size limitation of RAM_G.

Rudolph has covered the main options, scaling down the image or using the ASTC image type.

The encoding process for ASTC is quite slow, compared to decoding.
There is a real-time encoder called ASTCRT, (https://github.com/daoo/astcrt). You could try encoding the JPEG stream to ASTC stream on the fly. I may suggest they can use block size 6x6 and veryfast option while encoding.

Best Regards,
BRT Community

Hello Chris,

This could be an ESD issue if you are only experiencing this issue whilst not at your desk.

Is it the Cleo50 or Cleo35 modules you are using?

Best Regards,
BRT Community

Hello Juergen,

We're currently investigating this and will continue our discussion by email at the moment and we'll post an update here once we have closed the issue for other users to refer to in future. We'll send you another email in case you missed our first reply.

Best Regards,
BRT Community

Hello,

Yes the only difference is the IC which contains FT900 RevC.
We are working to get this corrected on the website.

The I2C1_SDA and I2C1_SCL signals are available via CN3 (GPIO47 and GPIO46 respectively).
I2C bus external pullups are also present on the hardware.

Many I2C devices (127) can be connected to the same I2C master.

Best Regards,
BRT Community

Hello Filippo,

The 2nd bullet point was already confirmed by us.

Let us look into the first point.

If there are any code errors, we will update in the next toolchain release.

In any case, the source code is provided so you can make any changes.

Best Regards,
BRT Community

Hi Rudolph,

Thanks for your feedback. We'll discuss these points with our development team and get back to you on these.

Best Regards, BRT Community