Stuck on black and white "XILLYBUS" screen while booting
Posted:
Hello,
I am using Xillinux 1.3c. I tested the xillydemo bundle and it all worked very well. The only thing I was lacking was I need a 2nd UART from one of the PMOD connectors. In the xillydemo build in Vivado 2014.4, I added UART0 through EMIO, made a design wrapper for the uart_tx and rx, and changed the xillydemo.xdc by replacing GPIO ports 54 and 55 to the uart_rx and uart_tx ports. It is my understanding that if a peripheral is added using a bus connector that already existed (gpio 54 and 55), then there is no need to re-generate boot.bin, just to replace the new .bit and .dtb on the SD card. I was able to successfully re-generate a new xillydemo.bit file and updated the devicetree.dtb accordingly, but I get stuck on the screen that just says XILLYBUS in black and white when trying to boot. That change is the only one I made. For such a change, will I have to re-generate boot.bin? I get stuck here because while I am able to get a new FSBL.elf for my build through the SDK, the u-boot.elf I tried using is not working. Can anyone help? If I provide all the necessary files (fsbl.elf, xillydemo.bit), could someone generate the boot.bin for me? Any help would be appreciated.
Thank you,
Chris
I am using Xillinux 1.3c. I tested the xillydemo bundle and it all worked very well. The only thing I was lacking was I need a 2nd UART from one of the PMOD connectors. In the xillydemo build in Vivado 2014.4, I added UART0 through EMIO, made a design wrapper for the uart_tx and rx, and changed the xillydemo.xdc by replacing GPIO ports 54 and 55 to the uart_rx and uart_tx ports. It is my understanding that if a peripheral is added using a bus connector that already existed (gpio 54 and 55), then there is no need to re-generate boot.bin, just to replace the new .bit and .dtb on the SD card. I was able to successfully re-generate a new xillydemo.bit file and updated the devicetree.dtb accordingly, but I get stuck on the screen that just says XILLYBUS in black and white when trying to boot. That change is the only one I made. For such a change, will I have to re-generate boot.bin? I get stuck here because while I am able to get a new FSBL.elf for my build through the SDK, the u-boot.elf I tried using is not working. Can anyone help? If I provide all the necessary files (fsbl.elf, xillydemo.bit), could someone generate the boot.bin for me? Any help would be appreciated.
Thank you,
Chris