Linux/66AK2L06: Gigabit Ethernet Net-cp issue

Ari Poutanen

Part Number: 66AK2L06
Other Parts Discussed in Thread: DP83867CS

Tool/software: Linux

Hello,

I have installed Arago Linux 4.4.32 on our custom K2L board. It uses DP83867 PHY chip and I have finally got it working with 100Mbit/s, but the 1Gbit/s speed does not work. I have exactly the same symptoms as described in the chapter "K2HK EVM Gigabit MDC/MDIO Signal Integrity Issue" of the "Linux Core NetCP User's Guide":

[   47.675204] netcp-1.0 2620110.netcp eth0: Link is Up - 1Gbps/Full - flow control off                                                                               
[   49.444816] netcp-1.0 2620110.netcp eth0: Link is Down

The link may jump even twice up and down, but it stays finally down and - does not work, of course.

The 100Mbit/s works just fine. Pinging a PC with 100Mbit/s NIC at 192.168.0.254 succeeds:

[   38.605205] netcp-1.0 2620110.netcp eth0: Link is Up - 100Mbps/Full - flow control off                                                                             
                                                                                                                                                                                      
root@k2l-evm:~# ping 192.168.0.254                                                                                                                                                    
PING 192.168.0.254 (192.168.0.254): 56 data bytes                                                                                                                                     
64 bytes from 192.168.0.254: seq=0 ttl=64 time=0.288 ms                                                                                                                               
64 bytes from 192.168.0.254: seq=1 ttl=64 time=0.174 ms                                                                                                                               
64 bytes from 192.168.0.254: seq=2 ttl=64 time=0.163 ms                                                                                                                               
^C                                                                                                                                                                                    
--- 192.168.0.254 ping statistics ---                                                                                                                                                 
3 packets transmitted, 3 packets received, 0% packet loss                                                                                                                             
round-trip min/avg/max = 0.163/0.208/0.288 ms                                                                                                                                         

I tried the software workaround as suggested in the same chapter, but with that the link stays permanently down.
I have also seen other articles suggesting changing the "link-interface" property in the device tree.
I have now tried with the "link-interface" values: <0>, <1>, <2> and <4>. None of them works.
The <1> seems be the only one making at least 100Mbit/s to work. The others disable also that.

Please tell me what I could try next.

Best regards,
Ari

over 8 years ago

0 Yordan Kovachev over 8 years ago

TI__Guru**** 161600 points

Hi Ari,

Can you share your dts files and the bootlog?
Also you're using the officially released linux SDK:
www.ti.com/.../processor-sdk-k2l
right?

Best Regards,
Yordan

0 Ari Poutanen over 8 years ago in reply to Yordan Kovachev

Expert 1140 points

Hello Yordan,

Yes, I have downloaded the official Processor SDK release package and built my kernel + UBI file system from that.

Here are the dts files I have modified. The rest of them are as got from the release package.

dts-files.tar.gz

Please see the boot log below.

Best regards,

Ari

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[ 0.000000] Booting Linux on physical CPU 0x0

[ 0.000000] Initializing cgroup subsys cpuset

[ 0.000000] Initializing cgroup subsys cpu

[ 0.000000] Initializing cgroup subsys cpuacct

[ 0.000000] Linux version 4.4.32-gadde2ca9f8 (neukkari@xskybex-laptop) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #5 SMP PREEMPT Fri Feb 3 10:30:18 EET 2017

