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 - BRT Community

Pages: 1 ... 19 20 [21] 22 23 ... 50
301
General Discussion / Re: Turning On the display
« on: September 27, 2021, 11:38:00 AM »
Hello,

Thank you for your query.

The following link will take you to the BT81X Series Programming Guide: https://brtchip.com/wp-content/uploads/2021/09/BRT_AN_033_BT81X-Series-Programming-Guide.pdf.

In this guide, section 2 contains information on startup. Please take a look at section 2.4 in particular as it describes the initialization sequence during boot up.

If you need any more information please get in touch.

Best regards

BRT Community

302
Discussion - EVE / Re: PALETTED4444 byte count
« on: September 24, 2021, 10:26:41 AM »
Hello,

On Paletted 4444 the stride would be 64 as it will have one byte per pixel.

The Paletted formats differ from the ARGB4444 in that the ARGB4444 have 2 bytes per pixel with the alpha and RGB values (4-bits each). The Paletted format instead has a byte per pixel which then refers to an index in the color palette (see the LUT (Look Up Table)  file which is also created).

You therefore get better color depth but only with a limited range of colours.

You'll probably find that the paletted 4 is just over half the size of ARGB4 because it uses this one byte per pixel plus a bit extra for the LUT.

We have a command GETPROPS which can check the next available free address after the loadimage is completed (on a PNG only) and so you can subtract the starting address (which you specified in LOADIMAGE) from your next free address returned by GETPROPS to get the size. If you use BT817/8 we also have CMD_GETPTR which does this.
You can find one example in section 7.3 below of GETPROPS
https://ftdichip.com/wp-content/uploads/2020/07/BRT_AN_014_FT81X_Simple_PIC_Library_Examples.pdf

Best Regards, BRT Community



303
Discussion - EVE / Re: Unwanted stripes on the EVE4 1024x600 picture
« on: September 24, 2021, 10:14:42 AM »
Hi JuSil,

You can also put the image into flash with the EVE Screen Editor and so that might be worth trying

If it also gives the lines in ESE when you output to the module, could you send us a copy of the image and we can try it,

EVE4 also has a few features which can help to give more time for the display lines to be rendered. Please see page 51 of the Programmers guide:
https://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/BRT_AN_033_BT81X_Series_Programming_Guide.pdf

- Adaptive Frame rate varies the PCLK to allow more time for the screen to be rendered in cases where there are a lot of items to render. however, it is for RGB panels only and not all panels support it. Therefore, you could check this is off,

- REG_AH_HCYCLE_MAX is a new feature in BT817/8 which instead extends the HCYCLE value in cases where there are too many items to render in the time available (e.g. how much time one row has based on PCLK and number of pixels in a row). You could try this to see if allowing EVE to extend the HCYCLE time helps.

- There is also REG_UNDERRUN which allows you to check if the underrun is occurring and if so the REG_AH_HCYCLE_MAX may help.

If it works from RAM, it sounds like the image data being read from flash is slowing down the rendering. You could check that the BLOB is loaded and that the flash is in full speed mode. Also, if you try a lower quality conversion of the same image this may help to confirm if the issue is related to this.

For flash programming, please ensure that your module gets sufficient power from the USB adapter  as if the voltage to EVE or the flash droops, you get communication errors. Also, make sure all of the SPI cables are well connected and are as short as possible to avoid any signal quality issues.

Best Regards, BRT Community


304
Discussion - EVE / Re: Unwanted stripes on the EVE4 1024x600 picture
« on: September 20, 2021, 05:03:59 PM »
Hello,

Thank you for you inquiry, could you please advise where the image is being stored (flash or ram)?

Also could you send the code you are using to display it and the image you are trying to display?

Best regards

BRT Community


305
Discussion - EVE / Re: Tracking is shifted to the top
« on: September 17, 2021, 05:20:46 PM »
Hi,

Glad to hear that you have resolved it,

You can store the calibration values in your MCU's Flash/EEPROM by running a calibration and once successfully completed, store the six REG_TOUCH_TRANSFORM values in your MCU and then re-write them back on each start-up.

