Problem running Linux 2.6.11 on MPC8272ADS

Problem running Linux 2.6.11 on MPC8272ADS

[Mike Rapoport]

Hi,
I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to 
hang up at the very beginning.
I use ads8272_defconfig and then enable console on SCC:

CONFIG_SERIAL_CPM=y
CONFIG_SERIAL_CPM_CONSOLE=y
CONFIG_SERIAL_CPM_SCC1=y


when I boot the kernel from the u-boot the system hangs up right after 
the kernel decompression.

-- 
Sincerely Yours,
Mike Rapoport
-----------------------------------------------------------------
CompuLab Ltd.
MALAT Bldg., Technion, Haifa, ISRAEL
Mailing address: P.O. Box 66, Nesher 36770, ISRAEL
Tel: 972-4-8290146
Fax: 972-4-8325251
Web: http://www.compulab.co.il

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Walter L. Wimer III]

Hi Mike,

I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
contains the following function:

  void __init
  m82xx_board_setup(void)
  {
  	/* Enable the 2nd UART port */
  	*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
  }


I had to ifdef-out the assignment statement above.  It appears that the
definition for BCSR_ADDR in the kernel code differs from what U-Boot is
using, and that area of memory isn't properly mapped into the kernel
address space this early in the boot sequence.  As a result, I was
getting an Oops() before the console was even enabled (I could see the
Oops message by examining the kernel's printk log buffer using a
BDI-2000 hardware debugger).



Good luck,

Walt Wimer
TimeSys Corporation




On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> Hi,
> I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to 
> hang up at the very beginning.
> I use ads8272_defconfig and then enable console on SCC:
> 
> CONFIG_SERIAL_CPM=y
> CONFIG_SERIAL_CPM_CONSOLE=y
> CONFIG_SERIAL_CPM_SCC1=y
> 
> 
> when I boot the kernel from the u-boot the system hangs up right after 
> the kernel decompression.
> 

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Kumar Gala]

A patch to make this work properly would be appreciated.

- kumar

On Mar 28, 2005, at 10:06 AM, Walter L. Wimer III wrote:

>
>
> Hi Mike,
>
> I had the same "hang" experience.=A0 The file =
arch/ppc/platforms/pq2ads.c
> contains the following function:
>
> =A0 void __init
>  =A0 m82xx_board_setup(void)
> =A0 {
>  =A0 =A0=A0=A0=A0=A0 /* Enable the 2nd UART port */
>  =A0 =A0=A0=A0=A0=A0 *(volatile uint *)(BCSR_ADDR + 4) &=3D =
~BCSR1_RS232_EN2;
> =A0 }
>
>
>
> I had to ifdef-out the assignment statement above.=A0 It appears that =
the
>  definition for BCSR_ADDR in the kernel code differs from what U-Boot=20=

> is
>  using, and that area of memory isn't properly mapped into the kernel
>  address space this early in the boot sequence.=A0 As a result, I was
>  getting an Oops() before the console was even enabled (I could see =
the
>  Oops message by examining the kernel's printk log buffer using a
>  BDI-2000 hardware debugger).
>
>
>
>
> Good luck,
>
> Walt Wimer
>  TimeSys Corporation
>
>
>
>
>
> On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
>  > Hi,
>  > I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem =
to
> > hang up at the very beginning.
>  > I use ads8272_defconfig and then enable console on SCC:
>  >
> > CONFIG_SERIAL_CPM=3Dy
> > CONFIG_SERIAL_CPM_CONSOLE=3Dy
> > CONFIG_SERIAL_CPM_SCC1=3Dy
> >
> >
> > when I boot the kernel from the u-boot the system hangs up right=20
> after
> > the kernel decompression.
> >
>
>  _______________________________________________
> Linuxppc-embedded mailing list
>  Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Walter L. Wimer III]

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


I'll submit one once I get everything else working on this board that I
need....  :-)


Walt



On Mon, 2005-03-28 at 10:21 -0600, Kumar Gala wrote:

