headers
Patil, Pankaj P. | 1 Mar 2006 01:41
Picon
Favicon

INIT:

Hi,
I am running u-boot & linux2.6.12 on a custom ppc board(functional HW).  I can get to the point where u-boot
loads the kernel, kernel does all the initialization,  loads the Root File System over NFS & calls the Init process.
Next, i am expecting to see a shell prompt. I am not sure where in the Init process i am failing. I have written
my own serial driver(Philips SC28L194 Quad UART--under development-possible culprit). The printks
work just fine.
All i see is the kernel calling the Init process & after a minute or so i see uart_close call.
The kernel runs just fine & responds to ping.
What can trigger a uart_close??(tty_release calls release_dev calls uart_close) I have a JTAG debugger.
What's the best way to debug once Init process is running??

I am attaching a dump of my console:
U-Boot 1.1.3 (Dec 16 2005 - 16:00:23), Build: 0.4.1

SysClock = 120Mhz , TClock = 120Mhz 
CPU:   MPC7447A v1.1  <at>  960 MHz
CPU bus mode : 60x

DRAM:  SPD Checksum ok!
-- DIMM1 has 2 banks
-- DIMM2 has 0 banks
ECC Initialization of Bank 0: Done
CAS Latency = 2 tRP = 3 tRAS = 6 tRCD=3
Total SDRAM memory is 1024 MB
Now running in RAM - U-Boot at: 00fc0000
Remapped Internal SRAM to 0xf2000000
Remapped Flash Card to 0xffc00000
FLASH:  4 MB
Addresses 32M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (32M - 16M): Done
(Continue reading)

Permalink | Reply | 0 comments |
headers
atul.sabharwal | 1 Mar 2006 02:03
Picon

RE: INIT:

Easy answer is do you have /dev/console in your file system.  Glibc
opens
/dev/console and the kernel uses /dev/ttyS0 as specified on the command
line.  There should not be any app calling uart_close as the console
deriver
should be opening it. 

--
Atul

Hi,
I am running u-boot & linux2.6.12 on a custom ppc board(functional HW).
I can get to the point where u-boot loads the kernel, kernel does all
the initialization,  loads the Root File System over NFS & calls the
Init process.
Next, i am expecting to see a shell prompt. I am not sure where in the
Init process i am failing. I have written my own serial driver(Philips
SC28L194 Quad UART--under development-possible culprit). The printks
work just fine.
All i see is the kernel calling the Init process & after a minute or so
i see uart_close call.
The kernel runs just fine & responds to ping.
What can trigger a uart_close??(tty_release calls release_dev calls
uart_close) I have a JTAG debugger. What's the best way to debug once
Init process is running??

I am attaching a dump of my console:
U-Boot 1.1.3 (Dec 16 2005 - 16:00:23), Build: 0.4.1

SysClock = 120Mhz , TClock = 120Mhz
(Continue reading)

Permalink | Reply | 0 comments |
headers
Laurent Lagrange | 1 Mar 2006 12:21

RE: Minor bug in file irq.h

Hello,

Here is a patch for the 2 bugs in irq.h.

This is the first time, I generate a patch.
I don't know if this is the right method.

Best regards
Laurent

>
> In the ./linux/include/asm-ppc/irq.h file, I encountered a problem with
the
> timer3 interrupt definition :
> #define     SIU_INT_TIMER3          ((uint)0x0e+CPM_IRQ_OFFSET)
>
> This definition generates a compilation error  because is interpreted as

Note that this is not the only such definition. At least this one  is
critical, too:

	#define SIU_INT_PC1             ((uint)0x3e+CPM_IRQ_OFFSET)

Best regards,

Wolfgang Denk

> -----Message d'origine-----
> De : Kumar Gala [mailto:galak <at> kernel.crashing.org]
> Envoye : mar. 28 fevrier 2006 15:38
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joyeau Sylvain | 1 Mar 2006 13:23

MPC85xx TSEC performance limits

Hi,

Does anybody already succeeded in getting full TX bandwidth on a TSEC
interface, transmitting 1500 bytes frames at netdev level (ie calling
directly dev_queue_xmit(skb)) for instance ?

With default Gianfar driver parameters, I can transmit only around
870Mb/s (while reception side is idle). The other TSEC interface is used
only to control a telnet terminal (~1Kb/s), the CPU is idle 60%,
6000irq/s.

I must decrease TX threshold value from 1024 to 128 to get 960Mb/s.

