Glen F

I can confirm that Vivado 2019.1 works as per the Nexys 4 DDR example instructions. When I have some spare time I will have compare the code generated by the two different versions to see what gets changed.

The old guide for getting a Microblaze server running on the Nexys 4 DDR (referenced above by JColvin) mostly works for getting the Ethernet to work on the Nexys board. If you follow it straight up, the network connection to your host machine (in my case a Windows 10 Laptop) is spotty and the connection quickly reverts to "Network cable unplugged". The Nexys A7 Reference Manual makes a note of how to fix this in section "4 Ethernet Phy". That is generate the "mii_to_rmii core" clock and the PHY clock separately in "clk_wiz_1". My clock settings are attached. "clk_out3" goes to the "mii_to_rmii core" and "clk_out4" goes to the external PHY clock pin "eth_ref_clk". Doing this makes the connection stable. However I am still not able to get Tera Term to connect to the echo server. I am using Vivado 2019.2 and Vitis 2019.2. I pulled the source code for the "mii_to_rmii core" from Vivado 2019.1 and set it up in an IP repository reference by 2019.2. When the echo servo starts I get messages on the COM port. In my case a separate Tera Term window connected to serial port COM6. See attached. Note I have modified the default IP address in the echo servo code. My regular internet connection was already using 192.168.1.xxx. I set up fixed IP on an unused Ethernet port on my laptop at 192.168.10.100. Connection via TCP/IP on Tera Term fails with "Connection timed out". Any thoughs on what to try nex t appreciated. Glen