[ 0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c5387d

[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache

[ 0.000000] Machine model: Texas Instruments Keystone 2 Lamarr EVM

[ 0.000000] Switching physical address space to 0x800000000

[ 0.000000] Reserved memory: created CMA memory pool at 0x000000081f800000, size 8 MiB

[ 0.000000] Reserved memory: initialized node dsp_common_cma_pool, compatible id shared-dma-pool

[ 0.000000] Reserved memory: created DMA memory pool at 0x0000000820000000, size 32 MiB

[ 0.000000] Reserved memory: initialized node dsp_reserved_mpm_area, compatible id shared-dma-pool

[ 0.000000] cma: Reserved 24 MiB at 0x000000087e400000

[ 0.000000] Forcing write-allocate cache policy for SMP

[ 0.000000] Memory policy: Data cache writealloc

[ 0.000000] psci: probing for conduit method from DT.

[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT

[ 0.000000] PERCPU: Embedded 11 pages/cpu @de5b0000 s14732 r8192 d22132 u45056

[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 391488

[ 0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=ubifs,2048

[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)

[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

[ 0.000000] Memory: 1517572K/1572864K available (5331K kernel code, 217K rwdata, 1776K rodata, 256K init, 270K bss, 22524K reserved, 32768K cma-reserved, 1024000K highmem)

[ 0.000000] Virtual kernel memory layout:

[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)

[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)

[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)

[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)

[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)

[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)

[ 0.000000] .text : 0xc0008000 - 0xc06f9044 (7109 kB)

[ 0.000000] .init : 0xc06fa000 - 0xc073a000 ( 256 kB)

[ 0.000000] .data : 0xc073a000 - 0xc0770438 ( 218 kB)

[ 0.000000] .bss : 0xc0772000 - 0xc07b58a0 ( 271 kB)

[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1

[ 0.000000] Preemptible hierarchical RCU implementation.

[ 0.000000] Build-time adjustment of leaf fanout to 32.

[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.

[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2

[ 0.000000] NR_IRQS:16 nr_irqs:16 16

[ 0.000000] GIC: Using split EOI/Deactivate mode

[ 0.000000] of_psc_clk_init: error registering clk clkpcie1

[ 0.000000] Architected cp15 timer(s) running at 199.68MHz (phys).

[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e0d652267, max_idle_ns: 440795206693 ns

[ 0.000004] sched_clock: 56 bits at 199MHz, resolution 5ns, wraps every 4398046511101ns

[ 0.000012] Switching to timer-based delay loop, resolution 5ns

[ 0.000173] keystone timer clock @199680000 Hz

[ 0.000396] Console: colour dummy device 80x30

[ 0.000415] Calibrating delay loop (skipped), value calculated using timer frequency.. 399.36 BogoMIPS (lpj=1996800)

[ 0.000426] pid_max: default: 32768 minimum: 301

[ 0.000510] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)

[ 0.000518] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)

[ 0.000974] Initializing cgroup subsys io

[ 0.000991] Initializing cgroup subsys memory

[ 0.001011] Initializing cgroup subsys devices

[ 0.001021] Initializing cgroup subsys freezer

[ 0.001034] Initializing cgroup subsys perf_event

[ 0.001044] Initializing cgroup subsys pids

[ 0.001066] CPU: Testing write buffer coherency: ok

[ 0.001271] /cpus/cpu@0 missing clock-frequency property

[ 0.001299] /cpus/cpu@1 missing clock-frequency property

[ 0.001308] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

[ 0.001337] Setting up static identity map for 0x80008300 - 0x80008430

[ 0.081357] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001

[ 0.081448] Brought up 2 CPUs

[ 0.081462] SMP: Total of 2 processors activated (798.72 BogoMIPS).

[ 0.081468] CPU: All CPU(s) started in HYP mode.

[ 0.081473] CPU: Virtualization extensions available.

[ 0.081835] devtmpfs: initialized

[ 0.092286] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0

[ 0.092540] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns

[ 0.093232] pinctrl core: initialized pinctrl subsystem

[ 0.093911] NET: Registered protocol family 16

[ 0.094696] DMA: preallocated 256 KiB pool for atomic coherent allocations

[ 0.120063] cpuidle: using governor ladder

[ 0.150082] cpuidle: using governor menu

[ 0.157592] irq: no irq domain found for /soc/keystone_irq@26202a0 !

[ 0.157805] irq: no irq domain found for /soc/keystone_irq@26202a0 !

[ 0.158017] irq: no irq domain found for /soc/keystone_irq@26202a0 !

[ 0.158234] irq: no irq domain found for /soc/keystone_irq@26202a0 !

[ 0.164823] No ATAGs?

[ 0.164848] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.

[ 0.164856] hw-breakpoint: maximum watchpoint size is 8 bytes.

[ 0.193678] pps_core: LinuxPPS API ver. 1 registered

[ 0.193708] PTP clock support registered

[ 0.193751] EDAC MC: Ver: 3.0.0

[ 0.194817] clocksource: Switched to clocksource arch_sys_counter

[ 0.203026] NET: Registered protocol family 2

[ 0.203545] TCP established hash table entries: 4096 (order: 2, 16384 bytes)

[ 0.203578] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)

[ 0.203634] TCP: Hash tables configured (established 4096 bind 4096)

[ 0.203676] UDP hash table entries: 256 (order: 1, 8192 bytes)

[ 0.203694] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)

[ 0.203812] NET: Registered protocol family 1

[ 0.204055] RPC: Registered named UNIX socket transport module.

[ 0.204062] RPC: Registered udp transport module.

[ 0.204068] RPC: Registered tcp transport module.

[ 0.204074] RPC: Registered tcp NFSv4.1 backchannel transport module.

[ 0.204253] Unpacking initramfs...

[ 0.208358] Freeing initrd memory: 64K (cfff0000 - d0000000)

[ 0.208523] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available

[ 0.209207] platform alarmtimer: set dma_pfn_offset00780000

[ 0.209516] futex hash table entries: 512 (order: 3, 32768 bytes)

[ 0.216253] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[ 0.216843] NFS: Registering the id_resolver key type

[ 0.216873] Key type id_resolver registered

[ 0.216880] Key type id_legacy registered

[ 0.216936] ntfs: driver 2.1.32 [Flags: R/O].

[ 0.218116] bounce: pool size: 64 pages

[ 0.218247] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)

[ 0.218261] io scheduler noop registered

[ 0.218274] io scheduler deadline registered

[ 0.218305] io scheduler cfq registered (default)

[ 0.218451] keystone_irq soc:keystone_irq@26202a0: irqchip registered, nr_irqs 28

[ 0.219065] ti,keystone-serdes 232a000.phy: init fw ks2_gbe_serdes.bin: version 3.3.0.2c

[ 0.221957] keystone-navigator-qmss soc:qmss@2a40000: qmgr start queue 0, number of queues 8192

[ 0.222103] keystone-navigator-qmss soc:qmss@2a40000: added qmgr start queue 0, num of queues 8192, reg_peek f0940000, reg_status f093c000, reg_config f093e000, reg_region f096200

[ 0.222431] keystone-navigator-qmss soc:qmss@2a40000: firmware file ks2_qmss_pdsp_acc48.bin downloaded for pdsp0

[ 0.222506] keystone-navigator-qmss soc:qmss@2a40000: firmware file ks2_qmss_pdsp_qos.bin downloaded for pdsp3

[ 0.222582] keystone-navigator-qmss soc:qmss@2a40000: firmware file ks2_qmss_pdsp_qos.bin downloaded for pdsp7

[ 0.223563] keystone-navigator-qmss soc:qmss@2a40000: qos: sched port @8096, drop sched @8000

[ 0.225321] keystone-navigator-qmss soc:qmss@2a40000: qos: sched port @6496, drop sched @6400

[ 0.227283] keystone-navigator-qmss soc:qmss@2a40000: qos version 0x200010b, magic valid

[ 0.227835] keystone-navigator-qmss soc:qmss@2a40000: qos version 0x200010b, magic valid

[ 0.228990] keystone-navigator-dma soc:knav_dmas@0: DMA dma_gbe registered 149 logical channels, flows 128, tx chans: 21, rx chans: 91

[ 0.276999] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled

[ 0.277079] platform serial8250: set dma_pfn_offset00780000

[ 0.279690] console [ttyS0] disabled

[ 0.279737] 2530c00.serial: ttyS0 at MMIO 0x2530c00 (irq = 26, base_baud = 12480000) is a 16550A

[ 1.104630] console [ttyS0] enabled

[ 1.108871] 2531000.serial: ttyS1 at MMIO 0x2531000 (irq = 27, base_baud = 12480000) is a 16550A

[ 1.118424] 2348400.serial: ttyS2 at MMIO 0x2348400 (irq = 68, base_baud = 12480000) is a 16550A

[ 1.127890] 2348800.serial: ttyS3 at MMIO 0x2348800 (irq = 69, base_baud = 12480000) is a 16550A

[ 1.221997] loop: module loaded

[ 1.225451] at24 0-0050: 131072 byte 24c1024 EEPROM, writable, 1 bytes/write

[ 1.233890] spi_davinci 21000400.spi: DMA is not supported (-19)

[ 1.240499] m25p80 spi32766.0: n25q128a11 (16384 Kbytes)

[ 1.245833] 2 ofpart partitions found on MTD device spi32766.0

[ 1.251640] Creating 2 MTD partitions on "spi32766.0":

[ 1.256786] 0x000000000000-0x000000100000 : "u-boot-spl"

[ 1.262945] 0x000000100000-0x000001000000 : "misc"

[ 1.268557] spi_davinci 21000400.spi: Controller at 0xf0a1e400

[ 1.274582] spi_davinci 21000600.spi: DMA is not supported (-19)

[ 1.280919] spi_davinci 21000600.spi: Controller at 0xf0a20600

[ 1.286989] platform Fixed MDIO bus.0: set dma_pfn_offset00780000

[ 1.293195] libphy: Fixed MDIO Bus: probed

[ 1.344839] davinci_mdio 26200f00.mdio: davinci mdio revision 1.7

[ 1.350908] libphy: 26200f00.mdio: probed

[ 1.355396] davinci_mdio 26200f00.mdio: phy[0]: device 26200f00.mdio:00, driver TI DP83867

[ 3.376981] serdes PLL not locked

[ 5.904412] serdes PLL not locked

[ 6.419869] netcp-1.0 2620110.netcp: cpts: overflow check period 350

[ 6.426221] netcp-1.0 2620110.netcp: CPTS: ref_clk_freq:599040000 calc_mult:3584875214 calc_shift:31 error:0 nsec/sec

[ 6.436805] netcp-1.0 2620110.netcp: initialized cpsw ale version 1.4

[ 6.443220] netcp-1.0 2620110.netcp: ALE Table size 1024

[ 6.449424] netcp-1.0 2620110.netcp: module(netcp-xgbe) not used for device

[ 6.456396] netcp-1.0 2620110.netcp: module(netcp-pa) not used for device

[ 6.465093] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 0

[ 6.473330] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 1

[ 6.481614] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 2

[ 6.489948] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 3

[ 6.498213] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 4

[ 6.506457] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 5

[ 6.514689] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 6

[ 6.522933] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 7

[ 6.531176] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 8

[ 6.539419] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 9

[ 6.547662] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 10

[ 6.555997] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 11

[ 6.564316] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 12

[ 6.572646] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 13

[ 6.580976] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 14

[ 6.589751] netcp-1.0 2620110.netcp: rx_chan_name netrx0-pa for port 1

[ 6.596502] i2c /dev entries driver

[ 6.603053] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xac

[ 6.609412] nand: Micron MT29F4G08ABBDAHC

[ 6.613403] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64

[ 6.621259] Bad block table found at page 262080, version 0x01

[ 6.627606] Bad block table found at page 262016, version 0x01

[ 6.633749] 3 ofpart partitions found on MTD device 30000000.nand

[ 6.639830] Creating 3 MTD partitions on "30000000.nand":

[ 6.645220] 0x000000000000-0x000000100000 : "u-boot"

[ 6.651044] 0x000000100000-0x000000180000 : "params"

[ 6.656822] 0x000000180000-0x000080000000 : "ubifs"

[ 6.661679] mtd: partition "ubifs" extends beyond the end of device "30000000.nand" -- size truncated to 0x1fe80000

[ 6.673291] davinci_nand 30000000.nand: controller rev. 2.5

[ 6.679548] NET: Registered protocol family 17

[ 6.684052] Key type dns_resolver registered

[ 6.688418] Registering SWP/SWPB emulation handler

[ 6.694345] ubi0: attaching mtd4

[ 6.944818] (NULL net_device): Link is Down

[ 6.948985] (NULL net_device): Link is Down

[ 8.862768] ubi0: scanning is finished

[ 8.877363] ubi0: attached mtd4 (name "ubifs", size 510 MiB)

[ 8.883001] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes

[ 8.889863] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048

[ 8.896639] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096

[ 8.903572] ubi0: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0

[ 8.909652] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128

[ 8.916856] ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 651617070

[ 8.925876] ubi0: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB handling: 76

[ 8.935174] ubi0: background thread "ubi_bgt0d" started, PID 59

[ 8.935184] hctosys: unable to open rtc device (rtc0)

[ 8.949434] UBIFS: parse sync

[ 8.953082] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 60

[ 9.015256] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"

[ 9.022627] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes

[ 9.032526] UBIFS (ubi0:0): FS size: 506507264 bytes (483 MiB, 3989 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)

[ 9.043194] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)

[ 9.049054] UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID CA58BFAB-FC7E-4596-B1E8-5C8EB0120E2A, small LPT model

[ 9.061193] VFS: Mounted root (ubifs filesystem) on device 0:14.

[ 9.069361] devtmpfs: mounted

[ 9.072450] Freeing unused kernel memory: 256K (c06fa000 - c073a000)

[ 9.078792] This architecture does not have kernel memory protection.

[ 9.290453] systemd[1]: System time before build time, advancing clock.

[ 9.347723] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.375844] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.387096] systemd[1]: systemd 229 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLK)

[ 9.405992] systemd[1]: Detected architecture arm.

Welcome to Arago 2016.10!

[ 9.437192] systemd[1]: Set hostname to <k2l-evm>.

[ 9.598073] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.629269] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.654773] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.727185] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.793145] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.802520] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.812084] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.870952] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)