The problem is that decreasing the TX threshold under 512 bytes has a
dramatic side effect: the Gianfar driver generates "TX underrun" events
as soon as  I start, in parallel, a DMA transfer from memory to memory.
Rather disappointing behavior from a PQ3 <at> 825MHz :-(

Any idea how to get full TX bandwidth _without_ modifying this
parameter?

Thanks.

--
sylvain
Permalink | Reply | 1 comment |
headers
Bora KARTAL | 1 Mar 2006 13:54
Picon

MVME5100 Exception: Program (Illegal Instruction)

Hi,

I am trying to run linuxppc 2.4.20 with a nfs mounted root file system on a Motorolla MVME5100 board with a
PowerPC 7410 processor. When I used the default kernel ımage shıpped with MontaVista Linux
development kit, it boots up and works fine. But when I build up a custom kernel I am getting the following
exception during bootup.

Residual-Data Located at: $1FE9077C

Exception: Program (Illegal Instruction)

SRR0 =00005000 SRR1 =00083040 Vector-Offset =00700

IP =00005000 MSR =00003040 CR =00000000 FPSCR =00000000

R0 =00000000 R1 =1FE00000 R2 =00000000 R3 =1FE9077C

R4 =00005000 R5 =00000000 R6 =00000000 R7 =00000000

R8 =00000000 R9 =00000000 R10 =00000000 R11 =00000000

R12 =00000000 R13 =00000000 R14 =00000000 R15 =00000000

R16 =00000000 R17 =00000000 R18 =00000000 R19 =00000000

R20 =00000000 R21 =00000000 R22 =00000000 R23 =00000000

R24 =00000000 R25 =00000000 R26 =00000000 R27 =00000000

R28 =00000000 R29 =00000000 R30 =00000000 R31 =00000000
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pantelis Antoniou | 1 Mar 2006 16:25

Re: MPC85xx TSEC performance limits

On Wednesday 01 March 2006 14:23, Joyeau Sylvain wrote:
> Hi,
> 
> Does anybody already succeeded in getting full TX bandwidth on a TSEC
> interface, transmitting 1500 bytes frames at netdev level (ie calling
> directly dev_queue_xmit(skb)) for instance ?
> 
> With default Gianfar driver parameters, I can transmit only around
> 870Mb/s (while reception side is idle). The other TSEC interface is used
> only to control a telnet terminal (~1Kb/s), the CPU is idle 60%,
> 6000irq/s.
> 
> I must decrease TX threshold value from 1024 to 128 to get 960Mb/s.
> 
> The problem is that decreasing the TX threshold under 512 bytes has a
> dramatic side effect: the Gianfar driver generates "TX underrun" events
> as soon as  I start, in parallel, a DMA transfer from memory to memory.
> Rather disappointing behavior from a PQ3 <at> 825MHz :-(
> 
> Any idea how to get full TX bandwidth _without_ modifying this
> parameter?
> 
> Thanks.
> 
> --
> sylvain
>

I don't know 85xx in any great detail, but most QUICCs have a register
that controls the DMA bus arbitration priorities. Find it and give
(Continue reading)

Permalink | Reply | 0 comments |
headers
#LI JIANGGAN# | 1 Mar 2006 18:16
Picon

RE: boot failure on lite5200b board

how about the following U-boot settings:

..............................

Hit any key to stop autoboot:  0
=> printenv
baudrate=115200
autoload=no
ethact=FEC ETHERNET
ethaddr=00:01:9F:00:27:2F
preboot=echo; echo Autostarting. Press any key to abort..; echo
bootdelay=5
hostname=icecube
bootfile=MPC5200/uImage
nv=nfsroot root=/dev/nfs rw nfsroot=10.190.3.113:/opt/eldk/rootfs
netmask=255.255.240.0
ipaddr=10.190.3.144
serverip=10.190.3.103
bootcmd=run net_nfs
rootfs=root=/dev/nfs rw
netdev=eth0
rootpath=/opt/eldk-4-0/rootfs
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
ramargs=setenv bootargs root=/dev/ram rw
addip=setenv bootargs ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube:eth0:off panic=1
net_nfs=tftp 200000 MPC5200/uImage;run nfsargs addip;bootm
stdin=serial
stdout=serial
stderr=serial

Environment size: 738/65532 bytes
=>                                .
................................

The output is still the same, it hangs after displaying arch:exit

I have also tried the above settings with console set, it gives the same output

I am really wondering whether the problem is with the kernel. Sylvain's kernel uImage is only around 600k while the one from freescale is 1.4M, anybody knows where the difference is?

.....................................

Autostarting. Press any key to abort..

Hit any key to stop autoboot:  0
Using FEC ETHERNET device
TFTP from server 10.190.3.103; our IP address is 10.190.3.144
Filename 'MPC5200/uImage'.
Load address: 0x200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###################################
done
Bytes transferred = 1510143 (170aff hex)
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.11.7
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1510079 Bytes =  1.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
ocp: exit
arch: exit

.....................

Regards,

Jianggan LI


From: John Rigby [mailto:jcrigby <at> gmail.com]
Sent: Sat 2/25/2006 1:17
To: #LI JIANGGAN#
Cc: tnt <at> 246tnt.com; linuxppc-embedded <at> ozlabs.org
Subject: Re: boot failure on lite5200b board

I don't think your syntax for appending to an env variable is correct:

try:
set bootargs $(bootargs) ...appended stuff...
instead of:
set bootargs env bootargs ...appended stuff....

Also to see what bootargs is actually set to after all the nested
commands, add a printenv just before the bootm

On 2/23/06, #LI JIANGGAN# <lijianggan <at> pmail.ntu.edu.sg> wrote:
>
>
> I have actually tried both kernel with both console configurations. It gave
> the same output, thus I presume that the problem lies somewhere else. I
> attached the log to this email.
>
>  the board is Lite5200B Version 1.0. Which .config file do you want?
>
>  Sylvain, we have ordered a debugging set but we are still waiting for
> delivery, the leaking time is said to be one month, tant pis. And the log I
> attached here are booting from a higher address (0x500000).
>
>  My current u-boot args:
>  Autostarting. Press any key to abort..
>
>  Hit any key to stop autoboot:  0
>  => printenv
>  baudrate=115200
>  autoload=no
>  ethact=FEC ETHERNET
>  flshroot=root=/dev/mtdblock2 rw
>  ethaddr=00:01:9F:00:27:2F
>  preboot=echo; echo Autostarting. Press any key to abort..; echo
>  bootdelay=5
>  hostname=icecube
>  bootfile=MPC5200/uImage
>  nv=nfsroot root=/dev/nfs rw nfsroot=10.190.3.113:/opt/eldk/rootfs
>  ip=ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::off
>  nfsroot=root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
>  bootcmd=run net_nfs
>  filesize=546
>  fileaddr=500000
>  netmask=255.255.240.0
>  ipaddr=10.190.3.144
>  serverip=10.190.3.103
>  setconsole=setenv bootargs console=ttyPSC0, 115200n8 console=tty1
>  rootfs=root=/dev/nfs rw nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
>  bootargs=env bootargs root=/dev/nfs rw
> nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
> ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::off
>  flash_nfs=run setconsole nfsargs addip;bootm
>  net_nfs=tftp 500000 MPC5200/uImage;run setconsole nfsargs addip;bootm
>  nfsargs=setenv bootargs env bootargs root=/dev/nfs rw
> nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
> ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::offroot=/dev/nfs
> rw
>  addip=setenv bootargs env bootargs root=/dev/nfs rw
> nfsroot=10.190.3.103:/opt/eldk-4-0/rootfs
> ip=10.190.3.144:10.190.3.103:10.190.3.103:255.255.240.0:icecube::off
>  ramargs=setenv bootargs root=/dev/ram rw
>  console=console=ttyS0,115200n8 console=tty1
>  stdin=serial
>  stdout=serial
>  stderr=serial
>
>  Environment size: 1472/65532 bytes
>  =>
>
>
>
>
>  USING Sylvain's KERNEL:
>
>  U-Boot 1.1.3 (Feb  6 2006 - 09:56:46)
>
>  CPU:   MPC5200 v2.2 at 462 MHz
>         Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
>  Board: Freescale MPC5200 (Lite5200B)
>  I2C:   85 kHz, ready
>  DRAM:  256 MB
>  FLASH: 32 MB
>  PCI:   Bus Dev VenId DevId Class Int
>          00  1a  1057  5809  0680  00
>  In:    serial
>  Out:   serial
>  Err:   serial
>  Net:   FEC ETHERNET
>  IDE:   Bus 0: OK
>    Device 0: not available
>    Device 1: not available
>
>  Autostarting. Press any key to abort..
>
>  Hit any key to stop autoboot:  0
>  Using FEC ETHERNET device
>  TFTP from server 10.190.3.103; our IP address is 10.190.3.144
>  Filename 'MPC5200/uImage'.
>  Load address: 0x500000
>  Loading: #################################################################
>           ################################################################
>  done
>  Bytes transferred = 658114 (a0ac2 hex)
>  ## Booting image at 00500000 ...
>     Image Name:   Linux-2.6.16-rc1
>     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>     Data Size:    658050 Bytes = 642.6 kB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
>  id mach(): done
>  MMU:enter
>  MMU:hw init
>  MMU:mapin
>  MMU:setio
>  MMU:exit
>  setup_arch: enter
>  setup_arch: bootmem
>  arch: exit
>
>
>
>  USING KERNEL FROM Freescale:
>
>  U-Boot 1.1.3 (Feb  6 2006 - 09:56:46)
>
>  CPU:   MPC5200 v2.2 at 462 MHz
>         Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
>  Board: Freescale MPC5200 (Lite5200B)
>  I2C:   85 kHz, ready
>  DRAM:  256 MB
>  FLASH: 32 MB
>  PCI:   Bus Dev VenId DevId Class Int
>          00  1a  1057  5809  0680  00
>  In:    serial
>  Out:   serial
>  Err:   serial
>  Net:   FEC ETHERNET
>  IDE:   Bus 0: OK
>    Device 0: not available
>    Device 1: not available
>
>  Autostarting. Press any key to abort..
>
>  Hit any key to stop autoboot:  0
>  Using FEC ETHERNET device
>  TFTP from server 10.190.3.103; our IP address is 10.190.3.144
>  Filename 'MPC5200/uImage'.
>  Load address: 0x500000
>  Loading: #################################################################
>           #################################################################
>           #################################################################
>           #################################################################
>           ###################################
>  done
>  Bytes transferred = 1510143 (170aff hex)
>  ## Booting image at 00500000 ...
>     Image Name:   Linux-2.6.11.7
>     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>     Data Size:    1510079 Bytes =  1.4 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
>  id mach(): done
>  MMU:enter
>  MMU:hw init
>  MMU:mapin
>  MMU:setio
>  MMU:exit
>  setup_arch: enter
>  setup_arch: bootmem
>  ocp: exit
>  arch: exit
>
>
>
>
>  -----Original Message-----
>  From: John Rigby [mailto:jcrigby <at> gmail.com]
>  Sent: Fri 2/24/2006 0:18
>  To: #LI JIANGGAN#
>  Subject: Re: boot failure on lite5200b board
>
>  If you are using Sylvain's kernel you need to set console=ttyPSC0.  If you
> are
>  using a kernel from Freescale then you need to set console=ttyS0.
>
>  Also what rev of the board do you have?
>
>
>
>  On 2/23/06, #LI JIANGGAN# <lijianggan <at> pmail.ntu.edu.sg> wrote:
>  >
>  >
>  > Thank you José María and Andrey for your advices, however the problem
>  > remains. I've tried setting the console (though I remember that our
> previous
>  > lite5200 board was working fine on kernel 2.4 without setting the
> console);
>  > meantime, I've set the booting image to 0x500000; I have also tried using
>  > the kernel image come together with the BSP, it's always the same error.
>  >
>  >  Sylvain, I've actually using your kernel source, the compiled image is
>  > around 700k (compared to the 1.4M image from the BSP), but it doesn't
> solve
>  > the problem. So I presume that the problem is lying somewhere else.
>  >
>  >  A SNAPSHOT OF THE BOOTING MESSAGES:
>  >
>  >
>  >  U-Boot 1.1.3 (Feb  6 2006 - 09:56:46)
>  >
>  >  CPU:   MPC5200 v2.2 at 462 MHz
>  >         Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
>  >  Board: Freescale MPC5200 (Lite5200B)
>  >  I2C:   85 kHz, ready
>  >  DRAM:  256 MB
>  >  FLASH: 32 MB
>  >  PCI:   Bus Dev VenId DevId Class Int
>  >          00  1a  1057  5809  0680  00
>  >  In:    serial
>  >  Out:   serial
>  >  Err:   serial
>  >  Net:   FEC ETHERNET
>  >  IDE:   Bus 0: OK
>  >    Device 0: not available
>  >    Device 1: not available
>  >
>  >  Autostarting. Press any key to abort..
>  >
>  >  Hit any key to stop autoboot:  0
>  >  Using FEC ETHERNET device
>  >  TFTP from server 10.190.3.103; our IP address is 10.190.3.144
>  >  Filename 'MPC5200/uImage'.
>  >  Load address: 0x100000
>  >  Loading:
>  > #################################################################
>  >
>  > ################################################################
>  >  done
>  >  Bytes transferred = 658114 (a0ac2 hex)
>  >  ## Booting image at 00100000 ...
>  >     Image Name:   Linux-2.6.16-rc1
>  >     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>  >     Data Size:    658050 Bytes = 642.6 kB
>  >     Load Address: 00000000
>  >     Entry Point:  00000000
>  >     Verifying Checksum ... OK
>  >     Uncompressing Kernel Image ... OK
>  >  id mach(): done
>  >  MMU:enter
>  >  MMU:hw init
>  >  MMU:mapin
>  >  MMU:setio
>  >  MMU:exit
>  >  setup_arch: enter
>  >  setup_arch: bootmem
>  >  arch: exit
>  >
>  >
>  >  I am wondering whether it's a kernel problem or more likely to be a
> problem
>  > lying with the U-boot. It seems to hang when executing setup_arch()
>  > function, or maybe there is sth else behind the wall?
>  >
>  >  Regards,
>  >  Jianggan LI
>  >
>  >
>  >
>  >
>  >  -----Original Message-----
>  >  From: Sylvain Munaut [mailto:tnt <at> 246tNt.com]
>  >  Sent: Thu 2/23/2006 15:38
>  >  To: #LI JIANGGAN#
>  >  Cc: linuxppc-embedded <at> ozlabs.org
>  >  Subject: Re: boot failure on lite5200b board
>  >
>  >  #LI JIANGGAN# wrote:
>  >  > Hello all,
>  >  >
>  >  > For my end-of-study project, I am working on an embedded system with
>  >  > reference of freescale's lite5200b reference board. I was trying to
> boot
>  >  > Linux 2.6.15 on the board (with the fec and bestcomm corrected).
> however
>  >  > the booting was stuck at the following stage:
>  >
>  >  In addition to what has already been said (use a higher address for the
>  >  image and don't forget console=ttyPSC0 in kernel command line), make
>  >  sure you use the kernel from my git tree, it contains a few patches from
>  >  John Rigby to add support for the lite5200b.
>  >
>  >  Please report if it works, I've not been able to test those myself since
>  >  i'm still on lite5200.
>  >
>  >
>  >          Sylvain
>  >
>  >
>  >
>  >
>  >
>  >
>  > _______________________________________________
>  > Linuxppc-embedded mailing list
>  > Linuxppc-embedded <at> ozlabs.org
>  > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>  >
>  >
>
>
>
>
>

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded <at> ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Permalink | Reply | 4 comments |
headers
Wade Farnsworth | 2 Mar 2006 00:45

Re: [PATCH 1/6] Support for UART 2 on 440SP and Luan

This fixes the IRQ number for UART 2 on the 440SP and adds support to
ibm440gx_get_clocks() for it.  It also enables the UART on the Luan.

--Wade

Signed off by: Wade Farnsworth <wfarnsworth <at> mvista.com>
Attachment (luan-uart2.patch): text/x-patch, 2731 bytes
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded <at> ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Permalink | Reply | 5 comments |
headers
Wade Farnsworth | 2 Mar 2006 00:47

Re: [PATCH 2/6] Add UIC settings for 440SP & Luan

This adds the necessary structures for the UIC polarity and triggering
on the 440SP & Luan.

-Wade

Signed off by: Wade Farnsworth <wfarnsworth <at> mvista.com>
Attachment (luan-uic.patch): text/x-patch, 1590 bytes
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded <at> ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Permalink | Reply | 4 comments |
headers
Wade Farnsworth | 2 Mar 2006 00:50

Re: [PATCH 3/6] PCIX fixes and enhancements for 440SP & Luan

This patch allows each bridge on the 440SP to be configured for both
host and adapter mode.  Previously, PCIX0 was configured for adapter
mode only.

Also fixes PCIXn_IO_BASE for PCIX1 and 2.

Signed off by: Wade Farnsworth <wfarnsworth <at> mvista.com>
Attachment (luan-pcix.patch): text/x-patch, 4304 bytes
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded <at> ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Permalink | Reply | 3 comments |

Gmane