> A patch to make this work properly would be appreciated.
> 
> - kumar
> 
> On Mar 28, 2005, at 10:06 AM, Walter L. Wimer III wrote:
> 
> >
> >
> > Hi Mike,
> >
> > I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
> > contains the following function:
> >
> >   void __init
> >    m82xx_board_setup(void)
> >   {
> >          /* Enable the 2nd UART port */
> >          *(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
> >   }
> >
> >
> >
> > I had to ifdef-out the assignment statement above.  It appears that the
> >  definition for BCSR_ADDR in the kernel code differs from what U-Boot 
> > is
> >  using, and that area of memory isn't properly mapped into the kernel
> >  address space this early in the boot sequence.  As a result, I was
> >  getting an Oops() before the console was even enabled (I could see the
> >  Oops message by examining the kernel's printk log buffer using a
> >  BDI-2000 hardware debugger).
> >
> >
> >
> >
> > Good luck,
> >
> > Walt Wimer
> >  TimeSys Corporation
> >
> >
> >
> >
> >
> > On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> >  > Hi,
> >  > I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to
> > > hang up at the very beginning.
> >  > I use ads8272_defconfig and then enable console on SCC:
> >  >
> > > CONFIG_SERIAL_CPM=y
> > > CONFIG_SERIAL_CPM_CONSOLE=y
> > > CONFIG_SERIAL_CPM_SCC1=y
> > >
> > >
> > > when I boot the kernel from the u-boot the system hangs up right 
> > after
> > > the kernel decompression.
> > >
> >
> >  _______________________________________________
> > Linuxppc-embedded mailing list
> >  Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

[-- Attachment #2: Type: text/html, Size: 4225 bytes --]

RE: Problem running Linux 2.6.11 on MPC8272ADS

[Bastos Fernandez Alexandre]

Hi, 

>From "linux/arch/ppc/platforms/pq2ads.h"
#define BCSR_ADDR ((uint) 0xf4500000)
>From "u-boot/include/configs/MPC8260ADS.h"
#define CFG_BCSR 0xF4500000
So ...
Which version of u-boot and/or linux tree are you using?
With linuxppc-2.5 and u-boot 1.2 everything works fine for me.
Maybe Mike's problem is other. Maybe not. :-)

Best regards,
Alex

> -----Original Message-----
> From:	Walter L. Wimer III [SMTP:walt.wimer@timesys.com]
> Sent:	Monday, March 28, 2005 6:07 PM
> To:	Mike Rapoport
> Cc:	linuxppc-embedded@ozlabs.org
> Subject:	Re: Problem running Linux 2.6.11 on MPC8272ADS
> 
> 
> Hi Mike,
> 
> I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
> contains the following function:
> 
>   void __init
>   m82xx_board_setup(void)
>   {
>   	/* Enable the 2nd UART port */
>   	*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
>   }
> 
> 
> I had to ifdef-out the assignment statement above.  It appears that the
> definition for BCSR_ADDR in the kernel code differs from what U-Boot is
> using, and that area of memory isn't properly mapped into the kernel
> address space this early in the boot sequence.  As a result, I was
> getting an Oops() before the console was even enabled (I could see the
> Oops message by examining the kernel's printk log buffer using a
> BDI-2000 hardware debugger).
> 
> 
> 
> Good luck,
> 
> Walt Wimer
> TimeSys Corporation
> 
> 
> 
> 
> On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> > Hi,
> > I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to 
> > hang up at the very beginning.
> > I use ads8272_defconfig and then enable console on SCC:
> > 
> > CONFIG_SERIAL_CPM=y
> > CONFIG_SERIAL_CPM_CONSOLE=y
> > CONFIG_SERIAL_CPM_SCC1=y
> > 
> > 
> > when I boot the kernel from the u-boot the system hangs up right after 
> > the kernel decompression.
> > 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: Problem running Linux 2.6.11 on MPC8272ADS

[Walter L. Wimer III]

Thanks for the data points, Alex.

I'm using U-Boot 1.1.1 and vanilla kernel.org 2.6.11.4 (actually now
2.6.11.5).  My BCSR_ADDR looks the same as what you've listed below, so
I'd guess the difference is with U-Boot...  (Another engineer here
installed U-Boot on my board, from, I believe, a binary copy he got from
a Freescale(?) CD...  I didn't build U-Boot from source...  That's
something I'll need to take a look at...)

Mike, have you discovered anything further about your problem?



Walt



On Tue, 2005-03-29 at 08:29 +0200, Bastos Fernandez Alexandre wrote:
> Hi, 
> 
> >From "linux/arch/ppc/platforms/pq2ads.h"
> #define BCSR_ADDR ((uint) 0xf4500000)
> >From "u-boot/include/configs/MPC8260ADS.h"
> #define CFG_BCSR 0xF4500000
> So ...
> Which version of u-boot and/or linux tree are you using?
> With linuxppc-2.5 and u-boot 1.2 everything works fine for me.
> Maybe Mike's problem is other. Maybe not. :-)
> 
> Best regards,
> Alex
> 
> > -----Original Message-----
> > From:	Walter L. Wimer III [SMTP:walt.wimer@timesys.com]
> > Sent:	Monday, March 28, 2005 6:07 PM
> > To:	Mike Rapoport
> > Cc:	linuxppc-embedded@ozlabs.org
> > Subject:	Re: Problem running Linux 2.6.11 on MPC8272ADS
> > 
> > 
> > Hi Mike,
> > 
> > I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
> > contains the following function:
> > 
> >   void __init
> >   m82xx_board_setup(void)
> >   {
> >   	/* Enable the 2nd UART port */
> >   	*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
> >   }
> > 
> > 
> > I had to ifdef-out the assignment statement above.  It appears that the
> > definition for BCSR_ADDR in the kernel code differs from what U-Boot is
> > using, and that area of memory isn't properly mapped into the kernel
> > address space this early in the boot sequence.  As a result, I was
> > getting an Oops() before the console was even enabled (I could see the
> > Oops message by examining the kernel's printk log buffer using a
> > BDI-2000 hardware debugger).
> > 
> > 
> > 
> > Good luck,
> > 
> > Walt Wimer
> > TimeSys Corporation
> > 
> > 
> > 
> > 
> > On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> > > Hi,
> > > I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to 
> > > hang up at the very beginning.
> > > I use ads8272_defconfig and then enable console on SCC:
> > > 
> > > CONFIG_SERIAL_CPM=y
> > > CONFIG_SERIAL_CPM_CONSOLE=y
> > > CONFIG_SERIAL_CPM_SCC1=y
> > > 
> > > 
> > > when I boot the kernel from the u-boot the system hangs up right after 
> > > the kernel decompression.
> > > 
> > 
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Walter L. Wimer III]

