P2020RDB boot probem

huyang · ‎12-13-2013

Hi there,

I have a problem with my P2020rdb-PC borad when boot the linux kernal in uboot.

The booting msg is shown as below:

=> bootm ef080000 2000000 ef040000

WARNING: adjusting available memory to 30000000

## Booting kernel from Legacy Image at ef080000 ...

Image Name: Linux-3.8.13-rt9-QorIQ-SDK-V1.4

Created: 2013-06-15 2:52:10 UTC

Image Type: PowerPC Linux Kernel Image (gzip compressed)

Data Size: 3985858 Bytes = 3.8 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 02000000 ...

Image Name: fsl-image-core-p2020rdb-20130615

Created: 2013-06-15 3:32:21 UTC

Image Type: PowerPC Linux RAMDisk Image (gzip compressed)

Data Size: 22026054 Bytes = 21 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

## Flattened Device Tree blob at ef040000

Booting using the fdt blob at 0xef040000

Uncompressing Kernel Image ... OK

Loading Ramdisk to 2eafe000, end 2ffff746 ... OK

Loading Device Tree to 03ff6000, end 03fff2c6 ... OK

WARNING: could not find compatible node fsl-usb2-dr: FDT_ERR_NOTFOUND.

Using P2020RDB-PC machine description

Memory CAM mapping: 256/256/256 Mb, residual: 256Mb

