[Apologies to Peter for the duplicate; earlier today I accidentally sent this reply to him rather than the list, so I'm forwarding it to the list in case anyone else is interested.] On Wed, May 27, 2015 at 7:35 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > That could be due to a number of reasons. Are you connected via > HDMI/usb or a serial console? Serial console over USB. MicroZed has an on-board CP2104 USB-serial bridge, connected to Zynq UART pins in MIO bank 1/501. > OK, what versions of u-boot and kernel? U-Boot identifies itself as U-Boot 2013.10. The kernel identifies as 3.8.0-xilinx. Both are forked from the Xilinx repos on github, with additional patches for MicroZed from VXM Design. The repo is: http://www.vxmdesign.com/zynq.html I haven't tried using that kernel with Fedora userspace yet; I was hoping to use the Fedora kernel. > Can you provide, via fpaste please, a log of the working boot? http://paste.fedoraproject.org/226254 > I suspect it's an issue with the DTB, do you know what version of > kernel the DT works with, where it comes from etc? I think the DT comes from Xilinx, but may have changes by VXM Design. It's here: https://github.com/vxmdesign/buildroot/blob/master/board/zynq/microzed/uzed.dts If there is a DT problem, is there a Fedora Zynq DT for another board that I should look at for comparison? > You'd only need different ones if our kernel was too large to fix in > the defined range. It's possible it is as we have a multiplatform > kernel which is quite a bit larger than a custom kernel for a specific > size. OK, I'll check that. > I've enabled a few ZYNQ devices in our u-boot in rawhide [1] so I'd be > interested in feedback how you get on with that. I'm not sure of the > feature set of the upstream zynq support. It's been on my list to look > at but I've not had anyone request it until now. I'd certainly be > interested in feedback and assistance in ensuring we can support these > moving forward. I'll certainly provide all of the feedback and patches that I can. It would be nice to see MicroZed as a supported Fedora ARM platform. > Interesting, I wonder if the upstream u-boot support uses the same > modification so as to not require the Xilinx FSBL. Once the above > build completes I'd be interested to here if the binary works to at > least get to a working u-boot prompt. Does your Zynq work still require a Xilinx FSBL? It appears that there's a 192KB limit on the boot.bin image size that the Zynq ROM will load into RAM, and normal u-boot is larger. It appears that the VXM Design hack is to build a small u-boot (37628 bytes) as boot.bin, and have that load and run a full u-boot. However, I haven't really dug into this so I could be mistaken. I need to redo the buildroot build from scratch and capture all the output to a log so I can figure out what the build actually does. Best regards, Eric _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