[ 9.965034] systemd[1]: [/lib/systemd/system/syslog-ng.service:6] Executable path is not absolute, ignoring: @SBINDIR@/syslog-ng -F -p @LOCALSTATEDIR@/run/syslogd.pid

[ 9.979896] systemd[1]: [/lib/systemd/system/syslog-ng.service:7] Executable path is not absolute, ignoring: @BASEBINDIR@/kill -HUP $MAINPID

[ 9.992744] systemd[1]: syslog-ng.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.

[ 10.092727] systemd[1]: syslog-ng.service: Cannot add dependency job, ignoring: Unit syslog-ng.service is not loaded properly: Invalid argument.

[ 10.134145] systemd[1]: syslog.socket: Socket service syslog-ng.service not loaded, refusing.

[ 10.142712] systemd[1]: Failed to listen on Syslog Socket.

[FAILED] Failed to listen on Syslog Socket.

See 'systemctl status syslog.socket' for details.

[ 10.187367] systemd[1]: Listening on Journal Socket (/dev/log).

[ OK ] Listening on Journal Socket (/dev/log).

[ 10.217965] systemd[1]: Created slice User and Session Slice.

[ OK ] Created slice User and Session Slice.

[ 10.244988] systemd[1]: Reached target Remote File Systems.

[ OK ] Reached target Remote File Systems.

[ 10.275112] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.

[ OK ] Started Dispatch Password Requests to Console Directory Watch.

[ 10.304934] systemd[1]: Reached target Swap.

[ OK ] Reached target Swap.

[ 10.325028] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.

[ OK ] Listening on /dev/initctl Compatibility Named Pipe.

[ 10.355071] systemd[1]: Started Forward Password Requests to Wall Directory Watch.

