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 09 Jun 2005 10:43 AM by  Anonymous
Troubles with Ethernet on Linux 2.6.11.11
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
giorgiomassa
New Member
New Member
Posts:


--
06 Jun 2005 08:21 AM
    Hello, I compiled and succesfully booted a 2.6.11.11 linux kernel, I also applied Marc Singer patches, however I'm unable to make the ethernet controller work.

    On the ethernet switch I can see the connect LEDs lights up for 1 second then they switch off, after 1 second it comes up again and so on forever. The activity and link LEDs on the board are always off.

    I found out that a similar problem has been caused by the first version of the SDK boards that had supplied a wrong voltage to the controller, however I double checked and my board is already fixed.

    I have no idea what else it could be. Here's my kernel log, trying to get an IP address from a DHCP server.

    Thanks for the help

    *******************************************************************************

    apex> xreceive 0xc0008000
    CCCboot console=ttyAM1 root=/dev/nfs ip=dhcp nfsroot=10.0.0.13:/tftpboot,v3,tcp
    Booting kernel at 0xc0008000...
    Uncompressing Linux........................................................................... done, booting the kernel.
    Linux version 2.6.11.11 (brain@DebianDevEnv) (gcc version 3.3) #2 Mon Jun 6 15:54:30 CEST 2005
    CPU: ARM922T [41029220] revision 0 (ARMv4T)
    CPU0: D VIVT write-back cache
    CPU0: I cache: 8192 bytes, associativity 64, 32 byte lines, 4 sets
    CPU0: D cache: 8192 bytes, associativity 64, 32 byte lines, 4 sets
    Machine: Logic Product Development LPD7A404-10
    Memory policy: ECC disabled, Data cache buffered
    Built 4 zonelists
    Kernel command line: console=ttyAM1 root=/dev/nfs ip=dhcp nfsroot=10.0.0.13:/tftpboot,v3,tcp
    PID hash table entries: 512 (order: 9, 8192 bytes)
    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: 8MB 8MB 8MB 8MB 8MB 8MB 8MB 8MB = 64MB total
    Memory: 62368KB available (1938K code, 356K data, 92K init)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    NET: Registered protocol family 16
    CLCD: registering amba devices
    0 -> 0
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    NetWinder Floating Point Emulator V0.97 (double precision)
    JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
    JFFS2: default compression mode: priority
    CLCD: LCD setup fb virt 0xffc00000 phys 0xc03c0000 l 26000 io 0xf8003000
    CLCD: lh7a40x FB hardware, 3.5in QVGA display
    CLCD: disabling LCD
    CLCD: enabling LCD
    Console: switching to colour frame buffer device 30x40
    Real Time Clock Driver v1.12
    serial: LH7A40X serial driver
    ttyAM0 at MMIO 0x80000600 (irq = 38) is a LH7A40X
    ttyAM1 at MMIO 0x80000700 (irq = 40) is a LH7A40X
    ttyAM2 at MMIO 0x80000800 (irq = 42) is a LH7A40X
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    loop: loaded (max 8 devices)
    smc91x: IOADDR ce054000 doesn't match configuration (300).
    smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
    eth0: SMC91C11xFD (rev 1) at 0xce054000 IRQ 64
    eth0: Ethernet addr: 00:08:ee:00:76:6c
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
    lh7a404-ohci lh7a404-ohci0: new USB bus registered, assigned bus number 1
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    sl811: driver sl811-hcd, 15 Dec 2004
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    NET: Registered protocol family 2
    IP: routing cache hash table of 512 buckets, 4Kbytes
    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)
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    Sending DHCP requests ...... timed out!
    IP-Config: Retrying forever (NFS root)...
    eth0: link down
    ......
    Anonymous
    Posts:


    --
    09 Jun 2005 10:43 AM
    Hello,

    R1, R2, R5, R6 on the SDK are different on the LH79524 card engine because it has a different Ethernet PHY which requires different output network. The LH79524 SDK Application Board is not intended to be compatible with any other card engine. My recommendation in this situation is to find the SDK Application Board that came with the LH7A404 card engine and try running your code on that and let me know the results.

    If you were to reverse engineer this FAQ:
    http://www.logicpd.com/su...q/faq.php?faq_id=121

    It would be possible to get Ethernet to work for your LH7A404 card engine. If you're comfortable making these changes this should be the best way to accomplish this. Please keep in mind that any board modifications will void any warranty that the kit had and modified kits will not be able to be supported.

    Regards,
    You are not authorized to post a reply.