This matched my experience as well.

Does anyone know why U-Boot 1.1.1 from Freescale uses a different BCSR
address than U-Boot 1.1.1 from Sourceforge?

Any opinions on which address is the "correct" one to use?  Kumar asked
for a patch to fix this, so what do we think the correct fix is?



Thanks!

Walt



On Wed, 2005-03-30 at 10:18 +0200, Mike Rapoport wrote:
> Walter,
> Thanks for you help. I've discovered several things and now the things 
> seem to work fine.
> I've used u-boot-1.1.1 that came with the Freescale BSP and it maps BCSR 
> to 0xf8000000. The "regular" u-boot-1.1.1 (from sf.net) maps the BCSR to 
> 0xf4500000 as well as the kernel does (arch/ppc/platforms/pq2ads.h). The 
> difference causes the "hang"-like behaviour when the kernel initializes 
> serial comm and kernel crash afterwards when FCC is initialized.
> 
> Mike.
> 
> >Thanks for the data points, Alex.
> >
> >I'm using U-Boot 1.1.1 and vanilla kernel.org 2.6.11.4 (actually now
> >2.6.11.5).  My BCSR_ADDR looks the same as what you've listed below, so
> >I'd guess the difference is with U-Boot...  (Another engineer here
> >installed U-Boot on my board, from, I believe, a binary copy he got from
> >a Freescale(?) CD...  I didn't build U-Boot from source...  That's
> >something I'll need to take a look at...)
> >
> >Mike, have you discovered anything further about your problem?
> >
> >
> >
> >Walt
> >
> >
> >
> >On Tue, 2005-03-29 at 08:29 +0200, Bastos Fernandez Alexandre wrote:
> >  
> >
> >>Hi, 
> >>
> >>>From "linux/arch/ppc/platforms/pq2ads.h"
> >>#define BCSR_ADDR ((uint) 0xf4500000)
> >>>From "u-boot/include/configs/MPC8260ADS.h"
> >>#define CFG_BCSR 0xF4500000
> >>So ...
> >>Which version of u-boot and/or linux tree are you using?
> >>With linuxppc-2.5 and u-boot 1.2 everything works fine for me.
> >>Maybe Mike's problem is other. Maybe not. :-)
> >>
> >>Best regards,
> >>Alex
> >>
> >>    
> >>
> >>>-----Original Message-----
> >>>From:	Walter L. Wimer III [SMTP:walt.wimer@timesys.com]
> >>>Sent:	Monday, March 28, 2005 6:07 PM
> >>>To:	Mike Rapoport
> >>>Cc:	linuxppc-embedded@ozlabs.org
> >>>Subject:	Re: Problem running Linux 2.6.11 on MPC8272ADS
> >>>
> >>>
> >>>Hi Mike,
> >>>
> >>>I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
> >>>contains the following function:
> >>>
> >>>  void __init
> >>>  m82xx_board_setup(void)
> >>>  {
> >>>  	/* Enable the 2nd UART port */
> >>>  	*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
> >>>  }
> >>>
> >>>
> >>>I had to ifdef-out the assignment statement above.  It appears that the
> >>>definition for BCSR_ADDR in the kernel code differs from what U-Boot is
> >>>using, and that area of memory isn't properly mapped into the kernel
> >>>address space this early in the boot sequence.  As a result, I was
> >>>getting an Oops() before the console was even enabled (I could see the
> >>>Oops message by examining the kernel's printk log buffer using a
> >>>BDI-2000 hardware debugger).
> >>>
> >>>
> >>>
> >>>Good luck,
> >>>
> >>>Walt Wimer
> >>>TimeSys Corporation
> >>>
> >>>
> >>>
> >>>
> >>>On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> >>>      
> >>>
> >>>>Hi,
> >>>>I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to 
> >>>>hang up at the very beginning.
> >>>>I use ads8272_defconfig and then enable console on SCC:
> >>>>
> >>>>CONFIG_SERIAL_CPM=y
> >>>>CONFIG_SERIAL_CPM_CONSOLE=y
> >>>>CONFIG_SERIAL_CPM_SCC1=y
> >>>>
> >>>>
> >>>>when I boot the kernel from the u-boot the system hangs up right after 
> >>>>the kernel decompression.
> >>>>
> >>>>        
> >>>>
> >>>_______________________________________________
> >>>Linuxppc-embedded mailing list
> >>>Linuxppc-embedded@ozlabs.org
> >>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >>>      
> >>>
> >
> >
> >  
> >
> 

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Kumar Gala]

