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

Pages: 1 ... 49 50 [51] 52 53 ... 60
751
Discussion - Drivers / Re: issue related to UM232H eval. board
« on: September 24, 2018, 10:13:30 AM »
Hello,

The signal may be degraded by rounding of edges and lowering of apparent amplitude if you have long connections or due to your scope probe. We recommend to use a high-frequency low-capacitance probe to measure the signal to ensure that what is shown on the scope is correct and that the probe itself does not affect the waveform by adding capacitance.

Some probes also have different characteristics depending on which mode they are in (e.g. 1x vs 10x). The probe used should have a frequency rating several times greater than the signal being measured and so generally a 200MHz or 300MHz probe is needed to see this signal accurately. Please check the datasheet of your probe to ensure that the 60MHz is well within its range.

Best Regards, FTDI Community

752
Discussion - Hardware / Re: UART and SPI in the same chip?
« on: September 21, 2018, 02:23:08 PM »
Hello,

Yes, please consider our FT2232H (2 channel) or FT4232H (4 channel) ICs.

So you could have one channel for UART and the other for SPI.
Note the SPI is a master only.
By default the channel is UART, so the other channel would need to be configured for SPI

See FTDI MPSSE Basics.
See our existing MPSSE Example projects:

https://www.ftdichip.com/Support/SoftwareExamples/MPSSE.htm

There are two options to use I2C/SPI modes with the MPSSE engine:

a.            Use LibMPSSE libraries. Example code is provided with the download. Please note that there is a beta version of LibMPSSE: libMPSSE__0_6_Beta.zip.
b.            Use D2XX drivers direct. Example code is shown at SPI. AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.

We have hardware available for test and evaluation:

FT2232H Mini-Module
FT2232H-56 Mini-Module

The FT2232H-56 Mini-Module is easier to power by just using a jumper. The other module requires some external connections.

Best Regards,
FTDI Community

753
Discussion - Hardware / Re: FT813 GRAM size 1MB to be increased soon?
« on: September 20, 2018, 12:06:09 PM »
Hello,

Yes, assuming the images are in the aforementioned ASTC these would be able to be loaded directly from flash memory and not into GRAM.

Best Regards,
FTDI Community

754
General Discussion / Re: FT812 DISPLAY
« on: September 18, 2018, 04:13:57 PM »
Hello,

The backlight is controlled by the following registers:
  • REG_PWM_HZ
  • REG_PWM_DUTY

Depending on which module you are using you may also need to toggle an GPIO pin to enable the displays backlight.

Best Regards,
FTDI Community

755
Discussion - Drivers / Re: issue related to UM232H eval. board
« on: September 17, 2018, 03:09:08 PM »
Hi Rajesh,

I'm afraid the drivers are not available in Verilog or VHDL. The device always requires a SetBitMode call to change the mode. In addition to sending the SetBitMode, the ISE application would also need to perform reads and writes via the D2xx drivers, and so your intended application would only be possible if the ISE has support for FTDI devices built in already or has a plug-in from the manufacturer to support FTDI devices. If ISE does not have this, writing your own data transfer application in Visual Studio instead for example would be required.

Best Regards, FTDI Community

756
General Discussion / Re: FT812 DISPLAY
« on: September 17, 2018, 11:16:43 AM »
Hello,

The following start-up sequence should be used with the FT81X, please note the 500ms delay at start-up:

