[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can I install debian on a e300 board?



-------- Original-Nachricht --------
> Datum: Sat, 04 Jun 2011 10:33:31 +0800
> Von: Bear <jilingshu@gmail.com>
> An: Gerhard Pircher <gerhard_pircher@gmx.net>
> CC: debian-powerpc@lists.debian.org
> Betreff: Re: Can I install debian on a e300 board?

> hi,
> Thanks for your help and I have successfully run my custom kernel on my 
> board via loading a fdt file:
> 
> U-Boot 1.3.0 (Dec 22 2008 - 11:19:29) MPC83XX
> 
> Reset Status:
> 
> CPU:   e300c3, MPC8313E, Rev: 21 at 333.333 MHz, CSB:  166 MHz
> Board: Freescale MPC8313ERDB
> I2C:   ready
> DRAM:  128 MB
> FLASH:  8 MB
> NAND:  32 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   TSEC0, TSEC1 [PRIME]
> Hit any key to stop autoboot:  0
> =>
> => setenv serverip 192.168.0.104
> => setenv loadaddr 0x01000000
> => setenv fdtaddr 0x02000000
> => dhcp
> Speed: 100, full duplex
> BOOTP broadcast 1
> DHCP client bound to address 192.168.0.103
> Using TSEC1 device
> TFTP from server 192.168.0.104; our IP address is 192.168.0.103
> Filename 'uImage'.
> Load address: 0x1000000
> Loading: #################################################################
>          
> #################################################################
>           ########
> done
> Bytes transferred = 2021460 (1ed854 hex)
> => tftp 0x02000000 mpc8313erdb.dtb
> Speed: 100, full duplex
> Using TSEC1 device
> TFTP from server 192.168.0.104; our IP address is 192.168.0.103
> Filename 'mpc8313erdb.dtb'.
> Load address: 0x2000000
> Loading: #
> done
> Bytes transferred = 7721 (1e29 hex)
> => bootm 0x01000000 - 0x02000000
> ## Booting image at 01000000 ...
>     Image Name:   Linux-2.6.39.1
>     Created:      2011-06-03  16:24:13 UTC
>     Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>     Data Size:    2021396 Bytes =  1.9 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... OK
>     Booting using the fdt at 0x2000000
>     Loading Device Tree to 007fd000, end 007fee28 ... OK
> Using MPC831x RDB machine description
> Linux version 2.6.39.1 (bear@debian) (gcc version 4.4.5 (Debian 4.4.5-8) 
> ) #1 Fri Jun 3 23:40:59 CST 2011
> bootconsole [udbg0] enabled
> setup_arch: bootmem
> mpc831x_rdb_setup_arch()
> Found FSL PCI host bridge at 0x00000000e0008500. Firmware bus number: 0->0
> PCI host bridge /sleep-nexus/pci@e0008500 (primary) ranges:
>   MEM 0x0000000090000000..0x000000009fffffff -> 0x0000000090000000
>   MEM 0x0000000080000000..0x000000008fffffff -> 0x0000000080000000
> Prefetch
>    IO 0x00000000e2000000..0x00000000e20fffff -> 0x0000000000000000
> arch: exit
> Zone PFN ranges:
>    DMA      0x00000000 -> 0x00008000
>    Normal   empty
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
>      0: 0x00000000 -> 0x00008000
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
> Kernel command line: root=/dev/ram console=ttyS0,115200
> PID hash table entries: 512 (order: -1, 2048 bytes)
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 124524k/131072k available (4080k kernel code, 6548k reserved, 
> 148k data, 1107k bss, 184k init)
> Kernel virtual memory layout:
>    * 0xfffdf000..0xfffff000  : fixmap
>    * 0xfdefb000..0xfe000000  : early ioremap
>    * 0xc9000000..0xfdefb000  : vmalloc & ioremap
> SLUB: Genslabs=15, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> NR_IRQS:512 nr_irqs:512 16
> IPIC (128 IRQ sources) at c9000700
> clocksource: timebase mult[6000002] shift[22] registered
> pid_max: default: 32768 minimum: 301
> Mount-cache hash table entries: 512
> NET: Registered protocol family 16
> 
> PCI: Probing PCI hardware
> bio: create slab <bio-0> at 0
> vgaarb: loaded
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> Switching to clocksource timebase
> Switched to NOHz mode on CPU #0
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> TCP reno registered
> UDP hash table entries: 256 (order: 0, 4096 bytes)
> UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
> NET: Registered protocol family 1
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> RPC: Registered tcp NFSv4.1 backchannel transport module.
> JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
> msgmni has been set to 245
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO 0xe0004500 (irq = 16) is a 16550A
> console [ttyS0] enabled, bootconsole disabled
> console [ttyS0] enabled, bootconsole disabled
> serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 17) is a 16550A
> brd: module loaded
> loop: module loaded
> fe000000.flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer 
> ID 0x000001 Chip ID 0x001001
> Amd/Fujitsu Extended Query Table at 0x0040
>    Amd/Fujitsu Extended Query version 1.3.
> fe000000.flash: Swapping erase regions for top-boot CFI table.
> number of CFI chips: 1
> cmdlinepart partition parsing not available
> RedBoot partition parsing not available
> fsl-lbc e0005000.localbus: read_byte beyond end of buffer
> fsl-lbc e0005000.localbus: read_byte beyond end of buffer
> fsl-lbc e0005000.localbus: read_byte beyond end of buffer
> NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 
> 3,3V 8-bit)
> cmdlinepart partition parsing not available
> RedBoot partition parsing not available
> Creating 3 MTD partitions on "e2800000.flash":
> 0x000000000000-0x000000100000 : "u-boot"
> 0x000000100000-0x000000400000 : "kernel"
> 0x000000400000-0x000002000000 : "fs"
> eLBC NAND device at 0xe2800000, bank 1
> Fixed MDIO Bus: probed
> fsl-gianfar e0024000.ethernet: enabled errata workarounds, flags: 0x7
> eth0: Gianfar Ethernet Controller Version 1.2, 04:00:00:00:00:0a
> eth0: Running with NAPI enabled
> eth0: RX BD ring size for Q[0]: 256
> eth0: TX BD ring size for Q[0]: 256
> fsl-gianfar e0025000.ethernet: enabled errata workarounds, flags: 0x7
> eth1: Gianfar Ethernet Controller Version 1.2, 04:00:00:00:00:0b
> eth1: Running with NAPI enabled
> eth1: RX BD ring size for Q[0]: 256
> eth1: TX BD ring size for Q[0]: 256
> Freescale PowerQUICC MII Bus: probed
> Freescale PowerQUICC MII Bus: probed
> e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
> e100: Copyright(c) 1999-2006 Intel Corporation
> usbmon: debugfs is not available
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> uhci_hcd: USB Universal Host Controller Interface driver
> /soc8313@e0000000/usb@23000: Invalid 'dr_mode' property, fallback to 
> host mode
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
> fsl-ehci fsl-ehci.0: irq 38, io mem 0xe0023000
> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> i2c /dev entries driver
> mpc-i2c e0003000.i2c: timeout 1000000 us
> rtc-ds1307 0-0068: rtc core: registered ds1339 as rtc0
> mpc-i2c e0003100.i2c: timeout 1000000 us
> md: linear personality registered for level -1
> md: raid0 personality registered for level 0
> md: raid1 personality registered for level 1
> TCP cubic registered
> NET: Registered protocol family 17
> Registering the dns_resolver key type
> rtc-ds1307 0-0068: setting system clock to 2000-01-03 15:08:10 UTC 
> (946912090)
> md: Waiting for all devices to be available before autodetect
> md: If you don't use raid, use raid=noautodetect
> md: Autodetecting RAID arrays.
> md: Scanned 0 and added 0 devices.
> md: autorun ...
> md: ... autorun DONE.
> List of all partitions:
> 1f00            8192 mtdblock0  (driver?)
> 1f01            1024 mtdblock1  (driver?)
> 1f02            3072 mtdblock2  (driver?)
> 1f03           28672 mtdblock3  (driver?)
> No filesystem could mount root, tried:  ext3 ext2
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(1,0)
> Rebooting in 180 seconds..
> 
> But unfortunately, it seems like the kernel still need a rootfs? I have 
> a SD card and I wanna install debian into it. Is there anyone who can 
> tell me how to do? Thanks.
I don't know, if your board has a specific SD/MMC card controller,
but you could try to enable "MMC_SPI" or "MMC_SDHCI_OF" with "make menuconfig".

