No ttyS device at I/O port 0xfe004500 for console

No ttyS device at I/O port 0xfe004500 for console

[Alex Zeffertt]

Hi list,

I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based board.  Through
some experimentation I have found I need "console=uart,io,0xfe004500"
in the kernel command line in order to get any output over the serial
port.

Half way through initialisation the kernel appears to swap from its "early"
8250 serial driver to a "full" 8250 serial driver.  At this point it prints
"No ttyS device at I/O port 0xfe004500 for console" and there is no
further output.

Does anyone have any idea what I may be doing wrong?

BTW, here's the output that I do get.

-------------------/snip--------------------------
U-Boot 1.1.3 (FSL Development) (Jun 13 2006 - 14:01:25) MPC83XX

Clock configuration:
   Coherent System Bus:  132 MHz
   Core:                 264 MHz
   QE:                   198 MHz
   Local Bus Controller: 132 MHz
   Local Bus:             66 MHz
   DDR:                  264 MHz
   SEC:                  132 MHz
   I2C1:                 132 MHz
CPU: MPC8323E, Rev: 10 at 264 MHz
Board: Freescale MPC832XEPB
I2C:   ready
DRAM:
    DDR RAM: 128 MB
FLASH: 16 MB
In:    serial
Out:   serial
Err:   serial
Net:   FSL GETH0
Hit any key to stop autoboot:  0
geth: PHY is Davicom DM9161A (181b8a0)
FSL GETH0: Full Duplex
FSL GETH0: Speed 100BT
FSL GETH0: Link is up
Using FSL GETH0 device
TFTP from server 10.0.0.107; our IP address is 10.0.6.65
Filename 'uImage'.
Load address: 0x200000
Loading: #################################################################
          #################################################################
          #################################################################
          ##########
done
Bytes transferred = 1046491 (ff7db hex)
## Booting image at 00200000 ...
    Image Name:   Linux-2.6.11
    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
    Data Size:    1046427 Bytes = 1021.9 kB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
Linux version 2.6.11 (ajz@zambia) (gcc version 3.4.3) #5 Tue Jun 13 17:36:46 BST 2006
Built 1 zonelists
Kernel command line: root=/dev/nfs rw nfsroot=10.0.0.107:/opt/eldk/ppc_6xx ip=10.0.6.65:10.0.0.107:10.0.0.1:255.255.0.0:eth0:off console=uart,io,0xfe004500
IPIC (128 IRQ sources, 8 External IRQs) at fe000700
QE IC (64 IRQ sources) at fe100080
PID hash table entries: 1024 (order: 10, 16384 bytes)
Early serial console at I/O port 0xfe004500 (options '134')
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 127488k available (1724k kernel code, 432k data, 100k init, 0k highmem)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
NET: Registered protocol family 16
SCSI subsystem initialized
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
MPC832XE MDS flash device: 1000000 at ff000000 Partition number 5
MPC832XE PB Flash Map Info: Found 1 x16 devices at 0x0 in 16-bit bank
  Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Creating 5 MTD partitions on "MPC832XE PB Flash Map Info":
0x00000000-0x00020000 : "HRCW"
0x00020000-0x00900000 : "JFFS2"
0x00900000-0x00d00000 : "Ramdisk"
0x00d00000-0x00f00000 : "Kernel"
0x00f00000-0x01000000 : "U-Boot"
MPC832XE MDS flash device initialized
i2c /dev entries driver
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
No ttyS device at I/O port 0xfe004500 for console

-------------------/snip--------------------------



TIA,

Alex

Re: No ttyS device at I/O port 0xfe004500 for console

[Kumar Gala]

On Jun 13, 2006, at 11:48 AM, Alex Zeffertt wrote:

> Hi list,
>
> I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based board.   
> Through
> some experimentation I have found I need "console=uart,io,0xfe004500"
> in the kernel command line in order to get any output over the serial
> port.
>
> Half way through initialisation the kernel appears to swap from its  
> "early"
> 8250 serial driver to a "full" 8250 serial driver.  At this point  
> it prints
> "No ttyS device at I/O port 0xfe004500 for console" and there is no
> further output.
>
> Does anyone have any idea what I may be doing wrong?
>
> BTW, here's the output that I do get.

