From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 95C151007EB for ; Sat, 7 May 2011 22:20:51 +1000 (EST) Received: by qyk7 with SMTP id 7so3577988qyk.17 for ; Sat, 07 May 2011 05:20:46 -0700 (PDT) MIME-Version: 1.0 Date: Sat, 7 May 2011 14:20:46 +0200 Message-ID: Subject: Regarding P2020 in AMP mode From: Prasanna Khanapur To: linuxppc-dev@lists.ozlabs.org Content-Type: multipart/alternative; boundary=90e6ba5bba87cc425204a2aea2fb List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --90e6ba5bba87cc425204a2aea2fb Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm running P2020 in AMP mode, each core running its linux os. Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are working fine. I'm facing problems with Ethernet interface(@24000) assigned to Core1, its not working. I'm using dts file which were added by : http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-September/075594.html Looks either there is some mistake in the dts file or my understanding is wrong. MDIO @24000 is defined in core0 dts file though the Ethernet is assigned to Core 1. DTS files : http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core0.dts http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core1.dts mdio@24520 { #address-cells = <1>; #size-cells = <0>; compatible = "fsl,gianfar-mdio"; reg = <0x24520 0x20>; phy0: ethernet-phy@0 { interrupt-parent = <&mpic>; interrupts = <3 1>; reg = <0x0>; }; phy1: ethernet-phy@1 { interrupt-parent = <&mpic>; interrupts = <3 1>; reg = <0x1>; }; }; Also, MDIO for 25520 has wrong register value: mdio@25520 { #address-cells = <1>; #size-cells = <0>; compatible = "fsl,gianfar-tbi"; reg = <0x26520 0x20>; tbi0: tbi-phy@11 { reg = <0x11>; device_type = "tbi-phy"; }; }; Please correct me if I'm wrong. Has freescale released a working dts files for P2020 in AMP mode ? as this seems to be not working. Best Regards Prasanna Khanapur. --90e6ba5bba87cc425204a2aea2fb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,
I'm running P2020 in AMP mode, each core running its linux os.<= /div>
Ethernet 1(@25000) and=A0Ethernet=A02(@26000) assigned to Core0 a= re working fine.
I'm facing problems with=A0Ethernet=A0interf= ace(@24000) assigned to Core1, its not working.

I'm using dts file which were added by :

Looks either there is some mistake in the dts file or m= y understanding is wrong.

MDIO @24000 is defined i= n core0 dts file though the=A0Ethernet=A0is assigned to Core 1.
<= br>
DTS files :=A0http://web.mornfall.net= /repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core0.dts 
		mdio@24520 {
			#address-cells =3D <1>;
			#size-cells =3D <0>;
			compatible =3D "fsl,gianfar-mdio";
			reg =3D <0x24520 0x20>;

			phy0: ethernet-phy@0 {
				interrupt-parent =3D <&mpic>;
				interrupts =3D <3 1>;
				reg =3D <0x0>;
			};
			phy1: ethernet-phy@1 {
				interrupt-parent =3D <&mpic>;
				interrupts =3D <3 1>;
				reg =3D <0x1>;
			};
		};
Also, MDIO for 25520 has wrong register value:
		mdio@25520 {
			#address-cells =3D <1>;
			#size-cells =3D <0>;
			compatible =3D "fsl,gianfar-tbi";
			reg =3D <0x26520 0x20>;

			tbi0: tbi-phy@11 {
				reg =3D <0x11>;
				device_type =3D "tbi-phy";
			};
		};


Please correct me if =A0I'm wrong. =A0Has freescale released a working = dts files for P2020 in AMP mode ? as this seems to be not working.
= Best Regards
Prasanna Khanapur.



--90e6ba5bba87cc425204a2aea2fb-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay1.mentorg.com (relay1.mentorg.com [192.94.38.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "relay1.mentorg.com", Issuer "Entrust Certification Authority - L1B" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 8F660B6F15 for ; Tue, 10 May 2011 06:22:37 +1000 (EST) Message-ID: <4DC84D09.5020909@mentor.com> Date: Mon, 09 May 2011 13:22:33 -0700 From: Hollis Blanchard MIME-Version: 1.0 To: Prasanna Khanapur Subject: Re: Regarding P2020 in AMP mode References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 05/07/2011 05:20 AM, Prasanna Khanapur wrote: > Hi, > I'm running P2020 in AMP mode, each core running its linux os. > Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are working > fine. > I'm facing problems with Ethernet interface(@24000) assigned to Core1, > its not working. > > I'm using dts file which were added by : > http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-September/075594.html > > Looks either there is some mistake in the dts file or my understanding > is wrong. > > MDIO @24000 is defined in core0 dts file though the Ethernet is assigned > to Core 1. > > DTS files : > http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core0.dts > http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p2020rdb_camp_core1.dts The fixed-link property in core1.dts indicates enet0 should use 1Gb link. Is that device connected to a 1Gb network? -- Hollis Blanchard Mentor Graphics, Embedded Systems Division From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Cybertrust SureServer Standard Validation CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id E29671007D5 for ; Tue, 10 May 2011 17:50:37 +1000 (EST) From: Aggrwal Poonam-B10812 To: Hollis Blanchard , Prasanna Khanapur Subject: RE: Regarding P2020 in AMP mode Date: Tue, 10 May 2011 07:50:26 +0000 Message-ID: <45903308677306428B6EE7E6FF5A5204120187@039-SN1MPN1-004.039d.mgd.msft.net> References: <4DC84D09.5020909@mentor.com> In-Reply-To: <4DC84D09.5020909@mentor.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Cc: "linuxppc-dev@lists.ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , The code looks to be correct in upstream, Can u mention the AMP boot steps you are using. 5.5.2.4 Test Procedure 1. Power on the board 2. Follow the command below at U-boot prompt=20 =3D> setenv =3D> setenv =3D> setenv ethact eTSEC2 =3D> setenv bootargs root=3D/dev/ram rw console=3DttyS0,115200 3. Bring up core1's kernel first:=20 =3D> setenv bootm_low 0x10000000 =3D> setenv bootm_size 0x8000000 =3D> tftp 11000000 uImage.core1 =3D> tftp 12000000 rootfs_min.ext2.gz.uboot =3D> tftp 10c00000 p1020rdb_camp_core1.dtb =3D> interrupts off=20 =20 =3D> bootm start 11000000 12000000 10c00000 =3D> bootm loados =3D> bootm ramdisk =3D> bootm fdt =3D> fdt boardsetup =3D> fdt chosen $initrd_start $initrd_end =3D> bootm prep =3D> cpu 1 release $bootm_low - $fdtaddr - As soon as, when you run the cpu 1 release $bootm_low - $fdtaddr - command,= Core-1 starts booting=20 and boot-up log can be observed on the UART#2 console. 4. Bring up core0's kernel(on the same u-boot console -UART#1): =3D> setenv bootm_low 0x0 =3D> setenv bootm_size 0x10000000 =3D> tftp 1000000 uImage.core0 =3D> tftp 2000000 rootfs_min.ext2.gz.uboot =3D> tftp c00000 p1020rdb_camp_core0.dtb =3D> bootm 1000000 2000000 c00000 The main catch here is to use eTSEC2 as active port at u-boot. I think I r= emember we also faced similar issue. Regards Poonam > -----Original Message----- > From: linuxppc-dev-bounces+poonam.aggrwal=3Dfreescale.com@lists.ozlabs.or= g > [mailto:linuxppc-dev- > bounces+poonam.aggrwal=3Dfreescale.com@lists.ozlabs.org] On Behalf Of > Hollis Blanchard > Sent: Tuesday, May 10, 2011 1:53 AM > To: Prasanna Khanapur > Cc: linuxppc-dev@lists.ozlabs.org > Subject: Re: Regarding P2020 in AMP mode >=20 > On 05/07/2011 05:20 AM, Prasanna Khanapur wrote: > > Hi, > > I'm running P2020 in AMP mode, each core running its linux os. > > Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are > > working fine. > > I'm facing problems with Ethernet interface(@24000) assigned to Core1, > > its not working. > > > > I'm using dts file which were added by : > > http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-September/075594.h > > tml > > > > Looks either there is some mistake in the dts file or my understanding > > is wrong. > > > > MDIO @24000 is defined in core0 dts file though the Ethernet is > > assigned to Core 1. > > > > DTS files : > > http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p202 > > 0rdb_camp_core0.dts > > http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p202 > > 0rdb_camp_core1.dts >=20 > The fixed-link property in core1.dts indicates enet0 should use 1Gb link. > Is that device connected to a 1Gb network? >=20 > -- > Hollis Blanchard > Mentor Graphics, Embedded Systems Division > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/linuxppc-dev From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 923711007D9 for ; Wed, 11 May 2011 21:23:53 +1000 (EST) Received: by qwf7 with SMTP id 7so208660qwf.38 for ; Wed, 11 May 2011 04:23:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <45903308677306428B6EE7E6FF5A5204120187@039-SN1MPN1-004.039d.mgd.msft.net> References: <4DC84D09.5020909@mentor.com> <45903308677306428B6EE7E6FF5A5204120187@039-SN1MPN1-004.039d.mgd.msft.net> Date: Wed, 11 May 2011 13:23:48 +0200 Message-ID: Subject: Re: Regarding P2020 in AMP mode From: Prasanna Khanapur To: "linuxppc-dev@lists.ozlabs.org" Content-Type: multipart/alternative; boundary=0015175d023879595004a2fe4ebd Cc: Aggrwal Poonam-B10812 , Hollis Blanchard List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --0015175d023879595004a2fe4ebd Content-Type: text/plain; charset=ISO-8859-1 I tried the suggestion of setting eTSEC2 as active port for the u-boot . Ethernet of Core1 (connected to 1G) is working now. Thanks for the inputs , they really helped ! Best Regards Prasanna Khanapur On Tue, May 10, 2011 at 9:50 AM, Aggrwal Poonam-B10812 wrote: > The code looks to be correct in upstream, > Can u mention the AMP boot steps you are using. > > > 5.5.2.4 Test Procedure > 1. Power on the board > 2. Follow the command below at U-boot prompt > => setenv > => setenv > => setenv ethact eTSEC2 > => setenv bootargs root=/dev/ram rw console=ttyS0,115200 > 3. Bring up core1's kernel first: > => setenv bootm_low 0x10000000 > => setenv bootm_size 0x8000000 > => tftp 11000000 uImage.core1 > => tftp 12000000 rootfs_min.ext2.gz.uboot > => tftp 10c00000 p1020rdb_camp_core1.dtb > => interrupts off > > => bootm start 11000000 12000000 10c00000 > => bootm loados > => bootm ramdisk > => bootm fdt > => fdt boardsetup > => fdt chosen $initrd_start $initrd_end > => bootm prep > => cpu 1 release $bootm_low - $fdtaddr - > > As soon as, when you run the cpu 1 release $bootm_low - $fdtaddr - command, > Core-1 starts booting > and boot-up log can be observed on the UART#2 console. > 4. Bring up core0's kernel(on the same u-boot console -UART#1): > => setenv bootm_low 0x0 > => setenv bootm_size 0x10000000 > => tftp 1000000 uImage.core0 > => tftp 2000000 rootfs_min.ext2.gz.uboot > => tftp c00000 p1020rdb_camp_core0.dtb > => bootm 1000000 2000000 c00000 > > > The main catch here is to use eTSEC2 as active port at u-boot. I think I > remember we also faced similar issue. > Regards > Poonam > > > -----Original Message----- > > From: linuxppc-dev-bounces+poonam.aggrwal=freescale.com@lists.ozlabs.org > > [mailto:linuxppc-dev- > > bounces+poonam.aggrwal=freescale.com@lists.ozlabs.org] On Behalf Of > > Hollis Blanchard > > Sent: Tuesday, May 10, 2011 1:53 AM > > To: Prasanna Khanapur > > Cc: linuxppc-dev@lists.ozlabs.org > > Subject: Re: Regarding P2020 in AMP mode > > > > On 05/07/2011 05:20 AM, Prasanna Khanapur wrote: > > > Hi, > > > I'm running P2020 in AMP mode, each core running its linux os. > > > Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are > > > working fine. > > > I'm facing problems with Ethernet interface(@24000) assigned to Core1, > > > its not working. > > > > > > I'm using dts file which were added by : > > > http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-September/075594.h > > > tml > > > > > > Looks either there is some mistake in the dts file or my understanding > > > is wrong. > > > > > > MDIO @24000 is defined in core0 dts file though the Ethernet is > > > assigned to Core 1. > > > > > > DTS files : > > > http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p202 > > > 0rdb_camp_core0.dts > > > http://web.mornfall.net/repos/linux-2.6/git/arch/powerpc/boot/dts/p202 > > > 0rdb_camp_core1.dts > > > > The fixed-link property in core1.dts indicates enet0 should use 1Gb link. > > Is that device connected to a 1Gb network? > > > > -- > > Hollis Blanchard > > Mentor Graphics, Embedded Systems Division > > _______________________________________________ > > Linuxppc-dev mailing list > > Linuxppc-dev@lists.ozlabs.org > > https://lists.ozlabs.org/listinfo/linuxppc-dev > > > --0015175d023879595004a2fe4ebd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I tried the suggestion of setting=A0eTSEC2=A0as active port for the u-boot = .
Ethernet =A0of Core1 (connected to 1G) is working now.

Thanks for the inputs , they really=A0helped=A0!

Best Regards
Prasanna Khanapur


On Tue, May 10, 2011 at 9:50 AM, Aggrwal Poonam-B10812 <B10812@freescale.com> wrote:
The code looks to be correct in upstream, Can u mention the AMP boot steps you are using.


5.5.2.4 Test Procedure
1. Power on the board
2. Follow the command below at U-boot prompt
=3D> setenv <serverip>
=3D> setenv <ipaddr>
=3D> setenv ethact eTSEC2
=3D> setenv bootargs root=3D/dev/ram rw console=3DttyS0,115200
3. Bring up core1's kernel first:
=3D> setenv bootm_low 0x10000000
=3D> setenv bootm_size 0x8000000
=3D> tftp 11000000 uImage.core1
=3D> tftp 12000000 rootfs_min.ext2.gz.uboot
=3D> tftp 10c00000 p1020rdb_camp_core1.dtb
=3D> interrupts off

=3D> bootm start 11000000 12000000 10c00000
=3D> bootm loados
=3D> bootm ramdisk
=3D> bootm fdt
=3D> fdt boardsetup
=3D> fdt chosen $initrd_start $initrd_end
=3D> bootm prep
=3D> cpu 1 release $bootm_low - $fdtaddr -

As soon as, when you run the cpu 1 release $bootm_low - $fdtaddr - command,= Core-1 starts booting
and boot-up log can be observed on the UART#2 console.
4. Bring up core0's kernel(on the same u-boot console -UART#1):
=3D> setenv bootm_low 0x0
=3D> setenv bootm_size 0x10000000
=3D> tftp 1000000 uImage.core0
=3D> tftp 2000000 rootfs_min.ext2.gz.uboot
=3D> tftp c00000 p1020rdb_camp_core0.dtb
=3D> bootm 1000000 2000000 c00000


The main catch =A0here is to use eTSEC2 as active port at u-boot. I think I= remember we also =A0faced similar issue.
Regards
Poonam

> -----Original Message-----
> From: linuxppc-dev-bounces+poonam.aggrwal=3Dfreescale.com@lists.ozlabs.org
> [mailto:linuxppc-dev-
> bounces+poonam.aggrwal=3Dfreescale.com@lists.ozlabs.org] On Behalf Of
> Hollis Blanchard
> Sent: Tuesday, May 10, 2011 1:53 AM
> To: Prasanna Khanapur
> Cc: linuxppc-dev@list= s.ozlabs.org
> Subject: Re: Regarding P2020 in AMP mode
>
> On 05/07/2011 05:20 AM, Prasanna Khanapur wrote:
> > Hi,
> > I'm running P2020 in AMP mode, each core running its linux os= .
> > Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are > > working fine.
> > I'm facing problems with Ethernet interface(@24000) assigned = to Core1,
> > its not working.
> >
> > I'm using dts file which were added by :
> > http://lists.ozlabs.org/pipermail/linux= ppc-dev/2009-September/075594.h
> > tml
> >
> > Looks either there is some mistake in the dts file or my understa= nding
> > is wrong.
> >
> > MDIO @24000 is defined in core0 dts file though the Ethernet is > > assigned to Core 1.
> >
> > DTS files :
> > http://web.mornfall.net/repos/linux-2.6= /git/arch/powerpc/boot/dts/p202
> > 0rdb_camp_core0.dts
> > http://web.mornfall.net/repos/linux-2.6= /git/arch/powerpc/boot/dts/p202
> > 0rdb_camp_core1.dts
>
> The fixed-link property in core1.dts indicates enet0 should use 1Gb li= nk.
> Is that device connected to a 1Gb network?
>
> --
> Hollis Blanchard
> Mentor Graphics, Embedded Systems Division
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.oz= labs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev



--0015175d023879595004a2fe4ebd--