Also,

If you guys come to some conclusion about a fix we can make to the=20
boards that would improve functionality, I'll try to get that back to=20
the board guys to look at implementing for future revs.

- kumar

On Mar 30, 2005, at 10:00 AM, Walter L. Wimer III wrote:

>
>
> This matched my experience as well.
>
> Does anyone know why U-Boot 1.1.1 from Freescale uses a different BCSR
> address than U-Boot 1.1.1 from Sourceforge?
>
> Any opinions on which address is the "correct" one to use?=A0 Kumar =
asked
>  for a patch to fix this, so what do we think the correct fix is?
>
>
>
>
> Thanks!
>
> Walt
>
>
>
>
> On Wed, 2005-03-30 at 10:18 +0200, Mike Rapoport wrote:
>  > Walter,
>  > Thanks for you help. I've discovered several things and now the=20
> things
> > seem to work fine.
>  > I've used u-boot-1.1.1 that came with the Freescale BSP and it maps=20=

> BCSR
> > to 0xf8000000. The "regular" u-boot-1.1.1 (from sf.net) maps the=20
> BCSR to
> > 0xf4500000 as well as the kernel does (arch/ppc/platforms/pq2ads.h).=20=

> The
> > difference causes the "hang"-like behaviour when the kernel=20
> initializes
> > serial comm and kernel crash afterwards when FCC is initialized.
>  >
> > Mike.
>  >
> > >Thanks for the data points, Alex.
>  > >
>  > >I'm using U-Boot 1.1.1 and vanilla kernel.org 2.6.11.4 (actually=20=