[ OK ] Started Forward Password Requests to Wall Directory Watch.

[ 10.384929] systemd[1]: Reached target Paths.

[ OK ] Reached target Paths.

[ 10.405047] systemd[1]: Listening on Journal Socket.

[ OK ] Listening on Journal Socket.

[ 10.425053] systemd[1]: Listening on udev Control Socket.

[ OK ] Listening on udev Control Socket.

[ 10.454986] systemd[1]: Listening on udev Kernel Socket.

[ OK ] Listening on udev Kernel Socket.

[ 10.475562] systemd[1]: Created slice System Slice.

[ OK ] Created slice System Slice.

[ 10.494954] systemd[1]: Reached target Slices.

[ OK ] Reached target Slices.

[ 10.545067] systemd[1]: Mounting Debug File System...

Mounting Debug File System...

[ 10.573762] systemd[1]: Starting Setup Virtual Console...

Starting Setup Virtual Console...

[ 10.617193] systemd[1]: Starting Journal Service...

Starting Journal Service...

[ 10.642587] systemd[1]: Starting Load Kernel Modules...

Starting Load Kernel Modules...

[ 10.671851] systemd[1]: Starting Create list of required static device nodes for the current kernel...

Starting Create list of required st... nodes for the current kernel...

[ 10.707227] systemd[1]: Mounting POSIX Message Queue File System...

Mounting POSIX Message Queue File System...

[ 10.739058] systemd[1]: Starting Remount Root and Kernel File Systems...

[ 10.745840] cryptodev: driver 1.8 loaded.

Starting Remount Root and Kernel File Systems...

[ 10.772768] systemd[1]: Mounting Temporary Directory...

[ 10.808572] NET: Registered protocol family 41

[ 10.825770] systemd[1]: Created slice system-getty.slice.

[ OK ] Created slice system-getty.slice.

[ 10.855674] systemd[1]: Created slice system-serial\x2dgetty.slice.

[ OK ] Created slice system-serial\x2dgetty.slice.

[ 10.885242] systemd[1]: Listening on Network Service Netlink Socket.

[ OK ] Listening on Network Service Netlink Socket.

[ 10.948946] systemd[1]: Mounted Debug File System.

[ OK ] Mounted Debug File System.

[ 10.975093] systemd[1]: Mounted POSIX Message Queue File System.

[ OK ] Mounted POSIX Message Queue File System.

[ 11.004988] systemd[1]: Mounted Temporary Directory.

[ OK ] Mounted Temporary Directory.

[ 11.025198] systemd[1]: Started Journal Service.

[ OK ] Started Journal Service.

[ OK ] Started Setup Virtual Console.

[FAILED] Failed to start Load Kernel Modules.

See 'systemctl status systemd-modules-load.service' for details.

[ OK ] Started Create list of required sta...ce nodes for the current kernel.

[ OK ] Started Remount Root and Kernel File Systems.

Starting udev Coldplug all Devices...

Starting Create Static Device Nodes in /dev...

Starting Apply Kernel Variables...

Starting Flush Journal to Persistent Storage...

[ OK ] Started Create Static Device Nodes in /dev.

[ OK ] Started Apply Kernel Variables.

[ 11.759327] systemd-journald[83]: Received request to flush runtime journal from PID 1

[ OK ] Started Flush Journal to Persistent Storage.

[ OK ] Reached target Local File Systems (Pre).

Mounting /media/ram...

Mounting /var/volatile...

Starting udev Kernel Device Manager...

[ OK ] Mounted /var/volatile.

[ OK ] Mounted /media/ram.

[ OK ] Started udev Coldplug all Devices.

[ OK ] Started udev Kernel Device Manager.

Starting Load/Save Random Seed...

[ OK ] Reached target Local File Systems.

Starting Create [ 12.231810] keystone-rproc 10800000.dsp0: assigned reserved memory node dsp_common_cma_pool

Volatile Files and Directories...

[ 12.293959] remoteproc0: 10800000.dsp0 is available

[ 12.299007] remoteproc0: Note: remoteproc is still under development and considered experimental.

[ 12.320945] remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[ OK ] Started Load/Save Random Seed.

[ 12.355015] davinci-wdt 22f0080.wdt: heartbeat 60 sec

[ 12.362624] keystone-rproc 11800000.dsp1: assigned reserved memory node dsp_common_cma_pool

[ OK 12.395869] remoteproc1: 11800000.dsp1 is available

m] [ 12.402254] remoteproc1: Note: remoteproc is still under development and considered experimental.

Started Create Volatile Files and Directories.[ 12.435610] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[ 12.479193] keystone-rproc 12800000.dsp2: assigned reserved memory node dsp_common_cma_pool

[ 12.492059] remoteproc2: 12800000.dsp2 is available

[ 12.513472] remoteproc2: Note: remoteproc is still under development and considered experimental.

[ 12.536613] remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[ 12.575611] keystone-rproc 13800000.dsp3: assigned reserved memory node dsp_common_cma_pool

[ 12.584008] remoteproc3: 13800000.dsp3 is available

[ 12.597258] remoteproc3: Note: remoteproc is still under development and considered experimental.

[ 12.613773] remoteproc3: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[ 12.675554] keystone-dsp-mem a0000000.dspmem: registered misc device dspmem

[ OK ] Found device /dev/ttyS0.

Starting Update UTMP about System Boot/Shutdown...

Starting Network Time Synchronization...

[ 13.103932] keystone-crypto soc:subsys@26080000:crypto@0: crypto accelerator enabled

[ OK ] Started Network Time Synchronization.

[ OK ] Reached target System Time Synchronized.

Starting Synchronize System and HW clocks...

[ OK ] Started Update UTMP about System Boot/Shutdown.

[FAILED] Failed to start Synchronize System and HW clocks.

See 'systemctl status sync-clocks.service' for details.

[ OK ] Reached target System Initialization.

[ OK ] Listening on dropbear.socket.

[ OK ] Started Daily Cleanup of Temporary Directories.

[ OK ] Reached target Timers.

[ OK ] Listening on D-Bus System Message Bus Socket.

[ OK ] Listening on RPCbind Server Activation Socket.

[ OK ] Reached target Sockets.

[ OK ] Reached target Basic System.

Starting tiipclad-daemon.service...

[ OK ] Started D-Bus System Message Bus.

Starting Network Service...

[ OK ] Started strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.

Starting Permit User Sessions...

Starting softhsm-daemon.service...

Starting run_srss_tc.service...

Starting TI Multiproc Manager...

Starting telnetd.service...