Code: [Select]
    MCU_PDlow();                                                                // PD low to reset device                                                               
    MCU_Delay_20ms();
    MCU_PDhigh();                                                               // PD high again
    MCU_Delay_20ms();

    // ---------------------- Optional clock configuration ---------------------   

    // Un-comment this line if using external crystal. Leave commented if using internal oscillator.
    // Note that most FTDI/BRT modules based on FT800/FT801 use an external crystal
    // EVE_CmdWrite(0x44, 0x00);           // 0x44 = HostCMD_CLKEXT

    // You can also send the host command to set the PLL here if you want to change it from the default
    // of 48MHz (FT80x) or 60MHz (FT81x)
    // The command would be called here before the Active command wakes up the device   
   
    // ---------- Wake FT8xx and delay to allow device to start-up -------------   
   
    EVE_CmdWrite(FT81x_ACTIVE, 0x00);                                           // Sends 00 00 00 to wake FT8xx
    MCU_Delay_500ms();                                                          // 500ms delay (EVE requires at least 300ms here))
   
    // --------------- Check that FT8xx ready and SPI comms OK -----------------
   
    while (EVE_MemRead8(REG_ID) != 0x7C)                                        // Read REG_ID register (0x302000) until reads 0x7C
    {
    }
     
    while (EVE_MemRead8(REG_CPURESET) != 0x00)                                  // Ensure CPUreset register reads 0 and so FT8xx is ready   
    {
    }

    // ------------------------- Display settings ------------------------------

    // 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
                     
    EVE_MemWrite16(REG_HSIZE,   lcdWidth);     
    EVE_MemWrite16(REG_HCYCLE,  lcdHcycle);     
    EVE_MemWrite16(REG_HOFFSET, lcdHoffset);   
    EVE_MemWrite16(REG_HSYNC0,  lcdHsync0);     
    EVE_MemWrite16(REG_HSYNC1,  lcdHsync1);     
    EVE_MemWrite16(REG_VSIZE,   lcdHeight);     
    EVE_MemWrite16(REG_VCYCLE,  lcdVcycle);     
    EVE_MemWrite16(REG_VOFFSET, lcdVoffset);   
    EVE_MemWrite16(REG_VSYNC0,  lcdVsync0);     
    EVE_MemWrite16(REG_VSYNC1,  lcdVsync1);     
    EVE_MemWrite8(REG_SWIZZLE,  lcdSwizzle);   
    EVE_MemWrite8(REG_PCLK_POL, lcdPclkpol);   
 
    FT81x_GPIO = EVE_MemRead8(REG_GPIO);                                        // Read the  GPIO register for a read/modify/write operation
    FT81x_GPIO = FT81x_GPIO | 0x80;                                             // set bit 7 of  GPIO register (DISP) - others are inputs
   EVE_MemWrite8(REG_GPIO, FT81x_GPIO);                                        // Enable the DISP signal to the LCD panel
   
    // Can move these 2 lines to after the first display list to make the start-up appear cleaner to the user
    EVE_MemWrite8(REG_PCLK, lcdPclk);                                           // Now start clocking data to the LCD panel
    EVE_MemWrite8(REG_PWM_DUTY, 127);
   
    // ---------------------- Touch and Audio settings -------------------------

    EVE_MemWrite16(REG_TOUCH_RZTHRESH, 1200);                                   // Eliminate any false touches

    EVE_MemWrite8(REG_VOL_PB, ZERO);                                            // turn recorded audio volume down
    EVE_MemWrite8(REG_VOL_SOUND, ZERO);                                         // turn synthesizer volume down
    EVE_MemWrite16(REG_SOUND, 0x6000);                                          // set synthesizer to mute

    // ----------------- First Display List to clear screen --------------------

    ramDisplayList = RAM_DL;                                                    // start of Display List
    EVE_MemWrite32(ramDisplayList, 0x02000000);                                 // Clear Color RGB sets the colour to clear screen to black

    ramDisplayList += 4;                                                        // point to next location
    EVE_MemWrite32(ramDisplayList, (0x26000000 | 0x00000007));                  // Clear 00100110 -------- -------- -----CST  (C/S/T define which parameters to clear)

    ramDisplayList += 4;                                                        // point to next location
    EVE_MemWrite32(ramDisplayList, 0x00000000);                                 // DISPLAY command 00000000 00000000 00000000 00000000 (end of display list)

    EVE_MemWrite32(REG_DLSWAP, DLSWAP_FRAME);                                   // Swap display list to make the edited one active


Please note that the Freescale samples are for the FT800 and not the FT81X, as such you should ensure you have the correct header files in your project. You can find the updated header files in our main SampleApp at the following:
https://www.ftdichip.com/Support/SoftwareExamples/FT800_Projects.htm

Best Regards,
FTDI Community

