Hi Grant,

	Thanks for your answer.
I have found in the System.map :
c020f0c4 b __log_buf

Is the address c020f0c4 relative to the .data segment?

I understand that when the system hangs I should type in the XMD window 
stop.

Is there anyway to examine the memory from the XMD window? or should I 
reload the u-boot and examine the memory from u-boot?

Best Regards

Mirek



On Tue, 28 Aug 2007, Grant Likely wrote:

On 8/28/07, Miroslaw Dach [off-list ref] wrote:

quoted

Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw
nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp
ip=::::virtex4-mirek:eth0:dhcp panic=1
Uncompressing Linux...


After that system just hangs.

I do not understand why it is possible to run zImage.elf straight from jtag
but it hangs when started from u-boot.

Is it any fundamental problem with running Linux from u-boot on ML403
(Virtex-4) boards?

No there isn't.  It should work.  Most likely the kernel did not hang
immediately, but rather the console is not setup correctly.  You need
to halt the processor after the hang and look at __log_buf in memory
(Find the address in System.map).

Cheers,
g.

quoted

Best Regards

Mirek

-- 
=============================================================================
          Miroslaw Dach (Miroslaw.Dach@psi.ch) - SLS/Controls Group 
                PSI - Paul Scherrer Institut CH-5232 Villigen
=============================================================================