Alex, where did you get this 2.6.11 kernel?  The public tree didn't  
have support for 83xx in 2.6.11.  I'd suggest looking at using  
something newer like 2.6.16 and see if you have the same issue.

- k

>
> -------------------/snip--------------------------
> U-Boot 1.1.3 (FSL Development) (Jun 13 2006 - 14:01:25) MPC83XX
>
> Clock configuration:
>    Coherent System Bus:  132 MHz
>    Core:                 264 MHz
>    QE:                   198 MHz
>    Local Bus Controller: 132 MHz
>    Local Bus:             66 MHz
>    DDR:                  264 MHz
>    SEC:                  132 MHz
>    I2C1:                 132 MHz
> CPU: MPC8323E, Rev: 10 at 264 MHz
> Board: Freescale MPC832XEPB
> I2C:   ready
> DRAM:
>     DDR RAM: 128 MB
> FLASH: 16 MB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   FSL GETH0
> Hit any key to stop autoboot:  0
> geth: PHY is Davicom DM9161A (181b8a0)
> FSL GETH0: Full Duplex
> FSL GETH0: Speed 100BT
> FSL GETH0: Link is up
> Using FSL GETH0 device
> TFTP from server 10.0.0.107; our IP address is 10.0.6.65
> Filename 'uImage'.
> Load address: 0x200000
> Loading:  
> #################################################################
>            
> #################################################################
>            
> #################################################################
>           ##########
> done
> Bytes transferred = 1046491 (ff7db hex)
> ## Booting image at 00200000 ...
>     Image Name:   Linux-2.6.11
>     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>     Data Size:    1046427 Bytes = 1021.9 kB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
> Linux version 2.6.11 (ajz@zambia) (gcc version 3.4.3) #5 Tue Jun 13  
> 17:36:46 BST 2006
> Built 1 zonelists
> Kernel command line: root=/dev/nfs rw nfsroot=10.0.0.107:/opt/eldk/ 
> ppc_6xx ip=10.0.6.65:10.0.0.107:10.0.0.1:255.255.0.0:eth0:off  
> console=uart,io,0xfe004500
> IPIC (128 IRQ sources, 8 External IRQs) at fe000700
> QE IC (64 IRQ sources) at fe100080
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Early serial console at I/O port 0xfe004500 (options '134')
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 127488k available (1724k kernel code, 432k data, 100k init,  
> 0k highmem)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> NET: Registered protocol family 16
> SCSI subsystem initialized
> JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
> Generic RTC Driver v1.07
> Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing  
> disabled
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
> loop: loaded (max 8 devices)
> MPC832XE MDS flash device: 1000000 at ff000000 Partition number 5
> MPC832XE PB Flash Map Info: Found 1 x16 devices at 0x0 in 16-bit bank
>   Intel/Sharp Extended Query Table at 0x0031
> Using buffer write method
> cfi_cmdset_0001: Erase suspend on write enabled
> Creating 5 MTD partitions on "MPC832XE PB Flash Map Info":
> 0x00000000-0x00020000 : "HRCW"
> 0x00020000-0x00900000 : "JFFS2"
> 0x00900000-0x00d00000 : "Ramdisk"
> 0x00d00000-0x00f00000 : "Kernel"
> 0x00f00000-0x01000000 : "U-Boot"
> MPC832XE MDS flash device initialized
> i2c /dev entries driver
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> No ttyS device at I/O port 0xfe004500 for console
>
> -------------------/snip--------------------------
>
>
>
> TIA,
>
> Alex
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: No ttyS device at I/O port 0xfe004500 for console

[Joakim Tjernlund]

