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 ... 34 35 [36] 37 38 ... 50
526
Discussion - EVE / Re: screensaver bitmap out of screen
« on: August 24, 2020, 04:05:38 PM »
Hello,

What display settings are you using in your code?

Best Regards,
BRT Community

527
Test and Review Area / Re: BRT_AN_025 Beta - Portable MCU library for EVE
« on: August 24, 2020, 04:02:09 PM »
Hello,

Glad to hear you have found a suitable solution to the issue you were seeing!
We will keep this in mind for the full release of BRT_AN_025.

Best Regards,
BRT Community

528
Discussion - EVE / Re: Bug: invalid options in commands are handled badly
« on: August 24, 2020, 03:56:49 PM »
Hello,

Thanks for the feedback!
Our normal suggestion would be to do error checking for invalid parameters within the code library.
however I will pass this on to the development team to see if such a feature can be added for future revisions of EVE.

Best Regards,
BRT Community

529
Discussion - EVE / Re: BT816 Screen Refresh
« on: August 14, 2020, 09:10:25 AM »
Hello,

Your assumption was correct as you can send a screen to EVE and it will persist until you draw the next screen or power down etc.

You should not need to re-send your display to refresh the screen unless you want to change the screen content.

What does your MCU/SPI bus do once you have sent the screen? Does the SPI remain completely idle or are you performing other operations (even to other SPI devices if they share the same lines with different chip select)?

If you stop sending any SPI commands after the screen is complete and displayed, does it make a difference?

Also, ensure the chip select is de-asserted when not taking to the BT816,

Best Regards, BRT Community

530
Discussion - MCU / Re: Opportunities of implementing MQTT and their benefits
« on: August 10, 2020, 02:20:35 PM »
Hello,

It is a method used in C to allow the passing of arbitrary data (as void *) to a function. The function can then optionally perform actions to determine how to handle the data. In this case a pointer is made to the data which assumes the data is of a particular structure.

The MQTT client in lwIP has an arbitrary argument which is passed to each callback function. This argument can be used to tell between different contexts (e.g. for different MQTT subscriptions etc). This argument is for the callback to mqtt_subscribe where a mqtt_incoming_publish_cb_t is passed. The argument passed to the callback allows the code to work out what to do with the incoming data.

Best Regards,
BRT Community

531
Discussion - MCU / Re: Opportunities of implementing MQTT and their benefits
« on: July 24, 2020, 04:36:57 PM »
Hello,

This is basic C language. It is called a typecast. More information on this is available online.

Best Regards,
BRT Community

532
Discussion - EVE / Re: Change polarity of Display Enable pin (DE)?
« on: July 23, 2020, 04:42:03 PM »
Hello,

Unfortunately it is not possible to alter the polarity of the DE pin on the BT81x.
In such a case you would need to employ an Invertor IC.

Best Regards,
BRT Community

533
Discussion - EVE / Re: Drawing filled polygon
« on: July 21, 2020, 04:08:29 PM »
Hi,

We're glad it helped,

Here is a way to add the gradient. You can draw the gradient based on the stencil:

Code: [Select]
CLEAR(1, 1, 1)); // clear screen

STENCIL_OP(INCR, INCR)
COLOR_MASK(0,0,0,0)
BEGIN(EDGE_STRIP_L)
VERTEX2II(30,100,0,0)
VERTEX2II(100,100,0,0)
VERTEX2II(150,150,0,0)
VERTEX2II(150,250,0,0)
VERTEX2II(100,300,0,0)
VERTEX2II(30,300,0,0)
VERTEX2II(80,250,0,0)
VERTEX2II(80,150,0,0)
VERTEX2II(30,100,0,0)
END()

STENCIL_OP(KEEP, KEEP)
COLOR_MASK(1,1,1,1) )
STENCIL_FUNC(EQUAL, 1, 255)
CMD_GRADIENT(73, 69, 0x0000FF, 80, 334, 0xFF0000)

STENCIL_FUNC(ALWAYS,0,255)
LINE_WIDTH(32)
COLOR_RGB(255, 255, 255)
BEGIN(LINE_STRIP)
VERTEX2II(30,100,0,0)
VERTEX2II(100,100,0,0)
VERTEX2II(150,150,0,0)
VERTEX2II(150,250,0,0)
VERTEX2II(100,300,0,0)
VERTEX2II(30,300,0,0)
VERTEX2II(30,300,0,0)
VERTEX2II(80,250,0,0)
VERTEX2II(80,150,0,0)
VERTEX2II(30,100,0,0)
END()
DISPLAY()
Best Regards, BRT Community

534
Discussion - EVE / Re: Drawing filled polygon
« on: July 20, 2020, 04:01:28 PM »
Hi,

Welcome to the forum,

This code works to produce your shape using a similar technique to what you were already using but with a left hand edge strip.

Maybe some other users can improve on it too

Best Regards, BRT Community

Code: [Select]
CLEAR(1, 1, 1)); // clear screen

COLOR_RGB(255, 100, 0)
STENCIL_OP(INCR,INCR)
COLOR_MASK(0,0,0,0)
BEGIN(EDGE_STRIP_L)
VERTEX2II(30,100,0,0)
VERTEX2II(100,100,0,0)
VERTEX2II(150,150,0,0)
VERTEX2II(150,250,0,0)
VERTEX2II(100,300,0,0)
VERTEX2II(30,300,0,0)
VERTEX2II(80,250,0,0)
VERTEX2II(80,150,0,0)
VERTEX2II(30,100,0,0)
END()

