Linux booting problem on Xilinx ppc
Dear friends,
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:
loaded at: 00400000 004B51E4
board data at: 00000000 00000018
relocated to: 0040526C 00405284
zimage at: 00405B2B 004B177C
avail ram: 004B6000 60000000
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rw
Uncompressing Linux...done.
Now booting the kernelThen it hangs. First it seems to me that the "avail ram" is not correct, since I configured only 32MB SDRAM. Moreover, if it's first powered on, the end address of "avail ram" would be FFD9FBED. Then I tried to investigate the problem using xmd. When launched, it says:
Processor(s) in System ::
PowerPC405(1) : ppc405_0
Address Map for Processor ppc405_0
(0x00000000-0x01ffffff) Infineon_Mobile_SDRAM_HYB25L128160AC_8plb
(0x40600000-0x4060ffff) RS232 plb->plb2opb->opb
(0x41200000-0x4120ffff) opb_intc_0 plb->plb2opb->opb
(0x41800000-0x4180ffff) SysACE_CompactFlash plb->plb2opb->opb
(0x41c00000-0x41c0ffff) opb_timer_1 plb->plb2opb->opb
(0x80200000-0x8020ffff) RS232_1 plb
(0x80400000-0x8040ffff) Broadcom_BCM5221_Ethernet_Transceiver plb
(0xfffe0000-0xffffffff) plb_bram_if_cntlr_1 plb PowerPC405(2) : ppc405_1
Address Map for Processor ppc405_1
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0. LPT base address = 0378h. ECP base address = 0778h.
Cable connection established.
INFO:MDT - Assumption: Selected Device 2 for debugging.
JTAG chain configuration
--------------------------------------------------
Device ID Code IR Length Part Name 1 0a001093 8 System_ACE 2 0129e093 14 XC2VP50
XMD: Connected to PowerPC target. Processor Version No : 0x200108a0 Address mapping for accessing special PowerPC features from XMD/GDB:
I-Cache (Data) : Disabled
I-Cache (Tag) : Disabled
D-Cache (Data) : Disabled
D-Cache (Tag) : Disabled
ISOCM : Start Address - 0xfffe0000, Size - 131072 bytes
TLB : Disabled
DCR : Disabled Connected to "ppc" target. id = 0
Starting GDB server for "ppc" target (id = 0) at TCP port no 1234
Then I download the Linux kernel using dow, and the following message
appears:
WARNING: Attempted to read location: 0xfffffffc. Reading ISOCM memory
not supported
section, .text: 0x00400000-0x00404b6c
section, .data: 0x00405000-0x004b2000
section, .bss: 0x004b2000-0x004b51e4 Downloaded Program linux_kernel/zImage.elf
Setting PC with program start addr = 0x00400000
PC reset to 0x00400000, Clearing MSR Register
After typing "run" command, the following appears:
PC reset to 0x00400000, Clearing MSR Register Processor started. Type "stop" to stop processor
Then after issuing "stop", it says "unable to stop processor"
I also tried kernel version 2.6.22, but the same thing happens, except that the "avail ram" changed to 7C9E2378 and it's the same no matter first powered on or not.
No idea how to continue...
Could somebody give me some help? Thanks!
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a12694083 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
And I checked the xparameters_ml300.h for the possible problem yet not found...
Quoted 91 lines · Junqiang Hu
Dear friends,
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000 Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rw Uncompressing Linux...done. Now booting the kernelThen it hangs. First it seems to me that the "avail ram" is not correct, since I configured only 32MB SDRAM. Moreover, if it's first powered on, the end address of "avail ram" would be FFD9FBED. Then I tried to investigate the problem using xmd. When launched, it says:
Processor(s) in System ::
PowerPC405(1) :
ppc405_0
Address Map for Processorppc405_0(0x00000000-0x01ffffff) Infineon_Mobile_SDRAM_HYB25L128160AC_8plb (0x40600000-0x4060ffff) RS232 plb->plb2opb->opb (0x41200000-0x4120ffff) opb_intc_0 plb->plb2opb->opb (0x41800000-0x4180ffff) SysACE_CompactFlash plb->plb2opb->opb (0x41c00000-0x41c0ffff) opb_timer_1 plb->plb2opb->opb (0x80200000-0x8020ffff) RS232_1 plb (0x80400000-0x8040ffff) Broadcom_BCM5221_Ethernet_Transceiver plb (0xfffe0000-0xffffffff) plb_bram_if_cntlr_1 plbPowerPC405(2) :
ppc405_1
Address Map for Processorppc405_1Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0. LPT base address = 0378h. ECP base address = 0778h.
Cable connection established.
INFO:MDT - Assumption: Selected Device 2 for debugging.JTAG chain configuration
--------------------------------------------------Device ID Code IR Length Part Name 1 0a001093 8 System_ACE 2 0129e093 14 XC2VP50XMD: Connected to PowerPC target. Processor Version No :
0x200108a0Address mapping for accessing special PowerPC features from XMD/GDB:I-Cache (Data) : Disabled I-Cache (Tag) : Disabled D-Cache (Data) : Disabled D-Cache (Tag) : Disabled ISOCM : Start Address - 0xfffe0000, Size - 131072 bytes TLB : Disabled DCR : DisabledConnected to "ppc" target. id = 0
Starting GDB server for "ppc" target (id = 0) at TCP port no 1234Then I download the Linux kernel using dow, and the following message
appears:WARNING: Attempted to read location:
0xfffffffc. Reading ISOCM memory
not supportedsection, .text: 0x00400000-0x00404b6c section, .data: 0x00405000-0x004b2000 section, .bss: 0x004b2000-0x004b51e4Downloaded Program linux_kernel/zImage.elf
Setting PC with program start addr =0x00400000
PC reset to0x00400000, Clearing MSR RegisterAfter typing "run" command, the following appears:
PC reset to0x00400000, Clearing MSR Register Processor started. Type "stop" to stop processor
Then after issuing "stop", it says "unable to stop processor"I also tried kernel version 2.6.22, but the same thing happens, except that the "avail ram" changed to 7C9E2378 and it's the same no matter first powered on or not.
No idea how to continue...
Could somebody give me some help? Thanks!
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a12694097 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
Quoted 4 lines · Junqiang Hu
Dear friends,
Quoted 8 lines
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000
I strongly recommend moving to a 2.6 kernel. Recent mainline has support for the Xilinx ppc built in.
Quoted 9 lines
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rw Uncompressing Linux...done.
Now booting the kernelThen it hangs. First it seems to me that the "avail ram" is not correct, since I configured only 32MB SDRAM. Moreover, if it's first powered on, the end address of "avail ram" would be FFD9FBED. Then I tried to investigate the problem using xmd. When launched, it says:
(If you're using u-boot) You might have a mismatch between the board info structure used by u-boot and the one used by Linux.
Also, you should use your debugger to inspect the __log_buf memory of the kernel. A common problem is the kernel starts booting, but the console is setup incorrectly and so you see nothing. But, you can read the console output directly from memory if you look at the __log_buf region (find the address in the System.map file; you might need to subtract 0xC0000000 from the address to view the memory)
Cheers,
g.
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
Hi Grant,
Thank you so much for the reply! Fortunately I got it work now -- it's
the crosstool compiler problem. Originally I was using gcc-4.1.0, yet when compiling kernel 2.6.22, I noticed that it says gcc-4.1.0 will miscompile the kernel, so I changed to another version, and now I can let it go!
Right now still not fully booted because of the SystemACE problem, or
maybe the partition is not correct. I'm still working on it, hopefully to get it solved soon :-)
Thanks,
-J.
Quoted 52 lines · Grant Likely-2 wrote:
Quoted 4 lines · Junqiang Hu
Dear friends,
Quoted 8 lines
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000I strongly recommend moving to a 2.6 kernel. Recent mainline has support for the Xilinx ppc built in.
Quoted 10 lines
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3 rw Uncompressing Linux...done.
Now booting the kernelThen it hangs. First it seems to me that the "avail ram" is not correct, since I configured only 32MB SDRAM. Moreover, if it's first powered on, the
end address of "avail ram" would be FFD9FBED. Then I tried to investigate the problem using xmd. When launched, it says:(If you're using u-boot) You might have a mismatch between the board info structure used by u-boot and the one used by Linux.
Also, you should use your debugger to inspect the
__log_bufmemory of the kernel. A common problem is the kernel starts booting, but the console is setup incorrectly and so you see nothing. But, you can read the console output directly from memory if you look at the__log_bufregion (find the address in the System.map file; you might need to subtract0xC0000000from the address to view the memory)Cheers,
g.Signature · 8 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195 _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a12696686 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
We are seeing similar problems (wrong memory displayed, kernel hangup) when compiling a 2.6.23-rc2 kernel with gcc 4.1.1 for an ml403 board. Using gcc 3.4.4 to compile the kernel, then there is no problem (the kernel boots)
Setting mem in the kernel config does not solve the issue.
Stelios S. Koroneos
Digital OPSiS - Embedded Intelligence
http://www.digital-opsis.com
Quoted 86 lines
-----Original Message-----
From:
[email protected] [mailto:linuxppc-embedded-bounces+stelios=stelioscellar.com@ozlabs .org]On Behalf Of Junqiang Hu
Sent: Sunday, September 16, 2007 7:40 AM
To: [email protected]
Subject: Re: Linux booting problem on Xilinx ppcHi Grant,
Thank you so much for the reply! Fortunately I got it work now -- it's
the crosstool compiler problem. Originally I was using gcc-4.1.0, yet when
compiling kernel 2.6.22, I noticed that it says gcc-4.1.0 will miscompile the kernel, so I changed to another version, and now I can let it go!Right now still not fully booted because of the SystemACE problem, or
maybe the partition is not correct. I'm still working on it, hopefully to get it solved soon :-)Thanks,
-J.Quoted 15 lines · Grant Likely-2 wrote:
Quoted 4 lines · Junqiang Hu
Dear friends,
Quoted 8 lines
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000Quoted 4 lines
I strongly recommend moving to a 2.6 kernel. Recent mainline has support for the Xilinx ppc built in.
Quoted 2 lines
Linux/PPC load: console=ttyS0,9600root=/dev/xsysace/disc0/part3 rw
Quoted 4 lines
Quoted 4 lines
Uncompressing Linux...done.
Now booting the kernelThen it hangs. First it seems to me that the "avail ram" is
not correct,
Quoted 1 line
Quoted 1 line
since I configured only 32MB SDRAM. Moreover, if it's first
powered on,
Quoted 2 lines
Quoted 2 lines
the
end address of "avail ram" would be FFD9FBED. Then I tried toinvestigate
Quoted 15 lines
Quoted 1 line
the problem using xmd. When launched, it says:
(If you're using u-boot) You might have a mismatch between the board info structure used by u-boot and the one used by Linux.
Also, you should use your debugger to inspect the
__log_bufmemory of the kernel. A common problem is the kernel starts booting, but the console is setup incorrectly and so you see nothing. But, you can read the console output directly from memory if you look at the__log_bufregion (find the address in the System.map file; you might need to subtract0xC0000000from the address to view the memory)Cheers,
g.Quoted 11 lines
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
[email protected]
(403) 399-0195
_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Quoted 3 lines
--
View this message in context:
http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf444906
0.html#a12696686
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Hello
I'm also working with ML403 board from Xilinx and have the same problem as you. The boot process stops after decompressing with the message "Now booting the kernel". We also used gcc-4.1.0 for the cross compilation. So, I would be glad to know, which gcc version have you used to get a working kernel!
Thanks,
Andreas
Quoted 75 lines · Junqiang Hu
Hi Grant,
Thank you so much for the reply! Fortunately I got it work now -- it's
the crosstool compiler problem. Originally I was using gcc-4.1.0, yet when compiling kernel 2.6.22, I noticed that it says gcc-4.1.0 will miscompile the kernel, so I changed to another version, and now I can let it go!Right now still not fully booted because of the SystemACE problem, or
maybe the partition is not correct. I'm still working on it, hopefully to get it solved soon :-)Thanks,
-J.Quoted 54 lines · Grant Likely-2 wrote:
Quoted 4 lines · Junqiang Hu
Dear friends,
Quoted 8 lines
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000I strongly recommend moving to a 2.6 kernel. Recent mainline has support for the Xilinx ppc built in.
Quoted 6 lines
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3
rw
Uncompressing Linux...done.
Now booting the kernelQuoted 6 lines
Then it hangs. First it seems to me that the "avail ram" is not correct, since I configured only 32MB SDRAM. Moreover, if it's first powered on, the
end address of "avail ram" would be FFD9FBED. Then I tried to investigate
the problem using xmd. When launched, it says:(If you're using u-boot) You might have a mismatch between the board info structure used by u-boot and the one used by Linux.
Also, you should use your debugger to inspect the
__log_bufmemory of the kernel. A common problem is the kernel starts booting, but the console is setup incorrectly and so you see nothing. But, you can read the console output directly from memory if you look at the__log_bufregion (find the address in the System.map file; you might need to subtract0xC0000000from the address to view the memory)Cheers,
g.Signature · 8 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195 _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13219154 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
In house we use the gcc 4.1.2, glibc 2.3.6 combo with success.
-- Mike
-----Original Message-----
From: aauer1 [mailto:[email protected]]=20
Sent: Monday, October 15, 2007 2:47 PM
To: [email protected]
Subject: Re: Linux booting problem on Xilinx ppc
Hello
I'm also working with ML403 board from Xilinx and have the same problem as you. The boot process stops after decompressing with the message "Now booting the kernel". We also used gcc-4.1.0 for the cross compilation. So, I would be glad to know, which gcc version have you used to get a working kernel!
Thanks,
Andreas
Quoted 9 lines · Junqiang Hu
=20
=20
Hi Grant,
=20
Thank you so much for the reply! Fortunately I got it work now --=20
it's the crosstool compiler problem. Originally I was using=20 gcc-4.1.0, yet when compiling kernel 2.6.22, I noticed that it says=20 gcc-4.1.0 will miscompile the kernel, so I changed to another version,
Quoted 20 lines
and now I can let it go!
=20
Right now still not fully booted because of the SystemACE problem,=20
or maybe the partition is not correct. I'm still working on it,=20 hopefully to get it solved soon :-)
=20
Thanks,
-J.
=20
=20Quoted 9 lines · Grant Likely-2 wrote:
=20
Quoted 7 lines · Junqiang Hu
Dear friends,
I'm trying to run Linux in AvNet (Memec)=20
Xilinx-XC2VP50-EVKT-FF1152 board. The Linux version I'm using is=20 2.4; the cross-compiler is gcc-4.1.0, glibc 2.3.6. When booting the
kernel, it shows:
Quoted 45 lines
Quoted 37 lines
Quoted 5 lines
loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000=20
I strongly recommend moving to a 2.6 kernel. Recent mainline has=20 support for the Xilinx ppc built in.Quoted 11 lines
Linux/PPC load: console=3DttyS0,9600=20root=3D/dev/xsysace/disc0/part3 rw
Uncompressing Linux...done.
Now booting the kernelThen it hangs. First it seems to me that the "avail ram" is not=20 correct, since I configured only 32MB SDRAM. Moreover, if it's=20 first powered on, the end address of "avail ram" would be FFD9FBED.=20 Then I tried to investigate the problem using xmd. When launched,=20 it says:
=20
(If you're using u-boot) You might have a mismatch between the board=20 info structure used by u-boot and the one used by Linux.
=20
Also, you should use your debugger to inspect the__log_bufmemory ofthe kernel. A common problem is the kernel starts booting, but the=20 console is setup incorrectly and so you see nothing. But, you can=20 read the console output directly from memory if you look at the=20
__log_bufregion (find the address in the System.map file; you might=20 need to subtract0xC0000000from the address to view the memory) =20
Cheers,
g.
=20
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.Quoted 8 lines
[email protected]
(403) 399-0195
_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
=20
=20
Quoted 2 lines
=20
=20
--
View this message in context:
http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html
#a13219154
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
Quoted 8 lines · On 10/15/07, aauer1 <[email protected]> wrote:
Hello
I'm also working with ML403 board from Xilinx and have the same problem as you. The boot process stops after decompressing with the message "Now booting the kernel". We also used gcc-4.1.0 for the cross compilation. So, I would be glad to know, which gcc version have you used to get a working kernel!
First step:
Get a JTAG debugger and look at the __log_buf address.
g.
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
I noticed this problem happens when on-chip memories are enabled in a design (it is 4th page in base system builder). Try to leave them "none" for both instruction and data.
Sergey
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of aauer1
Sent: Monday, October 15, 2007 1:47 PM
To: [email protected]
Subject: Re: Linux booting problem on Xilinx ppc
Hello
I'm also working with ML403 board from Xilinx and have the same problem as you. The boot process stops after decompressing with the message "Now booting the kernel". We also used gcc-4.1.0 for the cross compilation. So, I would be glad to know, which gcc version have you used to get a working kernel!
Thanks,
Andreas
Quoted 75 lines · Junqiang Hu
Hi Grant,
Thank you so much for the reply! Fortunately I got it work now -- it's
the crosstool compiler problem. Originally I was using gcc-4.1.0, yet when compiling kernel 2.6.22, I noticed that it says gcc-4.1.0 will miscompile the kernel, so I changed to another version, and now I can let it go!Right now still not fully booted because of the SystemACE problem, or
maybe the partition is not correct. I'm still working on it, hopefully to get it solved soon :-)Thanks,
-J.Quoted 54 lines · Grant Likely-2 wrote:
Quoted 4 lines · Junqiang Hu
Dear friends,
Quoted 8 lines
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000I strongly recommend moving to a 2.6 kernel. Recent mainline has support for the Xilinx ppc built in.
Quoted 6 lines
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3
rw
Uncompressing Linux...done.
Now booting the kernelQuoted 6 lines
Then it hangs. First it seems to me that the "avail ram" is not correct, since I configured only 32MB SDRAM. Moreover, if it's first powered on, the
end address of "avail ram" would be FFD9FBED. Then I tried to investigate
the problem using xmd. When launched, it says:(If you're using u-boot) You might have a mismatch between the board info structure used by u-boot and the one used by Linux.
Also, you should use your debugger to inspect the
__log_bufmemory of the kernel. A common problem is the kernel starts booting, but the console is setup incorrectly and so you see nothing. But, you can read the console output directly from memory if you look at the__log_bufregion (find the address in the System.map file; you might need to subtract0xC0000000from the address to view the memory)Cheers,
g.Signature · 8 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195 _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Signature · 9 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13 219154 Sent from the linuxppc-embedded mailing list archive at Nabble.com. _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
The on-chip memories are disabled. Only the BRAM is enabled. Now, we also use the ELDK 4.1 from Denx and the included cross compiler. The result is the same... the Kernel stops at "Now booting the kernel". Now, we also have an USB JTAG cable. So, we can debug the memory.
Probably, anyone has another idea.
Thanks,
Andreas
Quoted 130 lines · Sergey Oleynichenko
I noticed this problem happens when on-chip memories are enabled in a design
(it is 4th page in base system builder). Try to leave them "none" for both instruction and data.Sergey
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of aauer1
Sent: Monday, October 15, 2007 1:47 PM
To: [email protected]
Subject: Re: Linux booting problem on Xilinx ppcHello
I'm also working with ML403 board from Xilinx and have the same problem as you. The boot process stops after decompressing with the message "Now booting the kernel". We also used gcc-4.1.0 for the cross compilation. So, I
would be glad to know, which gcc version have you used to get a working kernel!Thanks,
AndreasQuoted 79 lines · Junqiang Hu
Hi Grant,
Thank you so much for the reply! Fortunately I got it work now --
it's
the crosstool compiler problem. Originally I was using gcc-4.1.0, yet when compiling kernel 2.6.22, I noticed that it says gcc-4.1.0 will miscompile the kernel, so I changed to another version, and now I can let it go!Right now still not fully booted because of the SystemACE problem, or
maybe the partition is not correct. I'm still working on it, hopefully to
get it solved soon :-)Thanks,
-J.Quoted 56 lines · Grant Likely-2 wrote:
Quoted 4 lines · Junqiang Hu
Dear friends,
Quoted 8 lines
I'm trying to run Linux in AvNet (Memec) Xilinx-XC2VP50-EVKT-FF1152
board. The Linux version I'm using is 2.4; the cross-compiler is
gcc-4.1.0, glibc 2.3.6. When booting the kernel, it shows:loaded at: 00400000 004B51E4 board data at: 00000000 00000018 relocated to: 0040526C 00405284 zimage at: 00405B2B 004B177C avail ram: 004B6000 60000000I strongly recommend moving to a 2.6 kernel. Recent mainline has support for the Xilinx ppc built in.
Quoted 6 lines
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace/disc0/part3
rw
Uncompressing Linux...done.
Now booting the kernelQuoted 8 lines
Then it hangs. First it seems to me that the "avail ram" is not correct,
since I configured only 32MB SDRAM. Moreover, if it's first powered on,
the
end address of "avail ram" would be FFD9FBED. Then I tried to investigate
the problem using xmd. When launched, it says:(If you're using u-boot) You might have a mismatch between the board info structure used by u-boot and the one used by Linux.
Also, you should use your debugger to inspect the
__log_bufmemory of the kernel. A common problem is the kernel starts booting, but the console is setup incorrectly and so you see nothing. But, you can read the console output directly from memory if you look at the__log_bufregion (find the address in the System.map file; you might need to subtract0xC0000000from the address to view the memory)Cheers,
g.Signature · 8 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195 _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embeddedSignature · 14 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13 219154 Sent from the linuxppc-embedded mailing list archive at Nabble.com. _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13239003 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
Quoted 6 lines · On 10/16/07, aauer1 <[email protected]> wrote:
The on-chip memories are disabled. Only the BRAM is enabled. Now, we also use the ELDK 4.1 from Denx and the included cross compiler. The result is the same... the Kernel stops at "Now booting the kernel". Now, we also have an USB JTAG cable. So, we can debug the memory.
Probably, anyone has another idea.
There are two common reasons for this behaviour:
1. kernel crashes before the console is configured
2. the console is not configured correctly.
In both cases; finding a way to look at __log_buf is the fastest way to figure out what is going on.
Cheers,
g.
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
Quoted 9 lines · Grant Likely
Quoted 6 lines · On 10/16/07, aauer1 <[email protected]> wrote:
The on-chip memories are disabled. Only the BRAM is enabled. Now, we also use the ELDK 4.1 from Denx and the included cross compiler. The result is the same... the Kernel stops at "Now booting the kernel". Now, we also have an USB JTAG cable. So, we can debug the memory.
Probably, anyone has another idea.
Quoted 6 lines
There are two common reasons for this behaviour:
1. kernel crashes before the console is configured
2. the console is not configured correctly.In both cases; finding a way to look at
__log_bufis the fastest way to figure out what is going on.
Woah. Grant's [good] advise notwithstanding, I'm confused
Signature · 4 lines
/"\ ASCII Ribbon Campaign | \ / | Email to user 'CTZ001' X Against HTML | at 'email.mot.com' / \ in e-mail & news |
Quoted 10 lines · T Ziomek
Quoted 7 lines · Grant Likely
There are two common reasons for this behaviour:
1. kernel crashes before the console is configured
2. the console is not configured correctly.In both cases; finding a way to look at
__log_bufis the fastest way to figure out what is going on.Woah. Grant's [good] advise notwithstanding, I'm confused
In what way?
Quoted 11 lines
--
/"\ ASCII Ribbon Campaign | \ / | Email to user 'CTZ001' X Against HTML | at 'email.mot.com' / \ in e-mail & news |_______________________________________________
Linuxppc-embedded mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
Ack, sorry! [was Re: Linux booting problem on Xilinx ppc]
In reply to Grant LikelyPlease ignore my previous msg; I wanted to <cancel> rather than <send>... Sorry.
Signature · 4 lines
/"\ ASCII Ribbon Campaign | \ / | Email to user 'CTZ001' X Against HTML | at 'email.mot.com' / \ in e-mail & news |
Hello.
Quoted 11 lines · Grant Likely-2 wrote:
Quoted 8 lines · On 10/16/07, aauer1 <[email protected]> wrote:
The on-chip memories are disabled. Only the BRAM is enabled. Now, we also use
the ELDK 4.1 from Denx and the included cross compiler. The result is the same... the Kernel stops at "Now booting the kernel". Now, we also have an
USB JTAG cable. So, we can debug the memory.
Probably, anyone has another idea.
Quoted 8 lines
There are two common reasons for this behaviour:
1. kernel crashes before the console is configured
2. the console is not configured correctly.In both cases; finding a way to look at
__log_bufis the fastest way to figure out what is going on.
I was able to look at the __log_buf variable with the JTAG cable. So, I recognized that the kernel doesn't halt after the "No booting the kernel" message. There are many output messages in the __log_buf variable until it stops at with a "Kernel panic" because the rootfs is not found (but this is the minor problem).
Now, I know that the kernel boots but I don't get an output with my Xilinx UartLite module. Are there some kernel modules which must be activated?? Btw. I have used the Linux-2.6-virtex kernel from
http://git.secretlab.ca/git/ and another Kernel (2.6.23 from kernel.org) - both with the same result.
Thanks a lot,
Andreas
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13252272 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
Quoted 10 lines · On 10/17/07, aauer1 <[email protected]> wrote:
I was able to look at the
__log_bufvariable with the JTAG cable. So, I recognized that the kernel doesn't halt after the "No booting the kernel" message. There are many output messages in the__log_bufvariable until it stops at with a "Kernel panic" because the rootfs is not found (but this is the minor problem).
Now, I know that the kernel boots but I don't get an output with my Xilinx UartLite module. Are there some kernel modules which must be activated?? Btw. I have used the Linux-2.6-virtex kernel from
http://git.secretlab.ca/git/ and another Kernel (2.6.23 from kernel.org) - both with the same result.
Post the output of __log_buf here please.
g.
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
Quoted 10 lines · Grant Likely-2 wrote:
Quoted 7 lines · On 10/17/07, aauer1 <[email protected]> wrote:
Now, I know that the kernel boots but I don't get an output with my Xilinx
UartLite module. Are there some kernel modules which must be activated?? Btw. I have used the Linux-2.6-virtex kernel from
http://git.secretlab.ca/git/ and another Kernel (2.6.23 from kernel.org) -
both with the same result.
Quoted 3 lines
Post the output of
__log_bufhere please.
Here is my dump of the __log_buf:
======================
<5>[ 0.000000] Linux version 2.6.23-rc2 ([email protected]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0 .0)) #8 Wed Oct 17 20:05:28 CEST 2007 <6>[ 0.000000] Xilinx ML403 Reference System (Virtex-4 FX) <7>[ 0.000000] Entering add_active_range(0, 0, 16384) 0 entries of 256 used <4>[ 0.000000] Zone PFN ranges: <4>[ 0.000000] DMA 0 -> 16384 <4>[ 0.000000] Normal 16384 -> 16384 <4>[ 0.000000] Movable zone start PFN for each node <4>[ 0.000000] early_node_map[1] active PFN ranges <4>[ 0.000000] 0: 0 -> 16384 <7>[ 0.000000] On node 0 totalpages: 16384 <7>[ 0.000000] DMA zone: 128 pages used for memmap <7>[ 0.000000] DMA zone: 0 pages reserved <7>[ 0.000000] DMA zone: 16256 pages, LIFO batch:3 <7>[ 0.000000] Normal zone: 0 pages used for memmap <7>[ 0.000000] Movable zone: 0 pages used for memmap <4>[ 0.000000] Built 1 zonelists in Zone order. Total pages: 16256 <5>[ 0.000000] Kernel command line: console=ttUL0 root=/dev/xsysace2 rw <6>[ 0.000000] Xilinx INTC #0 at 0x41200000 mapped to 0xFDFFF000 <4>[ 0.000000] PID hash table entries: 256 (order: 8, 1024 bytes) <4>[ 0.000325] Console: colour dummy device 80x25 <6>[ 0.001380] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) <6>[ 0.002924] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) <4>[ 0.029750] Memory: 63256k available (1172k kernel code, 384k data, 84k init, 0k highmem) <7>[ 0.030975] Calibrating delay loop... 299.00 BogoMIPS (lpj=598016) <4>[ 0.120718] Mount-cache hash table entries: 512 <6>[ 0.171779] io scheduler noop registered <6>[ 0.171857] io scheduler anticipatory registered (default) <6>[ 0.171884] io scheduler deadline registered <6>[ 0.172262] io scheduler cfq registered <6>[ 0.268268] uartlite.0: ttyUL0 at MMIO 0x40600000 (irq = 2) is a uartlite <4>[ 0.281400] RAMDISK driver initialized: 8 RAM disks of 8192K size 1024 blocksize <6>[ 0.282765] mice: PS/2 mouse device common for all mice <4>[ 0.286181] VFS: Cannot open root device "xsysace2" or unknown-block(0,0) <4>[ 0.286252] Please append a correct "root=" boot option; here are the available partitions: <0>[ 0.286323] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) <0>[ 0.286374] Rebooting in 180 seconds..
Thanks,
Andreas
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13259685 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
Quoted 32 lines · On 10/17/07, aauer1 <[email protected]> wrote:
Quoted 10 lines · Grant Likely-2 wrote:
Quoted 7 lines · On 10/17/07, aauer1 <[email protected]> wrote:
Now, I know that the kernel boots but I don't get an output with my Xilinx
UartLite module. Are there some kernel modules which must be activated?? Btw. I have used the Linux-2.6-virtex kernel from
http://git.secretlab.ca/git/ and another Kernel (2.6.23 from kernel.org) -
both with the same result.Quoted 3 lines
Post the output of
__log_bufhere please.Here is my dump of the
__log_buf:
======================<5>[ 0.000000] Linux version 2.6.23-rc2 ([email protected]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0 .0)) #8 Wed Oct 17 20:05:28 CEST 2007 <6>[ 0.000000] Xilinx ML403 Reference System (Virtex-4 FX) <7>[ 0.000000] Entering add_active_range(0, 0, 16384) 0 entries of 256 used <4>[ 0.000000] Zone PFN ranges: <4>[ 0.000000] DMA 0 -> 16384 <4>[ 0.000000] Normal 16384 -> 16384 <4>[ 0.000000] Movable zone start PFN for each node <4>[ 0.000000] early_node_map[1] active PFN ranges <4>[ 0.000000] 0: 0 -> 16384
Quoted 8 lines
<7>[ 0.000000] On node 0 totalpages: 16384 <7>[ 0.000000] DMA zone: 128 pages used for memmap <7>[ 0.000000] DMA zone: 0 pages reserved <7>[ 0.000000] DMA zone: 16256 pages, LIFO batch:3 <7>[ 0.000000] Normal zone: 0 pages used for memmap <7>[ 0.000000] Movable zone: 0 pages used for memmap <4>[ 0.000000] Built 1 zonelists in Zone order. Total pages: 16256 <5>[ 0.000000] Kernel command line: console=ttUL0 root=/dev/xsysace2 rw
Typo! :-)
Try "ttyUL0"
g.
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
Thanks. Now, I get the output over the serial line!!!!
Thanks, very much!
Andreas
Quoted 64 lines · Grant Likely-2 wrote:
Quoted 42 lines · On 10/17/07, aauer1 <[email protected]> wrote:
Quoted 5 lines · Grant Likely-2 wrote:
Quoted 3 lines · On 10/17/07, aauer1 <[email protected]> wrote:
Now, I know that the kernel boots but I don't get an output with my Xilinx
UartLite module. Are there some kernel modules which must beactivated??
Quoted 2 lines
Quoted 2 lines
Btw. I have used the Linux-2.6-virtex kernel from
http://git.secretlab.ca/git/ and another Kernel (2.6.23 fromkernel.org)
Quoted 6 lines
Quoted 2 lines
-
both with the same result.Post the output of
__log_bufhere please.Here is my dump of the
__log_buf:
======================<5>[ 0.000000] Linux version 2.6.23-rc2 ([email protected]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0 .0)) #8 Wed Oct 17 20:05:28 CEST 2007 <6>[ 0.000000] Xilinx ML403 Reference System (Virtex-4 FX) <7>[ 0.000000] Entering add_active_range(0, 0, 16384) 0 entries of 256 used <4>[ 0.000000] Zone PFN ranges: <4>[ 0.000000] DMA 0 -> 16384 <4>[ 0.000000] Normal 16384 -> 16384 <4>[ 0.000000] Movable zone start PFN for each node <4>[ 0.000000] early_node_map[1] active PFN ranges <4>[ 0.000000] 0: 0 -> 16384 <7>[ 0.000000] On node 0 totalpages: 16384 <7>[ 0.000000] DMA zone: 128 pages used for memmap <7>[ 0.000000] DMA zone: 0 pages reserved <7>[ 0.000000] DMA zone: 16256 pages, LIFO batch:3 <7>[ 0.000000] Normal zone: 0 pages used for memmap <7>[ 0.000000] Movable zone: 0 pages used for memmap <4>[ 0.000000] Built 1 zonelists in Zone order. Total pages: 16256 <5>[ 0.000000] Kernel command line: console=ttUL0 root=/dev/xsysace2Quoted 1 line
rw
Typo! :-)
Try "ttyUL0"
g.
Signature · 8 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195 _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Signature · 2 lines
View this message in context: http://www.nabble.com/Linux-booting-problem-on-Xilinx-ppc-tf4449060.html#a13260526 Sent from the linuxppc-embedded mailing list archive at Nabble.com.
Quoted 32 lines · On 10/17/07, aauer1 <[email protected] > wrote:
Quoted 10 lines · Grant Likely-2 wrote:
Quoted 7 lines · On 10/17/07, aauer1 <[email protected] > wrote:
Now, I know that the kernel boots but I don't get an output with my Xilinx
UartLite module. Are there some kernel modules which must be activated??Btw. I have used the Linux-2.6-virtex kernel from http://git.secretlab.ca/git/ and another Kernel (2.6.23 from kernel.org)-
both with the same result.Quoted 3 lines
Post the output of
__log_bufhere please.Here is my dump of the
__log_buf:
======================<5 >[ 0.000000] Linux version 2.6.23-rc2 ([email protected]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0 .0)) #8 Wed Oct 17 20:05:28 CEST 2007 <6 >[ 0.000000] Xilinx ML403 Reference System (Virtex-4 FX) <7 >[ 0.000000] Entering add_active_range(0, 0, 16384) 0 entries of 256 used <4 >[ 0.000000] Zone PFN ranges: <4 >[ 0.000000] DMA 0 - > 16384 <4 >[ 0.000000] Normal 16384 - > 16384 <4 >[ 0.000000] Movable zone start PFN for each node <4 >[ 0.000000] early_node_map[1] active PFN ranges <4 >[ 0.000000] 0: 0 - > 16384
Quoted 8 lines
<7 >[ 0.000000] On node 0 totalpages: 16384 <7 >[ 0.000000] DMA zone: 128 pages used for memmap <7 >[ 0.000000] DMA zone: 0 pages reserved <7 >[ 0.000000] DMA zone: 16256 pages, LIFO batch:3 <7 >[ 0.000000] Normal zone: 0 pages used for memmap <7 >[ 0.000000] Movable zone: 0 pages used for memmap <4 >[ 0.000000] Built 1 zonelists in Zone order. Total pages: 16256 <5 >[ 0.000000] Kernel command line: console=ttUL0 root=/dev/xsysace2 rw
try the command line bootargs console=ttyUL0,boardrate root=/dev/xsysace2 rw
you must make sure that you have the xsysace2 device, or you can take a test using ramdisk.i think it will run well