Go to previous topic
Go to next topic
Last Post 09 Jun 2010 09:04 PM by  Sancho0330
How to load Linux onto the i.MX31 LITE KIT
 36 Replies
Author Messages

lee@protect-usinc.com



New Member


Posts:
New Member


--
02 Apr 2007 08:03 AM
    We installed the i.MX31ADS BSP to a Linux server along with the patches to convert it over to the i.MX31 LiteKit. Everything seems to have been installed correctly. I my self don't know much about Linux but we have another guy here who know a lot about Linux on big servers. I'm try to figure out how to get the linux kernel programmed on to the lite kit. Right now the lite kit has the logic loader boot loader (LoLo) installed. I can power up the board talk to the boot loader just fine.
    I'm just not sure as to what needs to be loaded? I don't know what file to load in? Don't know if I can even use logic loader to program the linux kernel. A few written instructions would be great.

    Second part. Once we get the kernel in will I be able to log into the board through the Ethernet? If so what is the default IP?
    Thanks
    David

    blb



    New Member


    Posts:
    New Member


    --
    18 Apr 2007 11:01 AM
    Ocean_Front_View,

    I'm trying to get linux installed on our lite kit as well. I was wondering if you would mind posting the steps you did to get the linux bsp patched and compiled? I surely would appreciate it.

    TIA,
    blb

    Pixel



    New Member


    Posts:
    New Member


    --
    19 Apr 2007 08:40 AM
    Hi Ocean_Fron_View!!

    I add with blb.... would be very nice you post the steps you did to get linux bsp patched and compiled!!

    Thanks a lot!!

    randyc



    New Member


    Posts:
    New Member


    --
    23 Apr 2007 11:42 AM
    If I could solve this once and for all I would be golden:

    Internal error: Oops - undefined instruction: 0 [#6]
    Modules linked in:
    CPU: 0
    PC is at __link_path_walk+0x13c/0x1014
    LR is at nfs_permission+0x1f0/0x20c
    pc : [<c0093ac0>] lr : [<c00dcda0>] Not tainted
    sp : c03c3d78 ip : c27b9001 fp : c03c3dc4

    Here are my steps:

    My development system was RedHat 2.1AS

    1. Gather the bits needed

    download ltib package and mount iso or burn a CD. This came
    from the Freescale site:
    imx31_ads_20070128-rel3-ltib.iso
    I burned it to a CD and then mounted it on my linux development
    box:
    mount -t iso9660 -o ro /dev/cdrom /cdrom

    download the patches from this site, thanks to Hasan Yilmaz:
    http://mx31.lbox.ca/download/
    save as /tmp/linux-2.6.16-mx31-lite1.patch
    save as /tmp/smsc911x.patch

    get the device file:
    http://www.arm.linux.org....achines/download.php
    save as /tmp/mach-types

    get the second stage device loader (also thanks to Hasan!):
    http://mx31.lbox.ca/download/bootloader.tar.gz
    save to /tmp/bootloader.tar.gz

    2. build main bitset

    install iso bits (run ./install)

    * Note you run "install" as a non-root user
    * I installed to /scratch

    build bits (cd /scratch/ltib-XXX; ./ltib -c)

    * Note, again run as a non-root user. You will be prompted
    to give this user sudo privledges.

    * Also when prompted, check the boxes for

    Leave sources after building

    which will force kernel extraction and compilation. Let
    build run from here, taking any defaults.

    3. apply the patches, insert new mach-types file

    cd /scratch/ltib-XXX/rpm/BUILD/linux-2.6.19.2
    patch -p1 < /tmp/linux-2.6.16-mx31-lite1.patch

    With the first patch you'll get errors. Look at the patch itself and edit
    the files directly. You can determine which files had issues by doing
    a find on "*.rej" files. ONLY RUN THE PATCH ONCE and then just fix
    the files. You can always see the original version of the file (*.orig)
    to compare to what's supposed to be happening.

    I had to fix:
    arch/arm/mach-mx3/Makefile
    include/asm-arm/arch-mxc/hardware.h
    drivers/ide/arm/mxc_ide.c

    patch -p1 < /tmp/smsc911x.patch

    (This second patch should have no issues)

    cd ../linux/arch/arm/tools
    cp mach-types mach-types.orig
    cp /tmp/mach-types .

    4. recompile the kernel using ltib environment

    cd /scratch/ltib-XXX
    ./ltib -c

    choose at the FIRST menu:

    Configure the kernel
    and make sure you are still leaving the source!

    choose at the second menu:

    System Type -->
    Freescale MXC Implementations -->
    MX3 Options -->

    and when given a chance enable "MX31lite", disable "MX31ADS"

    additionally, I had to comment out some of the includes in
    arch/arm/mach-mx3/mx31lite.c
    arch/arm/mach-mx3/usb_lite.c
    after the recompile failed because the patch created these files and
    they made reference to include files that do not exist beyond 2.6.16

    also, since I chose to disable the ADS and only enable the LITE, I
    had to move some of the values found only in include/asm-arm/arch-mxc
    board-mx31ads.h to board-mx31lite.h, the build will complain when it
    can't find some value. Otherwise, just enable the "MX31ADS" but be
    prepared for a LOT of warnings.


    This is also where I edited the values for network setup,
    name of NTP server, etc. I did not use DHCP but a static IP.
    I also had to turn on the ethernet device driver for SMSC911X
    family, which is what the lite board uses (eth0)

    5. build second stage device loader

    mkdir /scratch/bootloader
    cd /scratch/bootloader
    mv /tmp/bootloader.tar.gz .
    gzip -d bootloader.tar.gz
    tar -xvf bootloader.tar

    vi Makefile
    fix path for CC, LD, AS. My path to the bin subdir was
    /opt/freescale/usr/local/gcc-4.1.1-glibc-2.4-nptl-6/arm-none-linux-gnueabi/arm-none-linux-gnueabi/bin
    also fix LIBGCC path, which is same as above except ends in
    "lib" instead of "bin"

    vi bootloaderstg2.c
    change COMMAND_LINE to the values you want. Mine looks like
    this:

    #define COMMAND_LINE "console=ttymxc0 root=/dev/nfs
    nfsroot=129.148.25.210:/tftpboot/rootfs rw init=/linuxrc
    ip=129.148.25.28::129.148.25.98:255.255.255.0 noalign"

    129.148.25.210 is my RedHat build/distro machine
    129.148.25.28 is the IP of my lite board
    129.148.25.98 is my gateway
    255.255.255.0 is my netmask

    make loader
    cp loader /tftpboot

    6. Housecleaning on the development/deployment system

    shut off firewall if it's on
    install tftp server and nfs server (I used "serviceconf")
    mkdir /tftpboot
    ln -s /scratch/ltib-XXX/rootfs /tftpboot/rootfs

    cp /scratch/ltib-XXX/rootfs/boot/* /tftpboot

    vi /etc/exports and add this line:
    /tftpboot/rootfs 129.148.25.28(rw,no_root_squash,async)

    vi /etc/xinetd.d/tftp and make it look like this:
    service tftp
    {
    disable = no
    socket_type = dgram
    protocol = udp
    wait = yes
    user = root
    server = /usr/sbin/in.tftpd
    server_args = /tftpboot
    }

    /etc/init.d/xinetd restart
    /etc/init.d/nfsserver restart
    (or /usr/sbin/exportfs)

    7. Connect i.MX31 board to network/tip

    tip in to board by whatever style you prefer. I used a Sun serial
    port, with baud=115200

    at console prompt:

    losh> ifconfig sm0 129.148.25.28 255.255.255.0 129.148.25.98

    8. load up the images

    first load the "loader" by figuring out it's starting address and
    size. Like so:

    # objdump -f /tftpboot/loader

    /tftpboot/loader: file format elf32-littlearm
    architecture: arm, flags 0x00000112:
    EXEC_P, HAS_SYMS, D_PAGED
    start address 0x800d03a8

    # ls -al /tftpboot/loader
    -rwxr-xr-x 1 root wheel 35342 Mar 21 12:39 /tftpboot/loader

    note the size is 35342, starting address is 0x800d03a8.

    Load this on the ARM device:

    losh> load raw 0x800d03a8 35342 /tftp/129.148.25.210:/tftpboot/loader

    and you should see this:

    loading from /tftp/129.148.25.210:/tftpboot/loader:
    loading raw binary to 0x800d03a8 (ram) len 00008a0e:
    ........done
    file loaded
    losh> ls
    R : load 35342
    D : tftp 0
    D : etc 0
    D : dev 0
    losh>


    Now load the linux image. Determine it's size, the loading address
    is already determined by the loader.c code above.

    # ls -al /tftpboot/zImage
    -rwxr-xr-x 1 root wheel 1629660 Mar 27 11:40 /tftpboot/zImage

    load it on the ARM device

    losh> load raw 0x81000000 1629660 /tftp/129.148.25.210:/tftpboot/zImage
    loading from /tftp/129.148.25.210:/tftpboot/zImage:
    loading raw binary to 0x81000000 (ram) len 0018dd98:
    .............................................................
    .............................................................
    .............................................................
    ...................done
    file loaded
    losh> ls
    R : load 1629660
    D : tftp 0
    D : etc 0
    D : dev 0
    losh>

    0x81000000 was what Hasan told me to use
    zImage is the "kernel image that can be loaded with Redboot"


    Once this is done, you "exec" the image.

    losh> exec 0x800d03a8 -

    I got some warnings but eventually I saw the "freescale" hostname
    appear. I could log in (if I first zapped the password in the
    rootfs/etc/shadow file for root, no idea what that was!) and could
    set the password but eventually I would get something like the
    following and the kernel would crash:

    BUG: warning at kernel/softirq.c:120/_local_bh_enable()
    Unable to handle kernel NULL pointer dereference at virtual address 00000000
    pgd = c0004000
    [00000000] *pgd=00000000
    Internal error: Oops: 817 [#2]
    Modules linked in:
    CPU: 0
    PC is at preempt_return+0xc/0x24
    LR is at preempt_return+0x0/0x24


    sooooo close!

    Randy (randy.crihfield@sun.com)

    bwil@willers2000.de



    New Member


    Posts:
    New Member


    --
    07 May 2007 04:12 AM
    hi randy,
    thanks a lot for the step-by-step guide.
    just, my litekit is still not booting. it's just hangs after i issue the 'exec' command.
    not even a 'Uncompressing ...' message comes up.

    could you post your bootloader and kernel image?
    that would help me to narrow down the possible problem.

    thanks,

    ben

    bwil@willers2000.de



    New Member


    Posts:
    New Member


    --
    07 May 2007 08:12 AM
    randy,
    don't mind. i just got it working.
    i'm loading the bootloader using
    #load elf /tftp/...

    now.

    thanks,

    ben

    randyc



    New Member


    Posts:
    New Member


    --
    07 May 2007 08:21 AM
    Whoops, yes, that should have been elf for the loader and raw for the zImage.

    I still don't have it working in a stable manner; my board complains about a lot of bad memory ("marked unusable by vendor") and once I get to the linux login prompt it will eventually (within 15 minutes) crash fatally. If anyone gets something more reliable working, I would of course appreciate the correction to my above steps.

    Randy

    OradFarez



    New Member


    Posts:
    New Member


    --
    07 May 2007 03:20 PM
    Is it possible that the "bad memory" problem has something to do with the hardware problems Logic PD has had? I have no idea which board revision you have and maybe you will never get it to be stable due to the hardware problems!

    If you know what to do, I would try dropping the memory clock from 133MHz to 66MHz and see if it gets more stable. This would need to be done before the memory controller is setup because the clock cannot be changed mid-operation.

    kurtl@logicpd.com



    New Member


    Posts:
    New Member


    --
    07 May 2007 06:21 PM
    OradFarez and group,

    The memory problem OradFarez refers to was LPD WindowsCE BSP software initialization bug that has been resolved. The fix works on all known hardware revisions.

    Good luck,
    -K

    bwil@willers2000.de



    New Member


    Posts:
    New Member


    --
    08 May 2007 05:11 AM
    randy,

    my system is working fine now. it's booting from
    nfs and flash as well. i pretty much followed your instructions on this.
    later on i just moved the kernel, rootfs and the bootloader to nand-flash.

    your bad memory appears to be in the flash, which you are not using, if i'm reading your instructions correctly.
    if you could post some logs, i could compare those to mine.


    thanks,

    ben.

    thehexa@gmail.com



    New Member


    Posts:
    New Member


    --
    09 May 2007 02:54 AM
    first of all, thanks randy, what you wrote is helping a lot.

    It is good to see that bwillers got it running nicely so there is still hope

    i'll post my results later, hopefully with a working system on my hands

    hasanhuseyin.yilmaz@vestel.com.tr



    New Member


    Posts:
    New Member


    --
    10 May 2007 01:51 AM
    Hi all
    does my patch work correctly on 2.6.19.2 kernel? it is intended to use with 2.6.16 kernel. I could prepare another patch for 2.6.19.2. if you want to use it. Can anyone give me description of the errors they see in kernel?
    Regards

    randyc



    New Member


    Posts:
    New Member


    --
    10 May 2007 09:18 AM
    Glad it's working for some of you, I look forward to it working for ME!

    Here is the error I am currently seeing, since I don't know beans about Linux I have no idea what to do or even where to start. Any hints would be much appreciated!

    MXC keypad loaded
    input: mxckpd as /class/input/input0
    i2c /dev entries driver
    Driver for 1-wire Dallas network protocol.
    Serial: MXC OWire driver
    IPU Post-filter loading
    SSI module loaded successfully
    PMIC Audio driver loading...
    PMIC Connectivity driver loading..
    DVFS & DPTC: using 27MHz CKIH table
    Unable to handle kernel NULL pointer dereference at virtual address 00000148
    pgd = c0004000
    [00000148] *pgd=00000000
    Internal error: Oops: 5 [#1]
    Modules linked in:
    CPU: 0
    PC is at spi_sync+0x3c/0x6c
    LR is at pmic_read+0x8c/0xc4
    pc : [<c018dff4>] lr : [<c01b5760>] Not tainted
    sp : c03e5e48 ip : c03e5e78 fp : c03e5e74
    r10: 00000000 r9 : 00000000 r8 : c03e5efc
    r7 : 00000000 r6 : c03e5e7c r5 : c03e5e7c r4 : c03e5e4c
    r3 : c018e024 r2 : c03e5e50 r1 : c03e5e7c r0 : 00000000
    Flags: nZcv IRQs on FIQs on Mode SVC_32 Segment kernel
    Control: C5387D
    Table: 80004000 DAC: 00000017
    Process swapper (pid: 1, stack limit = 0xc03e4250)
    Stack: (0xc03e5e48 to 0xc03e6000)
    Backtrace:
    [<c018dfb8>] (spi_sync+0x0/0x6c) from [<c01b5760>] (pmic_read+0x8c/0xc4)
    r7 = C03E5EA8 r6 = C03E5E7C r5 = C03E5ECC r4 = 00000000
    [<c01b56d4>] (pmic_read+0x0/0xc4) from [<c01b4c78>] (pmic_write_reg+0x30/0x68)
    r8 = 00000000 r7 = 00000001 r6 = 0000001D r5 = 0000003F
    r4 = 00000018
    [<c01b4c48>] (pmic_write_reg+0x0/0x68) from [<c01c2454>] (pmic_power_regulator_set_voltage+0x1f4/0x200)
    r6 = 00000000 r5 = 00000000 r4 = FF600400
    [<c01c2260>] (pmic_power_regulator_set_voltage+0x0/0x200) from [<c01c32ec>] (set_pmic_voltage+0x2c/0x6c)
    [<c01c32c0>] (set_pmic_voltage+0x0/0x6c) from [<c01c33b0>] (set_dptc_wp+0x84/0xa4)
    r5 = 00000000 r4 = C035E3CC
    [<c01c332c>] (set_dptc_wp+0x0/0xa4) from [<c001b8d0>] (init_dptc_controller+0x8c/0xec)
    r6 = 00000000 r5 = 00000000 r4 = C035E3CC
    [<c001b844>] (init_dptc_controller+0x0/0xec) from [<c001b9bc>] (dvfs_dptc_init+0x8c/0x27c)
    r5 = C035E3CC r4 = C02A90CC
    [<c001b930>] (dvfs_dptc_init+0x0/0x27c) from [<c00260c4>] (init+0x98/0x278)
    r8 = 00000000 r7 = 00000001 r6 = C03E4000 r5 = C0020EE4
    r4 = C0021444
    [<c002602c>] (init+0x0/0x278) from [<c0047b84>] (do_exit+0x0/0x978)
    r7 = 00000000 r6 = 00000000 r5 = 00000000 r4 = 00000000
    Code: e5814014 e5850008 e50b7028 e50b2024 (e5903148)
    <0>Kernel panic - not syncing: Attempted to kill init!

    I also see lots of message about "Bad eraseblock" but I am guess that is from my attempting to use /dev/nand which for me is a bust so far.

    Maybe this has something to do with the nand failure?

    mxc_nor_flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
    Support for command set 0003 not present
    gen_probe: No supported Vendor Command Set found
    mxc_nor_flash: probe of mxc_nor_flash.0 failed with error -5

    Randy

    blb



    New Member


    Posts:
    New Member


    --
    10 May 2007 04:50 PM
    randy,

    I was having the same issue. What I did was in the kernel configuration under "Drivers|Sound|Advanced Linux Sound Arch|ALSA Arm devices" I disabled the MXC PMIC and under "Drivers|MXC Support Drivers|MXC PMIC Support" I disabled this as well.

    Thanks for your detailed steps for getting the BSP going. It helped me out quite a bit.

    Barry

    randyc



    New Member


    Posts:
    New Member


    --
    10 May 2007 09:05 PM
    Thanks for the tip, Barry! Did you do anything else I didn't document? The sound error went away but I am still stuck with an NFS issue. Did you force the rootfs to use a different version of NFS somehow? Here's a typical error I am still seeing (and the system is still pretty unstable, bummer!)

    Randy

    Freeing init memory: 116K
    Setting the hostname to freescale
    Mounting /proc and /sys
    Internal error: Oops - undefined instruction: 0 [#1]
    Modules linked in:
    CPU: 0
    PC is at __link_path_walk+0x13c/0x1014
    LR is at nfs_permission+0x1f0/0x20c
    pc : [<c0093ac0>] lr : [<c00dcda0>] Not tainted
    sp : c205dd78 ip : c03b2001 fp : c205ddc4
    r10: 00000000 r9 : c03b2001 r8 : c03b2000
    r7 : c205c000 r6 : c2555c00 r5 : c205df00 r4 : 000041ed
    r3 : 00000000 r2 : 00000064 r1 : c205c000 r0 : 00000000
    Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user
    Control: C5387D
    Table: 8204C000 DAC: 00000015
    Process udev (pid: 776, stack limit = 0xc205c250)
    Stack: (0xc205dd78 to 0xc205e000)
    Backtrace:
    [<c0093984>] (__link_path_walk+0x0/0x1014) from [<c0094a18>] (link_path_walk+0x80/0x13c)
    [<c0094998>] (link_path_walk+0x0/0x13c) from [<c0094f4c>] (do_path_lookup+0x2d0/0x2f8)
    r8 = 00000001 r7 = C205DF00 r6 = 00000001 r5 = C03CE380
    r4 = FFFFFF9C
    [<c0094c7c>] (do_path_lookup+0x0/0x2f8) from [<c0095a48>] (__path_lookup_intent_open+0x54/0x94)
    [<c00959f4>] (__path_lookup_intent_open+0x0/0x94) from [<c0095b1c>] (path_lookup_open+0x24/0x2c)
    r7 = 00000003 r6 = FFFFFF9C r5 = C205DF00 r4 = 00020802
    [<c0095af8>] (path_lookup_open+0x0/0x2c) from [<c0095c90>] (open_namei+0x70/0x6b0)
    [<c0095c20>] (open_namei+0x0/0x6b0) from [<c0088460>] (do_filp_open+0x2c/0x4c)
    [<c0088434>] (do_filp_open+0x0/0x4c) from [<c00884d4>] (do_sys_open+0x54/0xe8)
    r5 = 00000000 r4 = 00020802
    [<c0088480>] (do_sys_open+0x0/0xe8) from [<c00885a0>] (sys_open+0x24/0x28)
    r8 = C0025F64 r7 = 00000005 r6 = 00019CC8 r5 = 00083354
    r4 = 00000000
    [<c008857c>] (sys_open+0x0/0x28) from [<c0025de0>] (ret_fast_syscall+0x0/0x2c)
    Code: 1a0003ab e1a0c009 e1a0000a e5d92000 (510b9038)
    Segmentation fault

    hasanhuseyin.yilmaz@vestel.com.tr



    New Member


    Posts:
    New Member


    --
    11 May 2007 08:52 AM
    I think your problem related to nfs servers permissions. please make sure you can mount nfs filesystem from another linux station. and check that if you can write and read from file system over nfs.

    blb



    New Member


    Posts:
    New Member


    --
    11 May 2007 10:38 AM
    Randy,

    Here is what my boot up sequence looks like:

    eth0: SMSC911x/921x identified at 0xc3200000, IRQ: 90
    eth0: SMSC911x MAC Address: 00:11:22:33:44:55
    eth0: link down
    Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
    ., OK
    IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.10.213
    IP-Config: Complete:
    device=eth0, addr=192.168.10.213, mask=255.255.255.0, gw=192.168.10.1,
    host=192.168.10.213, domain=blahblah.local, nis-domain=(none),
    bootserver=0.0.0.0, rootserver=192.168.10.225, rootpath=
    Looking up port of RPC 100003/2 on 192.168.10.225
    Looking up port of RPC 100005/1 on 192.168.10.225
    VFS: Mounted root (nfs filesystem).
    Freeing init memory: 112K
    Setting the hostname to freescale
    Mounting /proc and /sys
    Starting the hotplug events dispatcher udevd
    Synthesizing initial hotplug events
    Mounting filesystems

    Are you getting info about your ethernet device starting up?

    A couple of other things I did in the kernel configuration were under "drivers|MTD|RAM/ROM/Flashchips" enabled support for ST chips
    "drivers|Network Device Support|Ether(10 or 100 mbit)" enabled SMSC LAN911X and disabled CS89x0

    I also under "Target System Configuration | options |Network Setup" I enabled get network parameters using DHCP.

    I also had to get the NFS server running on my development system and to allow the litekit to attach

    HTH,
    Barry

    randyc



    New Member


    Posts:
    New Member


    --
    11 May 2007 11:02 AM
    Hello Barry!

    yes, I get the ethernet to configure correctly. I am using a static address not DHCP though. It does boot all the way to the login prompt sometimes, and I can change the root password, create files, etc. But if I touch the files "too much", say do a simple "ls" command like 10 times in a row, the system will either hang or give me that nfs_permissions problem. When it does that, it may or may not be fatal.

    once in a GREAT while it will boot up w/o any errors, but then start throwing errors once I log in. I will see if turning off the extra ether driver helps as you suggested.

    Hasan, I can indeed mount the file system correctly from another linux box, so the NFS is definately working on my server. It must be - I am as I said able to boot up to the login prompt and log in, you could not do that w/o the NFS working. It is just unstable, and I was wondering if others did something special that i was overlooking.

    my /etc/exports entry looks like this:

    /path/to/LTIB/rootfs 129.148.25.28(rw,no_root_squash,async)

    Randy

    blb



    New Member


    Posts:
    New Member


    --
    11 May 2007 11:08 AM
    Randy,

    My /etc/exports looks thus:

    path to LTIB/rootfs 192.168.10.* (rw, sync)

    Barry

    thehexa@gmail.com



    New Member


    Posts:
    New Member


    --
    14 May 2007 09:42 PM
    well, my system boots and i can use it a lot.
    I think the problem i am facing is at the ethernet driver.

    While im using the system via the serial conection everything works fine.
    But if I log via ssh and do some more extensive work (for example: ps aux or dmesg | less, etc) i get a kernel panic

    any ideas? i am using that driver randyc gave the link.

    kernel panic msg:


    Unable to handle kernel paging request at virtual address e01b78d8
    pgd = c198c000
    [e01b78d8] *pgd=00000000
    Internal error: Oops: 0 [#1]
    Modules linked in:
    CPU: 0
    PC is at 0xe01b78d8
    LR is at skb_copy_and_csum_bits+0x64/0x28c
    pc : [<e01b78d8>] lr : [<c01b78d8>] Not tainted
    sp : c2255a80 ip : 00000000 fp : c2255ac4
    r10: 00000000 r9 : c19a5448 r8 : c20e3a20
    r7 : 00000068 r6 : 00000008 r5 : 00000060 r4 : 00000060
    r3 : c19a5448 r2 : 00000000 r1 : c19a5448 r0 : f35fb8fd
    Flags: nZcv IRQs on FIQs on Mode SVC_32 Segment user
    Control: C5387D
    Table: 8198C000 DAC: 00000015
    Process sh (pid: 1650, stack limit = 0xc2254250)
    Stack: (0xc2255a80 to 0xc2256000)
    5a80: c2496ec0 00000000 c03019ec c023f650 c2255ac4 c2255aa0 c02202b8 00000008
    5aa0: c2255b28 00000060 00000000 c2666e40 c24c81ec c25d4224 c2255aec c2255ac8
    5ac0: c021dbc0 c01b7880 00000000 c1c3ca38 c2255b24 00000448 00000000 c24c81ec
    5ae0: c2255b24 c2255af0 c021d8b0 c021db88 c021db7c c2255b28 c2255b54 c20e3a20
    5b00: c2255b28 c24c81ec 00000060 c2666e40 c2667960 c25d4224 c2255b54 c2255b28
    5b20: c021da94 c021d868 c20e3a20 00000008 00000060 2018338a 00000000 00000448
    5b40: c2496e00 c20e3a20 c2255b84 c2255b58 c021f0bc c021da38 00000001 00000000
    5b60: 00000000 00000068 00000000 c2666e40 00000000 d201a8c0 c2255ba4 c2255b88
    5b80: c01b7040 c021efa4 c20e3a20 c2254000 00000000 c2666e40 c2255bc4 c2255ba8
    5ba0: c01f6dc4 c01b6f48 c2666e40 c2254000 c20e3a20 2701a8c0 c2255c14 c2255bc8
    5bc0: c01f870c c01f6b60 00000002 20000013 00000000 00000000 00000000 c1c3ca38
    5be0: c25c7ec0 c2668c38 c1c3ca38 c20e3a20 c0299908 00000000 c20e3a50 c02fbec4
    5c00: c2255cd4 0000008e c2255c34 c2255c18 c01d6204 c01f82d0 c20e3a50 c25d4210
    5c20: c20e3a20 c02fcf98 c2255c6c c2255c38 c01d68ac c01d60dc c2499800 c2254000
    5c40: c2692c00 c2517398 c2255dac c2255c58 c02fbeac c20e3a20 c2499800 00000008
    5c60: c2255c94 c2255c70 c01bd9d8 c01d6468 c009bb24 c20e3a20 c2499a60 ffffffff
    5c80: c2499800 00000000 c2255ccc c2255c98 c0161644 c01bd7f8 00000001 00000040
    5ca0: c01625a4 c24998bc c2499800 c02fbc28 c02fbc38 000042d6 c2254000 00000000
    5cc0: c2255cfc c2255cd0 c01bf7e4 c01614c0 c2254000 0000012c c2255d04 00000001
    5ce0: c02e8794 0000000a 00000003 00000002 c2255d1c c2255d00 c0048030 c01bf77c
    5d00: c0038590 00000000 0000ffff 00000001 c2255d2c c2255d20 c0048464 c0047fe4
    5d20: c2255d44 c2255d30 c00257cc c0048428 c0093ac8 ffffffff c2255dac c2255d48
    5d40: c00249e4 c0025788 c2668cdc 00000008 00000000 00000001 c2254000 c2255ec8
    5d60: c2254000 c1d8e000 c2668c38 c033e1c0 00000000 c2255dac c2255d90 c2255d90
    5d80: c009c13c c009c1a0 20000013 ffffffff c2255dac 00000000 c2255ec8 c2692360
    5da0: c2255dfc c2255db0 c0093794 c009c0a4 00000001 c0285888 c007b154 11163d8b
    5dc0: 00000005 c1928005 c03662a0 c2668c38 c2255dfc c1928000 c24f4818 c2255ec8
    5de0: c03662a0 c1928000 c2254000 c1928000 c2255e74 c2255e00 c0093a18 c0092990
    5e00: c24f4818 c03662a0 00060000 00000000 c2255f44 00000001 00000001 00000000
    5e20: 00000003 00000000 46492a67 00000000 00000000 00000000 c001f520 00000000
    5e40: c198c000 00000180 c2255f5c 00000002 00000000 c1928000 c03ad2c0 c2255ec8
    5e60: c2255ec8 00000001 c2255ea4 c2255e78 c0093f4c c00939a4 c2255ea4 c2255e88
    5e80: c1928000 00000001 c2255ec8 c1928000 c0024f64 00000005 c2255ec4 c2255ea8
    5ea0: c0094860 c0093c88 c2255f40 c2255ec8 000b72c8 000000c3 c2255f2c c2255ec8
    5ec0: c008cf14 c0094828 c25c4c38 c03662a0 00060000 00000000 c2255f44 00000001
    5ee0: 00000001 00000001 00000003 c1d8e000 46492a67 00000000 00000000 00000000
    5f00: c001f520 00000000 c198c000 00000180 c2255f5c 00000002 bea2e9d8 c2255f40
    5f20: c2255f3c c2255f30 c008d014 c008cefc c2255fa4 c2255f40 c008d038 c008d004
    5f40: c002a62c c005bd90 0000000c c03b41ed 00000008 00000000 00000000 ffffffff
    5f60: 000b7328 000b72c8 00000024 000a1d70 bea2ea68 00000005 c2255f9c c2255f88
    5f80: c002a6f0 c002a420 ffffffff 000b7328 000b7328 000b7328 00000000 c2255fa8
    5fa0: c0024de0 c008d024 000b7328 000b7328 000b7348 bea2e9d8 bea2e9d8 00000000
    5fc0: 000b7328 000b7328 000b72c8 000000c3 000b7348 bea2ea68 00000005 000a1d80
    5fe0: 0009c220 bea2e9d0 0004cd68 400f4e94 60000010 000b7348 00000000 00000000
    Backtrace:
    [<c01b7874>] (skb_copy_and_csum_bits+0x0/0x28c) from [<c021dbc0>] (skb_read_and_csum_bits+0x44/0x9c)
    [<c021db7c>] (skb_read_and_csum_bits+0x0/0x9c) from [<c021d8b0>] (xdr_partial_copy_from_skb+0x54/0x1d0)
    r6 = C24C81EC r5 = 00000000 r4 = 00000448
    [<c021d85c>] (xdr_partial_copy_from_skb+0x0/0x1d0) from [<c021da94>] (csum_partial_copy_to_xdr+0x68/0x150)
    [<c021da2c>] (csum_partial_copy_to_xdr+0x0/0x150) from [<c021f0bc>] (xs_udp_data_ready+0x124/0x1e0)
    r6 = C20E3A20 r5 = C2496E00 r4 = 00000448
    [<c021ef98>] (xs_udp_data_ready+0x0/0x1e0) from [<c01b7040>] (sock_queue_rcv_skb+0x104/0x124)
    r8 = D201A8C0 r7 = 00000000 r6 = C2666E40 r5 = 00000000
    r4 = 00000068
    [<c01b6f3c>] (sock_queue_rcv_skb+0x0/0x124) from [<c01f6dc4>] (udp_queue_rcv_skb+0x270/0x2e8)
    r7 = C2666E40 r6 = 00000000 r5 = C2254000 r4 = C20E3A20
    [<c01f6b54>] (udp_queue_rcv_skb+0x0/0x2e8) from [<c01f870c>] (udp_rcv+0x448/0x568)
    r7 = 2701A8C0 r6 = C20E3A20 r5 = C2254000 r4 = C2666E40
    [<c01f82c4>] (udp_rcv+0x0/0x568) from [<c01d6204>] (ip_local_deliver+0x134/0x228)
    [<c01d60d0>] (ip_local_deliver+0x0/0x228) from [<c01d68ac>] (ip_rcv+0x450/0x498)
    r6 = C02FCF98 r5 = C20E3A20 r4 = C25D4210
    [<c01d645c>] (ip_rcv+0x0/0x498) from [<c01bd9d8>] (netif_receive_skb+0x1ec/0x2a8)
    r7 = 00000008 r6 = C2499800 r5 = C20E3A20 r4 = C02FBEAC
    [<c01bd7ec>] (netif_receive_skb+0x0/0x2a8) from [<c0161644>] (smsc911x_poll+0x190/0x310)
    r8 = 00000000 r7 = C2499800 r6 = FFFFFFFF r5 = C2499A60
    r4 = C20E3A20
    [<c01614b4>] (smsc911x_poll+0x0/0x310) from [<c01bf7e4>] (net_rx_action+0x74/0x130)
    [<c01bf770>] (net_rx_action+0x0/0x130) from [<c0048030>] (__do_softirq+0x58/0xc4)
    r8 = 00000002 r7 = 00000003 r6 = 0000000A r5 = C02E8794
    r4 = 00000001
    [<c0047fd8>] (__do_softirq+0x0/0xc4) from [<c0048464>] (irq_exit+0x48/0x64)
    r6 = 00000001 r5 = 0000FFFF r4 = 00000000
    [<c004841c>] (irq_exit+0x0/0x64) from [<c00257cc>] (asm_do_IRQ+0x50/0x68)
    [<c002577c>] (asm_do_IRQ+0x0/0x68) from [<c00249e4>] (__irq_svc+0x44/0x80)
    r4 = FFFFFFFF
    [<c009c098>] (dput+0x0/0x218) from [<c0093794>] (__link_path_walk+0xe10/0x1014)
    r6 = C2692360 r5 = C2255EC8 r4 = 00000000
    [<c0092984>] (__link_path_walk+0x0/0x1014) from [<c0093a18>] (link_path_walk+0x80/0x13c)
    [<c0093998>] (link_path_walk+0x0/0x13c) from [<c0093f4c>] (do_path_lookup+0x2d0/0x2f8)
    r8 = 00000001 r7 = C2255EC8 r6 = C2255EC8 r5 = C03AD2C0
    r4 = C1928000
    [<c0093c7c>] (do_path_lookup+0x0/0x2f8) from [<c0094860>] (__user_walk_fd+0x44/0x64)
    [<c009481c>] (__user_walk_fd+0x0/0x64) from [<c008cf14>] (vfs_stat_fd+0x24/0x54)
    r7 = 000000C3 r6 = 000B72C8 r5 = C2255EC8 r4 = C2255F40
    [<c008cef0>] (vfs_stat_fd+0x0/0x54) from [<c008d014>] (vfs_stat+0x1c/0x20)
    r5 = C2255F40 r4 = BEA2E9D8
    [<c008cff8>] (vfs_stat+0x0/0x20) from [<c008d038>] (sys_stat64+0x20/0x44)
    [<c008d018>] (sys_stat64+0x0/0x44) from [<c0024de0>] (ret_fast_syscall+0x0/0x2c)
    r5 = 000B7328 r4 = 000B7328
    Code: bad PC value.
    <0>Kernel panic - not syncing: Aiee, killing interrupt handler!

    randyc



    New Member


    Posts:
    New Member


    --
    15 May 2007 08:35 AM
    My error dump looks similar to yours, hopefully someone can give us a hint on where to fix this:

    <1>Unable to handle kernel paging request at virtual address fffffffe
    pgd = c212c000
    [fffffffe] *pgd=80002021, *pte=00000000, *ppte=00000000
    Internal error: Oops: 17 3]
    Modules linked in:
    CPU: 0
    PC is at dput+0x28/0x218
    LR is at link_path_walk+0x118/0x13c
    pc : [<c009d0e0>] lr : [<c0094ad0>] Not tainted
    sp : c25c3da8 ip : c25c3dc8 fp : c25c3dc4
    r10: c2743000 r9 : c25c2000 r8 : c2743000
    r7 : c03922a0 r6 : c25c2000 r5 : c24eb998 r4 : fffffffe
    r3 : 00000000 r2 : 00000000 r1 : c030f210 r0 : fffffffe
    Flags: NzCv IRQs on FIQs on Mode SVC_32 Segment user
    Control: C5387D
    Table: 8212C000 DAC: 00000015
    Process klogd (pid: 800, stack limit = 0xc25c2250)
    Stack: (0xc25c3da8 to 0xc25c4000)
    3da0: c03922a0 fffffffe c24eb998 c25c3f00 c25c3e3c c25c3dc8
    3dc0: c0094ad0 c009d0c4 c24eb998 c03922a0 c0164a50 c24cb8bc c24cb800 00000101
    3de0: 00000001 00000000 c260f560 c2743000 c25c2000 4017a000 c25c3f64 c25c3f40
    3e00: c0088040 c00a0ca4 c0093628 00000001 00000000 c03d4120 c277d6e0 ffffff9c
    3e20: c03d1300 00000001 c25c3f00 00000001 c25c3e6c c25c3e40 c0094f6c c00949c4
    3e40: c008b030 c030ed90 ffffff9c ffffffe9 00000001 c25c3f00 c2743000 00000001
    3e60: c25c3e8c c25c3e70 c0095a68 c0094ca8 00000000 c25c3f00 ffffff9c 00000004
    3e80: c25c3ea4 c25c3e90 c0095b3c c0095a20 00000001 00000000 c25c3ef4 c25c3ea8
    3ea0: c0095cb0 c0095b24 00000001 c01c5ad4 000001b6 00000004 c031f7ac c277d6e0
    3ec0: c24cb800 00000008 c25c3efc 00000000 c25c3f00 ffffff9c 00000004 c2743000
    3ee0: c25c2000 4017a000 c25c3f64 c25c3ef8 c0088460 c0095c4c c25c3f00 c0162a30
    3f00: c20bf638 c03922a0 c0164a50 c24cb8bc c24cb800 00000101 00000001 00000000
    3f20: c260f560 c2743000 c25c2000 4017a000 c25c3f64 c25c3f40 c0088040 c00a0ca4
    3f40: c0093628 00000001 00000000 c03d4120 00000000 000001b6 c25c3f94 c25c3f68
    3f60: c00884d4 c0088440 c0039590 00000000 0000ffff 0009e318 00000008 0009e318
    3f80: 00000005 c0025f64 c25c3fa4 c25c3f98 c00885a0 c008848c 00000000 c25c3fa8
    3fa0: c0025de0 c0088588 0009e318 00000008 4016a5fc 00000000 000001b6 00000002
    3fc0: 0009e318 00000008 0009e318 00000005 00000008 00000000 4017a000 bea4772c
    3fe0: 000001b6 bea476c0 400cba64 400cb7f0 20000010 4016a5fc 00000000 00000000
    Backtrace:
    [<c009d0b8>] (dput+0x0/0x218) from [<c0094ad0>] (link_path_walk+0x118/0x13c)
    r6 = C25C3F00 r5 = C24EB998 r4 = FFFFFFFE
    [<c00949b8>] (link_path_walk+0x0/0x13c) from [<c0094f6c>] (do_path_lookup+0x2d0/0x2f8)
    r8 = 00000001 r7 = C25C3F00 r6 = 00000001 r5 = C03D1300 r4 = FFFFFF9C
    [<c0094c9c>] (do_path_lookup+0x0/0x2f8) from [<c0095a68>] __path_lookup_intent_open+0x54/0x94)
    [<c0095a14>] (__path_lookup_intent_open+0x0/0x94) from [<c0095b3c>] (path_lookup_open+0x24/0x2c)
    r7 = 00000004 r6 = FFFFFF9C r5 = C25C3F00 r4 = 00000000
    [<c0095b18>] (path_lookup_open+0x0/0x2c) from [<c0095cb0>] (open_namei+0x70/0x6b0)
    [<c0095c40>] (open_namei+0x0/0x6b0) from [<c0088460>] (do_filp_open+0x2c/0x4c)
    [<c0088434>] (do_filp_open+0x0/0x4c) from [<c00884d4>] (do_sys_open+0x54/0xe8)
    r5 = 000001B6 r4 = 00000000
    [<c0088480>] (do_sys_open+0x0/0xe8) from [<c00885a0>] (sys_open+0x24/0x28)
    r8 = C0025F64 r7 = 00000005 r6 = 0009E318 r5 = 00000008 r4 = 0009E318
    [<c008857c>] (sys_open+0x0/0x28) from [<c0025de0>] (ret_fast_syscall+0x0/0x2c)
    Code: e3cd6d7f e3c6603f e1a00004 e59f11d8 (e5943000)

    mhirsch



    New Member


    Posts:
    New Member


    --
    15 May 2007 09:00 AM
    Thanks you Randy for your notes.

    Unfortunatly for me, I boot up and get uncompress........

    and it then just hangs. How can I debug this?

    randyc



    New Member


    Posts:
    New Member


    --
    15 May 2007 09:08 AM
    Yes, sometimes I see that too. What I do is reset the device and try again (and again
    and again if need be).

    what I've noticed is that sometimes when I compile it doesn't seem to like the bits. But if I recompile w/o changing anything it will suddenly be happy and boot up every time. Very touchy (and difficult to engineer/debug)

    I noticed other folks don't boot the same way I do, I am not sure how they are doing it so perhaps someone with more linux knowledge can chime in here and suggest a different way of loading the kernel that is more robust.

    I also would like to boot with my rootfs in nand, but as you can probably see from my other posts my nand is all trashed for some reason and that makes it impractical. I am not sure how to recover from this or what is the cause. I also have a 2GB type1 compact flash card that I would love to instlal the rootfs on and boot from there (thus avoiding NFS entirely) but it's not clear to me how to go about doing that from the documentation.

    As for your problem, make sure your loader compiled correctly with the right values and it's being loaded correctly (right size, etc) that got me for a while until I realized the simple mistake I was making.

    Randy

    thehexa@gmail.com



    New Member


    Posts:
    New Member


    --
    15 May 2007 02:37 PM
    I am booting the way you described earlier and I'm having the same problem (sometimes it just doesn't boot)

    hasanhuseyin.yilmaz@vestel.com.tr



    New Member


    Posts:
    New Member


    --
    17 May 2007 12:04 AM
    Hi folks

    I havent seen such errors in my system but I suggest you follow the linux-arm-kernel@lists.arm.linux.org.uk mailing list. there are a lots of experienced people. you can post your questions and get answers.

    lwalkera



    New Member


    Posts:
    New Member


    --
    21 May 2007 11:24 AM
    I have a similar problem too. All I can get it to do is get to the end of uncompressing. Are there any patches available that apply cleanly to the latest Freescale BSP, or a working kernel zImage so that I can see if it's just me being stupid?

    thehexa@gmail.com



    New Member


    Posts:
    New Member


    --
    23 May 2007 09:19 PM
    anyone could get a stable system?

    I am still getting kernel panics.

    please reach me at thehexa@gmail.com, since PMs seems to be disabled here

    alvinchaung



    New Member


    Posts:
    New Member


    --
    24 May 2007 08:03 PM
    Posted By hexa on 23 May 2007 9:19 PM
    anyone could get a stable system?

    I am still getting kernel panics.

    please reach me at thehexa@gmail.com, since PMs seems to be disabled here




    maybe you can log the boot message to find the last complete kernel message before kernel panic happen

    first time when I follow the patch step written by randyc , I also got the kernel panic, and I found that it was failed after PMIC driver, so I disable PMIC driver at kernel config, and then boot seems success.

    A little experience to share.

    thehexa@gmail.com



    New Member


    Posts:
    New Member


    --
    25 May 2007 12:14 PM
    Posted By alvinchaung on 23 May 2007 9:19 PM
    Posted By hexa on 23 May 2007 9:19 PM
    anyone could get a stable system?

    I am still getting kernel panics.

    please reach me at thehexa@gmail.com, since PMs seems to be disabled here




    maybe you can log the boot message to find the last complete kernel message before kernel panic happen

    first time when I follow the patch step written by randyc , I also got the kernel panic, and I found that it was failed after PMIC driver, so I disable PMIC driver at kernel config, and then boot seems success.

    A little experience to share.




    I also got to that conclusion and disabled the PMIC drivers, i can boot the system without problems.

    After the system boots, everything seems to be normal, but then, with no particular reason, the kernel panics.

    Are you not getting that behaviour?

    regards,
    Kamakura

    vali



    New Member


    Posts:
    New Member


    --
    25 Jun 2007 03:58 PM
    Posted By randyc on 23 Apr 2007 11:42 AM

    1. Gather the bits needed

    download ltib package and mount iso or burn a CD. This came
    from the Freescale site:
    imx31_ads_20070128-rel3-ltib.iso





    Does somebody still have this iso file:
    imx31_ads_20070128-rel3-ltib.iso

    on freescale there is now imx31_ads_20070511-rel4-ltib.iso and I get a lot of rejects if I try to apply the patch on it.

    thanks,
    Vali

    vani.desai@honeywell.com



    New Member


    Posts:
    New Member


    --
    26 Dec 2007 12:08 AM
    Hi Ben,

    I am facing similare problem as yours. After exec command it hangs. No messages after that. Can you please let me know what procedure you followed to make it work.
    Thanks
    VD

    prashm_77@yahoo.com



    New Member


    Posts:
    New Member


    --
    26 Dec 2007 11:41 PM
    Hai

    We just downloaded unpatched linux-2.6.19 kernel from http://www.kernel.org and patch with http://caiaq.org/download...9.2-mx3lite.patch.gz (~1.1MB)

    It works fine

    macneibfallon



    New Member


    Posts:
    New Member


    --
    13 Feb 2008 04:57 AM
    Hello everyone,

    First I'd like to thank everyone working on this for all their help, special thanks to Randy for his great instructions.

    I've managed to get to the loader/zImage download step, then once I run



    exec 0x800d03a8 -



    It hangs.



    I'll figure it out i expect and post the possible solution but I was curious if someone was able to do it quicker?

    Anyone else experience this issue and sort it out?

    here's a dump from the terminal



    losh> ifconfig sm0 192.168.33.102 255.255.255.0 192.168.33.1

    losh> load raw 0x800d03a8 35342 /tftp/192.168.33.105:/tftpboot/loader

    loading from /tftp/192.168.33.105:/tftpboot/loader:

    loading raw binary to 0x800d03a8 (ram) len 00008a0e:

    ........done

    file loaded

    losh> load raw 0x81000000 1629660 /tftp/192.168.33.105:/tftpboot/zImage

    loading from /tftp/192.168.33.105:/tftpboot/zImage:

    loading raw binary to 0x81000000 (ram) len 0018dddc:

    ................................................................................

    ................................................................................

    ..........................................done

    file loaded

    losh> ls

    R : load 1629660

    D : tftp 0

    D : etc 0

    D : dev 0

    losh> exec 0x800d03a8 -

    lilja.magnus@gmail.com



    New Member


    Posts:
    New Member


    --
    13 Feb 2008 09:35 AM
    > losh> load raw 0x800d03a8 35342 /tftp/192.168.33.105:/tftpboot/loader

    If loader is the executable file as produced by gcc you can use this command instead:
    load elf /tftp/192.168.33.105:/tftpboot/loader

    You might also want to verify that the start address of loader is indeed 0x800d03a8 by using:
    objdump -f /tftpboot/loader

    Regards

    srinivasan.mohan@honeywell.com



    New Member


    Posts:
    New Member


    --
    24 Jul 2009 04:18 AM
    Posted By mlilja on 13 Feb 2008 9:35 AM
    > losh> load raw 0x800d03a8 35342 /tftp/192.168.33.105:/tftpboot/loader

    If loader is the executable file as produced by gcc you can use this command instead:
    load elf /tftp/192.168.33.105:/tftpboot/loader

    You might also want to verify that the start address of loader is indeed 0x800d03a8 by using:
    objdump -f /tftpboot/loader

    Regards




    Hi Magnus and others,
    I am unable to build loader as per the directions provided by randyc in posting.php?mode=quote&f=29&p=1074. I am getting "could not find -lc" error.
    Can you tell which might cause this problem? LTIB, that i am using is linux-2.6.22.6 (as suggested by magnus, in "yet another linux thread" forum

    linux-xfm5:/home/sr/linux_new/bootloader/bootloader # vi Makefile
    linux-xfm5:/home/sr/linux_new/bootloader/bootloader # make
    /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -c bootloaderstg2.c -I./include
    bootloaderstg2.c: In function 'setup_tags':
    bootloaderstg2.c:223: warning: passing argument 1 of 'setup_core_tag' makes pointer from integer without a cast
    bootloaderstg2.c: In function 'main':
    bootloaderstg2.c:250: warning: assignment makes pointer from integer without a cast
    /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-ld -o loader bootloaderstg2.o -static -T config.lds -lc -L /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueab/lib
    /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-ld: cannot find -lc
    make: *** [loader] Error 1

    - Srini

    srinivasan.mohan@honeywell.com



    New Member


    Posts:
    New Member


    --
    27 Jul 2009 07:31 AM
    Hi Magnus and others,
    I am unable to build loader as per the directions provided by randyc in posting.php?mode=quote&f=29&p=1074. I am getting "could not find -lc" error.
    Can you tell which might cause this problem? LTIB, that i am using is linux-2.6.22.6 (as suggested by magnus, in "yet another linux thread" forum

    linux-xfm5:/home/sr/linux_new/bootloader/bootloader # vi Makefile
    linux-xfm5:/home/sr/linux_new/bootloader/bootloader # make
    /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -c bootloaderstg2.c -I./include
    bootloaderstg2.c: In function 'setup_tags':
    bootloaderstg2.c:223: warning: passing argument 1 of 'setup_core_tag' makes pointer from integer without a cast
    bootloaderstg2.c: In function 'main':
    bootloaderstg2.c:250: warning: assignment makes pointer from integer without a cast
    /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-ld -o loader bootloaderstg2.o -static -T config.lds -lc -L /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueab/lib
    /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-ld: cannot find -lc
    make: *** [loader] Error 1

    - Srini[/quote]

    Hi,
    I could resolve this issue. For the benefit of others, I could resolve this by following the lib path mentioned in the following thread

    viewtopic.php?f=29&t=1445

    Thanks everyone
    Srini

    Sancho0330



    New Member


    Posts:
    New Member


    --
    09 Jun 2010 09:04 PM
    What is the second stage bootloader doing? Why do we need it?




    I got a kernel image from LinuxLink through a free trial. It gets up and running fine. They also provided a rootfs. Those images are here (they don't provide the source):

    https://linuxlink.timesys.com/webshare/2/index.pt/timesys/factory/logic_i.mx31lite_debugging/3/output/

    You may have to sign up for a trial.

    Here's a getting started guide..I followed most of it. I already had a tftp-server and nfs service

    https://linuxlink.timesys.com/node/2722


    ---