Starting Ethernet Bridge Filtering Tables...

[ OK ] Started Kernel Logging Service.

Starting Print notice about GPLv3 packages...

[ 14.612822] netcp-1.0 2620110.netcp eth0: Link is Down

[ 14.620423] pps pps0: new PPS source ptp0

Starting Login Service...

[ OK ] Started System Logging Service.

[ OK ] Started Network Service.

[ OK ] Started tiipclad-daemon.service.

[ OK ] Started Permit User Sessions.

[ OK ] Started run_srss_tc.service.

[ OK ] Started telnetd.service.

[ OK ] Started Ethernet Bridge Filtering Tables.

[FAILED] Failed to start TI Multiproc Manager.

See 'systemctl status mpmsrv-daemon.service' for details.

[ OK ] Started Getty on tty1.

[ OK ] Started Serial Getty on ttyS0.

[ OK ] Reached target Network.

Starting Lightning Fast Webserver With Light System Requirements...

[ OK ] Started Vsftpd ftp daemon.

Starting Network Name Resolution...

[ OK ] Started Login Service.

[ 16.160828] NET: Registered protocol family 15

[ OK ] Started Lightning Fast Webserver With Light System Requirements.

[ OK ] Started softhsm-daemon.service.

[ OK ] Started Network Name Resolution.

[ 16.481377] Initializing XFRM netlink socket

Starting thttpd.service...

[ OK ] Started thttpd.service.

Starting rng-tools.service...

[ OK ] Started rng-tools.service.

Starting gdbserverproxy.service...

[ OK ] Started gdbserverproxy.service.

Starting matrix-gui-2.0.service...

[ OK ] Started matrix-gui-2.0.service.

Starting thermal-zone-init.service...

Starting parse-ip.service...

[ OK ] Started thermal-zone-init.service.

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

NOTICE: This file system contains the following GPLv3 packages:

autoconf

binutils

cpp-symlinks

cpp

dosfstools

g++-symlinks

g++

gawk

gcc-symlinks

gcc

gdb

gdbc6x

gdbserver

libgmp10

libmpc3

libmpfr4

make

If you do not wish to distribute GPLv3 components please remove

the above packages prior to distribution. This can be done using

the opkg remove command. i.e.:

opkg remove <package>

Where <package> is the name printed in the list above

NOTE: If the package is a dependency of another package you

will be notified of the dependent packages. You should

use the --force-removal-of-dependent-packages option to

also remove the dependent packages as well

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

[ OK ] Started Print notice about GPLv3 packages.

#>>>>> LCD 12

IP Address:

[ OK ] Started parse-ip.service.

_____ _____ _ _

| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_

| | _| .'| . | . | | __| _| . | | | -_| _| _|

|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|

|___| |___|

Arago Project k2l-evm ttyS0

Arago 2016.10 k2l-evm ttyS0

k2l-evm login:

0 Rex Chang over 8 years ago in reply to Yordan Kovachev

TI__Guru 50170 points

Hi, Ari,

I'll look into the issue and get back to you.

Rex

0 Ari Poutanen over 8 years ago in reply to Rex Chang

Expert 1140 points

Hello Rex,

I printed out all the DP83867 register values in the driver "drivers/net/phy/dp83867.c" function "dp83867_config_init" when the cable was plugged into a 1Gb/s NIC in a PC. See them below. It looks like the auto-negotiation fails.

Our chip is 83867CSRGZ. The datasheet we are using is the SNLS504.

Best regards,

Ari