> BTW: The official installer in Business Card CD seems not work with me:
> U-Boot 1.3.0 (Dec 22 2008 - 11:19:29) MPC83XX
> 
> Reset Status:
> 
> CPU:   e300c3, MPC8313E, Rev: 21 at 333.333 MHz, CSB:  166 MHz
> Board: Freescale MPC8313ERDB
> I2C:   ready
> DRAM:  128 MB
> FLASH:  8 MB
> NAND:  32 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   TSEC0, TSEC1 [PRIME]
> Hit any key to stop autoboot:  0
> => setenv serverip 192.168.0.104
> => setenv fdtaddr 0x02000000
> => setenv loadaddr 0x01000000
> => dhcp
> Speed: 100, full duplex
> BOOTP broadcast 1
> DHCP client bound to address 192.168.0.103
> Using TSEC1 device
> TFTP from server 192.168.0.104; our IP address is 192.168.0.103
> Filename 'uImage'.
> Load address: 0x1000000
> Loading: #################################################################
>          
> #################################################################
>          
> #################################################################
>          
> #################################################################
>          
> #################################################################
>          
> #################################################################
>          
> #################################################################
>           ####################
> done
> Bytes transferred = 6967619 (6a5143 hex)
> => tftp 0x02000000 mpc8313erdb.my.dtb
> Speed: 100, full duplex
> Using TSEC1 device
> TFTP from server 192.168.0.104; our IP address is 192.168.0.103
> Filename 'mpc8313erdb.my.dtb'.
> Load address: 0x2000000
> Loading: #
> done
> Bytes transferred = 7721 (1e29 hex)
> => bootm 0x01000000 - 0x02000000
> ## Booting image at 01000000 ...
>     Image Name:   Debian-businesscard-squeeze
>     Created:      2011-06-03  11:37:07 UTC
>     Image Type:   PowerPC Linux Kernel Image (uncompressed)
>     Data Size:    6967555 Bytes =  6.6 MB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
> OK
>     Booting using the fdt at 0x2000000
>     Loading Device Tree to 007fd000, end 007fee28 ... OK
> 
> and it hang.
As I mentioned before, the platform support/setup code for your board
isn't compiled into the Debian kernel. Thus the kernel can't identify
the "compatible = "MPC8313ERDB", "MPC831xRDB", "MPC83xxRDB";" property
in the device tree for your board.

Gerhard
-- 
NEU: FreePhone - kostenlos mobil telefonieren!			
Jetzt informieren: http://www.gmx.net/de/go/freephone


Reply to: