DA9062 ICP Programmer - Incompatible with Xilinx Vivado

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
8 posts / 0 new
Last post
tentner
Offline
Last seen:2 months 1 week ago
加入:2018-12-07 09:36
DA9062 ICP Programmer - Incompatible with Xilinx Vivado

Hello,

we are using the DA9062 together with a Xilinx Zynq (I think this combination is also advertised by Dialog...).

However, at start of mass production we ran into a very annoying issue: We cannot install the ICP Progammer on the same computer as the Vivado Lab (Xilinx Programmer):

One of both will not work. My guess is e.g. a conflicting USB driver.

Do you have any ideas how we could analyze / fix this issue?

Thanks,

Thomas

Device:
ED_Dialog
Offline
Last seen:1 month 3 weeks ago
Staff
加入:2017-09-18 11:54
Hello Thomas,

Hello Thomas,

I have not seen this issue before. So you is it that you cannot programmed both device or is it you cannot install both GUIs?

Is this with the ICP GUI or the command line tool?

Kind regards,

Elliott

tentner
Offline
Last seen:2 months 1 week ago
加入:2018-12-07 09:36
We can install both, one of

We can install both, one of both will not work, i.e. it will not find the device (but beside that there is no error message). We have seen this behavior on two different computers. We are using the latest versions of both tools.

We use the GUI.

Regards,

Thomas

ED_Dialog
Offline
Last seen:1 month 3 weeks ago
Staff
加入:2017-09-18 11:54
Hello Thomas,

Hello Thomas,

So you see the issue when you load up the GUI not when programming?

We have two version of the ICP tool, the GUI and a command line tool. I take it, you are using the GUI?

tentner
Offline
Last seen:2 months 1 week ago
加入:2018-12-07 09:36
Hello Eliott,

Hello Eliott,

the guy from the production line is already in the weekend (we have a long weekend in Austria). But I think he reported that the GUI starts up regularly but shows no connected board (although it is connected, of course). (On another PC without Vivado it works. I think it also worked on the PC before we installed Vivado. And we have seen this same topic also on another PC.)

We have not tested the command line tool yet.

Regards,

Thomas

ED_Dialog
Offline
Last seen:1 month 3 weeks ago
Staff
加入:2017-09-18 11:54
Hi Thomas,

Hi Thomas,

Would you be able to share a schematic of the DA9062?

Could you also explain the process you are following to program the DA9062?

你想计划同时ICssame time?

Kind regards,

Elliott

tentner
Offline
Last seen:2 months 1 week ago
加入:2018-12-07 09:36
Hi Elliott,

Hi Elliott,

it is for sure not a schematic issue, as the same programmer board works on a different PC (I think it even worked before installing Vivado, at least this as the case on another PC some time ago - but at that time we did not put so much attention to this).

No, we are first (trying to) programm the DA9062, after that power-cycle and program the Zynq (otherwise the Zynq would have no power as it is powered by the DA9062).

My strong guess is that Vivado and your tool are using the same USB library or driver (or at least a lib with the same name), but different versions that are incompatible and therefore resulting in this conflicht. But I do not know how we could further debug/fix this.

Regards,

Thomas

tentner
Offline
Last seen:2 months 1 week ago
加入:2018-12-07 09:36
Hi Elliott,

Hi Elliott,

short update: We completely deinstalled Vivado and the Dialog GUI including the drivers.

Then we reinstalled Vivado -> Vivado Progamming worked.

Then we installed the command line tool -> works too, Vivado appears to be still working. (We did not seperately install the driver in the driver folder - not sure if this is done automatically by the command line tool installer, I think for the GUI it was necessary to install it manually.)

So for the moment it looks like we have a working environment (we do not want to install the GUI again, to not risk to break things). We will double-check the whole setup tomorrow.

Regards,

Thomas