[   16.473017] TI DP83867 26200f00.mdio:00: direct reg address: 0x00, value = 0x1140
[   16.480735] TI DP83867 26200f00.mdio:00: direct reg address: 0x01, value = 0x796d
[   16.494976] TI DP83867 26200f00.mdio:00: direct reg address: 0x02, value = 0x2000
[   16.514908] TI DP83867 26200f00.mdio:00: direct reg address: 0x03, value = 0xa231
[   16.522415] TI DP83867 26200f00.mdio:00: direct reg address: 0x04, value = 0x01e1
[   16.544895] TI DP83867 26200f00.mdio:00: direct reg address: 0x05, value = 0xc1e1
[   16.552431] TI DP83867 26200f00.mdio:00: direct reg address: 0x06, value = 0x006f
[   16.560357] TI DP83867 26200f00.mdio:00: direct reg address: 0x07, value = 0x2001
[   16.575065] TI DP83867 26200f00.mdio:00: direct reg address: 0x08, value = 0x4000
[   16.595255] TI DP83867 26200f00.mdio:00: direct reg address: 0x09, value = 0x0300
[   16.602788] TI DP83867 26200f00.mdio:00: direct reg address: 0x0a, value = 0x3800
[   16.610586] TI DP83867 26200f00.mdio:00: direct reg address: 0x0d, value = 0x401f
[   16.625182] TI DP83867 26200f00.mdio:00: direct reg address: 0x0e, value = 0x1140
[   16.632727] TI DP83867 26200f00.mdio:00: direct reg address: 0x0f, value = 0x3000
[   16.659209] TI DP83867 26200f00.mdio:00: direct reg address: 0x10, value = 0x5848
[   16.666792] TI DP83867 26200f00.mdio:00: direct reg address: 0x11, value = 0xbf02
[   16.674303] TI DP83867 26200f00.mdio:00: direct reg address: 0x12, value = 0x0000
[   16.682098] TI DP83867 26200f00.mdio:00: direct reg address: 0x13, value = 0x5c40
[   16.689679] TI DP83867 26200f00.mdio:00: direct reg address: 0x14, value = 0x2fc7
[   16.697950] TI DP83867 26200f00.mdio:00: direct reg address: 0x15, value = 0x0000
[   16.705525] TI DP83867 26200f00.mdio:00: direct reg address: 0x16, value = 0x0000
[   16.713019] TI DP83867 26200f00.mdio:00: direct reg address: 0x17, value = 0x0040
[   16.720645] TI DP83867 26200f00.mdio:00: direct reg address: 0x18, value = 0x6150
[   16.728245] TI DP83867 26200f00.mdio:00: direct reg address: 0x19, value = 0x4444
[   16.735832] TI DP83867 26200f00.mdio:00: direct reg address: 0x1a, value = 0x0002
[   16.743345] TI DP83867 26200f00.mdio:00: direct reg address: 0x1e, value = 0x0002
[   16.750931] TI DP83867 26200f00.mdio:00: direct reg address: 0x1f, value = 0x0000
[   16.758654] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0025, value = 0x0400
[   16.767411] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0031, value = 0x10b0
[   16.776377] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0032, value = 0x00d3
[   16.784402] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0033, value = 0x0000
[   16.793421] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0037, value = 0x0003
[   16.802286] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0043, value = 0x07a0
[   16.811302] TI DP83867 26200f00.mdio:00: indirect reg address: 0x006e, value = 0x0820
[   16.820813] TI DP83867 26200f00.mdio:00: indirect reg address: 0x006f, value = 0x0000
[   16.829775] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0071, value = 0x0000
[   16.838793] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0072, value = 0x0000
[   16.847576] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0086, value = 0x0077
[   16.863507] TI DP83867 26200f00.mdio:00: indirect reg address: 0x00d3, value = 0x0000
[   16.872552] TI DP83867 26200f00.mdio:00: indirect reg address: 0x00fe, value = 0xe721
[   16.881306] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0134, value = 0x1000
[   16.892715] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0135, value = 0x0000
[   16.901861] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0136, value = 0x0000
[   16.911787] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0137, value = 0x0000
[   16.922260] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0138, value = 0x0000
[   16.931796] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0139, value = 0x0000
[   16.940580] TI DP83867 26200f00.mdio:00: indirect reg address: 0x013a, value = 0x0000
[   16.951961] TI DP83867 26200f00.mdio:00: indirect reg address: 0x013b, value = 0x0000
[   16.961082] TI DP83867 26200f00.mdio:00: indirect reg address: 0x013c, value = 0x0000
[   16.969813] TI DP83867 26200f00.mdio:00: indirect reg address: 0x013e, value = 0x0000
[   16.981274] TI DP83867 26200f00.mdio:00: indirect reg address: 0x013f, value = 0x0000
[   16.990446] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0140, value = 0x0000
[   16.999204] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0141, value = 0x0000
[   17.010507] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0142, value = 0x0000
[   17.019680] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0143, value = 0x0000
[   17.030464] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0144, value = 0x0000
[   17.039844] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0145, value = 0x0000
[   17.049772] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0146, value = 0x0000
[   17.059203] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0147, value = 0x0000
[   17.068792] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0148, value = 0x0000
[   17.087556] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0149, value = 0x0000
[   17.087761] TI DP83867 26200f00.mdio:00: indirect reg address: 0x014a, value = 0x0000
[   17.087969] TI DP83867 26200f00.mdio:00: indirect reg address: 0x014b, value = 0x0000
[   17.088176] TI DP83867 26200f00.mdio:00: indirect reg address: 0x014c, value = 0x0000
[   17.088384] TI DP83867 26200f00.mdio:00: indirect reg address: 0x014d, value = 0x0000
[   17.088594] TI DP83867 26200f00.mdio:00: indirect reg address: 0x014e, value = 0x0000
[   17.088799] TI DP83867 26200f00.mdio:00: indirect reg address: 0x014f, value = 0x0000
[   17.089006] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0150, value = 0x0000
[   17.089216] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0151, value = 0x0000
[   17.089424] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0152, value = 0x0000
[   17.089631] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0153, value = 0x0000
[   17.089839] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0154, value = 0x0000
[   17.090045] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0155, value = 0x0000
[   17.090253] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0156, value = 0x0000
[   17.090461] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0157, value = 0x0000
[   17.090668] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0158, value = 0x0000
[   17.090879] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0159, value = 0x0000
[   17.091088] TI DP83867 26200f00.mdio:00: indirect reg address: 0x015a, value = 0x0000
[   17.091297] TI DP83867 26200f00.mdio:00: indirect reg address: 0x015b, value = 0x0000
[   17.091504] TI DP83867 26200f00.mdio:00: indirect reg address: 0x015c, value = 0x0000
[   17.091710] TI DP83867 26200f00.mdio:00: indirect reg address: 0x015d, value = 0x0000
[   17.091916] TI DP83867 26200f00.mdio:00: indirect reg address: 0x015e, value = 0x0000
[   17.092124] TI DP83867 26200f00.mdio:00: indirect reg address: 0x015f, value = 0x0000
[   17.092337] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0161, value = 0x000c
[   17.092541] TI DP83867 26200f00.mdio:00: indirect reg address: 0x016f, value = 0x0095
[   17.092751] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0170, value = 0x0c0f
[   17.092958] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0172, value = 0x0000
[   17.093165] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0180, value = 0x0752
[   17.093372] TI DP83867 26200f00.mdio:00: indirect reg address: 0x01a7, value = 0xf020
[   17.093579] TI DP83867 26200f00.mdio:00: indirect reg address: 0x0000, value = 0x1140

0 Zeb over 8 years ago in reply to Ari Poutanen

Intellectual 380 points

One more bit of information: After the linux boots, connecting to 100M network is fine. This can be repeated by pulling the cable off and on again. Link is always working. But if we attempt to connect to 1Gb network (either a PC or a switch), link comes up and then right after down (with cable still connected). After it does this, connecting back to a 100M network does not work - link is now permanently down. Just as if some process in Linux dies (although no crash reported by Linux or any other additional message).

When do you have time to look into this issue?

EDIT: And we are using the SGMII mode on the PHY. 100Mbit/sec speed was also tested by sending message to PC using TCP/IP, also reception of messages was ok. So with 100M everyting is ok. With 1G speed, nothing works.

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

Hi, Zeb,

I contacted TI hardware engineer and ran through your configuration with him. Once I hear back from him, we'll update you. Thanks!

Rex

0 Zeb over 8 years ago in reply to Rex Chang

Intellectual 380 points

Ari stabbed the kernel and recorded the PHY registers while the 1Gbps link becomes up (these are register values before the link goes down) :