COLOR_MASK(1,1,1,1) )
STENCIL_FUNC(EQUAL, 1, 255)
BEGIN(EDGE_STRIP_L)
VERTEX2II(300,0,0,0)
VERTEX2II(300,300,0,0)
END()

STENCIL_FUNC(ALWAYS,0,255)
LINE_WIDTH(32)
COLOR_RGB(255, 255, 255)
BEGIN(LINE_STRIP)
VERTEX2II(30,100,0,0)
VERTEX2II(100,100,0,0)
VERTEX2II(150,150,0,0)
VERTEX2II(150,250,0,0)
VERTEX2II(100,300,0,0)
VERTEX2II(30,300,0,0)
VERTEX2II(30,300,0,0)
VERTEX2II(80,250,0,0)
VERTEX2II(80,150,0,0)
VERTEX2II(30,100,0,0)
END()
DISPLAY()

535
Discussion - EVE / Re: BT815 with Capacitive ST1633
« on: July 17, 2020, 03:44:12 PM »
Hi,

I'm afraid that only the CTP listed in AN_336 below will work with EVE (in some cases others which have identical I2C protocol and registers to the supported ones may also work but some of these even have very subtle differences)

https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/AN_336_FT8xx-Selecting-an-LCD-Display.pdf

If you are not able to use a screen which has a CTP which is supported, you may also be able to use the Touch Host mode mentioned in AN_336 where your MCU connects to the CTP, and takes readings and writes them back to registers on EVE over the usual SPI link. That way you can support a wider range of CTP as your MCU can account for any differences in I2C protocol.

Best Regards,
BRT Community

536
Discussion - EVE / Re: Can the FT813 drive a 854x480 (FWVGA) display ?
« on: July 15, 2020, 01:37:14 PM »
Hello,

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. It is possible to run EVE at higher resolutions, but this will result in a slower refresh rate for the screen.

If we take a working example from the following WQVGA settings:
 
Code: [Select]
// 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 the clock down to 30Mhz (assuming system clock of 60Mhz).

Result = 30,000,000/487,200 = ~ 61 fps

In short, yes EVE can drive a FWVGA display, you would just achieve a slightly slower refresh rate than using a WVGA display for example.

Best Regards,
BRT community

537
Discussion - EVE / Re: FT800 Bitmap Handles
« on: July 13, 2020, 03:27:57 PM »
Hello,

Could you advise how large your images are when de-compressed? Also, could you post some code snippets of how you load the images to the bitmap handles and then how you display them?

If you prefer not to post code, you can email us at support.emea@brtchip.com

Best Regards,
BRT Community

538
Discussion - MCU / Re: FT900 Watchdog no reset
« on: July 08, 2020, 05:15:59 PM »
Hello,

Please refer to our watchdog example as part of AN_360 FT9xx Example Applications.

Full source code is provided to allow you to see the watchdog in operation.

This can be found at the following location as part of the FT9xx Toolchain.

C:\Users\Username\Documents\Bridgetek\FT9xx\2.5.0\Examples\Watchdog Example 1

You can also refer to AN_365 FT9xx API Programmers Manual for more information on the watchdog API functions.

Best Regards,
BRT Community

539
Discussion - EVE / Re: BRT81x blob and SPI RAM instead of Flash
« on: July 06, 2020, 02:47:49 PM »
Hello,

Quote from: TSL on July 03, 2020, 12:48:22 AM
Question 1.
Espressif has produced the SPI PSRAM recently. It is 64Mbit in size and could make a great option for RAM_G extension.
Is it possible to use it with BRT81x?
The PSRAM has a partly compatible to SPI Flash generic command set, it has QSPI mode, but the detect may be complicated because ID commands differ. I'm afraid that CMD_FLASHATTACH will simply fail with PSRAM.
I would greatly appreciate the authoritative comment on this.

Question 2.
Is it possible to modify or recompile the blob to create an own version for custom purposes? E.g. the case above needs 8 dummy cycles for PSRAM to read in QSPI fast mode.
What is blob format? Is it an executable code or a set of parameters? I couldn't find any info on this in the official documentation.
Could you please clarify these aspects?


Currently using an external PSRAM IC to extend RAM_G is not supported by EVE. We are looking into the possibility of adding this feature for future versions of EVE. Was this the only reason you were looking into using this PSRAM IC?

Best Regards,
BRT Community

540
Discussion - EVE / Re: screensaver bitmap out of screen
« on: July 06, 2020, 02:43:27 PM »
Hello,

Yes this is to be expected, it is a function of how the bitmap is placed on the screen.
The bitmap is positioned via the top left corner of the image when drawn. i.e. the x/y used by VERTEX2F represents the top left of the image. The VERTEX2F command updated via the macro register when using the screensaver command updates according to the screen parameters used, so it is possible that the bitmap may move off of the screen.

It is possible to use some translate commands to centre the image on the VERTEX2F position used, however this may still result in section of the bitmap appearing to be off of the screen.

Best Regards,
BRT Community

Pages: 1 ... 34 35 [36] 37 38 ... 50