> now
>  > >2.6.11.5).=A0 My BCSR_ADDR looks the same as what you've listed=20
> below, so
>  > >I'd guess the difference is with U-Boot...=A0 (Another engineer =
here
>  > >installed U-Boot on my board, from, I believe, a binary copy he=20
> got from
>  > >a Freescale(?) CD...=A0 I didn't build U-Boot from source...=A0 =
That's
>  > >something I'll need to take a look at...)
>  > >
>  > >Mike, have you discovered anything further about your problem?
>  > >
>  > >
>  > >
>  > >Walt
>  > >
>  > >
>  > >
>  > >On Tue, 2005-03-29 at 08:29 +0200, Bastos Fernandez Alexandre=20
> wrote:
>  > >=A0
> > >
>  > >>Hi,
> > >>
>  > >>>=46rom "linux/arch/ppc/platforms/pq2ads.h"
> > >>#define BCSR_ADDR ((uint) 0xf4500000)
>  > >>>=46rom "u-boot/include/configs/MPC8260ADS.h"
> > >>#define CFG_BCSR 0xF4500000
>  > >>So ...
>  > >>Which version of u-boot and/or linux tree are you using?
>  > >>With linuxppc-2.5 and u-boot 1.2 everything works fine for me.
>  > >>Maybe Mike's problem is other. Maybe not. :-)
>  > >>
>  > >>Best regards,
>  > >>Alex
>  > >>
>  > >>=A0=A0=A0
> > >>
>  > >>>-----Original Message-----
>  > >>>From:=A0=A0=A0=A0=A0 Walter L. Wimer III =
[SMTP:walt.wimer@timesys.com]
> > >>>Sent:=A0=A0=A0=A0=A0 Monday, March 28, 2005 6:07 PM
>  > >>>To:=A0=A0=A0=A0=A0=A0=A0 Mike Rapoport
> > >>>Cc:=A0=A0=A0=A0=A0=A0=A0 linuxppc-embedded@ozlabs.org
> > >>>Subject:=A0=A0 Re: Problem running Linux 2.6.11 on MPC8272ADS
> > >>>
>  > >>>
>  > >>>Hi Mike,
>  > >>>
>  > >>>I had the same "hang" experience.=A0 The file=20
> arch/ppc/platforms/pq2ads.c
> > >>>contains the following function:
>  > >>>
>  > >>>=A0 void __init
>  > >>>=A0 m82xx_board_setup(void)
> > >>>=A0 {
>  > >>>=A0=A0 /* Enable the 2nd UART port */
>  > >>>=A0=A0 *(volatile uint *)(BCSR_ADDR + 4) &=3D ~BCSR1_RS232_EN2;
> > >>>=A0 }
>  > >>>
>  > >>>
>  > >>>I had to ifdef-out the assignment statement above.=A0 It appears=20=

> that the
>  > >>>definition for BCSR_ADDR in the kernel code differs from what=20
> U-Boot is
>  > >>>using, and that area of memory isn't properly mapped into the=20
> kernel
>  > >>>address space this early in the boot sequence.=A0 As a result, I=20=

