FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - gokhannsahin

Pages: [1] 2
1
Discussion - Software / Re: EVE Screen Editor Font Problem
« on: June 20, 2019, 02:49:58 PM »
Hi,
I'm using the last version is v3.2.1.

2
Discussion - Software / EVE Screen Editor Font Problem
« on: June 20, 2019, 07:17:50 AM »
Hi everyone,
I can't upload a font(.ttf file) to eve screen editor, it always gives an error that is "Freetype not available"
I guess that this new version has a bug because there was no problem in other versions.


3
Discussion - Software / BT815 Camera with STM32
« on: January 11, 2019, 02:20:24 PM »
Hi everyone,
I'm using BT815 and need to display a camera on it. I read your FT91x camera application note and ordered the OV5640.
All settings were set in your example and I can see all signals, also, get the HAL_DCMI_VsyncEventCallback, HAL_DCMI_LineEventCallback interrupt callback after started the transfer.
Another example different from yours it can get full data and its data seems meaningful.
However, with your example I can't get any data the buffer, it's always empty.
I start the DCMI module with that command HAL_DCMI_Start_DMA(&hdcmi, DCMI_MODE_CONTINUOUS, (uint32_t)buffer, 512);
What's the DMA buffer length for BT815 to display camera? Could you give me an example of using a camera with STM32 or any ARM MCU?

4
Discussion - Software / Re: BT815 Image Issue
« on: December 12, 2018, 10:43:54 AM »
The TFT which displays nothing without series resistors although set the above parameters is 4.3".
I'm using a custom design.

For 4.3" : https://drive.google.com/open?id=1bXh_Una4K4U98xN-_ZY4dj9pAg5Jo7JJ
For 7" : https://drive.google.com/open?id=1wB1WP6SLpVglopnsS2-mWtQzSnnK-w_h

5
Discussion - Software / Re: BT815 Image Issue
« on: December 11, 2018, 12:48:19 PM »
Hi,
The result is the same, it has white pixels.
I think the display settings are correct because when a series resistor is connected to VSYNC and HSYNC pins, it displays the screens.
The settings parameters;
Code: [Select]
#define settingQVGALCDPARAMETER \
{ \
480U, /* Active width of LCD display */ \
272U, /* Active height of LCD display */      \
548U, /* Total number of clocks per line */   \
43U, /* Start of active line */    \
0U, /* Start of horizontal sync pulse */    \
41U, /* End of horizontal sync pulse */    \
292U, /* Total number of lines per screen */  \
12U, /* Start of active screen  */    \
0U, /* Start of vertical sync pulse */    \
10U, /* End of vertical sync pulse */    \
5, /* Pixel Clock */      \
0, /* Define RGB output pins */    \
1, /* Define active edge of PCLK */    \
} \

Also, I enclosed the display parameters which in the datasheet of TFT.

6
Discussion - Software / BT815 Image Issue
« on: December 10, 2018, 12:20:37 PM »
Hi everyone,
I was using FT813 in my project but migrated it to BT815 today. The two projects are using the same images.
The screen of one that is with FT813 is very well but BT815 has lots of white pixels. (PALETTED8 has been used)
I enclosed the screens of them, you can see the difference. Why?
Hsync,vsync,disp pins of FT813 etc. has a series resistors at your example schematic of the datasheet.
However, there is no a series resistor in BT815 datasheets. Can this problem cause related to these resistors?
Furthermore, I have two different TFT in my project, one is 7" and other is 4.3". 7" can display my design screen but 4.3" is an empty page.
4.3" also needs these resistors?
Finally, in the startup, BT815 is slower than FT813, the difference is around 1-1,5 second. Why? BT815 is checking something in the startup?
(The embedded codes are the same for them)



7
Discussion - Software / Re: BT815 Car Dashboard
« on: October 24, 2018, 08:59:44 PM »
Thanks for answering.
However, I mean that which format has been used to convert the images in your demo? PALETTED4444,ARG1555 etc. which one?
My images don't look as good as yours, in color transition, white dot pixels appear.
Best regards.

8
Discussion - Software / BT815 Car Dashboard
« on: October 22, 2018, 08:18:39 PM »
Hi everyone,
Please let me know which format is been used in BT815 Car Dashboard board. I can't display image on LCD as in your demo.

9
Discussion - Software / Re: FT813 CRC calculating and adressing
« on: October 07, 2018, 03:08:58 PM »
Please help me! How can I know that it has been reset?

10
Discussion - Software / Re: FT813 CRC calculating and adressing
« on: September 03, 2018, 07:23:07 PM »
Well, how to check the MCU whether has been reset? If the REG_READ and REG_WRITE registers are zero, does it mean that the chip has really been reset?

11
Discussion - Software / Re: FT813 CRC calculating and adressing
« on: August 06, 2018, 02:29:27 PM »
I'm still getting the error while checking CMD_READ_COMMAND and CMD_WRITE_COMMAND. Please help me? And I would appreciate if you help me with my other questions?

12
Discussion - Software / Re: FT813 CRC calculating and adressing
« on: July 30, 2018, 07:02:03 PM »
Thank you so much. It works as I want.