> On Jun 13, 2006, at 11:48 AM, Alex Zeffertt wrote:
> 
> > Hi list,
> >
> > I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based 
> board.   
> > Through
> > some experimentation I have found I need 
> "console=uart,io,0xfe004500"
> > in the kernel command line in order to get any output over 
> the serial 
> > port.
> >
> > Half way through initialisation the kernel appears to swap from its 
> > "early"
> > 8250 serial driver to a "full" 8250 serial driver.  At this 
> point it 
> > prints "No ttyS device at I/O port 0xfe004500 for console" 
> and there 
> > is no further output.
> >
> > Does anyone have any idea what I may be doing wrong?
> >
> > BTW, here's the output that I do get.
> 
> Alex, where did you get this 2.6.11 kernel?  The public tree 
> didn't have support for 83xx in 2.6.11.  I'd suggest looking 
> at using something newer like 2.6.16 and see if you have the 
> same issue.

I suspect he got from the same place I did, freescales LTIB dev. env.
which has been patched to support 832x. I am having the same problem as he
has, any info on what the problem might be would be great.

Also, if anyone has any info on when these patches will be sent upstream, I 
sure would like to hear about it.

 Jocke

RE: No ttyS device at I/O port 0xfe004500 for console

[Chuck Meade]

> > On Jun 13, 2006, at 11:48 AM, Alex Zeffertt wrote:
> > 
> > > Hi list,
> > >
> > > I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based 
> > board.   
> > > Through
> > > some experimentation I have found I need 
> > "console=uart,io,0xfe004500"
> > > in the kernel command line in order to get any output over 
> > the serial 
> > > port.
> > >
> > > Half way through initialisation the kernel appears to swap from its 
> > > "early"
> > > 8250 serial driver to a "full" 8250 serial driver.  At this 
> > point it 
> > > prints "No ttyS device at I/O port 0xfe004500 for console" 
> > and there 
> > > is no further output.
> > >
> > > Does anyone have any idea what I may be doing wrong?
> > >
> > > BTW, here's the output that I do get.
> > 
> > Alex, where did you get this 2.6.11 kernel?  The public tree 
> > didn't have support for 83xx in 2.6.11.  I'd suggest looking 
> > at using something newer like 2.6.16 and see if you have the 
> > same issue.
> 
> I suspect he got from the same place I did, freescales LTIB dev. env.
> which has been patched to support 832x. I am having the same problem as he
> has, any info on what the problem might be would be great.
> 
> Also, if anyone has any info on when these patches will be sent upstream, I 
> sure would like to hear about it.
> 
>  Jocke

Hi Joakim,

Same here -- go into arch/ppc/platforms/83xx and edit file mpc83xx_sys.c.
If you are using the 8323e cpu, then you need to make sure that file has
code to support the 8323E.  Mine didn't, so I got no platform devices 
initialized (no serial port, no Eth devs).  I added a block of code to support
the 8323E (set mask to 0xffff0000 and "value" to 0x80620000, then the 
device list for the 8323E).  Use existing code there as a guide, it was not
difficult once I figured out that this was the problem.

If you are using a newer LTIB release than me, perhaps yours is fixed.
The one I have is from 3/15/06.

Anyway, this works fine for me and addresses the problem of the platform
devs not getting initialized.

Chuck

RE: No ttyS device at I/O port 0xfe004500 for console

[Joakim Tjernlund]

> > 
> > I suspect he got from the same place I did, freescales LTIB 
> dev. env.
> > which has been patched to support 832x. I am having the 
> same problem 
> > as he has, any info on what the problem might be would be great.
> > 
> > Also, if anyone has any info on when these patches will be sent 
> > upstream, I sure would like to hear about it.
> > 
> >  Jocke
> 
> Hi Joakim,
> 
> Same here -- go into arch/ppc/platforms/83xx and edit file 
> mpc83xx_sys.c.
> If you are using the 8323e cpu, then you need to make sure

Yes, got one of those.
 
> that file has code to support the 8323E.  Mine didn't, so I 
> got no platform devices initialized (no serial port, no Eth 
> devs).  I added a block of code to support the 8323E (set 
> mask to 0xffff0000 and "value" to 0x80620000, then the device 
> list for the 8323E).  Use existing code there as a guide, it 
> was not difficult once I figured out that this was the problem.

