Hi Scott: I am still stuck at Linux kernel booting in MPC8343EA based board.
I have disabled "Ethernet, PCI, USB, dma engines " in the *.dts file and also in the kernel config. I am using MPC8349emitxgp.dts ; enabled MPC8349ITX support in kernel config also. In fact, I tried building MPC8349emITX; MPC8349MDS also. Same behaviour! With this, the kernel boots up (explicitly passing the DTB file and cuImage NEVER worked) and hangs after I am using Linux-V-2.6.27.18 and using powerpc-e300c3-gnu toolchain - gcc-4.1.69-eglibc-2.5.69-1 to build u-boot-1.3.2 & linux. With this, the kernel boots up (explicitly passing the DTB file and cuImage NEVER worked) and hangs after printing "Calibrating delay loop... 133.12 BogoMIPS (lpj=266240)" With a few debug printks looks like the kernel hangs in "cpu_idle" in --main/init.c Any clues..?? HELP!!! Please find the dts file and screen-dump below: Thanks, Junita DTS file: ======= /dts-v1/; / { model = "MPC8349EMITXGP"; compatible = "MPC8349EMITXGP", "MPC834xMITX", "MPC83xxMITX"; #address-cells = <1>; #size-cells = <1>; aliases { serial0 = &serial0; }; cpus { #address-cells = <1>; #size-cells = <0>; PowerPC,8...@0 { device_type = "cpu"; reg = <0x0>; d-cache-line-size = <32>; i-cache-line-size = <32>; d-cache-size = <32768>; i-cache-size = <32768>; timebase-frequency = <0>; // from bootloader bus-frequency = <0>; // from bootloader clock-frequency = <0>; // from bootloader }; }; memory { device_type = "memory"; reg = <0x00000000 0x10000000>; }; soc8...@e0000000 { #address-cells = <1>; #size-cells = <1>; device_type = "soc"; compatible = "simple-bus"; ranges = <0x0 0xe0000000 0x00100000>; reg = <0xe0000000 0x00000200>; bus-frequency = <0x0fe502a8>; // from bootloader w...@200 { device_type = "watchdog"; compatible = "mpc83xx_wdt"; reg = <0x200 0x100>; }; i...@3000 { #address-cells = <1>; #size-cells = <0>; cell-index = <0>; compatible = "fsl-i2c"; reg = <0x3000 0x100>; interrupts = <14 0x8>; interrupt-parent = <&ipic>; dfsrr; }; m...@24520 { #address-cells = <1>; #size-cells = <0>; compatible = "fsl,gianfar-mdio"; reg = <0x24520 0x20>; }; serial0: ser...@4500 { cell-index = <0>; device_type = "serial"; compatible = "ns16550"; reg = <0x4500 0x100>; clock-frequency = <0>; // from bootloader interrupts = <9 0x8>; interrupt-parent = <&ipic>; }; ipic: p...@700 { interrupt-controller; #address-cells = <0>; #interrupt-cells = <2>; reg = <0x700 0x100>; device_type = "ipic"; }; }; }; Screen-shot: ========== Trying TSEC0 Speed: 100, full duplex Using TSEC0 device TFTP from server 192.168.201.14; our IP address is 192.168.201.199 Filename '8349.dtb'. Load address: 0x900000 Loading: # done Bytes transferred = 12288 (3000 hex) SC3000> bootm 0x00600000 - 0x00900000 ## Booting image at 00600000 ... Image Name: Linux-2.6.27.18 Created: 2009-12-11 0:16:24 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 850785 Bytes = 830.8 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x0FF9BD48 => set upper limit to 0x00800000 ## cmdline at 0x007FFF00 ... 0x007FFF2E bd address = 0x0FF9BFC4 memstart = 0x00000000 memsize = 0x10000000 flashstart = 0xFE000000 flashsize = 0x00080000 flashoffset = 0x00034000 sramstart = 0x00000000 sramsize = 0x00000000 bootflags = 0x00000001 intfreq = 399.999 MHz busfreq = 266.666 MHz ethaddr = 00:E0:0C:00:8C:01 IP addr = 192.168.201.199 baudrate = 115200 bps Skipping initrd Booting using the fdt at 0x900000 No initrd ## device tree at 0x00900000 ... 0x00902FFF (len=12288=0x3000) Loading Device Tree to 007fc000, end 007fefff ... OK Updating property 'timebase-frequency' = 03 f9 40 aa Updating property 'bus-frequency' = 0f e5 02 a8 Updating property 'clock-frequency' = 17 d7 83 fc Updating property 'bus-frequency' = 0f e5 02 a8 Updating property 'clock-frequency' = 0f e5 02 a8 ## Transferring control to Linux (at address 00000000) ... Using MPC834x ITX machine description Linux version 2.6.27.18 (r...@localhost.localdomain) (gcc version 4.1.2) #26 Th9 -> find_legacy_serial_port() stdout is /soc8...@e0000000/ser...@4500 Found legacy serial port 0 for /soc8...@e0000000/ser...@4500 mem=e0004500, taddr=e0004500, irq=0, clk=266666664, speed=0 legacy_serial_console = 0 default console speed = 115740 <- find_legacy_serial_port() console [udbg0] enabled setup_arch: bootmem mpc834x_itx_setup_arch() arch: exit Top of RAM: 0x8000000, Total RAM: 0x8000000 Memory hole size: 0MB Zone PFN ranges: DMA 0x00000000 -> 0x00008000 Normal 0x00008000 -> 0x00008000 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x00000000 -> 0x00008000 On node 0 totalpages: 32768 free_area_init_node: node 0, pgdat c01b6224, node_mem_map c01d0000 DMA zone: 32512 pages, LIFO batch:7 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: root=/dev/ram rw console=ttyS0,115200 mem=128M IPIC (128 IRQ sources) at fdffd700 PID hash table entries: 512 (order: 9, 2048 bytes) time_init: decrementer frequency = 66.666666 MHz time_init: processor frequency = 399.999996 MHz clocksource: timebase mult[3c00001] shift[22] registered clockevent: decrementer mult[1111] shift[16] cpu[0] -> check_legacy_serial_console() console was specified ! Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) SC3000 - After vfs_caches_init_early -1 SC3000 - After vfs_caches_init_early-2 Memory: 127912k/131072k available (1688k kernel code, 3000k reserved, 68k data,)SC3000 - After vfs_caches_init_early-3 SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Calibrating delay loop... 133.12 BogoMIPS (lpj=266240) On 12/7/09, Scott Wood <scottw...@freescale.com> wrote: > > On Sun, Dec 06, 2009 at 10:41:25PM -0800, ajij...@gmail.com wrote: > > Hi > > > > We have an MPC8343EA based custom board. > > > > I am not able to get Linux up and running in this. No serial output to > debug further. > > U-boot shows correct 'bdinfo' & 'clocks' output. > > inux hangs at machine_probe. > > Check that the platform file you're intending to use matches the compatible > field in the root node of the device tree -- and that said platform file is > actually being built. > > > -Scott >
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev