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


Pages: [1] 2 3 ... 10
 1 
 on: October 09, 2018, 12:09:17 PM 
Started by TonyZ - Last Post by FTDI Community
Hi Tony,

In the output code file, you should see a definition corresponding to the 'address' field of the font properties. We used Consola here and so your definition may be different.


In the code below we set the start address defined as 1000 and so we got:

#define RAM_FONTS_CONSOLA 1000
static ft_uchar8_t fonts_consola[] = {
   /*('file properties: ', 'resolution ', 16, 'x', 22, 'format ', 'L8', 'stride ', 16)*/0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
[remainder of font data]


Then later at the bottom of the code you should see the following where the code is loaded into RAM_G beginning at location 1000
   Ft_Gpu_Hal_WrMem(phost,RAM_FONTS_CONSOLA, fonts_consola, sizeof(fonts_consola));
   Ft_Gpu_CoCmd_SetFont2(phost,0, 1000, 32);

Does this match what you see?

If you have some screenshots or further information you can also send it to our support address support1@ftdichip.com.

Best Regards, FTDI Community

 2 
 on: October 07, 2018, 03:08:58 PM 
Started by gokhannsahin - Last Post by gokhannsahin
Please help me! How can I know that it has been reset?

 3 
 on: October 04, 2018, 08:21:15 PM 
Started by TonyZ - Last Post by TonyZ
Hello,
Thank you for your reply.

I had actually already tried unchecking the "compressed" option and I can, indeed, see the metric block at the beginning of the output data. However, the
the starting address of RAMG always appears as 0,0,0,0 regardless of what I set it to in the screen editor. Is this a bug, or is the starting address irrelevant?

Note that I'm using SETFONT2, not SETFONT in my software.

Regards,
Tony

 4 
 on: October 04, 2018, 07:54:39 PM 
Started by TylerTiede - Last Post by TylerTiede
We already have boards made, and these will be going into a sealed case. We program the boards using the debugger module during assembly. Afterwards, the user only has access to update the device over USB.

 We are trying to avoid having devices shipped back to us if the user unplugs their device during updating.

Tyler

 5 
 on: October 02, 2018, 09:34:31 AM 
Started by armadafg - Last Post by Rudolph
I do not know about Hotmcu and I am not sure if I really want to anymore.

But it looks like Matrix Orbital has plans for BT815/BT816 modules: https://www.matrixorbital.com/ftdi-eve/eve-bt815


>The BT81X should be available by the end of the year.

Hmm, not so nice.

Okay, what about updating the datasheet and perhaps the programming manual in advance, perhaps with a fat PRELIMINARY watermark across all pages?

 6 
 on: October 01, 2018, 11:53:24 AM 
Started by Rajesh@sys - Last Post by FTDI Community
Hello,

Yes, TxE# tells your FPGA that there is space in the buffer and if you keep writing data to the FIFO without reading at the PC side, then the buffer will fill up and the device will tell you to stop.

Your application in Visual Studio should check for data being available using FT_GetStatus or FT_GetQueueStatus as shown in the document below. If there is any data available (RxBytes > 0) then you would read the data with FT_Read.

When you write the data to the FIFO from the FPGA, you will find that FT_GetStatus/FT_GetQueueStatus show the number of bytes. You can use a loop in the application in Visual Studio which keeps checking for data and reads any data available and puts it in a buffer in the application.

You can find the example code in the document below.

https://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_167_FIFO_Basics.pdf

Best Regards, FTDI Community


 7 
 on: September 28, 2018, 03:01:45 PM 
Started by Pereubu123 - Last Post by Pereubu123
In the documentation: "..
each channel would be opened with a different instance
and ... Open: 
ftStatus = myFtdiDeviceCHA.OpenByIndex(0);
ftStatus = myFtdiDeviceCHB.OpenByIndex(1);
..."


The question is how to open two instances:

FTDI myFtdiDeviceCHB = new FTDI();
ftStatus = myFtdiDeviceCHB.OpenByIndex(1);

I am writing in C#.
From there I should  access BDBUS and BCBUS...

But I could not access B channel?
Have I done something wrong?

 8 
 on: September 28, 2018, 11:16:55 AM 
Started by armadafg - Last Post by FTDI Community
Hello,

The BT81X should be available by the end of the year.

Best Regards,
FTDI Community

 9 
 on: September 28, 2018, 08:41:36 AM 
Started by armadafg - Last Post by armadafg
I would also like to know when the bt82x will be available.
On your site it is indicated June 2018 but I do not see it anywhere

 10 
 on: September 28, 2018, 07:58:23 AM 
Started by Rajesh@sys - Last Post by Rajesh@sys
thanks for the previous suggestions


As i indicated earlier,

we are using  FPGA based hardware to write the data in UM232H(tool ISE). After some no of writes TXE is gone low to high, Hence, we are NOT able write further.
our understanding is that , Sense the visual studio/laptop  does NOT do fifo read operation. The TXE remains high,
our current issue is
 we are not able to read back the data from UM232h/FIFO via COM PORT. because we are using synchronous fifo mode(using ONLY D2XX).


<
FYI
so for configuring UM232H in synch. fifo mode and reading we are using VISUAL STUDIO 2017.>


i want to know


1)how does visual studio knows when to read the data from fifo.
                is it based on any bit of the software register (or) any hardware signal from board. (such as fifo full)—it is not accessible by the software

3)how to access read operation from visual studio.

Pages: [1] 2 3 ... 10