Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 22 Jan 2009 03:29 PM by  mikee@logicpd.com
about linux bootup
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
xianglj@jiasin.com
New Member
New Member
Posts:


--
07 Jan 2009 10:53 PM
    As I flashed the "uImage-beta"and "rootfstype-beta.jffs2" into the board step by step followed by 1008573A_MPC8360_U-Boot_Labs.pdf,and then boot up:

    U-Boot 1.1.3 R6 (Oct 2 2007 - 16:13:46) MPC83XX

    Clock configuration:
    Coherent System Bus: 330 MHz
    Core: 660 MHz
    QE: 495 MHz
    Local Bus Controller: 330 MHz
    Local Bus: 41 MHz
    DDR: 330 MHz
    DDR Secondary: 330 MHz
    SEC: 110 MHz
    I2C1: 330 MHz
    I2C2: 330 MHz
    CPU: MPC8360E, Rev: 21 at 660 MHz
    RCW: 0xA0600004 0x0A04008F
    Board: Freescale MPC8360 Com Express - Pilot
    I2C: ready
    DRAM: DDR 256 MB
    FLASH: 8 MB
    Read production data: done
    Part Number: 1008746
    Model Name : COMMPC8360E-10-2752FCR
    Model Rev : A
    Serial # : 5007M03738
    board_get_nth_enetaddr:1093 which 1 1:d8:77
    board_get_nth_enetaddr:1093 which 2 1:d8:76
    board_get_nth_enetaddr:1093 which 3 1:d8:75
    Using external PCI clock
    PCI 32bit
    In: serial
    Out: serial
    Err: serial
    NAND: 64 MB
    Net: FSL GETH0
    Hit any key to stop autoboot: 0
    ## Booting image at ff860000 ...
    Image Name: Linux-2.6.11
    Image Type: PowerPC Linux Kernel Image (gzip compressed)
    Data Size: 1322864 Bytes = 1.3 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK
    Linux version 2.6.11 (peter@blackhole) (gcc version 3.4.3) #8 Thu Sep 6 14:17:23 EDT 2007
    Built 1 zonelists
    Kernel command line: root=/dev/mtdblock4 rootfstype=jffs2 rw console=ttyS0,115200
    IPIC (128 IRQ sources, 8 External IRQs) at fe000700
    QE IC (64 IRQ sources) at fe100080
    PID hash table entries: 2048 (order: 11, 32768 bytes)
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 256768k available (2168k kernel code, 552k data, 116k init, 0k highmem)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    scheduling while atomic: swapper/0x00000002/0
    Call trace: [c021a41c] [c00041c0] [c029cc38] [c029cb80] [c028e608] [000035fc]
    NET: Registered protocol family 16
    PCI: Probing PCI hardware
    PCI: bridge rsrc 0..ffffff (100), parent c026df80
    PCI: bridge rsrc 80000000..9fffffff (200), parent c026df64
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    Console: switching to colour frame buffer device 80x30
    spi_m25p40 version 1.0 init
    register char dev with major 254
    Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
    ttyS0 at MMIO 0xe0004500 (irq = 9) is a 16550A
    ttyS1 at MMIO 0xe0004600 (irq = 10) is a 16550A
    pci_register_driver:403 error 0
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
    loop: loaded (max 8 devices)
    MPC8360E PB flash device: 800000 at ff800000 Partition number 4
    MPC8360E Com Express Flash Map Info: Found 1 x16 devices at 0x0 in 16-bit bank
    check_cmd_set:227 type 0x0001
    Intel/Sharp Extended Query Table at 0x010A
    Using buffer write method
    cfi_cmdset_0001: Erase suspend on write enabled
    Creating 4 MTD partitions on "MPC8360E Com Express Flash Map Info":
    0x00000000-0x00060000 : "u-boot"
    0x00060000-0x001c0000 : "Kernel"
    0x001c0000-0x007e0000 : "JFFS2"
    0x007e0000-0x00800000 : "broken CFI code"
    MPC8360E PB flash device initialized
    Attempting to connect to MPC83XX Nand via UPM
    NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit)
    Scanning device for bad blocks
    Creating 2 MTD partitions on "NAND 64MiB 3,3V 8-bit":
    0x00000000-0x00800000 : "Com Express NAND FS 0"
    0x00800000-0x04000000 : "Com Express NAND FS 1"
    Connected to MPC86XX Nand via UPM
    driver Freescale MPC8360/MPC832x USB Host Driver, Revision: 1.0
    config_transceiver: mode 2
    fsl-qe-usb fsl-qe-usb0: at 0xfe1006c0,irq 139
    fsl-qe-usb fsl-qe-usb0: new USB bus registered, assigned bus number 1
    usb usb1: Product: FHCI HOST Controller
    usb usb1: Manufacturer: Linux 2.6.11 fsl-qe-usb
    usb usb1: SerialNumber: fsl-qe-usb
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    config_transceiver: mode 4
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.0:USB HID core driver
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    eth0: Running with NAPI enabled
    eth1: Running with NAPI enabled
    eth2: Running with NAPI enabled
    eth3: Running with NAPI enabled
    NET: Registered protocol family 2
    IP: routing cache hash table of 2048 buckets, 16Kbytes
    TCP established hash table entries: 16384 (order: 5, 131072 bytes)
    TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
    TCP: Hash tables configured (established 16384 bind 16384)
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    Empty flash at 0x0069d17c ends at 0x0069d200
    VFS: Mounted root (jffs2 filesystem).
    Freeing unused kernel memory: 116k init
    Setting the hostname to freescale
    Mounting filesystems
    Setting up networking on loopback device:
    Setting up networking on eth0:
    udhcpc (v0.9.9-pre) started
    udhcpc[784]: udhcpc (v0.9.9-pre) started
    eth0: Setting MII master to UCC0
    eth0: PHY is Broadcom 5481 (143bca2)
    jffs2_get_inode_nodes(): Data CRC failed on node at 0x0069d974: Read 0x82aac52a, calculated 0xf462e0ee
    Sending discover...
    udhcpc[784]: Sending discover...
    Sending discover...
    udhcpc[784]: Sending discover...
    Sending discover...
    udhcpc[784]: Sending discover...
    No lease, forking to background.
    udhcpc[784]: No lease, forking to background.
    Setting up networking on eth1:
    udhcpc (v0.9.9-pre) started
    udhcpc[798]: udhcpc (v0.9.9-pre) started
    eth1: Setting MII master to UCC1
    eth1: PHY is Broadcom 5481 (143bca2)
    Sending discover...
    udhcpc[798]: Sending discover...
    Sending discover...
    udhcpc[798]: Sending discover...
    Sending discover...
    udhcpc[798]: Sending discover...
    No lease, forking to background.
    udhcpc[798]: No lease, forking to background.
    Starting inetd:
    Starting the dropbear ssh server:


    Welcome to Freescale Semiconductor Embedded Linux Environment

    !!!!! WARNING !!!!!!!

    The default password for the root account is: root
    please change this password using the 'passwd' command
    and then edit this message (/etc/issue) to remove this message
    freescale login: udhcpc[794]: Sending discover...
    udhcpc[794]: Sending discover...
    udhcpc[794]: Sending discover...
    udhcpc[808]: Sending discover...
    udhcpc[808]: Sending discover...
    udhcpc[808]: Sending discover...



    what's the meaning "udhcpc[794] & udhcpc[808]"? DO I have wrong env of uboot?
    TKS!
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    22 Jan 2009 03:29 PM
    Those messages should simply indicate that your kit is looking to receive a network address from a DHCP server.
    You are not authorized to post a reply.