Need a working image for Quartz64B

[balbes150]

That's my guess too, but it could also be an u-boot problem. If another boot loader would have the same issue, then it becomes even more likely to be a HW problem.

The reason is not u-boot. Before it, a binary blob starts controlling the primary memory configuration, u-boot and EDK2 use almost the same primary blob. There is no output since the start of the primary loader , which means the hardware is not working.