[ 115.885179] netcp-1.0 2620110.netcp eth0: Link is Up - 1Gbps/Full - flow control off
[ 115.892936] netcp-1.0 2620110.netcp eth0: direct reg address: 0x00, value = 0x1140
[ 115.902682] netcp-1.0 2620110.netcp eth0: direct reg address: 0x01, value = 0x796d
[ 115.911309] netcp-1.0 2620110.netcp eth0: direct reg address: 0x02, value = 0x2000
[ 115.919885] netcp-1.0 2620110.netcp eth0: direct reg address: 0x03, value = 0xa231
[ 115.928459] netcp-1.0 2620110.netcp eth0: direct reg address: 0x04, value = 0x01e1
[ 115.937061] netcp-1.0 2620110.netcp eth0: direct reg address: 0x05, value = 0xc1e1
[ 115.944647] netcp-1.0 2620110.netcp eth0: direct reg address: 0x06, value = 0x006f
[ 115.954133] netcp-1.0 2620110.netcp eth0: direct reg address: 0x07, value = 0x2001
[ 115.961876] netcp-1.0 2620110.netcp eth0: direct reg address: 0x08, value = 0x4000
[ 115.969490] netcp-1.0 2620110.netcp eth0: direct reg address: 0x09, value = 0x0300
[ 115.977103] netcp-1.0 2620110.netcp eth0: direct reg address: 0x0a, value = 0x3800
[ 115.984690] netcp-1.0 2620110.netcp eth0: direct reg address: 0x0d, value = 0x401f
[ 115.992305] netcp-1.0 2620110.netcp eth0: direct reg address: 0x0e, value = 0x1140
[ 115.999918] netcp-1.0 2620110.netcp eth0: direct reg address: 0x0f, value = 0x3000
[ 116.007506] netcp-1.0 2620110.netcp eth0: direct reg address: 0x10, value = 0x5848
[ 116.015120] netcp-1.0 2620110.netcp eth0: direct reg address: 0x11, value = 0xbf02
[ 116.022707] netcp-1.0 2620110.netcp eth0: direct reg address: 0x12, value = 0x0000
[ 116.030322] netcp-1.0 2620110.netcp eth0: direct reg address: 0x13, value = 0x5c40
[ 116.037909] netcp-1.0 2620110.netcp eth0: direct reg address: 0x14, value = 0x29c7
[ 116.045523] netcp-1.0 2620110.netcp eth0: direct reg address: 0x15, value = 0x0000
[ 116.053111] netcp-1.0 2620110.netcp eth0: direct reg address: 0x16, value = 0x0000
[ 116.060699] netcp-1.0 2620110.netcp eth0: direct reg address: 0x17, value = 0x0040
[ 116.068286] netcp-1.0 2620110.netcp eth0: direct reg address: 0x18, value = 0x6150
[ 116.075900] netcp-1.0 2620110.netcp eth0: direct reg address: 0x19, value = 0x4444
[ 116.083488] netcp-1.0 2620110.netcp eth0: direct reg address: 0x1a, value = 0x0002
[ 116.091102] netcp-1.0 2620110.netcp eth0: direct reg address: 0x1e, value = 0x0002
[ 116.098690] netcp-1.0 2620110.netcp eth0: direct reg address: 0x1f, value = 0x0000
[ 116.106460] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0025, value = 0x0400
[ 116.114541] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0031, value = 0x10b0
[ 116.122649] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0032, value = 0x0053
[ 116.130757] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0033, value = 0x0000
[ 116.138864] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0037, value = 0x0003
[ 116.146972] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0043, value = 0x07a0
[ 116.155079] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x006e, value = 0x0820
[ 116.163160] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x006f, value = 0x0000
[ 116.171268] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0071, value = 0x0000
[ 116.179376] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0072, value = 0x0000
[ 116.187483] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0086, value = 0x0077
[ 116.195590] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x00d3, value = 0x0000
[ 116.203674] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x00fe, value = 0xe721
[ 116.211779] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0134, value = 0x1000
[ 116.219887] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0135, value = 0x0000
[ 116.227969] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0136, value = 0x0000
[ 116.236076] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0137, value = 0x0000
[ 116.244157] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0138, value = 0x0000
[ 116.252265] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0139, value = 0x0000
[ 116.260376] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x013a, value = 0x0000
[ 116.268481] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x013b, value = 0x0000
[ 116.276588] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x013c, value = 0x0000
[ 116.284669] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x013e, value = 0x0000
[ 116.292777] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x013f, value = 0x0000
[ 116.300885] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0140, value = 0x0000
[ 116.308992] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0141, value = 0x0000
[ 116.317100] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0142, value = 0x0000
[ 116.325208] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0143, value = 0x0000
[ 116.333290] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0144, value = 0x0000
[ 116.341396] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0145, value = 0x0000
[ 116.349504] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0146, value = 0x0000
[ 116.357616] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0147, value = 0x0000
[ 116.365719] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0148, value = 0x0000
[ 116.373800] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0149, value = 0x0000
[ 116.381908] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x014a, value = 0x0000
[ 116.390016] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x014b, value = 0x0000
[ 116.398123] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x014c, value = 0x0000
[ 116.406231] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x014d, value = 0x0000
[ 116.414312] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x014e, value = 0x0000
[ 116.422420] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x014f, value = 0x0000
[ 116.430527] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0150, value = 0x0000
[ 116.438635] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0151, value = 0x0000
[ 116.446742] netcp-1.0 2620110.netcp eth0: indirect reg address: 0x0152, value = 0x0000
[ 116.454803] netcp-1.0 2620110.netcp eth0: Link is Down

While going through these, I cannot see any errors or anything that would indicate that something is wrong. But still, the link goes down automatically. We tried to record the PHY registers after the link goes down but for some reason Linux just crahses.

Then a few words about the layout:

The PHY and SOC are located on separate boards and these boards have a high speed connector in between them (SAMTEC QTH-QSH connectors). According to Samtec's test data, our connectors' measured test data show that the 1.25GHz speed is not a problem through this connector.

In the layout (on both cards), SGMII signals (both RX and TX pair) have an impedance of 100ohm (diffpair impedance) and routing is done correctly on an impedance controlled layer without any stubs, also within both pairs length mismatch is less than 1mils. On both upper and lower layers of the SGMII signals the copper is continuous.

Series capacitors are in place in both pairs' ends, SOC tx line (PHY RX) caps are located just before the PHY. SOC RX line caps are just before SOC RX pins.

PHY TX+ pin includes the strap resistors (these are NC) and they are also placed just before the PHY and symmetrically placed so that this pair does not 'get disturbed' or the pair does not 'separate'. And for symmetry reasons resistor divider was added also to the TX-. But in both of these signals, there are no resistors connected.

We are completely lost with this issue...... Do you know of ANY application where the 83867CS has been successfully implemented with 1Gbit Ethernet, in SGMII mode and with Linux?

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

Hi, Zeb,

Your layout information will be helpful. We reviewed the datasheets for both K2E/L SoC and DP83867. I just want to point out that DP83867 only supports RGMII, not SGMII. As far as software driver, DP83867 driver checks the PHY if it is not RGMII, it returns without confinuing further. I am still working with Hardware engineer to see how this can be resolved, and what will be the impact. We are also trying to understand why it even works with 100Mb rate if they are different interfaces.

Rex

0 Rex Chang over 8 years ago in reply to Rex Chang

TI__Guru 50170 points

Hi, Ari & Zeb,

