BRT Community

I see, so it will work with 0.5W 8Ohm type of speaker, I will try with SMD speaker soldered onboard.

Thank you

Hi,
I have only very little knowledge about audio circuit (amplifier, filter, etc), so please forgive me.

What should be the recommended circuit to connect to the audio output pin (AUDIO_L) on BT815/6 ? So that it can working to play a sound/tone/voice.
and also at the end of the circuit should be connected to a speaker right?
What is the specification of speaker for use with EVE BT815/6 chip?

Thank you.

Hi,

in the EAB custom touch, it said that this custom touch that compile the tiny C language is BT817/8 support only.
Is this method require the CTP interface to be connected directly to host MCU or can just connect to BT817?

In the section 6.7.2 of AN_336, it's using host mode and require the CTP connected to host MCU, and it give example for FT801, FT811/813. While the new approach in the EAB support BT817/8 only. Is there any significant different?

Hi,
is there application note/user manual/tutorial that describe this approach? I can't find it in the datasheet and the programming guide.

and I also want to ask is BT815/7 support ILITEK 2511 touch controller IC?

Thanks

Hi, is this the same with using touch host mode where the host MCU connected to the touch controller IC and fetch the data to EVE?

Thanks

Hi, I just want to ask if BT815 or BT817 support ATMXT336T touch controller IC?
Will it work if we set the I2C address in REG_TOUCH_CONFIG to 0x40 for ATMXT336T ?
just like we set it to 0x5D for Goodix controller and 0x38 for Focaltech IC.

Thanks

Hi, let's say I want to send Host Memory Write/Read to the RAM_CMD circular buffer.
First I set low the SPI CS (Chip Select) line, then I send the address that I'm going to write (this is RAM_CMD address + cmdOffset),
and then I send byte-0, byte-1, byte-2, so on.
I keep sending the SPI clock without pulling high the SPI CS line.
Then when it reach the end address of RAM_CMD (end of circular buffer) will it loop back by itself? or I need to handle this in my program?
(Check when it reach the end, then I pull high CS, then send again the address)
The same when read from RAM_CMD circular buffer, will it loop back automatically when reach the end address?

Thanks

Yes, it turn out to be small bug i missed in my program.
Now it work already, thank you.

Hi, when I use CMD_TEXT it always give me black text.
How to be able to output text with different color using CMD_TEXT?

I tried BEGIN(BITMAPS) then COLOR_RGB, before I call CMD_TEXT, but it doesn't affect the resulting text, it still with black color.
(Btw, the CMD_TEXT that I called is using a custom font)

I want to use custom font in my application, and I'm following this App Note "BRT_AN_014_FT81X_Simple_PIC_Library_Examples".

In the section 6.2, I got a little confused, when it calculate the raw data address, why the value is negative?

(Address of data in RAM_G) + (Metric Block size) â€" (32 characters worth of (stride * height))
1000 + 148 â€" (32*(3*25))
= 1000 + 148 â€" 2400
= -1252

and then -1252 is fed to BITMAP_SOURCE

API_LIB_BeginCoProList();
API_CMD_DLSTART();
API_CLEAR_COLOR_RGB(0, 0, 0);
API_CLEAR(1,1,1);
API_BITMAP_HANDLE(14);
API_BITMAP_SOURCE(-1252);
API_BITMAP_LAYOUT(L1,3,25);
API_BITMAP_SIZE(NEAREST, BORDER, BORDER, 18,25);

The BITMAP_SOURCE command has 22-bit address as parameter, so -1252 will be 0x3FFB1C after clipped to 22-bit address.
But the RAM_G on FT81x device only from 0x000000 to 0x0FFFFF, it's out of range.
Can help me understand this?

Another thing is, after we set the custom font, and we want to call CMD_TEXT or CMD_NUMBER and use the custom font,
do the character that we use must be included in the converted character in our font?
For example i call CMD_TEXT with text string "abc", but my custom font is in UTF-8 format and i don't have 'a', 'b', 'c' in the converted font index, will it work?

Thank you

Hi, i'm following the example source code (sample project) provided.
Inside the function "API_LIB_WriteDataToCMD" it call the function "EVE_IncCMDOffset" and give 'CurrentChunk' as input. But CurrentChunk is uint16_t, while "EVE_IncCMDOffset" take unsigned char commandsize as input.
Just want to clarify?

Hi,
when using CMD_INFLATE we only provide the "Ptr" which is the destination address in RAM_G, then we write stream of bytes of the compressed image. We don't provide the size (total number of bytes) of our compressed image. So, how does the processor know when it is the end of our stream of bytes?
When write the REG_CMD_WRITE > REG_CMD_READ, then wait for a while, then write again another data, it could be the continuation of byte stream, and it could be a new CMD issued. So how the processor distinguish it?

Another question is after issuing CMD_INFLATE, we want to know the end address in RAM_G that was populated by calling CMD_GETPTR. This command returning the end address of decompressed data, so if we want to decompress another image, then the next address we specify in CMD_INFLATE ("Ptr") shoud be +1 from what we get from CMD_GETPTR?

Hi, I'm using FT811, when i use gradient color via CMD_GRADIENT there're some horizontal darker line/strip appearing on the screen. This is only happening when i use gradient, and only for red color (blue and green no darker line/strip occuring).
Here's my LCD parameter:

// LCD display parameters
UINT16 lcdWidth = 800; // Active width of LCD display
UINT16 lcdHeight = 480; // Active height of LCD display
UINT16 lcdHcycle = 928; // tot length of line (hoffset + data + front porch)
UINT16 lcdHoffset = 88; // start of active/data line ((hsync1 - hsync0) + back porch)
UINT16 lcdHsync0 = 0; // start of hsync
UINT16 lcdHsync1 = 48; // end of hsync
UINT16 lcdVcycle = 525; // total number of line (voffset + data + front porch)
UINT16 lcdVoffset = 32; // start of active/data line ((vsync1 - vsync0) + back porch)
UINT16 lcdVsync0 = 0; // start of vsync
UINT16 lcdVsync1 = 4; // end of vsync
UINT8 lcdPclk = 2; // Pixel Clock = 60 MHz / 2 = 30 MHz (LCD spec min-typ-max 20-33-50MHz)
UINT8 lcdSwizzle = 0; // Define RGB output pins
UINT8 lcdPclkpol = 1; // PCLK polarity is on the falling edge

And I was observing, if I make the clock higher (PCLK = 1) the line become lesser, but if I reduce the clock (PCLK = 3, 4, 5) the dark strip become many.
And the dark strip only happen for horizontal gradient applied, it's smooth if i use vertical gradient.

What could be the cause of this? How can i eliminate this completely?
Is this due to FT811 not a true RGB only 18 bit?

Hi, so it really depend on the LCD panel that we use.

Is there a LCD panel that only provide pins for CTP for example: supply, gnd, scl, sda, rst, and int
and other LCD panel have many more pins for the CTP function (probably 20-30 pins), what's the different?

Hi, on several commercial product using EVE with capacitive touch, they use Focaltech IC for example FT5206.
So from EVE IC (FT811, BT815) to FT5206 was connected by I2C, in total 4 pins (SDA, SCL, RST, INT).
What i want to know is the connection from FT5206 to the capacitive panel, what is it and what is the pin definition?

Thank you.