Hi John, John Mcgrath wrote:
Well, this problem has strangely resolved itself!!After a lot of hacking, and attempts, it is now booting beautifully (Thanks guys!!!)
The only thing that I changed was the early printK uartlite address, to be the uartlite address in my system.It seems after I did this, it all worked. I’m not sure why this would be, but I hope to be able to repeat J
This is abug that I must fix - basically the early_printk output code loops checking the status of the UART - but if that address is wrong, it loops forever reading status of a device that isn't there :(
I will make sure this is fixed in the next release. Regards, John ___________________________ microblaze-uclinux mailing list microblaze-uclinux@xxxxxxxxxxxxxx Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/