Hi ADI Support,
for creating a graphical user interface on an LCD connected via PPI the ADI website suggests CPEG from Swell Software. Are there also from ADI any tools available?
Tommy wrote: Hi ADI Support, for creating a graphical user interface on an LCD connected via PPI the ADI website suggests CPEG from Swell Software. Are there also from ADI any tools available? RegardsThomas
ADI provides a library of graphics primatives in the form of the Blackfin 2D Graphics Library (BF2DGL) which is available on our Software Modules download page (see the link below).
We are also aware of the a number of graphics packages which have been made available for the Blackfin, including the following (and probably more):
SDL - Simple DirectMedia Layer - http://www.libsdl.org/Qt - Graphics View - http://doc.trolltech.com/4.2/graphicsview.htmlDirectFB - DirectFB 2.0 - http://www.directfb.org/Adobe Flash Player -http://www.calsoftlabs.com/Adobe-flash-player/flash-porting.htmlMicrium - uC/GUI - http://www.micrium.com/products/gui/gui.htmlWRTime - http://www.wrtime.com/Swellsoft - http://www.swellsoftware.com/Altia - http://www.altia.com/
Just saw the new BF 2D library. Are there any more details on this available. Like does it support anti-aliasing, subpixel positioning, etc.
Let me know where we can read more.
The major features are listed in this url (http://www.analog.com/en/embedded-processing-dsp/blackfin/BF_GFX2D-00/processors/product.html), For additional details you can download the software and go through the Product Specs Sheet and Product Reference Guide documents that are included in the package.
The current release doesn't support anti-aliasing and subpixel positioning.
I am using the ADI_2D graphic lib. The required lib libadi_graphics2d.dlb needs about 2.4 MByte. Could you explain why the size of the lib requires 2.4 MByte?
Thanks for help!
The library itself needs two medium size chunks of memory; one of them is a read memory to store font information and another one as a temp buffer. They are in the memory sections called adi_slow_prio_r and adi_slow_prio_temp.
In addition the library needs the application code to allocate two more big chunks of memory.
One of them is for display. For BF54x and BF527 where there is a LCD, the display size is 480x272. Since RGB888 is the display format, space allocated for each display buffer is 480x272*3. We have 2 of them in the example code to operate in ping-pong mode. This adds up to 783K Bytes.
The second big buffer allocated by example code is for overlays. Overlay is the buffer (or canvas) where the image is drawn before it is transferred to display buffer. There are 3 overlays used in the example code though application can use more or less. At the minimum one overlay buffer is required. The overlay buffer is of display buffer size (480x272). It is in ARGB (Alpha Red Green Blue) format. So, the size is 480x272*4. Since 3 buffers are used the memory allocated is 480x272*4*3 = 1.5M.
Depending on application requirement, these buffer requirements can be scaled up or down. I believe the numbers you are referring to is from our example code.
Hope this helps.
Retrieving data ...