757
Discussion - Software / Re: VNC2 Debugger Issue
« on: September 14, 2018, 04:35:40 PM »
Hello, Please contact our email support channel on support1@ftdichip.com for details of upgrading the prog loader.

Best Regards,
FTDI Community

758
Discussion - Hardware / Re: FT813 GRAM size 1MB to be increased soon?
« on: September 14, 2018, 03:02:23 PM »
Hello,

It is possible with the BT81x to display an image directly from flash memory without loading it into GRAM first, when the image is in the ASTC format. There is a slight speed penalty when reading image data in from flash via GRAM.

Best Regards,
FTDI Community

759
Discussion - Hardware / Re: FT813 GRAM size 1MB to be increased soon?
« on: September 12, 2018, 03:40:41 PM »
Hello,

Our upcoming BT815/6 series of EVE ICs will also only include 1MByte of internal graphics RAM. However these new ICs include support for external flash memory which can be used to store/offload graphics elements such as images, custom fonts and widgets from the integrated RAM.
You can find out more about the BT815/6 at the following page:
http://brtchip.com/bt81x/

Best Regards,
FTDI Community

760
Discussion - Drivers / Re: issue related to UM232H eval. board
« on: September 12, 2018, 02:31:31 PM »
Hi Rajesh,

You should see the clock being generated by the FT232H once you have called the FT_SetBitMode to set sync FIFO mode. Please check the return value from all D2xx calls to make sure you get FT_OK (for success) if you don't see the clock signal.

You should have EEPROM set for 245 FIFO mode (this is equivalent to async FIFO) and then use FT_SetBitMode to move to sync FIFO.

Regards, FTDI Community


761
Discussion - Drivers / Re: Poor throughput via USB Bulk transfer VNC2
« on: September 12, 2018, 09:44:56 AM »
This is being handled via email and any solution will be posted here for other user's benefit.

FTDI Community

762
Discussion - Drivers / Re: issue related to UM232H eval. board
« on: September 11, 2018, 04:09:26 PM »
Hi Rajesh,

I'm afraid the driver can't be changed to make it start in this mode. You would need to make calls to our driver to set the mode. Likewise, other applications might not have D2xx API calls for reading and writing and so even if in sync FIFO mode, another application not using the D2xx driver calls would not be able to read and write data.

To use the device in this mode with other types of IDE, you would either need to use D2xx within that environment and make driver calls (e.g. if a D2xx wrapper exists for ISE) or to make a small Visual Studio application which talks to the D2xx driver and sits between it and ISE.

What kind of API does ISE provide for device such as FT232H?  If it only provides a COM port, then the other modes such as UART or async FIFO could be used (selected by EEPROM and not by SetBitMode) but the virtual COM can't work with sync FIFO.  Other modes which are selected by SetBitMode would need D2xx in ISE or you to write an intermediate filter layer.

Best Regards, FTDI Community

763
Discussion - Drivers / Re: issue related to UM232H eval. board
« on: September 11, 2018, 10:03:50 AM »
Hello,

The package which you mentioned will install the D2xx driver which will provide an API for your own program to call, and will not need any modification itself. You would then write a separate application in a development environment such as Visual Studio to use the device via the driver. This would use the driver API calls such as FT_Open, FT_SetBitMode etc. from the programmers guide.

You can install the driver by downloading, extracting and running this executable installer and then connecting the device to the USB port. It should show under the Universal Serial Bus Controllers section of device manager.
https://www.ftdichip.com/Drivers/CDM/CDM21228_Setup.zip

Then, you can use the examples in this technical note as a starting point for your own application.
https://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_167_FIFO_Basics.pdf

Best Regards, FTDI Community





764
Discussion - Drivers / Re: C232HM used as xilinx JTAG
« on: September 10, 2018, 01:09:14 PM »
Hi,

We do not have a tool that reads this proprietary area.

Regards,
FTDI Community

765
Discussion - Drivers / Re: C232HM used as xilinx JTAG
« on: September 07, 2018, 03:39:47 PM »
Hi,

Thanks for your question. Please contact our email support via support1@ftdichip.com and we will assist you further.

Regards,
FTDI Community

Pages: 1 ... 49 50 [51] 52 53 ... 60