It is worth including a way to force a re-calibration too when doing this (via a button on the screen, or by holding a touch on power-up, or by a physical button on your PCB if you prefer not to have an on-screen way of triggering it)

Best Regards, BRT Community

306
Discussion - EVE / Re: Tracking is shifted to the top
« on: September 15, 2021, 03:03:18 PM »
Hi,

We tried this code below from one of our samples on the BT817 and the touch was aligned on the slider correctly, you could try this to see if it works,

Do you have any other code in your display list which may also be affecting the tracking area?
Also, do you use any screen rotation etc.

Best Regards, BRT Community

Code: [Select]
void eve_display(void)
{
    uint32_t TrackerVal = 0;
    uint8_t TagVal = 0;
    uint16_t SlideVal = 0;
    uint16_t Button3D = 0;
    uint8_t color = 0;
   
    while(1)
    {
        EVE_LIB_BeginCoProList();                                               // Begin new screen
        EVE_CMD_DLSTART();                                                      // Tell co-processor to create new Display List
       
        EVE_CLEAR_COLOR_RGB(0, 0, 0);                                           // Specify color to clear screen to
        EVE_CLEAR(1,1,1);                                                       // Clear color, stencil, and tag buffer
       
        EVE_TAG_MASK(1);                                                        // Enable tagging

        EVE_TAG(2);                                                             // Tag following items with tag 2
        EVE_CMD_FGCOLOR(0x0000FF);                                              // Blue foreground color
        EVE_CMD_BUTTON(100, 200, 80, 30, 27, Button3D, "Button");               // Draw button
       
        EVE_TAG(5);                                                             // Tag following items with tag 5
        EVE_CMD_SLIDER(300, 100, 200, 30, 0, SlideVal, 255);                    // Draw a slider
        EVE_CMD_TRACK(300, 100, 200, 30, 5);                                    // Place a tracker
       
        EVE_TAG_MASK(0);                                                        // Mask tagging so that following items won't be tagged
       
        EVE_BEGIN(EVE_BEGIN_POINTS);                                                    // Draw a dot in red at 140, 100)
        EVE_POINT_SIZE(30*16); 
        EVE_COLOR_RGB(color, 0, 0);                                             // Set colour to blue and write some text
        EVE_VERTEX2F((140*16), (100*16));
        EVE_END();
       
        EVE_DISPLAY();                                                          // Tell EVE that this is end of list
        EVE_CMD_SWAP();                                                         // Swap buffers in EVE to make this list active

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

        // ------ read tag and tracker values --------
        TagVal = HAL_MemRead8(EVE_REG_TOUCH_TAG);                                   // Get Tag value
        TrackerVal = HAL_MemRead32(EVE_REG_TRACKER);                                // Read the value of the tag and track register

        if(TagVal == 2)   
        {// If button pushed tag register will read 2
            color = 0xFF;                                                       // change red amount to 255
            Button3D = 256;                                                     // Give the button a pushed-in appearance
        }
        else 
        {// Otherwise...
            color = 0x00;                                                       // change red amount to 0 so dot is not visible
            Button3D = 0;                                                       // Button has 3D effect (not pushed in))
        }
       
        if(TagVal == 5)                                                         // if slider touched...
        {
            SlideVal = (TrackerVal >> 24);                                      // ... then get the tracker value.
            // Note: Value of tracking is 16 bits but we only use upper 8 bits since the slider is set for 8 bit resolution
        }
               
       
        // Result of button press and slider value will be displayed next time round
    }
}
   

307
Discussion - MCU / Re: Firmware flash issue on target board
« on: September 14, 2021, 05:10:42 PM »
Hello Mathieu,

It would be best to contact support with an email so we can better assist you on this issue as there is quite a lot of information to send.

Please use this link to find the support team's email address: https://brtchip.com/contact-us/

Best regards,

BRT Community


308
Discussion - EVE / Re: Rotating a text
« on: September 07, 2021, 04:54:45 PM »
Hello,

