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 28 Aug 2008 07:57 AM by  htjgdw@hotmail.com
How to porting i.MX27ADS Linux BSP to MX27litekit?
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
htjgdw@hotmail.com
New Member
New Member
Posts:


--
10 Aug 2008 06:26 PM
    Hi, all friends,
    I'm trying to complie i.MX27ADS linux kernel and running on MX27litekit.
    Compile has finished and get zImage file. But when I download it to board, it hangs after compressing.......
    So could anyone encounter this thing? And how to resolve it?
    If could any help, I'll appreciate for it.
    zyzyis@gmail.com
    New Member
    New Member
    Posts:


    --
    19 Aug 2008 05:12 AM
    Hi,

    Actually the kernel does not hang just after the uncompressing but hangs somewhere in the UART driver. The reason that you did not get any output is because the serial port driver between MX27ADS and MX27LITEKIT is different. And because of that, the console ttymxc0 in your kernel command fails and printk is not able to print any thing on the screen. You can figure this out by doing a printk trick that inserts a printascii to print the printk_buf.

    One solution I did is to port the driver from mainline mx27ads kernel which uses the IMX console driver instead of the MXC console driver in the Freescale BSP. Or you can do in the other way round that you uses the mainline kernel as a code base and port the rest of the drivers from Freescale BSP into the mainline kernel.

    I'm still debugging the NAND driver right now and I will submit my code until everything works well.

    Cheers,
    htjgdw@hotmail.com
    New Member
    New Member
    Posts:


    --
    19 Aug 2008 09:05 AM
    Hi,zyzyis
    Thank you for your help.
    I'll try the first solution you adviced. Thank you:)
    B.R.
    Wei Huang
    htjgdw@hotmail.com
    New Member
    New Member
    Posts:


    --
    25 Aug 2008 09:49 PM
    Hi, all
    Unfortunately, I think don't have additional time and energy to finish porting linux on MX27LITEKIT. Hope anyone can complete this issue.
    zyzyis@gmail.com
    New Member
    New Member
    Posts:


    --
    28 Aug 2008 06:56 AM
    Yeah, I hope someone can help us too. I'm still having problem with the Ethernet and SD card drivers which make me not able to boot the RFS.

    Here is my boot message:
    Quote:
    Linux version 2.6.19.2 (yin@localhost.localdomain) (gcc version 4.2.1) #111 PREEMPT Thu Aug 28 14:22:42 CEST 2008
    CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
    Machine: Freescale i.MX27ADS
    Memory policy: ECC disabled, Data cache writeback
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    Built 1 zonelists. Total pages: 32512
    Kernel command line: console=ttymxc0,115200 root=/dev/mtdblock3 init=/sbin/init ip=dhcp
    MXC IRQ initialized
    PID hash table entries: 512 (order: 9, 2048 bytes)
    Actual CLOCK_TICK_RATE is 14250000 Hz
    Actual HRT CLOCK_TICK_RATE is 14250000 Hz
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 128MB = 128MB total
    Memory: 126464KB available (2632K code, 592K data, 96K init)
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    NET: Registered protocol family 16
    MXC GPIO hardware
    AIPI VA base: 0xd4000000
    Generic PHY: Registered new driver
    SCSI subsystem initialized
    CSPI: mxc_spi-1 probed
    CSPI: mxc_spi-2 probed
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    MXC I2C driver
    mc13783 Rev 3.3 FinVer 0 detected
    Device spi1.0 probed
    PMIC Character device: successfully loaded
    PMIC RTC successfully probed
    PMIC Light successfully loaded
    PMIC Power successfully probed
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
    TCP: Hash tables configured (established 4096 bind 2048)
    TCP reno registered
    MX27: Power management module initialized
    Freescale i.MX27 Dynamic Power Management.
    NetWinder Floating Point Emulator V0.97 (double precision)
    yaffs Aug 26 2008 18:41:23 Installing.
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    Real TIme clock Driver v1.0
    MXC WatchDog Driver 2.0
    MXC Watchdog # 0 Timer: initial timeout 60 sec
    Serial: IMX driver
    loop: loaded (max 8 devices)
    SMSC LAN83C185: Registered new driver
    FEC ENET Version 0.2
    eth0: ethernet 00:08:ee:01:f8:56
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
    fec: PHY @ 0x1f, ID 0x0007c0c3 -- unknown PHY!
    MXC: IDE driver, (c) 2004-2006 Freescale Semiconductor
    ATA interface call clock enable ATA CLK
    mxc_ide_resetproc: resetting ATA controller
    ide0: Bus empty, interface released.
    MXC MTD nor Driver 2.0
    mxc_nor_flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
    Intel/Sharp Extended Query Table at 0x0035
    cfi_cmdset_0001: Erase suspend on write enabled
    Searching for RedBoot partition table in mxc_nor_flash.0 at offset 0x1f0000
    No RedBoot partition table detected in mxc_nor_flash.0
    Creating 2 MTD partitions on "mxc_nor_flash.0":
    0x00000000-0x00040000 : "LoLo Bootloader"
    0x00040000-0x00050000 : "Bootloader config"
    MXC MTD nand Driver 2.0
    NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit)
    Scanning device for bad blocks
    Bad eraseblock 1945 at 0x01e64000
    Bad eraseblock 2561 at 0x02804000
    Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit":
    0x00000000-0x02000000 : "NAND RootFS"
    0x00000000-0x04000000 : "<NULL>"
    0x00000000-0x04000000 : "<NULL>"
    0x00000000-0x04000000 : "<NULL>"
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    i2c /dev entries driver
    Driver for 1-wire Dallas network protocol.
    Serial: MXC OWire driver
    SSI module loaded successfully
    PMIC Audio driver loading...
    PMIC Battery successfully probed
    PMIC Connectivity driver loading..
    DPTC controller initialized
    SEC: mxc_sec_mod_init() called
    MXC MMC/SD driver
    mxcmci: probe of mxcmci.0 failed with error -22
    mxcmci: probe of mxcmci.1 failed with error -22
    Advanced Linux Sound Architecture Driver Version 1.0.13 (Tue Nov 28 14:07:24 2006 UTC).
    Control ALSA component registered
    ALSA device list:
    #0: MXC Freescale with PMIC
    TCP cubic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    Time: mx27_hrt clocksource has been installed.
    Sending DHCP requests ...... timed out!
    fec_stop : Graceful transmit stop did not complete !
    IP-Config: Retrying forever (NFS root)...
    Sending DHCP requests ...
    htjgdw@hotmail.com
    New Member
    New Member
    Posts:


    --
    28 Aug 2008 07:57 AM
    That is good enough for your work.
    I hope I can see the boot information on my board in the future:)
    You are not authorized to post a reply.