hmm, you don't have a patch handy?

> 
> If you are using a newer LTIB release than me, perhaps yours is fixed.
> The one I have is from 3/15/06.

Me too, I have requested that freescale release a new LTIB with proper support,
but who knows when the will be.

> 
> Anyway, this works fine for me and addresses the problem of 
> the platform devs not getting initialized.
> 
> Chuck
> 
> 
> 

RE: No ttyS device at I/O port 0xfe004500 for console

[Chuck Meade]

> > Hi Joakim,
> > 
> > Same here -- go into arch/ppc/platforms/83xx and edit file 
> > mpc83xx_sys.c.
> > If you are using the 8323e cpu, then you need to make sure
> 
> Yes, got one of those.
>  
> > that file has code to support the 8323E.  Mine didn't, so I 
> > got no platform devices initialized (no serial port, no Eth 
> > devs).  I added a block of code to support the 8323E (set 
> > mask to 0xffff0000 and "value" to 0x80620000, then the device 
> > list for the 8323E).  Use existing code there as a guide, it 
> > was not difficult once I figured out that this was the problem.
> 
> hmm, you don't have a patch handy?

Here you go:

--- mpc83xx_sys.c-ORIG	2006-06-13 17:54:36.577339832 -0400
+++ mpc83xx_sys.c	2006-06-13 17:56:02.394293672 -0400
@@ -136,6 +136,23 @@ struct ppc_sys_spec ppc_sys_specs[] = {
 #endif
 		},
 	},