Yes, I use burst mode when to write the commands.(DMA) And I pay attention to the CS pin being low while transferring.
Well, once the transfer is completed, should I write manually the new cmd_write_reg value while using command buffer? Or it will update this register itself? For.ex. after transferred the commands of 3012, the following method is right?
Code: [Select]
uint32_t cmdBufferWr = ft800memRead32(REG_CMD_WRITE);
ft800memWrite32(REG_CMD_WRITE, cmdBufferWr + 3012);
ulCommandIndex = 0;

Also, sometimes REG_CMD_READ isn't equal to REG_CMD_WRITE. What can I do then? Should I reset the co-processor? If yes, I'm using the quadspi module and it has four lines while communicating the processor. After I send the reset command does it still keeps communicating 4 lines, or need to send the ft800memWrite8(REG_SPI_WIDTH, 0x02); again? Although the active_command is sent, it always is the black screen not turn the backlight on. Do it need the all command at the initializing again? The code is as the following;

Code: [Select]
ftcmdwrite4lines(RST_PULSE);
ftcmdwrite(FT_EXTERNAL_CLOCK);//or ftcmdwrite4(FT_EXTERNAL_CLOCK);
ftcmdwrite(COMMAND_ACTIVE);//or ftcmdwrite4(COMMAND_ACTIVE);
HAL_Delay(500);
//ftmemwrite8(SPI_WIDTH,2);
ftmemwrite8(PWM_DUTY,100);//it writes 4 lines

Furthermore, the images that are converted both ARG1555 and PALATTED4444 doesn't look right on the screen. The pixels of the image which is converted as ARGB1555 looks square. Lots of white pixels are looked while using the image which is converted as PALATTED444 on the screen (800x480). I would like to use a transparent image. Is there a method to solve these problems, different tool or format?

13
Discussion - Software / FT813 CRC calculating and adressing
« on: July 27, 2018, 08:04:47 PM »
Hi everyone,
I'm using the FT813 in my project and it has lots of images is around 66 on a screen but almost all is small picture or symbol.
I'm using the crc calculating avoid errors while transferring. However, I'm confused a point in the datasheet, it says that read to ıf CommandWriteAddress + 12 to get the calculated crc value. Well, if this command address is 4092, I still have to read +12, so 4092+12? If yes, then, will there be an overflow in command buffer? Or should the (4092+12)-4096=8th address be read?

Furthermore, I'm using a shadow command buffer and inserting the commands to it. Then they are sent to FT813 via DMA as the following example. Each transfer before, I read the reg_cmd_write and add the new commands to it. However, it read 2048 from reg_cmd_write and need 3012 bytes commands. What can I do at this point? Should I add 3012 to 2048 that is equal to 5060? Or clear the cmd_write and cmd_read registers?

Code: [Select]
uint32_t cmdBufferWr= ft800memRead32(REG_CMD_WRITE);

sCommands.Instruction = 0x00;
sCommands.InstructionMode = QSPI_INSTRUCTION_NONE;
sCommands.AddressMode = QSPI_ADDRESS_4_LINES;
sCommands.DdrMode = QSPI_DDR_MODE_DISABLE;
sCommands.AddressSize = QSPI_ADDRESS_24_BITS;
sCommands.AlternateByteMode = QSPI_ALTERNATE_BYTES_NONE;
sCommands.AlternateBytesSize = QSPI_ALTERNATE_BYTES_8_BITS;
sCommands.AlternateBytes = 0x00;
sCommands.Address = (cmdBufferWr + RAM_CMD) | 0x800000;
sCommands.DataMode = QSPI_DATA_4_LINES;
sCommands.NbData = ulCommandIndex;
sCommands.DummyCycles = 0;
sCommands.DdrHoldHalfCycle = QSPI_DDR_HHC_ANALOG_DELAY;
sCommands.SIOOMode = QSPI_SIOO_INST_EVERY_CMD;

s_transfer_reg_to_ftdi.b_state = IMAGE_TRANSFERRING_FTDI;
__FTDI_SELECT();
vDelayUs(300);
HAL_QSPI_Command(&hqspi, &sCommands, HAL_QPSI_TIMEOUT_DEFAULT_VALUE);
HAL_QSPI_Transmit_DMA(&hqspi, (uint8_t*) &ucCmdBuffer[0]);

14
Discussion - Hardware / Analog Camera with FT81x
« on: March 14, 2018, 10:53:04 AM »
Hi everyone,
I'm using your product is FT813 and would like to display a camera image. The resolution of TFT is 800x480 and the MCU is STM32F446.
I have to use a video decoder because an analog camera will be used. In your reference guides suggest a digital camera module for using MJPEG.
However, there is no information about an analog camera. I'm thinking of using TI's decoder chip is TVP5150AM1 and any analog camera. I guess that the bit size of the interface will be 8bits.
Finally, the data that received from DCMI module via DMA will be transferred to FT813 via again DMA of QuadSPI. These images have to be JPEG? If yes, the camera and decoder chip have to support JPEG, so the specific products can be used?
 

15
Discussion - Software / Re: Lower case letter problem
« on: November 21, 2017, 11:12:08 AM »
Is there any problem using the setfont2? or I'm making mistake?

Pages: [1] 2