Connect MicroBlaze Debug Module (MDM) to Virtual JTAG in Vivado IP Integrator

I have posted my problem in , but I realise that it seems to be a different issue, as in the implemented design, the MDM is not connected to anything:


Therefore I would like to know the correct configuration to connect to MDM.

Below are what I originally posted in #641

-----

I hope this is the right place to post here, as I am expericing a similar problem:

Right now I'm working to put a MicroBlaze core with Vivado IP Integrator flow, however, I can't connect to the MicroBlaze Debug Module (MDM) when I deployed in on an EC2 F1 instance.

My design is as following:
design files: [aws_mb_example.zip](https://github.com/aws/aws-fpga/files/15334751/aws_mb_example.zip)

I have followed , which mentioned to use "EXTERNAL HIDDEN" for BSCAN in MDM:

However, it seems failed to identify MDM, as when I connect it with XSCT, I got the following:
Top left is the SSH session of EC2 F1, which was running `hw_server` and `sudo fpga-start-virtual-jtag -P 10201 -S 0`
Bottom left is the Vivado tcl shell, connected to the Virtual JTAG on F1
Bottom right is the XSCT, also connected to the Virtual JTAG on F1
The commands are run in this order: SSH > Vivado > XSCT

The targets command in XSCT gives 8-digit numbers only, but supposedly it should gives something like "MicroBlaze Debug Module".

May I ask if there is any problem with my design with a MicroBlaze? Is there an alternative method to connect to MDM, or is there an example design for MicroBlaze that worked with AWS EC2?

Thank you.

Start with the attached aws_mb_example.zip and the MDM configuration shown in the issue, then compare the Vivado IP Integrator design with the linked issue #507 guidance. Reproduce the connection sequence using hw_server, sudo fpga-start-virtual-jtag -P 10201 -S 0, Vivado, and XSCT; done means XSCT identifies the MicroBlaze Debug Module instead of only returning 8-digit targets.

Written by the indexing model from the issue text.