There are several ways to do it and we will post a small example. The text rotation is normally done on a character by character basis or you can rotate the entire completed string as a single bitmap.

Best regards

BRT Community

309
Hello,

The following code will draw the desired circle with the line through it,

Code: [Select]
BEGIN(LINES)
LINE_WIDTH(48)
COLOR_RGB(0x0, 0xFF, 0xFF)
VERTEX2F(1688, 1384)
VERTEX2F(4768, 5056)
END()

BEGIN(POINTS)


CLEAR_COLOR_A(0)
COLOR_MASK(0, 0, 0, 1)

BLEND_FUNC(ONE, ONE_MINUS_SRC_ALPHA)
POINT_SIZE(1600)
VERTEX2F(3200, 3200)

BLEND_FUNC(ZERO, ONE_MINUS_SRC_ALPHA)
POINT_SIZE(1520)
VERTEX2F(3200, 3200)

COLOR_MASK(1, 1, 1, 0)

BLEND_FUNC(DST_ALPHA, ONE)
COLOR_RGB(3, 182, 0)
POINT_SIZE(1600)
VERTEX2F(3200, 3200)
BLEND_FUNC(SRC_ALPHA, ONE_MINUS_SRC_ALPHA)

END()

However after some investigation it appears as if the CLEAR_COLOR_RGB command is causing the behaviour you are seeing where the circle isn't being drawn. For example if you alter this to black or red the circle is drawn correctly. I believe this sample was designed only to utilise a black background, but I will confirm this with the development team, and in the meantime investigate a solution to this issue.

Best Regards,
BRT Community

310
Hello,

Thank you for your question, would you be able to provide an example of what you are trying to draw on the screen for reference?

Best Regards,
BRT Community

311
Hello,

I've chased the developers up on this to see if we can make it happen.

I would like to second the vote on upping the font size, I know that would be helpful for my project, thank you!

T

Best Regards,
BRT Community

312
Discussion - EVE / Re: EVE Asset Builder
« on: August 20, 2021, 11:25:27 AM »
Hello,

Thank you for the details.

Yes, actually EAB 2.3 was supposed to have been released, however we found an issue in the ASTC convertor and we are rolling all of these updates into EAB 2.4 which I expect to released in the second week of September..

Best Regards,
BRT Community

313
General Discussion / Re: Linux toolchain
« on: August 10, 2021, 05:07:47 PM »
Hello,

We only provide the toolchain for Windows.

However we have heard other customers having the tools compiled for both mac and linux, and everything is functioning just fine.
This is because the tools used are open source.

See AN 325 FT9xx Toolchain Installation Guide for more information.

The only issue is programming the part.
You can, of course, use the open-source dfu-util to program the part, however if you end up breaking dfu mode, you have to use windows to recover with the one-wire programmer (FT900Prog.exe).
Your application code should have a DFU interface included if you want to use that. DFU is good for in-field updates but not during the development phase. See the GPIO DFU Example in AN_360 for reference.

So unfortunately we can’t support the toolchain on anything other than Windows.

Best Regards,
BRT Community

314
Discussion - EVE / Re: REG_CMDB_WRITE bulk transfer
« on: August 10, 2021, 04:51:12 PM »
Hi Paul,

Yes, you can also use burst writes on other areas of memory too as Rudolph mentioned (e.g. to write image data to RAM_G) which helps to speed this up a lot,

Best Regards, BRT Community

315
Discussion - EVE / Re: Button press/release vs. holding example
« on: August 09, 2021, 11:44:20 AM »
Hello,

Thank you for your question.

Unfortunately there isn't any functionality within the touch registers on EVE that would denote a 'hold' at a specific touch location on the screen or tagged object.
This functionality would need to be implemented in your MCU code, for example your touch routine would need to determine if first, a touch has occurred, then if the touch is on a tagged object, then you check that within a given time period that the REG_TOUCH_TAG register is still reporting the same value, to establish if a 'hold' has occurred.

Best Regards,
BRT Community

Pages: 1 ... 19 20 [21] 22 23 ... 50