Alchitry Au board interfacing issue

I am new to Alchitry Au board, currently I’m facing 2 issues which i list here i already ask in Alchitry Au forum but did not receive any response yet.

so could you please give me a guidance.

Issue 1:

Finding a connector for Alchitry Au Board. Not able to find the connectors for accessing I/O Pins of a board, which connectors/cables should I use or any alternative options?

Issue 2:

I downloaded the windows driver, Xilinx USB cable but unable to fix the issue. when I tried Alchitry Au lab loader it works properly but when though the Xilinx vivado I am not able do it. could you please guide me how can i resolve this error.

> This is my console message:

  • open_hw_manager

  • connect_hw_server -allow_non_jtag

  • INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121

  • INFO: [Labtools 27-2222] Launching hw_server…

  • INFO: [Labtools 27-2221] Launch Output:

  • ****** Xilinx hw_server v2024.1.0

  • **** Build date : Mar 6 2024 at 20:50:54

  • ** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.

  • INFO: [Labtools 27-3415] Connecting to cs_server url TCP:localhost:0

  • INFO: [Labtools 27-3417] Launching cs_server…

  • INFO: [Labtools 27-2221] Launch Output:

  • ******** Xilinx cs_server v2024.1.0

  • ****** Build date : Mar 09 2024-05:30:37

  • **** Build number : 2024.1.1709942437

  • ** Copyright 2017-2022 Xilinx, Inc. All Rights Reserved.

  • ** Copyright 2022-2025 Advanced Micro Devices, Inc. All Rights Reserved.

  • connect_hw_server: Time (s): cpu = 00:00:02 ; elapsed = 00:00:34 . Memory (MB): peak = 1543.020 ; gain = 8.191

  • refresh_hw_server {localhost:3121}

  • WARNING: [Labtoolstcl 44-27] No hardware targets exist on the server [localhost:3121]

  • Check to make sure the cable targets connected to this machine are properly connected

  • and powered up, then use the refresh_hw_server command to re-register the hardware targets.strong text****strong text

Let me know if you need anything else.

Issue 1:

Assuming you are talking about the V1 version of the boards, SparkFun currently sells them

Depending on your application, you could also use a Br board to avoid using these connectors directly. Alchitry Br Prototype Element Board

Sourcing these could be a pain and was a big factor in the change to the easier to find connectors on the new V2 boards. Products – Alchitry

You can find these at many retailers like DigiKey

https://www.digikey.com/en/products/detail/hirose-electric-co-ltd/DF40HC-4-0-80DS-0-4V-51/2530298

https://www.digikey.com/en/products/detail/hirose-electric-co-ltd/DF40HC-4-0-50DS-0-4V-51/5132169

https://www.digikey.com/en/products/detail/hirose-electric-co-ltd/DF40C-50DP-0-4V-51/1969486

https://www.digikey.com/en/products/detail/hirose-electric-co-ltd/df40c-80dp-0-4v-51/1969492

Issue 2:

Are you connecting the Xilinx cable to the JTAG pins on the header or trying something else?

The easiest way to use JTAG is with the on-board JTAG bridge. You can program the V1 boards with the “program_ftdi” program included with Vivado. It will then show up in the hardware manager. See No Devices Detected with Vivado Hardware Manager - #5 by alchitry

The new V2 boards come with this pre-done.

As per your suggestion I implement the “Program_ftdi” but still I am facing same issue.
I read this topic and followed all the steps but, hardware target on local server still not exists, No Devices Detected with Vivado Hardware Manager - #5 by alchitry.
I tried multiple times and reinstalled the Xilinx USB cable driver manually, but didn’t get any solution.
I updated the Xilinx Vivado tool 2024.2 >>> 2024.2.1
here I also attached the file for your reference.
Could you please guide me how can I solve these errors.
Let me know if you need anything else.

You can check that the board was programmed correctly from program_ftdi by reading back part of the config with FT_Prog. It should say “Xilinx” under “Manufacture Desc”. Check it by plugging your board in then going to DEVICES->Scan and Parse. It should then show it in the main window.

I’m planning to roll a utility into Alchitry Labs to program the FTDI chip for you as well if you’re having issues with program_ftdi.