DerekM

The obvious difference is in terms of programmable logic resources; the 7Z030 has about 4x as much as everything as the 7Z010. That might not be a problem if you are only trying to get up to speed on Zynq-7000 development. But one thing to watch out for is that the 7Z030 has high-performance I/O pads, as well as GTX transceiver tiles; the 7Z010 has only high-rate I/O pads and no transceiver tiles. If you need this type of functionality then you will not be able to do a direct migration from 7Z010 to 7Z030. At best you could use a 7Z012S or 7Z015 to start out, but that only gets you (GTP) transceiver tiles, not HP I/O. Here's a handy guide: https://www.xilinx.com/support/documentation/selection-guides/zynq-7000-product-selection-guide.pdf

I have some very up-to-date guides that target both SDK and Vitis, and specifically target the Zybo-Z7-20 and -10 (ZedBoard support files also included): https://github.com/der-mur/book1-zynq-intro The guides can be found in the step-by-step folder. There is also a TCL flow that you can follow if you do not want to build the related FPGA design in Vivado.

I've had issues with the Cypress driver before. First, I would check if you can see the ZedBoard COM port appearing in Device Manager in Windows. And even if you can, uninstall and reinstall the driver. That worked for me before. After that, I'm out of ideas, unfortunately...

For the ZedBoard, you need to ensure that you have the Cypress USB drivers installed. I think this is the one: https://www.cypress.com/documentation/software-and-drivers/microsoft-certified-usb-uart-driver You also need to use two micro-b USB cables with your board; I think it is J14 for UART and J17 for JTAG. When you install the driver and connect the UART cable, you should be able to see the COM port in the PC device driver settings (in Windows). Use the COM port in your terminal app. That should get you going. If you still have issues, check that the UART used by the Zynq (in Vivado Zynq-7000 block diagram) and the stdout setting in the BSP (in SDK) match up.

Are you saying that the terminal output doesn't work for this particular project (VDMA), or that it doesn't work for any project? Because there are different debug approaches depending on the problem. If you have the latter problem, then you must build a completely different project with just the Zynq processor and test it with a simple "Hello World program. The current project is too complicated to test a simple printf issue.

@canisio, If you're interested, I also have a range of projects which use Pmod JF on the Zybo-Z7-20 as a GPIO test header: https://github.com/der-mur/book1-zynq-intro/tree/master/step-by-step