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 18 Jul 2005 04:45 PM by  Anonymous
Problem when Filesystem is in Compact Flash
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
lawriekurian@greymatterindia.com
New Member
New Member
Posts:


--
24 Mar 2004 06:33 AM
    As per the documentation given ...
    Logic DN: 70000071 REV:A
    Loading linux from CF card (Topic 5.2)
    We have copied the rootfilesystem in the compact flash ...
    the kernel boots up and ...
    we keep getting this message in between - before and after having logged in...
    # hda: write_intr: status=0x50 { DriveReady SeekComplete }
    which eventually corrupts the filesystem in the compact flash.
    So linux cannot be booted again until the the entire steps to load the files on the CF card are redone (Topic 5.2.2).
    Please help us out...

    Here are the messages shown on the terminal ...
    losh> exec 0x40100000 - root=/dev/hda1 hd=980,8,32
    kernel cmdline: 'root=/dev/hda1 hd=980,8,32' at 200c0100
    jumping to: 40100000...
    Uncompressing Linux..............................................
    done, booting the kernel.
    Linux version 2.4.17-rmk2-lineo5 (root@embedded) (gcc version 2.95.3 20010315 (r
    elease)) #8 Tue Mar 23 23:28:54 UTC 2004
    Processor: ARM ARM720T revision 3
    Architecture: LogicPD LH79520 Card Engine
    On node 0 totalpages: 8192
    zone(0): 8192 pages.
    zone(1): 0 pages.
    zone(2): 0 pages.
    Kernel command line: console=ttyAM1,115200 root=/dev/hda1 hd=980,8,32
    setup_timer(): timerLoad=32256
    Console: colour dummy device 80x30
    Calibrating delay loop... 25.70 BogoMIPS
    Memory: 32MB = 32MB total
    Memory: 14288KB available (1204K code, 252K data, 76K init)
    Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
    Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
    POSIX conformance testing by UNIFIX
    Linux NET4.0 for Linux 2.4
    Based upon Swansea University Computer Society NET3.039
    Initializing RT netlink socket
    Starting kswapd
    ttyAM0 at MEM 0xfffc0000 (irq = 23) is a AMBA PrimeCell PL011
    ttyAM1 at MEM 0xfffc1000 (irq = 24) is a AMBA PrimeCell PL011
    ttyAM2 at MEM 0xfffc2000 (irq = 25) is a AMBA PrimeCell PL011
    Console: switching to colour frame buffer device 30x40
    LH79520 Watchdog Timer: timer margin 60 sec
    block: 64 slots per queue, batch=16
    RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
    hda: 122MB, CHS=980/8/32
    Partition check:
    hda: hda1 hda2 hda3
    eth0: SMC91C11xFD(rev:1) at 0xf4800000 IRQ:4 DMA:0 (16-bit) MEM:8192b NOWAIT:1
    eth0: ADDR: 00:08:ee:00:12:37
    NET4: Linux TCP/IP 1.0 for NET4.0
    IP Protocols: ICMP, UDP, TCP
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 2048 bind 2048)
    NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
    RAMDISK: Couldn't find valid RAM disk image starting at 0.
    Freeing initrd memory: 16384K
    VFS: Mounted root (ext2 filesystem).
    Freeing init memory: 76K
    modprobe: modprobe: Can't locate module char-major-4
    serial console detected. Disabling virtual terminals.
    init started: BusyBox v0.52 (2004.03.19-10:45+0000) multi-call binary
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    *** Running rc.modules
    *** Running rc.serial
    *** Attempting to start S15inet
    *** Attempting to start S20network
    *** Attempting to start S23portmap
    *** Attempting to start S35dhcpcd
    *** Running rc.local

    (none) login: Could not read calibration: /etc/pointercal
    modprobe: modprobe: Can
    't locate module char-major-254
    open(/dev/pwm0) error
    root
    login[20]: root login on `ttyAM1'

    # hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    ls
    # hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    hda: write_intr: status=0x50 { DriveReady SeekComplete }
    cd ..
    #

    Lawrie
    simon
    New Member
    New Member
    Posts:


    --
    20 Jun 2005 10:45 PM
    Was there ever any response to this kind of problem?

    We are having the same issues with the CF being corrupted.
    Anonymous
    Posts:


    --
    04 Jul 2005 01:26 PM
    Hello,

    If you are having CF card data corruption, please verify that your application board have the inverter that changes MSTR_nRST to MSTR_RST for the CF card RESET line. A long time ago, on older SDK application boards, the RESET polarity going to the CF card was reversed. This was odd because CF cards worked most of the time, but data corruption was known to occur over time.

    Regards,
    simon
    New Member
    New Member
    Posts:


    --
    04 Jul 2005 07:09 PM
    Ok,

    The revision of my Application board is Rev F. What is required for me to determine if I have the correct RESET polarity? And how do I fix it if it is wrong?

    EDIT: I have downloaded the appropriate schematic and can see that the RESET line going to the CF Card Socket is marked as "MSTR_nRST". I assume this means that there is a problem. Is there a workaround?

    Cheers.
    simon
    New Member
    New Member
    Posts:


    --
    18 Jul 2005 04:33 PM
    Is it possible to get some help with this? We are getting to a point in the project where it is now affecting the deployment timescale of the product.

    If someone could point me where I can get some help on this it will be greatly appreciated. I've had no experience with complex embedded hardware so a bit of a "lead by the hand" would be nice initially.

    Cheers,
    Simon
    Anonymous
    Posts:


    --
    18 Jul 2005 04:45 PM
    Simon,

    Have you applied the patch that is released for the BDK on Logic's download page? You can reference the readme file in the .zip for more information:

    http://www.logicpd.com/do...-LLH79520-1.0.1b.tgz

    For the most timely response to support requests please use the "Ask a Question" page at the following link:

    http://www.logicpd.com/support/askaquestion.php

    Please keep in mind that this an unsupported Linux BSP meant as a reference, Logic can assist you with your development if you require further aid.

    Thank you,
    You are not authorized to post a reply.