BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - rsc

Pages: [1]
1
Discussion - EVE / Fonts and xxx.ttf files
« on: December 11, 2019, 01:16:37 PM »
Hello,

I want to generate a font for traditional and simplified Chinese.
this already works with the simfang.ttf and the eve asset builder.
Now we want to use other xxx.ttf files for fonts.

which xxx.ttf files one can I still use for this (except licenses)? What else do I have to consider to display the xxx.ttf files correctly?

Best Regards
rsc

2
Hi,

as already described, if i read out the end address i get the start address. See lines:
ParameterAddr = ((Reg_Cmd_Write_Offset - 12) & 4095);                       // Go back by 12 bytes to get end address parameter
End_Address = EVE_MemRead32((RAM_CMD + ParameterAddr));

used pic:
home_v4.jpg JPEG to show on display
home_v4_converted.jpg generated with EAB 1.0 in Output Format: PNG/JPEG (EVE Product Range: FT81x)
home_v4_converted.h generated with HxD tool

// var
extern unsigned char u8f_MainHomeJPG_60x60[2649]; // home_v4_converted.h converted and generated header file for home_v4.jpg

//code
void main(void)
{
    uint32_t u32_ErrorCode = (uint32_t)e_NO_ERROR;
   
    u32_ErrorCode = u32_MCUconfig_SystemInit(); // RSC timer 1 active!!!
       
    if ( (uint32_t)e_NO_ERROR == u32_ErrorCode )
    {
        v_MCUconfig_App();  // MCU app init
       
        APP_Init();         // EVE initialisation
    }
   
   
    if ( (uint32_t)e_NO_ERROR == u32_ErrorCode )
    {
 
        APP_LoadImageRSC_JPG();

    }
   
   
    while ( 1 )
    {

    }//end of while   
   
}

//----------------------------------------------------------------------------------------------------------

void APP_LoadImageRSC_JPG(void)
{
    uint16_t Reg_Cmd_Write_Offset = 0;
    uint16_t ParameterAddr = 0;
    uint32_t End_Address = 0;
    uint32_t Width = 0;
    uint32_t Height = 0;
    uint32_t StartAddress = 0;
       
    API_LIB_BeginCoProList();                                                   // Begin new co-processor list
    API_CMD_LOADIMAGE(StartAddress,0);                                          // Load image command. Extract data to RAM_G + 0, options = 0
    API_LIB_EndCoProList();                                                     // Finish the co-processor list
    API_LIB_WriteDataToCMD(u8f_MainHomeJPG_60x60, sizeof(u8f_MainHomeJPG_60x60)); // Send data immediately after the command (since we don't select MEDIAFIFO as source in Options))
    API_LIB_AwaitCoProEmpty();                                                  // Await completion of the Load Image. Image will now be in RAM_G
       
    // ###### Check parameters of decompressed image ########
    API_LIB_BeginCoProList();                                                   // Begin co-pro list
    API_CMD_GETPROPS(0, 0, 0);                                                  // GetProps command with three dummy 32-bit values
    API_LIB_EndCoProList();                                                     // Finish the co-processor list
    API_LIB_AwaitCoProEmpty();                                                  // Await the command completion

    Reg_Cmd_Write_Offset = EVE_MemRead16(REG_CMD_WRITE);                        // Check current pointer value

    ParameterAddr = ((Reg_Cmd_Write_Offset - 12) & 4095);                       // Go back by 12 bytes to get end address parameter
    End_Address = EVE_MemRead32((RAM_CMD + ParameterAddr));

    ParameterAddr = ((Reg_Cmd_Write_Offset - 8) & 4095);                        // Go back by 8 bytes to get width parameter
    Width = EVE_MemRead32((RAM_CMD+ParameterAddr));   

    ParameterAddr = ((Reg_Cmd_Write_Offset - 4) & 4095);                        // Go back by 4 bytes to get height parameter
    Height = EVE_MemRead32((RAM_CMD+ParameterAddr));   
   
    // ######################################################     

    API_LIB_BeginCoProList();                                                   // Begin new screen
    API_CMD_DLSTART();                                                          // Tell co-processor to create new Display List
    API_CLEAR_COLOR_RGB(0, 0, 0);                                               // Specify color to clear screen to
    API_CLEAR(1,1,1);                                                           // Clear color, stencil, and tag buffer
    API_COLOR_RGB(255,255,255);                                                 // White colour will display image with original colours
   
    API_BITMAP_HANDLE(0);                                                       // Tell FT81x the properties of the bitmap we will display.
    API_CMD_SETBITMAP( 0, RGB565, Width, Height); // source (RAMG), Format, size_x, size_y
       
    API_BEGIN(BITMAPS);     
    API_VERTEX2II( 100, 100, 0, 0); // x, y, handle, cell                                                // Display image at (200,200)
    API_END();
   
    // ###### OPTIONAL SECTION - print parameters of decompressed image ########
//    API_COLOR_RGB(255,255,255);                                                 // Print labels
//    API_CMD_TEXT(300, 200, 28, 0, "End Addr");
//    API_CMD_TEXT(300, 240, 28, 0, "Width");   
//    API_CMD_TEXT(300, 280, 28, 0, "Height");   
//   
//    API_CMD_NUMBER(400, 200, 28, 0, End_Address);                               // Print associated values
//    API_CMD_NUMBER(400, 240, 28, 0, Width);
//    API_CMD_NUMBER(400, 280, 28, 0, Height);
//    API_CMD_SETBASE(16);
//    API_CMD_NUMBER(500, 200, 28, 0, End_Address);
    // ######  END OF OPTIONAL SECTION - print parameters of decompressed image ########

    API_DISPLAY();                                                              // Tell EVE that this is end of list
    API_CMD_SWAP();                                                             // Swap buffers in EVE to make this list active
    API_LIB_EndCoProList();                                                     // Finish the co-processor list burst write
    API_LIB_AwaitCoProEmpty();                                                  // Wait until co-processor has consumed all commands
   
   //APP_SnapShot2PPM();                                                        // Un-comment to take snapshot (see BRT_AN_014)
   
    while(1)
    {
    }
}