> was
>  > >>>getting an Oops() before the console was even enabled (I could=20=

> see the
>  > >>>Oops message by examining the kernel's printk log buffer using a
>  > >>>BDI-2000 hardware debugger).
>  > >>>
>  > >>>
>  > >>>
>  > >>>Good luck,
>  > >>>
>  > >>>Walt Wimer
>  > >>>TimeSys Corporation
>  > >>>
>  > >>>
>  > >>>
>  > >>>
>  > >>>On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
>  > >>>=A0=A0=A0=A0=A0
> > >>>
>  > >>>>Hi,
>  > >>>>I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it=20
> seem to
> > >>>>hang up at the very beginning.
>  > >>>>I use ads8272_defconfig and then enable console on SCC:
>  > >>>>
>  > >>>>CONFIG_SERIAL_CPM=3Dy
> > >>>>CONFIG_SERIAL_CPM_CONSOLE=3Dy
> > >>>>CONFIG_SERIAL_CPM_SCC1=3Dy
> > >>>>
>  > >>>>
>  > >>>>when I boot the kernel from the u-boot the system hangs up=20
> right after
> > >>>>the kernel decompression.
> > >>>>
>  > >>>>=A0=A0=A0=A0=A0=A0=A0
> > >>>>
>  > >>>_______________________________________________
> > >>>Linuxppc-embedded mailing list
>  > >>>Linuxppc-embedded@ozlabs.org
> > >>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>  > >>>=A0=A0=A0=A0=A0
> > >>>
>  > >
>  > >
>  > >=A0
> > >
>  >
>
>  _______________________________________________
> Linuxppc-embedded mailing list
>  Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: Problem running Linux 2.6.11 on MPC8272ADS

[Li Yang-r58472]

Well, it seems to be a historic problem.  Freescale BSP was originally ported from u-boot-1.0.0 and linux-2.4.22.  So the BCSR was freely chosen as 0xf8000000.  Later, we updated them to u-boot-1.1.1 and linux-2.4.26, and make the BCSR consistent to older version.  However the sourceforge u-boot-1.1.1 support for MPC8272ADS was committed by Arabella guys, they chose BCSR mapping to 0xf4500000.  Kumar's MPC8272 support which is in 2.6.11 source was developed using sourceforge u-boot-1.1.1 seemingly.

This might brought up a question that if we need a convention or something to define the recommended memory mapping for PowerPC BSPs.  As there are different groups of people around the world developing BSPs for PowerPC platforms, and often the communication between them is very limited.

For now using kernel and u-boot released from the same vendor is recommended.


Best Regards,
Leo


