FAQ: [#6405] Can not ping between two adf7021(2010)

Document created by Aaronwu Employee on Sep 11, 2013
Version 1Show Document
  • View in full screen mode

[#6405] Can not ping between two adf7021

Submitted By: Vivi Li

Open Date

2010-12-13 23:24:30    

Priority:

Medium     Assignee:

Michael Hennerich

Status:

Open     Fixed In Release:

N/A

Found In Release:

2011R1     Release:

Category:

N/A     Board:

N/A

Processor:

BF537     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Assigned (Not Start)

Uboot version or rev.:

    Toolchain version or rev.:

trunk

App binary format:

N/A     

Summary: Can not ping between two adf7021

Details:

 

Can not ping between two adf7021.

This happens on 2010r1 branch and trunk.

 

--

Linux version 2.6.34.7-ADI-2010R1-svn9479 (test@uclinux41) (gcc version 4.3.5 (ADI-2010R1-RC4) ) #260 Mon Nov 8 12:07:49 CST 2010

register early platform devices

bootconsole [early_shadow0] enabled

bootconsole [early_BFuart0] enabled

early printk enabled on early_BFuart0

Limiting kernel memory to 56MB due to anomaly 05000263

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x001206e0

  rodata    = 0x001206e0-0x0018e0c4

  bss       = 0x0018f000-0x0019f514

  data      = 0x0019f514-0x001ba000

    stack   = 0x001b8000-0x001ba000

  init      = 0x001ba000-0x00897000

  available = 0x00897000-0x03800000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 0

Blackfin support (C) 2004-2010 Analog Devices, Inc.

Compiled for ADSP-BF537 Rev 0.2

Warning: Compiled for Rev 2, but running on Rev 3

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 125 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

  External memory: cacheable in instruction cache

Data Cache Enabled for CPU0

  External memory: cacheable (write-back) in data cache

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 14224

Kernel command line: root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600

PID hash table entries: 256 (order: -2, 1024 bytes)

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 47980k/65536k RAM, (7028k init code, 1149k kernel code, 615k data, 1024k dma, 7740k reserved)

Hierarchical RCU implementation.

NR_IRQS:138

Configuring Blackfin Priority Driven Interrupts

console [ttyBF0] enabled, bootconsole disabled

console [ttyBF0] enabled, bootconsole disabled

Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

Blackfin L1 Data A SRAM: 16 KB (16 KB free)

Blackfin L1 Data B SRAM: 16 KB (16 KB free)

Blackfin L1 Instruction SRAM: 48 KB (35 KB free)

NET: Registered protocol family 16

Blackfin DMA Controller

stamp_init(): registering device resources

bio: create slab <bio-0> at 0

bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

Switching to clocksource bfin_cs_cycles

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

msgmni has been set to 93

alg: No test for stdrng (krng)

io scheduler noop registered

io scheduler cfq registered (default)

bfin-uart: Blackfin serial driver

bfin-uart.0: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

brd: module loaded

dma_alloc_init: dma_page @ 0x028de000 - 256 pages at 0x03f00000

adf702x spi0.18: ADF702XNet Wireless Ethernet driver

bfin_mii_bus: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=24)@sclk=125MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

TCP cubic registered

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:15:37 UTC (937)

Freeing unused kernel memory: 7028k freed

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_|_| |_|\____|/_/\_\       |

     dP   .    Y8b.       \   For™¥¹zj¤ed proce'$HH      'Y88b        \___________________________________/

  :8P    '      :888•        •Í±…

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            - http://blackfin.uclinux.org/

\    YP"    `| 8P  `.          - http://docs.blackfin.uclinux.org/

/     \.___.d|    .'           - http://www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    - http://www.analog.com/blackfin

 

Have a lot of fun...

 

 

BusyBox v1.16.2 (2010-11-08 10:24:51 CST) hush - the humble shell

 

root:/> PuTTY

sh: can't execute 'PuTTY': No such file or directory

root:/>

root:/>

root:/>

root:/>

root:/>

root:/> ifconfig

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

root:/> ifconfig eth0 192.168.1.4

root:/> ifconfig

eth0      Link encap:Ethernet  HWaddr 22:DA:E2:A8:86:2A

          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:10

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

root:/> ping 192.168.1.4

PING 192.168.1.4 (192.168.1.4): 56 data bytes

64 bytes from 192.168.1.4: seq=0 ttl=64 time=0.392 ms

64 bytes from 192.168.1.4: seq=1 ttl=64 time=0.228 ms

64 bytes from 192.168.1.4: seq=2 ttl=64 time=0.237 ms

64 bytes from 192.168.1.4: seq=3 ttl=64 time=0.226 ms

64 bytes from 192.168.1.4: seq=4 ttl=64 time=0.239 ms

64 bytes from 192.168.1.4: seq=5 ttl=64 time=0.227 ms

^C

--- 192.168.1.4 ping statistics ---

6 packets transmitted, 6 packets received, 0% packet loss

round-trip min/avg/max = 0.226/0.258/0.392 ms

root:/>

root:/>

 

(set up another adf7021 and set ip to 192.168.1.3)

 

root:/> ping 192.168.1.3

PING 192.168.1.3 (192.168.1.3): 56 data bytes

--

 

Follow-ups

 

--- Sonic Zhang                                              2010-12-13 23:45:49

Michael, can you take a look?

 

--- Michael Hennerich                                        2010-12-14 05:29:44

Sonic,

 

Did this test ever pass?

I assume not. It's very likely a board configuration problem.

I wouldn't consider this a critical bug.

 

I'll take a look once I have time.

 

-Michael

 

 

--- Vivi Li                                                  2010-12-14 22:15:06

Michael,

 

I never test the ping function before as I had only one adf7021 board. Another

adf7021 board arrived just a week ago.

 

-Vivi

 

--- Vivi Li                                                  2011-12-22 03:29:58

I've test with two adf7021 boards and they can't ping to each other.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

config.linux.adf702x    application/octet-stream    36000    Vivi Li

Attachments

Outcomes