Linux version 3.8.13-rt9-QorIQ-SDK-V1.4 (jenkins@topsy) (gcc version 4.7.2 (GCC3

Found initrd at 0xeeafe000:0xeffff746

CPU maps initialized for 1 thread per core

bootconsole [udbg0] enabled

setup_arch: bootmem

mpc85xx_rdb_setup_arch()

mpc85xx_rdb_setup_arch: Could not find Quicc Engine node

MPC85xx RDB board from Freescale Semiconductor

arch: exit

Zone ranges:

DMA [mem 0x00000000-0x2fffffff]

Normal empty

HighMem [mem 0x30000000-0x3fffffff]

Movable zone start for each node

Early memory node ranges

node 0: [mem 0x00000000-0x3fffffff]

MMU: Allocated 1088 bytes of context maps for 255 contexts

PERCPU: Embedded 7 pages/cpu @c112b000 s6432 r8192 d14048 u32768

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096

Kernel command line: root=/dev/ram rw ramdisk_size=10000000 console=ttyS0,115200

PID hash table entries: 4096 (order: 2, 16384 bytes)

Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

Memory: 942548k/1048576k available (7724k kernel code, 106028k reserved, 300k d)

Kernel virtual memory layout:

* 0xfff5f000..0xfffff000 : fixmap

* 0xffc00000..0xffe00000 : highmem PTEs

* 0xffbfd000..0xffc00000 : early ioremap

* 0xf1000000..0xffbfd000 : vmalloc & ioremap

SLUB: Genslabs=15, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1

Hierarchical RCU implementation.

RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.

NR_IRQS:512 nr_irqs:512 16

mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe40000, max 2 CPUs

mpic: ISU size: 256, shift: 8, mask: ff

mpic: Initializing for 256 sources

mpc85xx_rdb_pic_init: Could not find qe-ic node

clocksource: timebase mult[a000000] shift[24] registered

Console: colour dummy device 80x25

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

mpic: requesting IPIs...

Brought up 2 CPUs

devtmpfs: initialized

NET: Registered protocol family 16

Found FSL PCI host bridge at 0x00000000ffe09000. Firmware bus number: 0->0

PCI host bridge /pcie@ffe09000 (primary) ranges:

MEM 0x00000000a0000000..0x00000000bfffffff -> 0x00000000a0000000

IO 0x00000000ffc10000..0x00000000ffc1ffff -> 0x0000000000000000

/pcie@ffe09000: PCICSRBAR @ 0xfff00000

Found FSL PCI host bridge at 0x00000000ffe0a000. Firmware bus number: 0->0

PCI host bridge /pcie@ffe0a000 ranges:

MEM 0x0000000080000000..0x000000009fffffff -> 0x0000000080000000

IO 0x00000000ffc00000..0x00000000ffc0ffff -> 0x0000000000000000

/pcie@ffe0a000: PCICSRBAR @ 0xfff00000

PCI: Probing PCI hardware

fsl-pci ffe09000.pcie: PCI host bridge to bus 0000:00

pci_bus 0000:00: root bus resource [io 0x0000-0xffff]

pci_bus 0000:00: root bus resource [mem 0xa0000000-0xbfffffff]

pci_bus 0000:00: root bus resource [bus 00-ff]

pci 0000:00:00.0: ignoring class 0x0b2000 (doesn't match header type 01)

pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

pci 0000:00:00.0: PCI bridge to [bus 01-ff]

fsl-pci ffe0a000.pcie: PCI host bridge to bus 0001:02

pci_bus 0001:02: root bus resource [io 0x20000-0x2ffff] (bus address [0x0000-0)

pci_bus 0001:02: root bus resource [mem 0x80000000-0x9fffffff]

pci_bus 0001:02: root bus resource [bus 02-ff]

pci 0001:02:00.0: ignoring class 0x0b2000 (doesn't match header type 01)

pci 0001:02:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

pci 0001:02:00.0: PCI bridge to [bus 03-ff]

pci 0000:00:00.0: PCI bridge to [bus 01]

pci 0000:00:00.0: bridge window [io 0x0000-0xffff]

pci 0000:00:00.0: bridge window [mem 0xa0000000-0xbfffffff]

pci 0001:02:00.0: PCI bridge to [bus 03]

pci 0001:02:00.0: bridge window [io 0x20000-0x2ffff]

pci 0001:02:00.0: bridge window [mem 0x80000000-0x9fffffff]

pci 0000:00:00.0: enabling device (0106 -> 0107)

pci 0001:02:00.0: enabling device (0106 -> 0107)

fsl-l2ctlr ffe20000.l2-cache-controller: Entire L2 as cache, provide valid srame

fsl-l2ctlr: probe of ffe20000.l2-cache-controller failed with error -22

bio: create slab <bio-0> at 0

Freescale Elo / Elo Plus DMA driver

fsl-elo-dma ffe0c300.dma: #0 (fsl,eloplus-dma-channel), irq 76

fsl-elo-dma ffe0c300.dma: #1 (fsl,eloplus-dma-channel), irq 77

fsl-elo-dma ffe0c300.dma: #2 (fsl,eloplus-dma-channel), irq 78

fsl-elo-dma ffe0c300.dma: #3 (fsl,eloplus-dma-channel), irq 79

fsl-elo-dma ffe21300.dma: #0 (fsl,eloplus-dma-channel), irq 20

fsl-elo-dma ffe21300.dma: #1 (fsl,eloplus-dma-channel), irq 21

fsl-elo-dma ffe21300.dma: #2 (fsl,eloplus-dma-channel), irq 22

fsl-elo-dma ffe21300.dma: #3 (fsl,eloplus-dma-channel), irq 23

vgaarb: loaded

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

pps_core: LinuxPPS API ver. 1 registered

PTP clock support registered

Advanced Linux Sound Architecture Driver Initialized.

Switching to clocksource timebase

NET: Registered protocol family 2

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 4, 65536 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

TCP: reno registered

UDP hash table entries: 512 (order: 2, 16384 bytes)

UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)

NET: Registered protocol family 1

RPC: Registered named UNIX socket transport module.

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

Trying to unpack rootfs image as initramfs...

rootfs image is not initramfs (no cpio magic); looks like an initrd

Freeing initrd memory: 21512k freed

Freescale PMC driver

audit: initializing netlink socket (disabled)

type=2000 audit(0.404:1): initialized

bounce pool size: 64 pages

HugeTLB registered 1 MB page size, pre-allocated 0 pages

HugeTLB registered 4 MB page size, pre-allocated 0 pages

HugeTLB registered 16 MB page size, pre-allocated 0 pages

HugeTLB registered 64 MB page size, pre-allocated 0 pages

HugeTLB registered 256 MB page size, pre-allocated 0 pages

HugeTLB registered 1 GB page size, pre-allocated 0 pages

NFS: Registering the id_resolver key type

Key type id_resolver registered

Key type id_legacy registered

NTFS driver 2.1.30 [Flags: R/O].

msgmni has been set to 1501

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Freescale Display Interface Unit (DIU) framebuffer driver

Serial: 8250/16550 driver, 2 ports, IRQ sharing enabled

serial8250.0: ttyS0 at MMIO 0xffe04500 (irq = 42) is a 16550A

console [ttyS0] enabled, bootconsole disabled

serial8250.0: ttyS1 at MMIO 0xffe04600 (irq = 42) is a 16550A

Generic non-volatile memory driver v1.1

brd: module loaded

loop: module loaded

nbd: registered device at major 43

st: Version 20101219, fixed bufsize 32768, s/g segs 256

ef000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x00001

Amd/Fujitsu Extended Query Table at 0x0040

Amd/Fujitsu Extended Query version 1.3.

number of CFI chips: 1

5 ofpart partitions found on MTD device ef000000.nor

Creating 5 MTD partitions on "ef000000.nor":

0x000000000000-0x000000040000 : "NOR Vitesse-7385 Firmware"

ftl_cs: FTL header not found.

0x000000040000-0x000000080000 : "NOR DTB Image"

ftl_cs: FTL header not found.

0x000000080000-0x000000400000 : "NOR Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000400000-0x000000f00000 : "NOR JFFS2 Root File System"

ftl_cs: FTL header not found.

0x000000f00000-0x000001000000 : "NOR U-Boot Image"

ftl_cs: FTL header not found.

NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bi6

Bad block table found at page 65504, version 0x01

Bad block table found at page 65472, version 0x01

6 ofpart partitions found on MTD device ff800000.flash

Creating 6 MTD partitions on "ff800000.flash":

0x000000000000-0x000000100000 : "NAND U-Boot Image"

fsl-lbc ffe05000.localbus: Parity or Uncorrectable ECC error: LTESR 0x20000001

fsl,elbc-fcm-nand ff800000.nand: command failed: fir 412e0000 fcr 0 status 20000

0x000000100000-0x000000200000 : "NAND DTB Image"

ftl_cs: FTL header not found.

0x000000200000-0x000000600000 : "NAND Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000600000-0x000000a00000 : "NAND Compressed RFS Image"

ftl_cs: FTL header not found.

0x000000a00000-0x000001100000 : "NAND JFFS2 Root File System"

ftl_cs: FTL header not found.

0x000001100000-0x000002000000 : "NAND Writable User area"

ftl_cs: FTL header not found.

eLBC NAND device at 0xff800000, bank 1

fsl_espi ffe07000.spi: master is unqueued, this is deprecated

m25p80 spi32766.0: found s25sl12801, expected m25p80

m25p80 spi32766.0: s25sl12801 (16384 Kbytes)

5 ofpart partitions found on MTD device spi32766.0

Creating 5 MTD partitions on "spi32766.0":

0x000000000000-0x000000080000 : "SPI U-Boot Image"

ftl_cs: FTL header not found.

0x000000080000-0x000000100000 : "SPI DTB Image"

ftl_cs: FTL header not found.

0x000000100000-0x000000500000 : "SPI Linux Kernel Image"

ftl_cs: FTL header not found.

0x000000500000-0x000000900000 : "SPI Compressed RFS Image"

ftl_cs: FTL header not found.

0x000000900000-0x000001000000 : "SPI JFFS2 RFS"

ftl_cs: FTL header not found.

fsl_espi ffe07000.spi: at 0xf10c2000 (irq = 59)

libphy: Fixed MDIO Bus: probed

libphy: Freescale PowerQUICC MII Bus: probed

fsl-gianfar ffe24000.ethernet: ptp 1588 is initialized.

fsl-gianfar ffe24000.ethernet eth0: mac: 00:04:9f:02:00:fd

fsl-gianfar ffe24000.ethernet eth0: Running with NAPI enabled

fsl-gianfar ffe24000.ethernet eth0: RX BD ring size for Q[0]: 256

fsl-gianfar ffe24000.ethernet eth0: TX BD ring size for Q[0]: 256

fsl-gianfar ffe25000.ethernet: ptp 1588 is initialized.

fsl-gianfar ffe25000.ethernet eth1: mac: 00:04:9f:02:01:fd

fsl-gianfar ffe25000.ethernet eth1: Running with NAPI enabled

fsl-gianfar ffe25000.ethernet eth1: RX BD ring size for Q[0]: 256

fsl-gianfar ffe25000.ethernet eth1: TX BD ring size for Q[0]: 256

fsl-gianfar ffe26000.ethernet: ptp 1588 is initialized.

fsl-gianfar ffe26000.ethernet eth2: mac: 00:04:9f:02:02:fd

fsl-gianfar ffe26000.ethernet eth2: Running with NAPI enabled

fsl-gianfar ffe26000.ethernet eth2: RX BD ring size for Q[0]: 256

fsl-gianfar ffe26000.ethernet eth2: TX BD ring size for Q[0]: 256

pps pps0: new PPS source ptp0

ucc_geth: QE UCC Gigabit Ethernet Controller

e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

ehci-pci: EHCI PCI platform driver

ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

And it just stuck there, it seems have some problem with USB module on board, is that correct?

Our uboot file, uImage file, file system and dtb file were all from SDK1.4.

Is there any one have similar problem?

Thanks for all your help in community.

Regards,

Hu

kuoweihsu · ‎11-02-2014

Hi, Hu,

We have the same problem using SDK 1.6 and still don't know what is wrong. Would you fix this issue??

scottwood · ‎11-03-2014

Please post a new issue with a console dump and other details (e.g. chip type) specific to your situation.

addiyi · ‎12-13-2013

Hi Hu,

Please check to have Vitesse 7385 Switch Firmware (can be found in SDK - QorIQ-SDK-V1.4-PPCE500V2-IMAGE-20130625-yocto\p2020rdb\boot\ folder) starting with adress 0xef00_0000 in u-boot, or 0xff00_0000 if you want to program it using CW.

Adrian

huyang · ‎12-15-2013

Hi Adrian,

Nice to meet u again.

We already flash the vsc2bin to the address 0xff00_0000 by CW, and set the start address 0xef00_0000 in uboot.

Is this the problem that related to Vitesse 7385 Firmware? It looks like USB not boot correctly.

Thanks.

Hu

P2020RDB boot probem

P2020RDB boot probem

QorIQ P2 Devices