Thanks.

Best Regards
rsc

3
Hello,
I have noticed the following:
We use a 32bit PIC and the FT813. The communication takes place via the SPI bus with 10Mbaud.
When I convert a jpeg image in the EVE Asset Builder 1.0 with the output format PNG / JPEG, then convert the image in HxD into a hexfile and embed it in the program, the image is displayed correctly. However, the end address of the file is read out incorrectly. There is always the start address again in it. The width and height of the picture are returned correctly.
The end addresses of the png files are correctly returned (conversion in the EVE Asset Builder 1.0 to output format RGB565). The following pictures then overlay the picture because they get wrong start address.
Is that a bug or am I doing something wrong?

Best regards
rsc

4
Discussion - EVE / Re: problem with API_COLOR_RGB / display settings
« on: June 04, 2019, 09:23:13 AM »
Hi,

I solved the problem. PCLK for LCD LVDS driver requires a R_pullup or R_pulldown to use rising/falling edge triggered clocking. Both were placed on PCB. I removed R_pulldown and it works.

Best regards
rsc

5
Discussion - EVE / Re: problem with API_COLOR_RGB / display settings
« on: June 03, 2019, 08:32:05 AM »
Hi,

corruption on screen if colours >190 on own board with ft813 and pic32mz2048efm144.

1)   Text APP_Text example with changes for a better indication of the error

API_COLOR_RGB(255,255,255); // terrible
API_COLOR_RGB(190,190,190); // ok

>> do all items (such as points and lines) also show corruption when any of the colours is greater than 190? <<
-   it looks like it's just in connection with text

Thank you in advance.

Best regards,
rsc

6
Discussion - EVE / problem with API_COLOR_RGB / display settings
« on: May 23, 2019, 09:26:48 AM »
hi,

we are using FT813 and pic32mz... on own app-board for our application.
Used display is AT070MP01

timing parameters:
// AT070MP01
    lcdWidth   = 800;                                                           // Active width of LCD display
    lcdHeight  = 480;                                                           // Active height of LCD display
    lcdHcycle  = 960;                                                           // Total number of clocks per line
    lcdHoffset = 88;   // lcdHoffset < (lcdHcycle - lcdWidth)                   // Start of active line
    lcdHsync0  = 0;                                                             // Start of horizontal sync pulse
    lcdHsync1  = 48;                                                            // End of horizontal sync pulse
    lcdVcycle  = 528;                                                           // Total number of lines per screen
    lcdVoffset = 32;   // lcdVoffset < (lcdVcycle - lcdHeight)                  // 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 = 0;                                                             // Define active edge of PCLK

For quick start we are using code from Application Note BRT_AN_014,
FT81X examples using the Microchip PIC microcontroller as the SPI master
with API_Layer, EVE_Layer and MCU_Layer.

