• 0

size of tms/tdi bitarrays from DjtgPutTmsTdiBits


Question

5 answers to this question

Recommended Posts

  • 0

Hi @perdue

Looking at the source code the maximum cbitpairs is uint32max - 7
There is a default 10 sec timeout for the transfers (function calls) and it can be changed with DmgrSetTransTimeout if you want.
Instead of this, 
I would rather transfer the data in about 1 sec chunks, so it can be aborted in the higher level app.

Link to post
Share on other sites
  • 0

Hi @attila,

very thanks, this was the problem. It's works now. The complete transmission needs a time ca. 1min.

But is see another problem in conjunction to debug this problem with ddd:

First is started our tool which is using the digilent libs.
Then setup any breakpoints in ddd and attach running app.
Let running ddd with continue. The app works in background as on process.
Now the app reach a breakpoint, stopped before DjtgPutTmsTdiBits.
So i switch to ddd and will step over next and DjtgPutTmsTdiBits fails.

It's occours not, if i'am not using ddd.

Is in DjtgPutTmsTdiBits a watch for switch processid and if so, block transmission ?

We have at least installed the linux64 driver :
digilent.adept.runtime_2.21.2-x86_64.tar.gz
with
ftdi.drivers_1.4.8-x86_64 insided.

Very thanks,

P

 

Link to post
Share on other sites
  • 0

Hi @perdue

The actual data transfers are performed in separate thread.
When a function is called in blocking mode, with overlapped false, it will wait for the transfer semaphore to signal completion.
I don't remember having issue in debugging apps which use Adept libs.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now