Could you contact TI local FAE and provide a diagram of the circuit implementation of K2E and PHY
with the interfaces labeled, also indicate the location of the resistors?
TI hardware engineer would like to review it.

Thanks!

Rex

0 Zeb over 8 years ago in reply to Rex Chang

Intellectual 380 points

Hi Rex,

Just to clarify, we are using the DP83867CS PHY which supports SGMII.

I have been in contact with TI office in Finland and they have been very helpful. Also, I sent them the schematic part of the PHY but did not send any layout documentation. But I will discuss with them and possibly send some gerber files for further examination. I will ask them to be in contact with you so that information is not spread all over TI - hopefully you will end up discussing together with them. And due to confidentiality reasons, I am not allowed to share any design documentation here in a public forum.

The driver code seems quite simple so is it possible for you to add the SGMII support? This support of only RGMII is very disappointing news since the driver documentation does not mention anywhere that it does not support SGMII. While I was doing the HW design, I checked all documentation and decided that the CS PHY is the way to go since there was no mention that only RGMII is supported. I cannot now go back and make new PCBs, far too expensive to go back to RGMII now since we are close to manufacturing the 1st production batch for the DSP cards.

I sincerely hope this issue can be resolved. If not, we're in big trouble.

- Zeb

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

Hi, Zeb,

I got the design this morning and forwarded to hardware engineer to review. We'll probably go through FAE channel for further discussion instead of posting here in public forum.

Rex

0 Rex Chang over 8 years ago in reply to Rex Chang

TI__Guru 50170 points

Hi, Zeb & Ari,

Just realized that for a schematics review, TI FAE needs to submit it through a TI review website,
ap-fpdsp-swapps.dal.design.ti.com/.../OMAP3_Catalog_Apps_Main_Page
I asked Esa to submit it so it can be reviewed.

I also hear back from development team that the kernel driver does not support SGMII at this time due to not having any test EVMs to validate it prior to posting to the Linux Kernel.

However, u-boot does support SGMII as developed by another customer. You may want to look at the u-boot code in drivers/net/phy/ti.c and migrate it to the kernel.

Rex

0 Ari Poutanen over 8 years ago in reply to Rex Chang

Expert 1140 points

Hello Rex,

we have already studied the u-boot code and seen that it supports the SGMII, but it also works only for 100Mbps. 1Gbps does not work in u-boot either.

Thanks anyway! :-)

Best regards,

Ari

0 Zeb over 8 years ago in reply to Ari Poutanen

Intellectual 380 points

Do you know Rex if the uboot driver code for SGMII has worked @1Gb? This would be very valuable information for us at the moment.

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

Hi, Zeb,

We don't have data on what the individual who added the code was able to achieve but the code reads that it should support 1Gb data rates. The U-boot handles the SGMII configuration. Gernerally, the PHY handles the speed negotiation. Be sure to have the pin straps correct on the device.

Rex

0 Zeb over 8 years ago in reply to Rex Chang

Intellectual 380 points

All straps have been already checked many times, they are fine (also checked by the local TI). Problem is in the SGMII autoneg, that fails @1Gb. Samtec made a simulation (sent to local TI, you should get it also) with trace lengths (I supplied them the exact length of the traces) and connectors being used and according to results, 1.25G should be just fine. As for your experts analysis for the layout, I have heard nothing yet. When will they give their opinion?

In the meantime I tried to find the base address for SGMII Boot Configuration registers but failed (doc SPRUGV9D, page 3-114). What is the address for these in K2L? I am especially interested in the SGMII_SERDES_CGFRX and SGMII_SERDES_CFGTX.

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

Hi, Zeb,

The document you used is for Keystone-1 device (Multicore DSP), not for Keystone-2 device (Multicore ARM+DSP). You can find GbE and Serdes Documents under K2L page, www.ti.com/.../technicaldocuments.

KS-2 GbE for K2E/L is SPRUHZ3A. Serdes is SPRUHO3A. K2E/L uses 4-Lane PHY configuration.

Rex

0 Zeb over 8 years ago in reply to Rex Chang

Intellectual 380 points

Hi Rex,

Sorry, this is a bit confusing.... The serdes doc for K2L is the SPRUHO3A but on page 39:
---------------------------------------
For details on SGMII SerDes configuration registers, definitions and settings, see the KeyStone
Architecture GbE User Guide, in Related Documentation from Texas Instruments.
-----------------------------------------
Selecting 'Related documentation from Texas Instruments' goes to point SPRUGV9D which talks Keystone I and II separately.

That is how I ended up in the SPRUGV9D. If this is not a mistake in the documentation, please inform us the address of SGMII_SERDES_CGFRX and SGMII_SERDES_CFGTX registers. If these settings are somewhere else, please let me know where I can find these settings.

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

HI, Zeb,

Those registers don't apply to Keystone-2 devices. Only keystone-1 (C64x and c66x) has those registers.

Rex

0 Rex Chang over 8 years ago in reply to Rex Chang

TI__Guru 50170 points

Zeb,

Please refer to this thread for more detailed info: e2e.ti.com/.../546319

Rex

0 Zeb over 8 years ago in reply to Rex Chang

Intellectual 380 points

Rex,

Thank you for the link! This documentation is a big mess.... It is impossible to follow all this, I find it difficult to know my way home after ping-ponging around for the full day. You should really update the documentation to be more clear.
I was linked to SPRAC37 and it tells that you there are the regs for RX tuning which was originally mentioned that they dont exist. We will try to run some tests based on this doc. It is also very general but that seems to be the way to proceed although I am not very optimistic that these tests are easily performed.

- Zeb

0 Zeb over 8 years ago in reply to Zeb

Intellectual 380 points

Issue is now resolved, problem was in DP83867CS. New DP83867 updated datasheet (revised Feb 2017) had a change in strap resistor setting RX_CTRL: Modes 1 & 2 should not be used and mode 3 & 4 should be used only. So we changed to mode 3 and now 1Gb Ethernet works just fine.

It is still a bit strange since the strap mode register showed that autoneg was enabled in mode 1 but SGMII autoneg failed. Now in mode 3 SGMII autoneg also works. Enormous amount of sw debugging - just because of a mistake in datasheet!!!!

0 Rex Chang over 8 years ago in reply to Zeb

TI__Guru 50170 points

Hi, Zeb,

Thanks for the info and glad it works finally. I'll pass the info to the development team to see if where we can improve in the documentation.

I'll close this thread. Please open a new thread if there is any other issue. Thanks!

Rex

Processors

Processors forum

Linux/66AK2L06: Gigabit Ethernet Net-cp issue