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 <serverip> => setenv <ipaddr> => 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....@lists.ozlabs.org > [mailto:linuxppc-dev- > bounces+poonam.aggrwal=freescale....@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 _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev