Vivado 2023.2 unable to connect

[zeldin]

When I try to connect to ftdiJTAG from Vivado 2023.2, the first protocol packet it sends is

E.Locator.Hello.["ZeroCopy"]

This makes ftdiJTAG say

Bad initial char 0x45
Unexpected character!

and close the connection.

Is it no longer possible to use the old protocol in Vivado 2023.2? Or do I just need to do something special (rather than select "remote server" in the connection wizard) to connect?

[zeldin]

Did some googling and eventually found this thread:
https://adaptivesupport.amd.com/s/question/0D52E00007IPiwVSAT/xvc-protocol-specification-out-of-date?language=en_US

And yes, using connect_hw_server followed by open_hw_target -xvc_url hostname:2542 in the Tcl Console does work.

Sorry about the noise...

[norumwe12]

Good to hear that you have things working.   I’m using ftdiJTAG with 2023.2 and 2024.1.   Did the notes in the ftdiJTAG.1 man page not work for you?  The procedure is a little convoluted but it’s what I found that works.   Of course the tcl console approach you mentioned works fine too.   -- Eric ***@***.*** Sep 15, 2024, at 6:48 AM, Marcus Comstedt ***@***.***> wrote: Did some googling and eventually found this thread: https://adaptivesupport.amd.com/s/question/0D52E00007IPiwVSAT/xvc-protocol-specification-out-of-date?language=en_US And yes, using connect_hw_server followed by open_hw_target -xvc_url hostname:2542 in the Tcl Console does work. Sorry about the noise... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[zeldin]

Ah, yes, the procedure described in the manpage works too. I guess I'm just confused by the fact that I have to select "target is on local machine" when the opposite is true... 🫤