+	{
+		.ppc_sys_name	= "8323E",
+		.mask		= 0xFFFF0000,
+		.value		= 0x80620000,
+#ifdef CONFIG_QE
+		.num_devices	= 4,
+#else
+		.num_devices	= 2,
+#endif
+		.device_list	= (enum ppc_sys_devices[])
+		{
+			MPC83xx_IIC1, MPC83xx_DUART,
+#ifdef CONFIG_QE
+			MPC83xx_QE_UCC3, MPC83xx_QE_UCC4,
+#endif
+		},
+	},
 	{	/* default match */
 		.ppc_sys_name	= "",
 		.mask 		= 0x00000000,


Regards,
Chuck

Re: No ttyS device at I/O port 0xfe004500 for console

[Kumar Gala]

> Here you go:

Let me know if this fixes the issues you guys are seeing with your  
83xx boards.  If so, I'll clean up this patch and push it upstream.

- k

> --- mpc83xx_sys.c-ORIG	2006-06-13 17:54:36.577339832 -0400
> +++ mpc83xx_sys.c	2006-06-13 17:56:02.394293672 -0400
> @@ -136,6 +136,23 @@ struct ppc_sys_spec ppc_sys_specs[] = {
>  #endif
>  		},
>  	},
> +	{
> +		.ppc_sys_name	= "8323E",
> +		.mask		= 0xFFFF0000,
> +		.value		= 0x80620000,
> +#ifdef CONFIG_QE
> +		.num_devices	= 4,
> +#else
> +		.num_devices	= 2,
> +#endif
> +		.device_list	= (enum ppc_sys_devices[])
> +		{
> +			MPC83xx_IIC1, MPC83xx_DUART,
> +#ifdef CONFIG_QE
> +			MPC83xx_QE_UCC3, MPC83xx_QE_UCC4,
> +#endif
> +		},
> +	},
>  	{	/* default match */
>  		.ppc_sys_name	= "",
>  		.mask 		= 0x00000000,
>
>
> Regards,
> Chuck
>

Re: No ttyS device at I/O port 0xfe004500 for console

[Alex Zeffertt]

Kumar Gala wrote:
>> Here you go:
> 
> Let me know if this fixes the issues you guys are seeing with your 83xx 
> boards.  If so, I'll clean up this patch and push it upstream.
> 
> - k


Great, thank you!

Your patch and the params "console=uart,io,0xfe004500 console=ttyS0" in
the kernel command line do the trick.

Alex



> 
>> --- mpc83xx_sys.c-ORIG    2006-06-13 17:54:36.577339832 -0400
>> +++ mpc83xx_sys.c    2006-06-13 17:56:02.394293672 -0400
>> @@ -136,6 +136,23 @@ struct ppc_sys_spec ppc_sys_specs[] = {
>>  #endif
>>          },
>>      },
>> +    {
>> +        .ppc_sys_name    = "8323E",
>> +        .mask        = 0xFFFF0000,
>> +        .value        = 0x80620000,
>> +#ifdef CONFIG_QE
>> +        .num_devices    = 4,
>> +#else
>> +        .num_devices    = 2,
>> +#endif
>> +        .device_list    = (enum ppc_sys_devices[])
>> +        {
>> +            MPC83xx_IIC1, MPC83xx_DUART,
>> +#ifdef CONFIG_QE
>> +            MPC83xx_QE_UCC3, MPC83xx_QE_UCC4,
>> +#endif
>> +        },
>> +    },
>>      {    /* default match */
>>          .ppc_sys_name    = "",
>>          .mask         = 0x00000000,
>>
>>
>> Regards,
>> Chuck
>>
> 

RE: No ttyS device at I/O port 0xfe004500 for console

[Joakim Tjernlund]

Hi Chuck

> 
> > > Hi Joakim,
> > > 
> > > Same here -- go into arch/ppc/platforms/83xx and edit file 
> > > mpc83xx_sys.c.
> > > If you are using the 8323e cpu, then you need to make sure
> > 
> > Yes, got one of those.
> >  
> > > that file has code to support the 8323E.  Mine didn't, so 
> I got no 
> > > platform devices initialized (no serial port, no Eth 
> devs).  I added 
> > > a block of code to support the 8323E (set mask to 0xffff0000 and 
> > > "value" to 0x80620000, then the device list for the 8323E).  Use 
> > > existing code there as a guide, it was not difficult once 
> I figured 
> > > out that this was the problem.
> > 
> > hmm, you don't have a patch handy?
> 
> Here you go:

Thanks, now it boot into the ramdisk and a get a login prompt and all, but I don't
see any output during kernel startup(only a few garbage chars).
Tried the console params Alex sent but makes no difference. How does
your cmdline look like?

RE: No ttyS device at I/O port 0xfe004500 for console

[Joakim Tjernlund]

 
> 
> Hi Chuck
> 
> > 
> > > > Hi Joakim,
> > > > 
> > > > Same here -- go into arch/ppc/platforms/83xx and edit file 
> > > > mpc83xx_sys.c.
> > > > If you are using the 8323e cpu, then you need to make sure
> > > 
> > > Yes, got one of those.
> > >  
> > > > that file has code to support the 8323E.  Mine didn't, so
> > I got no
> > > > platform devices initialized (no serial port, no Eth
> > devs).  I added
> > > > a block of code to support the 8323E (set mask to 
> 0xffff0000 and 
> > > > "value" to 0x80620000, then the device list for the 
> 8323E).  Use 
> > > > existing code there as a guide, it was not difficult once
> > I figured
> > > > out that this was the problem.
> > > 
> > > hmm, you don't have a patch handy?
> > 
> > Here you go:
> 
> Thanks, now it boot into the ramdisk and a get a login prompt 
> and all, but I don't see any output during kernel 
> startup(only a few garbage chars).
> Tried the console params Alex sent but makes no difference. 
> How does your cmdline look like?

ahem, I forgot the obvious console=ttyS0. Now it works, thanks a lot

 Jocke

RE: No ttyS device at I/O port 0xfe004500 for console

[Chuck Meade]

Hi Joakim,

> > > Here you go:
> > 
> > Thanks, now it boot into the ramdisk and a get a login prompt 
> > and all, but I don't see any output during kernel 
> > startup(only a few garbage chars).
> > Tried the console params Alex sent but makes no difference. 
> > How does your cmdline look like?
> 
> ahem, I forgot the obvious console=ttyS0. Now it works, thanks a lot

Sure no problem.

Chuck

Re: No ttyS device at I/O port 0xfe004500 for console

[Alex Zeffertt]

Kumar Gala wrote:
> 
> On Jun 13, 2006, at 11:48 AM, Alex Zeffertt wrote:
> 
>> Hi list,
>>
>> I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based board.  
>> Through
>> some experimentation I have found I need "console=uart,io,0xfe004500"
>> in the kernel command line in order to get any output over the serial
>> port.
>>
>> Half way through initialisation the kernel appears to swap from its 
>> "early"
>> 8250 serial driver to a "full" 8250 serial driver.  At this point it 
>> prints
>> "No ttyS device at I/O port 0xfe004500 for console" and there is no
>> further output.
>>
>> Does anyone have any idea what I may be doing wrong?
>>
>> BTW, here's the output that I do get.
> 
> Alex, where did you get this 2.6.11 kernel?  The public tree didn't have 
> support for 83xx in 2.6.11.  I'd suggest looking at using something 
> newer like 2.6.16 and see if you have the same issue.
> 
> - k

Hi Kumar, I got it from Freescale's MPC8323EMDS linux BSP.

As far as I am aware this is the only source which has support for this
board.  (Hopefully they will eventually upstream their changes!)

I'll have a look at 2.6.11 and see whether it is feasable to port
the board support to it.

Thanks,

Alex

RE: No ttyS device at I/O port 0xfe004500 for console

[Joakim Tjernlund]

 

> -----Original Message-----
> From: 
> linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se@ozlabs.
> org 
> [mailto:linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se
> @ozlabs.org] On Behalf Of Alex Zeffertt
> Sent: den 13 juni 2006 18:48
> To: linuxppc-embedded@ozlabs.org
> Subject: No ttyS device at I/O port 0xfe004500 for console
> 
> Hi list,
> 
> I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based 
> board.  Through some experimentation I have found I need 
> "console=uart,io,0xfe004500"
> in the kernel command line in order to get any output over 
> the serial port.

Alex, can you post your complete u-boot env(printenv). I am trying to do
the same as you but I havn't gotten any output yet. I managed to wipe my
u-boot & u-boot env and the docs arent that great :(

 Jocke

Re: No ttyS device at I/O port 0xfe004500 for console

[Alex Zeffertt]

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

Joakim Tjernlund wrote:
>  
> 
>> -----Original Message-----
>> From: 
>> linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se@ozlabs.
>> org 
>> [mailto:linuxppc-embedded-bounces+joakim.tjernlund=lumentis.se
>> @ozlabs.org] On Behalf Of Alex Zeffertt
>> Sent: den 13 juni 2006 18:48
>> To: linuxppc-embedded@ozlabs.org
>> Subject: No ttyS device at I/O port 0xfe004500 for console
>>
>> Hi list,
>>
>> I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based 
>> board.  Through some experimentation I have found I need 
>> "console=uart,io,0xfe004500"
>> in the kernel command line in order to get any output over 
>> the serial port.
> 
> Alex, can you post your complete u-boot env(printenv). I am trying to do
> the same as you but I havn't gotten any output yet. I managed to wipe my
> u-boot & u-boot env and the docs arent that great :(
> 
>  Jocke
> 

No problem.

I just had to try absolutely *every* possible option for the console parameter.
Eventually this worked (for the early serial output only, not for /dev/console
output.)

See attached for my u-boot environment

Alex



[-- Attachment #2: u-boot.log --]
[-- Type: text/plain, Size: 1470 bytes --]

U-Boot 1.1.3 (FSL Development) (Jun 13 2006 - 14:01:25) MPC83XX
 
Clock configuration:
  Coherent System Bus:  132 MHz
  Core:                 264 MHz
  QE:                   198 MHz
  Local Bus Controller: 132 MHz
  Local Bus:             66 MHz
  DDR:                  264 MHz
  SEC:                  132 MHz
  I2C1:                 132 MHz
CPU: MPC8323E, Rev: 10 at 264 MHz
Board: Freescale MPC832XEPB
I2C:   ready
DRAM:
   DDR RAM: 128 MB
FLASH: 16 MB
In:    serial
Out:   serial
Err:   serial
Net:   FSL GETH0
Hit any key to stop autoboot:  0
=> printenv
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;bootm $loadaddr $ramdiskaddr
bootdelay=6
loads_echo=1
loadaddr=200000
netdev=eth0
ramdiskaddr=400000
ramdiskfile=ramfs.83xx
ethact=FSL GETH0
ethaddr=00:04:9f:00:00:00
ipaddr=10.0.6.65
netmask=255.255.0.0
serverip=10.0.0.107
gatewayip=10.0.0.1
rootpath=/opt/eldk/ppc_6xx
bootfile=uImage
baudrate=9600
consoledev=uart,io,0xfe004500
bootargs=root=/dev/nfs rw nfsroot=10.0.0.107:/opt/eldk/ppc_6xx ip=10.0.6.65:10.0.0.107:10.0.0.1:255.255.0.0:eth0:off console=uart,io,0xfe004500
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$netdev:off console=$consoledev $othbootargs;tftp $loadaddr $bootfile;bootm $loadaddr
bootcmd=run nfsboot
stdin=serial
stdout=serial
stderr=serial
 
Environment size: 871/8188 bytes
=>

RE: No ttyS device at I/O port 0xfe004500 for console

[Joakim Tjernlund]

=20
> Kumar Gala wrote:
> >> Here you go:
> >=20
> > Let me know if this fixes the issues you guys are seeing=20
> with your 83xx=20
> > boards.  If so, I'll clean up this patch and push it upstream.
> >=20
> > - k
>=20
>=20
> Great, thank you!
>=20
> Your patch and the params "console=3Duart,io,0xfe004500=20
> console=3DttyS0" in
> the kernel command line do the trick.

I think you should loose the "console=3Duart,io,0xfe004500", don't think
it is needed
sine the "console=3DttyS0" will override it.

>=20
> Alex
>=20
>=20
> >> +        .device_list    =3D (enum ppc_sys_devices[])
> >> +        {
> >> +            MPC83xx_IIC1, MPC83xx_DUART,
> >> +#ifdef CONFIG_QE
> >> +            MPC83xx_QE_UCC3, MPC83xx_QE_UCC4,
> >> +#endif
> >> +        },
> >> +    },
> >>      {    /* default match */
> >>          .ppc_sys_name    =3D "",
> >>          .mask         =3D 0x00000000,

This device list appears to be common to all 8323E CPUs and to me this
looks
like a board unique list. Seems to that this list is better off in the=20
mpc832xe_mds.c board file. That would make it easier for custom boards I
think.

 Jocke

RE: No ttyS device at I/O port 0xfe004500 for console

[Chuck Meade]

> I think you should loose the "console=uart,io,0xfe004500", don't think
> it is needed
> sine the "console=ttyS0" will override it.

I agree.  I use "console=ttyS0,115200".

> > >> +        .device_list    = (enum ppc_sys_devices[])
> > >> +        {
> > >> +            MPC83xx_IIC1, MPC83xx_DUART,
> > >> +#ifdef CONFIG_QE
> > >> +            MPC83xx_QE_UCC3, MPC83xx_QE_UCC4,
> > >> +#endif
> > >> +        },
> > >> +    },
> > >>      {    /* default match */
> > >>          .ppc_sys_name    = "",
> > >>          .mask         = 0x00000000,
> 
> This device list appears to be common to all 8323E CPUs and to me this
> looks
> like a board unique list. Seems to that this list is better off in the 
> mpc832xe_mds.c board file. That would make it easier for custom boards I
> think.
> 
>  Jocke

Whatever is decided here is fine by me -- I followed the style of the 
existing code when adding this code block.  The current 2.6.17 kernel has
the device lists in this same file, for the CPU variants that are supported
in the "public tree".

But you are right, the CPU itself has more UCCs, and other peripherals, than
shown here.  These are just the ones that are used by the existing platform
device drivers I am aware of.  If you know of any additions to make to this
list for the 8323E let us know.

Chuck