Re: [microblaze-uclinux] "Found romfs @... klimit" message during kernel boot

["Victor G." <vga9@xxxxxx>]

On Tue, Jul 14, 2009 at 8:03 PM, Michal Simek<michal.simek@xxxxxxxxxxxxx> wrote:
>
>
> Victor G. wrote:
>>> For MMU kernel which I have up
>>>
>>> grep "__log_buf" System.map
>>> c0519bf0 b __log_buf
>>>
>>> My main memory starts at 0x90000000 -> changed log buffer 0x90519bf0 (you get for noMMU kernel this
>>> address)
>>>
>>> Reset board and read this addr by md. You get the similar output.
>>> What do you have there? Please send full log not only part of it!
>>
>> Here is the memory at __log_buf. Note that messages stop after
>> uartlite. I am expecting something in the lines of the following after
>> that, but there is nothing.
>> RAMDISK driver initialized: ...
>> eth0: using fifo mode.
>
> I think that the problem is just that your system is too slow.
> Missing command line shouldn't be a problem. For sure you can add it
> console=/dev/ttyUL0,115200 in kernel menuconfig.
> I still recommend you to enable caches in hw for speedup and recompile kernel
> with new Kconfig file. Then you can see if is wrong or not.
>
> Michal
>...

Hi Michal,

Please note that I am in the process of adding caches as you have
suggested (but started another post).

In the meanwhile, in my __log_buf I saw "ttyUL0 at MMIO 0x84000000
(irq = 2) is a uartlite". However, I am using /dev/ttyS0. Is it the
same thing? On the internet I found several examples of outputs by
kernel of both, the message above and similar to the following: "ttyS0
at MMIO 0x84000000 (irq = 2) is a uartlite". Currently, I am using a
serial cable without USB adapter as before. Is my configuration
somehow incorrect? Maybe that is why the output was not printing to
the serial console?

I have tried using the following and all resulted in the same output
(the klimit message followed by the first letter of __log_buf
outputted to kermit--L--i.e. "Linux ...")
petalinux-jtag-boot -p system.xmp -t 0 -a 0x90000000 -c
"console=ttyUL0,115200" -i /tftpboot/image.bin
petalinux-jtag-boot -p system.xmp -t 0 -a 0x90000000 -c
"console=ttyS0,115200" -i /tftpboot/image.bin
petalinux-jtag-boot -p system.xmp -t 0 -a 0x90000000 -c
"ttyUL0,115200" -i /tftpboot/image.bin
petalinux-jtag-boot -p system.xmp -t 0 -a 0x90000000 -c "ttyS0,115200"
-i /tftpboot/image.bin

I have also tried with USB-serial adapter and Hyperterminal on Windows
to make sure it is not Linux USB-serial driver issue and received the
same klimit message. Hopefully it will be resolved with caches
enabled. However, I am still curious about differences between ttyUL0
and ttyS0 in kernel and /dev/

Thanks,
Victor
___________________________
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/