topic Re: IMX6Q -PCIE+i210 ethernet controller in u-boot in i.MX Processors

IMX6Q -PCIE+i210 ethernet controller in u-boot

agnel_terry — Tue, 14 May 2019 21:44:09 GMT

HI ,

I have accustom hardware uses IMX6q which has a intel i210 ethernet controller connected to PCIE of IMX6Q , I had configured the PCIE in Kernel and enabled the e1000 driver , I am able to enumerate the controller ping works fine, etc.

whereas when I try to configure the controller and PCIE in UBoot, I see PCI driver listing the devices but the ethernet controller is not seen in the "NET:" looks like the e1000 driver is not getting linked to built-in.o

Can someone help me with the correct configuration of the uboot for PCIE and e1000. (I am not using driver model, I am configuring my 2017 in the legacy way.

Below is my Uboot log

U-Boot 2017.03 (May 14 2019 - 14:22:34 -0700)

CPU:   Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
CPU:   Automotive temperature grade (-40C to 125C) at 55C
Reset cause: POR
Board: iMX6q Sbare-SD
I2C:   ready
DRAM: 2 GiB
spi setup
i2C INIT :
PMIC: PFUZE100 ID=0x10
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

PCI:
00:01.0     - 16c3:abcd - Bridge device
   01:00.0    - 8086:1533 - Network controller
No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In:    serial
Out:   serial
Err:   serial
switch to partitions #0, OK
mmc0 is current device
Net:   FEC
Normal Boot
Hit any key to stop autoboot: 0
=> pci
Scanning PCI devices on bus 0
BusDevFun VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
00.01.00   0x16c3     0xabcd     Bridge device           0x04
Cannot read bus configuration: -1
=> pci 1
Scanning PCI devices on bus 1
BusDevFun VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
01.00.00   0x8086     0x1533     Network controller      0x00
Cannot read bus configuration: -1

=> pci header 1
vendor ID =                   0x16c3
device ID =                   0xabcd
command register ID =         0x0007
status register =             0x0010
revision ID =                 0x01
class code =                  0x06 (Bridge device)
sub class code =              0x04
programming interface =       0x00
cache line =                  0x08
latency time =                0x00
header type =                 0x01
BIST =                        0x00
base address 0 =              0x01000000
base address 1 =              0x00000000
primary bus number =          0x00
secondary bus number =        0x01
subordinate bus number =      0x01
secondary latency timer =     0x00
IO base =                     0x00
IO limit =                    0x00
secondary status =            0x0000
memory base =                 0x0120
memory limit =                0x0120
prefetch memory base =        0x1000
prefetch memory limit =       0x0000
prefetch memory base upper = 0x00000000
prefetch memory limit upper = 0x00000000
IO base upper 16 bits =       0x0000
IO limit upper 16 bits =      0x0000
expansion ROM base address = 0x01100000
interrupt line =              0xff
interrupt pin =               0x01
bridge control =              0x0000

Thanks and Regards

Terry

Re: IMX6Q -PCIE+i210 ethernet controller in u-boot

igorpadykov — Wed, 15 May 2019 05:41:25 GMT

Hi Terry

one can check ifdef CONFIG_PCI in uboot/include/configs/mx6sabresd.h

and test several cards

mx6sabresd.h\configs\include - uboot-imx - i.MX U-Boot

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: IMX6Q -PCIE+i210 ethernet controller in u-boot

agnel_terry — Wed, 15 May 2019 16:00:07 GMT

Hi Igor,

Thank you for the response, the problem is not on the PCI/PCIE layer, as mentioned I am able to see the device getting listed in the PCI:

PCI:
00:01.0 - 16c3:abcd - Bridge device
01:00.0 - 8086:1533 - Network controller

whereas its not seen in the NET :, The net shows only the IMX6 FEC, I had added "CONFIG_E1000=y" for the ethernet controller driver, still I don't see the device getting listed under,NET.

Thanks

Terry

Re: IMX6Q -PCIE+i210 ethernet controller in u-boot

igorpadykov — Wed, 15 May 2019 23:45:54 GMT

Hi Terry

as this is not specific imx issue this may be posted on uboot mail list

U-Boot Info Page

Best regards
igor

Re: IMX6Q -PCIE+i210 ethernet controller in u-boot

agnel_terry — Thu, 16 May 2019 16:14:26 GMT

Thank you Igor, will post it in the u-boot info page

Re: IMX6Q -PCIE+i210 ethernet controller in u-boot

mike — Thu, 12 Sep 2019 14:12:04 GMT

HI Terry

for the i210 in defconfig

CONFIG_NET_VENDOR_INTEL=y

CONFIG_IGB=y
CONFIG_IGB_HWMON=y

lspci

04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

I am also fighting the iMX6q with i210 and XR17V358 - The PCIe works on some PCBs work and not on other PCBs

Regards

Mike

回复： IMX6Q -PCIE+i210 ethernet controller in u-boot

tzeng015 — Thu, 13 Oct 2022 08:19:39 GMT

I have a big problem and need your help.

(47) Intel i210 Plug in crash - YouTube

My Board : Imx8mm

Linux version : 5.10

Ethernet Card : Intel I210

When I plugged in the line to RJ45, this is the kernel messaage.

Please give me a hand.

thank you

[ 1645.118487] igb 0000:01:00.0: Detected Tx Unit Hang 1011-1 XXXXXXXX
[ 1645.118487] Tx Queue <3>
[ 1645.118487] TDH <0>
[ 1645.118487] TDT <1>
[ 1645.118487] next_to_use <1>
[ 1645.118487] next_to_clean <0>
[ 1645.118487] buffer_info[next_to_clean]
[ 1645.118487] time_stamp <100051ed0>
[ 1645.118487] next_to_watch <0000000037bbc16b>
[ 1645.118487] jiffies <100052197>
[ 1645.118487] desc.status <4f4000>
[ 1647.839563] ------------[ cut here ]------------
[ 1647.844215] 1007-3 XXXX NETDEV WATCHDOG: eth1 (igb): transmit queue 0 timed out
[ 1647.851607] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:485 dev_watchdog+0x300/0x310
[ 1647.859876] Modules linked in: overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine rng_core authenc libdes crct10dif_ce caam secvio error gpio_ir_recv rc_core fuse
[ 1647.877395] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.72-lts-5.10.y+g22ec7e8cbace #1
[ 1647.885570] Hardware name: FSL i.MX8MM EVK board (DT)
[ 1647.890624] pstate: 20000005 (nzCv daif -PAN -UAO -TCO BTYPE=--)
[ 1647.896635] pc : dev_watchdog+0x300/0x310
[ 1647.900647] lr : dev_watchdog+0x300/0x310
[ 1647.904656] sp : ffff800011d4bd90
[ 1647.907970] x29: ffff800011d4bd90 x28: ffff0000c0e9f940
[ 1647.913287] x27: 0000000000000004 x26: ffff0000c180c480
[ 1647.918605] x25: 0000000000000140 x24: 00000000ffffffff
[ 1647.923923] x23: ffff0000c180c3dc x22: 0000000000000000
[ 1647.929238] x21: ffff800011b36000 x20: ffff0000c180c000
[ 1647.934554] x19: 0000000000000000 x18: 0000000000000030
[ 1647.939869] x17: 0000000000000000 x16: 0000000000000000
[ 1647.945185] x15: ffff800011b427f8 x14: 4454454e20585858
[ 1647.950501] x13: ffff800011b517b0 x12: 00000000000005eb
[ 1647.955818] x11: 00000000000001f9 x10: ffff800011ba97b0
[ 1647.961136] x9 : 00000000fffff000 x8 : ffff800011b517b0
[ 1647.966453] x7 : ffff800011ba97b0 x6 : 0000000000000003
[ 1647.971768] x5 : 0000000000000000 x4 : 0000000000000000
[ 1647.977084] x3 : 0000000000000000 x2 : 0000000000000100
[ 1647.982399] x1 : 298971a5ac26f600 x0 : 0000000000000000
[ 1647.987716] Call trace:
[ 1647.990166] dev_watchdog+0x300/0x310
[ 1647.993834] call_timer_fn.constprop.0+0x24/0x80
[ 1647.998454] __run_timers.part.0+0x1f4/0x22c
[ 1648.002726] run_timer_softirq+0x3c/0x7c
[ 1648.006651] efi_header_end+0x124/0x290
[ 1648.010490] irq_exit+0xdc/0xfc
[ 1648.013634] __handle_domain_irq+0x80/0xe0
[ 1648.017733] gic_handle_irq+0xc0/0x140
[ 1648.021483] el1_irq+0xcc/0x180
[ 1648.024629] cpuidle_enter_state+0x130/0x2f0
[ 1648.028901] cpuidle_enter+0x38/0x50
[ 1648.032480] do_idle+0x218/0x2a0
[ 1648.035710] cpu_startup_entry+0x24/0x70
[ 1648.039636] rest_init+0xd8/0xe8
[ 1648.042869] arch_call_rest_init+0x10/0x1c
[ 1648.046966] start_kernel+0x4ac/0x4e4
[ 1648.050629] ---[ end trace a9279d2e8a564f58 ]---