|
It seems I am not the only one having this problem. I read through some old emails on this mailing list, and someone mentioned something about the romfs beginning exactly in the .bss section of the image, and that the romfs is "moved" at boot time to another location. Have I misunderstood this? If this is the case, then where exactly does it move it to? If it is not being moved, perhaps there is a conflict with the romfs and the .bss section? It seems to point to some problem with reading the romfs. The uclinux[mtd] probe seems to find the filesystem ok (I dont know what it does to do this...) but are thre any simple tests that I could include in the init/main.c to test romfs readability before the hang I usually get? By hang I mean where it is unable execute the first file in the romfs, around line 650 of init/main.c Also, a few more curious points: After the "hang", I have seen the console echo back characters to me when typed. Does this indicate some life in the system? Also, on some occasions, I have seen XMD report an error just at this hang point, and print a handful or random characters to the screen. Is it possible that uClinux is trying to use the debug uart as some kind on console? Shouldn't it use the same uart (console_uart) that is has been using all the time while booting? Curious issues!! p.s. a bit off-topic, but anyone tried the MicroBlaze version 4.0 with cachelink, multichanel SDRAM controller and hard fpu with uClinux yet? Is it blindingly fast? I've seen that (in theory - dont have a chip to test it yet), a typical uclinux system, supporting all of the above, could run about 150MHz on a V4 LX25-12. That's pretty fast!!! Cheers, John mcnernbm@notes.udayton.edu wrote:
--
***********************************************************************
/ /\/ John McGrath
\ \ Xilinx Inc.
\_\/\
Telephone: +353 21 4355 704
FAX:
John.McGrath@xilinx.com
X I L I N X I N C.
***********************************************************************
|