Displayd App-Code:
void RSC_Text(void)                                                         
{
    API_LIB_BeginCoProList();                                                   // Begin new screen
    API_CMD_DLSTART();                                                          // Tell co-processor to create new Display List
       
    API_CLEAR_COLOR_RGB(0, 0, 0);                                               // Specify color to clear screen to
    API_CLEAR(1,1,1);                                                           // Clear color, stencil, and tag buffer
   
    API_COLOR_RGB(255, 255, 255);                                               // Set color to white
    API_CMD_TEXT(80, 30, 30, 0, "1) This is a test string! what is going wrong?");                                      // Draw the text string
   
    API_COLOR_RGB(180, 180, 180);                                               // Set color to white
    API_CMD_TEXT(80, 80, 30, 0, "2) This is a test string! what is going wrong?");                                      // Draw the text string
   
    API_COLOR_RGB(180, 180, 0);                                               // Set color to white
    API_CMD_TEXT(80, 130, 30, 0, "3) This is a test string! what is going wrong?");                                      // Draw the text string
   
    API_COLOR_RGB(0, 180, 180);                                               // Set color to white
    API_CMD_TEXT(80, 180, 30, 0, "4) This is a test string! what is going wrong?");
   
    API_COLOR_RGB(191, 191, 191);                                               // Set color to white
    API_CMD_TEXT(80, 230, 30, 0, "5) This is a test string! what is going wrong?");
   
    API_COLOR_RGB(0, 180, 0);                                               // Set color to white
    API_CMD_TEXT(80, 280, 30, 0, "6) This is a test string! what is going wrong?");
   
    API_COLOR_RGB(180, 0, 0);                                               // Set color to white
    API_CMD_TEXT(80, 330, 30, 0, "7) This is a test string! what is going wrong?");
   
    API_COLOR_RGB(200, 191, 190);                                               // Set color to white
    API_CMD_TEXT(80, 380, 30, 0, "8) This is a test string! what is going wrong?");
   
    API_COLOR_RGB(0, 0, 180);                                               // Set color to white
    API_CMD_TEXT(80, 430, 30, 0, "9) This is a test string! what is going wrong?");
     
 
    API_DISPLAY();                                                              // Tell EVE that this is end of list
    API_CMD_SWAP();                                                             // Swap buffers in EVE to make this list active

    API_LIB_EndCoProList();                                                     // Finish the co-processor list burst write
    API_LIB_AwaitCoProEmpty();                                                  // Wait until co-processor has consumed all commands

    //APP_SnapShot2PPM();                                                       // Un-comment to take snapshot (see BRT_AN_014)
   
    while(1)
    {
    }
}

After successfully init we display same strings on display with different
text colors (see appendix).

Problem: if R > 190, G > 190, B > 190 there are distortions in the text to see with
API_COLOR_RGB( R, G, B );
Distortions on displayd lines 1), 5).

Does anyone have any hints?

Best regards
rsc

7
Hi,

an update to issue. If I start the myProject.exe file directly from the folder myProject\Build\ME813AU WH50C\x86 Release\Bin then all pictures are shown. But that does not happen when I do build and update to hardware in eve screen designer 4.5 beta 2. For this, the images do not have to be copied again into the folder. The hint of pauljiao was very close.
Thanks to pauljiao.

Best regards
rsc

8
Hi,

is there any hints why displaying the images fails? I had two examples (ColorPicker and WashingMachine) created and sent to you.
I have to present the results on Monday and there it is decided whether we use the graphics controller or not.

Best regards
rsc

9
hi pauljiao,

thanks for the suggestion. Unfortunately that did not work. The pictures are not displayed

best regards
rsc

10
Discussion - EVE / ME813AU-WH50C DEV BOARD/Eve Screen Designer 4.5 Beta 2
« on: January 18, 2019, 01:15:03 PM »
hi

we are starting a new project with EVE FT813Q. The SampleApps are working fine on
ME813AU-WH50C DEV BOARD with Visual Studio Express 2017 after updated
LibFT4222 files in EVE SampleApp projects.

Now we are using Eve Screen Designer 4.5 Beta 2 with ME813AU-WH50C DEV BOARD.
The Problem is that images are don't displayed on ME813AU-WH50C DEV BOARD screen.
ESD Labels, buttons, progress bars... will displayed on screen but all images,
widgets with images will don't displayed on the screen.

Can you help us with this issue? Should LibFT4222 files updated before starting build and updating to hardware?

Pages: [1]