> -----Original Message-----
> From: linuxppc-embedded-bounces@ozlabs.org
> [mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Walter L. Wimer
> III
> Sent: Thursday, March 31, 2005 12:00 AM
> To: Linux PPC Embedded list
> Subject: Re: Problem running Linux 2.6.11 on MPC8272ADS
> 
> 
> This matched my experience as well.
> 
> Does anyone know why U-Boot 1.1.1 from Freescale uses a different BCSR
> address than U-Boot 1.1.1 from Sourceforge?
> 
> Any opinions on which address is the "correct" one to use?  Kumar asked
> for a patch to fix this, so what do we think the correct fix is?
> 
> 
> 
> Thanks!
> 
> Walt
> 
> 
> 
> On Wed, 2005-03-30 at 10:18 +0200, Mike Rapoport wrote:
> > Walter,
> > Thanks for you help. I've discovered several things and now the things
> > seem to work fine.
> > I've used u-boot-1.1.1 that came with the Freescale BSP and it maps BCSR
> > to 0xf8000000. The "regular" u-boot-1.1.1 (from sf.net) maps the BCSR to
> > 0xf4500000 as well as the kernel does (arch/ppc/platforms/pq2ads.h). The
> > difference causes the "hang"-like behaviour when the kernel initializes
> > serial comm and kernel crash afterwards when FCC is initialized.
> >
> > Mike.
> >
> > >Thanks for the data points, Alex.
> > >
> > >I'm using U-Boot 1.1.1 and vanilla kernel.org 2.6.11.4 (actually now
> > >2.6.11.5).  My BCSR_ADDR looks the same as what you've listed below, so
> > >I'd guess the difference is with U-Boot...  (Another engineer here
> > >installed U-Boot on my board, from, I believe, a binary copy he got from
> > >a Freescale(?) CD...  I didn't build U-Boot from source...  That's
> > >something I'll need to take a look at...)
> > >
> > >Mike, have you discovered anything further about your problem?
> > >
> > >
> > >
> > >Walt
> > >
> > >
> > >
> > >On Tue, 2005-03-29 at 08:29 +0200, Bastos Fernandez Alexandre wrote:
> > >
> > >
> > >>Hi,
> > >>
> > >>>From "linux/arch/ppc/platforms/pq2ads.h"
> > >>#define BCSR_ADDR ((uint) 0xf4500000)
> > >>>From "u-boot/include/configs/MPC8260ADS.h"
> > >>#define CFG_BCSR 0xF4500000
> > >>So ...
> > >>Which version of u-boot and/or linux tree are you using?
> > >>With linuxppc-2.5 and u-boot 1.2 everything works fine for me.
> > >>Maybe Mike's problem is other. Maybe not. :-)
> > >>
> > >>Best regards,
> > >>Alex
> > >>
> > >>
> > >>
> > >>>-----Original Message-----
> > >>>From:	Walter L. Wimer III [SMTP:walt.wimer@timesys.com]
> > >>>Sent:	Monday, March 28, 2005 6:07 PM
> > >>>To:	Mike Rapoport
> > >>>Cc:	linuxppc-embedded@ozlabs.org
> > >>>Subject:	Re: Problem running Linux 2.6.11 on MPC8272ADS
> > >>>
> > >>>
> > >>>Hi Mike,
> > >>>
> > >>>I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
> > >>>contains the following function:
> > >>>
> > >>>  void __init
> > >>>  m82xx_board_setup(void)
> > >>>  {
> > >>>  	/* Enable the 2nd UART port */
> > >>>  	*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
> > >>>  }
> > >>>
> > >>>
> > >>>I had to ifdef-out the assignment statement above.  It appears that the
> > >>>definition for BCSR_ADDR in the kernel code differs from what U-Boot is
> > >>>using, and that area of memory isn't properly mapped into the kernel
> > >>>address space this early in the boot sequence.  As a result, I was
> > >>>getting an Oops() before the console was even enabled (I could see the
> > >>>Oops message by examining the kernel's printk log buffer using a
> > >>>BDI-2000 hardware debugger).
> > >>>
> > >>>
> > >>>
> > >>>Good luck,
> > >>>
> > >>>Walt Wimer
> > >>>TimeSys Corporation
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> > >>>
> > >>>
> > >>>>Hi,
> > >>>>I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to
> > >>>>hang up at the very beginning.
> > >>>>I use ads8272_defconfig and then enable console on SCC:
> > >>>>
> > >>>>CONFIG_SERIAL_CPM=y
> > >>>>CONFIG_SERIAL_CPM_CONSOLE=y
> > >>>>CONFIG_SERIAL_CPM_SCC1=y
> > >>>>
> > >>>>
> > >>>>when I boot the kernel from the u-boot the system hangs up right after
> > >>>>the kernel decompression.
> > >>>>
> > >>>>
> > >>>>
> > >>>_______________________________________________
> > >>>Linuxppc-embedded mailing list
> > >>>Linuxppc-embedded@ozlabs.org
> > >>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> > >>>
> > >>>
> > >
> > >
> > >
> > >
> >
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Eugene Surovegin]

On Thu, Mar 31, 2005 at 11:03:00AM +0800, Li Yang-r58472 wrote:
> Well, it seems to be a historic problem.  Freescale BSP was 
> originally ported from u-boot-1.0.0 and linux-2.4.22.  So the BCSR 
> was freely chosen as 0xf8000000.  Later, we updated them to 
> u-boot-1.1.1 and linux-2.4.26, and make the BCSR consistent to older 
> version.  However the sourceforge u-boot-1.1.1 support for 
> MPC8272ADS 
> was committed by Arabella guys, they chose BCSR mapping to 
> 0xf4500000.  Kumar's MPC8272 support which is in 2.6.11 source was 
> developed using sourceforge u-boot-1.1.1 seemingly.
> 
> This might brought up a question that if we need a convention or 
> something to define the recommended memory mapping for PowerPC BSPs.  
> As there are different groups of people around the world developing 
> BSPs for PowerPC platforms, and often the communication between them 
> is very limited.
> 
> For now using kernel and u-boot released from the same vendor is recommended.
> 

There is trivial solution which will work regardless on which version 
of U-Boot and kernel you are using.

