Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - scoprioprise

Pages: [1]

General Discussion / Be aware where you install

« on: September 02, 2020, 09:58:20 AM »

Hi everybody,
I'm facing a strange, where not fancy, behaviour of the Eclipse-for-FT9xx.
And I spotted is caused by the position of libraries.
If you install your eclipse in program files (x86), you will likely have the libraries put in a path like
C:\Program Files (x86)\Bridgetek\FT9xx Toolchain\Toolchain\hardware\include

well, this is a administrative rights protected area (win 7 but every other newer) and you can be misleaded

I've imported a 2.5.0 library includes and source over a 2.3.2 library (and used git to keep the ability of switching back and forth)
But today I've stepped into the fact that what i thought it was a 2.5.0 library is "cached" somewhere and read as a 2.3.2 library.

I'm moving now the include path to see if anything changes.

Discussion - MCU / OTP programming can be triggered unconciously?

« on: November 12, 2019, 11:14:18 AM »

Hi, I'm working on a custom board with FT900, I have a problem that seems to be like I've triggered the OneTimeProgram setup.
How can I detect if I'm in that situation?

Program is still in (so hw is good) and working, but I cannot change it anymore.
The Eclipse cannot recognize device, ftdi programmer shows a BLANK space where shall write "FT900" when abel to program.

Any help?

Discussion - MCU / Errata in examples for FT90x

« on: February 20, 2019, 01:46:57 PM »

I just wanted to sum up errors ( or, at least, not so clear statements ) in code examples.
By now, I found:

CAN example 3: tx.data[] is a 8 byte array, so you can't access the tx.data[8] element. In other languages, you would get an OutOfBoundException, here you read/write spurious data. Not a big deal, however can lead to strange behaviour in other codes.
DAC example 1: dac_start(0) with dac_mode_single starts the FIFO mechanism, thus leading to a delay in first output and a buffer delay when passing "realtime" data. DAC_write starts the dac itself, so there's no need (not to say, erroneous) to explicitly start the DAC.

Hope you all can add your experience, thus helping refining documentation.

Discussion - MCU / FT90x ADC & DAC section quite undocumented

« on: January 22, 2019, 04:42:44 PM »

Hi Everyone,
I'm developing a custom board based upon FT902 rev B, I'm facing a little problem using ADC's.

In fact, there is little or none documentation on ADC module... but also DAC is missing some important informations

I have a BIG difference between measured (with a calibrated multimeter) and translated from MCU.
I'm using the adc_example3 from the toolchain 2.5.0 installer to get samples.

While 0 is 0 (as channels connected are almost grounded) For instance,measured 0,85V are translated into a 185/1024, which shall mean 0,59V...

In case of DAC , it has a immense delay from setting data to obtaining a real output.

Are there any specific application notes or specific infos?
Everiyhing I found is AN-324, pages 39-41 & BRT_AN_020 pages 42-45 + 223 -224, TN159 where some errata address use of buffer, but nothing else.