[__strcmp_sse42]

Hi Michael,

we have used a Linux7. But i am think, this was not the problem.
We have found, that it works also with digilent (2.27.9) libs, then we load the libs with dlopen (... ,RTLD_LAZY | RTLD_DEEPBIND),
but with an older build profile from us.
Also, i do not know, how stable that construct is over time.

But very thanks for answers,
Thanks, Percy

[__strcmp_sse42]

Hi all,

We have a strange problem for using the runtime libs in version 
digilent.adept.runtime_2.27.9-x86_64

Currently, we use digilent.adept.runtime_2.21.3-x86_64, a driver libftd2xx.so.1.4.22 is installed.
This works for long time. Now, we are would use an Arty7 Board.
In this constellation, we become bit errors in using jtag - chain operations (using DjtgPutTmsTdiBits).

For that we download digilent.adept.runtime_2.27.9-x86_64 and link the needed libraries
libdabs, libdftd2xx, libdjtg, libdmgr, libdpcomm on to our application.
On start application we use even the new libs.

But it crashes before main function is called in app.

Now we have done an experiment:
we link the old (2.21.3) runtime libs to our app.
For start the app we use the new (2.27.9) libs.

This works for us perfect. The tests are working.
But this is a problem in logic to link old libs for using a newer version.

Is this problem known, or is where a solution ?
Can be a solution to get a download link to the runtime_2.22 (but complete set, also for windows) ?

Many thanks for an answer !