DO NOT hardcode such stuff in TWO DIFFERENT places, do this only in 
one, in this case it should be firmware (e.g. U-Boot).

In kernel just read BRx register for that chip select and use this 
address for accesses from the kernel. This is how I do on all my 
board ports.

No need to establish any artificial conventions on memory map, etc.

--
Eugene

RE: Problem running Linux 2.6.11 on MPC8272ADS

[Li Yang-r58472]

Good point.
There is also IMMR need to be passed from bootloader to kernel.  We can make more use of the u-boot bd_info mechanism.  But it binds ppc linux to u-boot boot loader.  I don't know if we should make it a porting convention.

Best Regards,
Leo

> -----Original Message-----
> From: Eugene Surovegin [mailto:ebs@ebshome.net]
> Sent: Thursday, March 31, 2005 11:27 AM
> To: Li Yang-r58472
> Cc: Walter L. Wimer III; Gala Kumar K.-galak; Linux PPC Embedded list
> Subject: Re: Problem running Linux 2.6.11 on MPC8272ADS
> 
> On Thu, Mar 31, 2005 at 11:03:00AM +0800, Li Yang-r58472 wrote:
> > Well, it seems to be a historic problem.  Freescale BSP was
> > originally ported from u-boot-1.0.0 and linux-2.4.22.  So the BCSR
> > was freely chosen as 0xf8000000.  Later, we updated them to
> > u-boot-1.1.1 and linux-2.4.26, and make the BCSR consistent to older
> > version.  However the sourceforge u-boot-1.1.1 support for
> > MPC8272ADS
> > was committed by Arabella guys, they chose BCSR mapping to
> > 0xf4500000.  Kumar's MPC8272 support which is in 2.6.11 source was
> > developed using sourceforge u-boot-1.1.1 seemingly.
> >
> > This might brought up a question that if we need a convention or
> > something to define the recommended memory mapping for PowerPC BSPs.
> > As there are different groups of people around the world developing
> > BSPs for PowerPC platforms, and often the communication between them
> > is very limited.
> >
> > For now using kernel and u-boot released from the same vendor is recommended.
> >
> 
> There is trivial solution which will work regardless on which version
> of U-Boot and kernel you are using.
> 
> DO NOT hardcode such stuff in TWO DIFFERENT places, do this only in
> one, in this case it should be firmware (e.g. U-Boot).
> 
> In kernel just read BRx register for that chip select and use this
> address for accesses from the kernel. This is how I do on all my
> board ports.
> 
> No need to establish any artificial conventions on memory map, etc.
> 
> --
> Eugene

Re: Problem running Linux 2.6.11 on MPC8272ADS

[Eugene Surovegin]

On Thu, Mar 31, 2005 at 04:22:26PM +0800, Li Yang-r58472 wrote:
> Good point.
> There is also IMMR need to be passed from bootloader to kernel.  We 
> can make more use of the u-boot bd_info mechanism.  But it binds ppc 
> linux to u-boot boot loader.  I don't know if we should make it a 
> porting convention.

Well, immr is _already_ part of bd_t passed from U-Boot! I was 
surprised that none of board ports (some of which are made for U-Boot 
only) use this. 

In 8248 based board port I'm working on right now, I already defined 
CPM_MAP_ADDR as follows:

#define CPM_MAP_ADDR            (((bd_t*)__res)->bi_immr_base)

--
Eugene

RE: Problem running Linux 2.6.11 on MPC8272ADS

[Jon Loeliger]

On Thu, 2005-03-31 at 02:22, Li Yang-r58472 wrote:
> Good point.
> There is also IMMR need to be passed from bootloader to kernel.  We
> can make more use of the u-boot bd_info mechanism.  But it binds ppc
> linux to u-boot boot loader.  I don't know if we should make it a
> porting convention.

Hi guys,

So, just for the record here, Kumar and I are moving the ppc32
line away from bd_t towards an OpenFirmware flattened device tree.
That data will still have a place for the IMMR to be passed.

Under another Subject:, I'll describe a brief outline of
The Plan So Far so people can take shots at it. :-)

> Best Regards,
> Leo

Thanks,
jdl