From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound6-dub-R.bigfish.com (outbound-dub.frontbridge.com [213.199.154.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 3F75ADDED2 for ; Thu, 20 Mar 2008 02:11:15 +1100 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C889CE.8F0A5900" Subject: RE: Uart(lite)/ELDK 4.1 section mismatch -> ML403 Date: Wed, 19 Mar 2008 08:36:02 -0600 In-Reply-To: <2516330804619D4EA81F9AC9ACE9D874341E39@ADCSVR.adc.arcobel.nl> References: <2516330804619D4EA81F9AC9ACE9D874341E39@ADCSVR.adc.arcobel.nl> From: "John Linn" To: "Rob Schalken" , Message-Id: <20080319143615.2AFDC1AE81B9@mail73-dub.bigfish.com> List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C889CE.8F0A5900 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi Rob, =20 It sounds like your xparameters*.h with the #defines for the device addresses is right for the uart as the bootstrap loader is working. =20 I don't believe early boot works was my experience with it. =20 What messages did you see in the __log_bug as this is the best tool, is it booting all the way without a console or crashing during boot when it tries to start the console? =20 Make sure the #define XPAR_DDR_0_SIZE 0x4000000 is in the xparameters_ml403.h. It it's wrong the kernel will crash quickly based on my experience. =20 Xilinx has a git server that I have been working on updating, not sure how many changes there are in our git server as opposed to what you have. I have been testing arch/ppc with the ML405 which is the same as the ML403 except a larger FPGA, but my testing has been with the 550 UART as the default. I realize it's a tangent, but you can pull from our server if you want as I know the state of it (git://git.xilinx.com/linux-2.6-xlnx.git). =20 =20 Thanks John Linn =20 ________________________________ From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of Rob Schalken Sent: Wednesday, March 19, 2008 8:02 AM To: linuxppc-embedded@ozlabs.org Subject: Uart(lite)/ELDK 4.1 section mismatch -> ML403 =20 I want to Port the Linux 2.6.24.3 to the ML403 board. I tried some different configurations: =20 **UartLite After changing some defines and creating some symbolic link, the simple boot loader seems to Work. My kernel also starts because when I read the memory (using XMD), I could read the _log_buf and Some information was put in. I used the kernel command line: console=3DttyUL0 ip=3Doff root=3D/dev/ram rw. =20 But I did not get any kernel message on my serial console! When I enabled the early boot text over Serial port, the compiler gives some errors (gen550_init, RS_TABLE_SIZE, etc.)! =20 **16550 Uart After my disaster with the Uartlite, I started to use the 16550 uart. But I immediately get the following Error: arch/ppc/boot/common/ns16550.c:22: error: 'RS_TABLE_SIZE' undeclared here (not in a function) arch/ppc/boot/common/ns16550.c:24: error: 'SERIAL_PORT_DFNS' undeclared here (not in a function) make[2]: *** [arch/ppc/boot/common/ns16550.o] Error 1 make[1]: *** [arch/ppc/boot/common] Error 2 make: *** [zImage] Error 2 =20 I use ELDK 4.1 toolchain, which result in the following section mismatch (warning) WARNING: vmlinux.o(.text+0x223c): Section mismatch: reference to .init.text:earl y_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x2254): Section mismatch: reference to .init.text:mach ine_init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x2258): Section mismatch: reference to .init.text:MMU_ init (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x22b2): Section mismatch: reference to .init.text:star t_kernel (between 'start_here' and 'initial_mmu') WARNING: vmlinux.o(.text+0x22b6): Section mismatch: reference to .init.text:star t_kernel (between 'start_here' and 'initial_mmu') =20 By the way, the hardware is working, this has been tested!! =20 Could someone help to get a uart work! I only want to receive a message from the kernel!!!!=20 =20 =20 ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email=20 ______________________________________________________________________ ------_=_NextPart_001_01C889CE.8F0A5900 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi = Rob,

 

It sounds like your xparameters*.h = with the #defines for the device addresses is right for the uart as the bootstrap = loader is working.

 

I don’t believe early boot = works was my experience with it.

 

What messages did you see in the = __log_bug as this is the best tool, is it booting all the way without a console or crashing during boot when it tries to start the = console?

 

Make sure the #define = XPAR_DDR_0_SIZE 0x4000000 is in the xparameters_ml403.h. It it’s wrong the kernel = will crash quickly based on my experience.

 

Xilinx has a git server that I have = been working on updating, not sure how many changes there are in our git = server as opposed to what you have.  I have been testing arch/ppc with the = ML405 which is the same as the ML403 except a larger FPGA, but my testing has been with = the 550 UART as the default.  I realize it’s a tangent, but you = can pull from our server if you want as I know the state of it = (git://git.xilinx.com/linux-2.6-xlnx.git).  

 

Thanks

John = Linn

 

From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org] = On Behalf Of Rob Schalken
Sent: Wednesday, March = 19, 2008 8:02 AM
To: = linuxppc-embedded@ozlabs.org
Subject: Uart(lite)/ELDK = 4.1 section mismatch -> ML403

 

I want to Port the Linux 2.6.24.3 to the ML403 board.  I tried some different configurations:

 

**UartLite

After changing some defines and creating some symbolic link, the simple boot = loader seems to

Work. My kernel also starts because when I read the memory (using XMD), I = could read the _log_buf = and

Some information was put in. I used the kernel command line: console=3DttyUL0 = ip=3Doff root=3D/dev/ram rw. 

But I did not get any kernel message on my serial console! When I enabled = the early boot text over

Serial port, the compiler gives some errors (gen550_init, RS_TABLE_SIZE, = etc.)!

 

**16550 Uart

After my disaster with the Uartlite, I started to use the 16550 uart. But I immediately get the following

Error:

arch/ppc/boot/common/ns16550.c:22: error: = 'RS_TABLE_SIZE' undeclared here (not in a function)

arch/ppc/boot/common/ns16550.c:24: error: 'SERIAL_PORT_DFNS' undeclared here (not in a = function)

make[2]: *** [arch/ppc/boot/common/ns16550.o] = Error 1

make[1]: *** [arch/ppc/boot/common] Error = 2

make: *** [zImage] Error = 2

 

I use ELDK 4.1 toolchain, which result in the following section mismatch (warning)

WARNING: vmlinux.o(.text+0x223c): Section = mismatch: reference to .init.text:earl y_init (between 'start_here' and = 'initial_mmu')

WARNING: vmlinux.o(.text+0x2254): Section = mismatch: reference to .init.text:mach ine_init (between 'start_here' and = 'initial_mmu')

WARNING: vmlinux.o(.text+0x2258): Section = mismatch: reference to .init.text:MMU_ init (between 'start_here' and = 'initial_mmu')

WARNING: vmlinux.o(.text+0x22b2): Section = mismatch: reference to .init.text:star t_kernel (between 'start_here' and = 'initial_mmu')

WARNING: vmlinux.o(.text+0x22b6): Section = mismatch: reference to .init.text:star t_kernel (between 'start_here' and = 'initial_mmu')

 

By the way, the hardware is working, this has been = tested!!

 

Could someone help to get a uart work! I only want to receive a message from = the kernel!!!!

 

 


______________________________________________________________________ This email has been scanned by the MessageLabs Email Security = System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

------_=_NextPart_001_01C889CE.8F0A5900--