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

Pages: [1] 2 3 ... 10
 1 
 on: May 22, 2020, 02:47:36 PM 
Started by SpicyChef - Last Post by SpicyChef
Rudolph,

Thanks to your code I was able to find the problem in mine.

 2 
 on: May 21, 2020, 04:42:31 PM 
Started by nroos - Last Post by FTDI Community
Hello,

To use I2C with FT232H, see AN_135 FTDI MPSSE Basics and our existing MPSSE Example projects:

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

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

a. Use LibMPSSE libraries. Example code is provided with the download.

b. Use D2XX drivers direct. Example code is shown at I2C.
AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.

Option b is the best option to use the D2XX drivers direct (no dependency on libMPSSE library).

Best Regards,
FTDI Community

 3 
 on: May 21, 2020, 01:33:56 PM 
Started by kukdh1 - Last Post by FTDI Community
Hello,

Is there any news about Apple's re-signing of the driver?

Yes, actually we have just managed to re-sign and notarize our VCP driver package for macOS 10.15.
We still need to do a couple things before we can release this online, update release notes, etc.


Best Regards,
FTDI Community

 4 
 on: May 20, 2020, 04:43:16 PM 
Started by kukdh1 - Last Post by otherguy
Is there any news about Apple's re-signing of the driver?

 5 
 on: May 20, 2020, 04:34:31 PM 
Started by asusrog - Last Post by FTDI Community
Hello,

Please test in a loopback fashion.

Simply connect TXD to RXD and use a terminal program like PuTTY to send/receive characters.

Note that PuTTY will only show received characters unless your force ON the sent characters (in the settings).

Please also test with our known good hardware which you can also use for reference:

https://www.ftdichip.com/Products/Modules/DevelopmentModules.htm

Best Regards,
FTDI Community

 6 
 on: May 19, 2020, 07:32:48 AM 
Started by Rudolph - Last Post by Rudolph
I have no idea why this forum is still up and why there is so much posted here.
I am more active over at:  http://www.brtcommunity.com/

That said, I have a code library for FT8xx/BT8xx that could answer a couple of questions that are posted here:
https://github.com/RudolphRiedel/FT800-FT813

I have examples projects for Arduino, ATSAMC21 and ATSAME51.
My goal is to support all the EVE displays out there, at least these that I can actually get and that are documented.

And I went multi-plattform right from the start, I have support for a whole bunch of micros including AVR, ATSAM, STM32 and RISC-V.

 7 
 on: May 19, 2020, 07:15:07 AM 
Started by SpicyChef - Last Post by Rudolph
I have an Arduino example for my driver library: https://github.com/RudolphRiedel/FT800-FT813/tree/4.x/example_projects

The display is selected in EVE_config.h.
And the pins for CS and PD are configured at the end of EVE_target.h.

 8 
 on: May 18, 2020, 06:02:35 PM 
Started by nroos - Last Post by nroos
Hello,

Is there maybe a guide what i actually have to do to connect a I2C slave device to a PC and communicate with the device in Linux? For the conversion i would use a UM232H module.

The application notes i found so far explained always just a part, not the big picture. With the research i have done so far i found out that using D2xx and libMPSSE should do it on the software side. Compiling was successful, running the static example (static_link) also until it waited for incoming data.

But now what do i do with the UM232H? Do i have to configure it somehow? To which of the 16 connections do i attach my I2C device? I looked at the wires with a scope; one wire obviously had a data transfer on it. But there was no wire with the clock...

It would be really helpful if there was a document which just says: Do this, do that and so on, to avoid all this time consuming research.

Kind regards


 9 
 on: May 18, 2020, 04:20:23 PM 
Started by SpicyChef - Last Post by SpicyChef
Unfortunately still doesn't work, all I can see is the back light turning on.
I'm not sure where I'm going wrong with the code, since the logic reading seems to be good.

If you could look at the logic reading and help me, it would be greatly appreciated.

 10 
 on: May 18, 2020, 03:02:07 PM 
Started by SpicyChef - Last Post by FTDI Community
Hello,

Each time you want to update the screen, you must also have a swap as the display list has two buffers. After writing the new list, you swap that one so that it becomes active and you can edit the other one and so on. Therefore, try adding a swap after your DISPLAY in your main loop at the bottom.


    wr32(RAM_DL + 0, CLEAR_COLOR_RGB(0,0,255)); //CLEAR_COLOR_RGB0,0,0
    wr32(RAM_DL + 4, CLEAR(1,1,1));
    wr32(RAM_DL + 8, DISPLAY);
    wr8(REG_DLSWAP,0x02); 


Best Regards, FTDI Community

Pages: [1] 2 3 ... 10