This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/66AK2E05: PCIe Soft Reset

Part Number: 66AK2E05

Tool/software: Linux

Hello, 

I am using PCIe Interface to communicate between keystone 2 as a root complex and an picozed board as an endpoint. However i want do reset the PCIe in case there is a connection lost, without rebooting my system. Any idea how i might be able to do this? I have tried to remove and rescan the PCIe Bridge, it doesnt work for me. I believe there is a Reset command Register in the application space registers that can be used to soft reset the PCIe Bridge. Any ideas how i might be able to access it?

 

  • Hi,

    See the PCI Express (PCIe) User Guide for Keystone II devices (www.ti.com/.../sprugs6d.pdf), section 2.13.2 Software Reset Considerations:
    The PCIESS module contains a software reset (INIT_RST) bit in the Reset Command Register (RSTCMD) that is used to issue a hot reset.

    Best Regards,
    Yordan
  • Thanks for your reply Yordon,
    I am kind of new to this, and i am not sure how can i access the Reset Command Register, Can you help me out? How can i access and modify the register in linux environment.
  • Can you tell me how can i access the register?
  • Hi,

    One possibility is to use devmem2 command from linux console. The command should be executed as:
    devmem2 0x21800014 ===> this accesses Reset Command Register for PCIe 0 config
    devmem2 0x21020014 ===> this accesses Reset Command Register for PCIe 1 config

    Another option is to implement reset sequence in the PCIe driver in linux kernel, which complies with the sequence described in the PCIe User Guide. The source is located in drivers/pci/controller/.

    Best Regards,
    Yordan
  • I tried using the first suggested solution, it does not seem to work, this is the configuration space when everything is working fine.

    I simulate the link drop condition by resetting the Picozed board, and the configuration space seems to be corrupted afterwards, as you can see in the picture below.

    I tried the solution suggested by you, but the configuration space is still corrupted. I tried the following.

    The configuration space is still same,

     

    Any ideas whats wrong with it?

  • Hi,

    Are you getting any error messages on your console, when the device is reset? Can you share it?
    Can you post your bootlog?

    Best Regards,
    Yordan
  • Hi,
    this is what i get when i dmesg



    root@k2hk-evm:~# dmesg

    [ 3690.007461] keystone-netcp 2090000.netcp: pdsp 5 firmware: keystone/pa_pdsp45_pam.fw
    [ 3690.015386] keystone-netcp 2090000.netcp: could not find interface 2 node in device tree
    [ 3690.023506] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
    [ 3690.031715] keystone-netcp 2090000.netcp: could not find interface 3 node in device tree
    [ 3690.039833] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
    [ 3690.048052] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
    [ 3690.056173] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
    [ 3690.065269] dwc3 2690000.dwc3: no usb2 phy configured
    [ 3690.070342] platform 2690000.dwc3: Driver dwc3 requests probe deferral
    [ 3690.077314] usbcore: registered new interface driver usb-storage
    [ 3690.083755] mousedev: PS/2 mouse device common for all mice
    [ 3690.089547] i2c /dev entries driver
    [ 3690.093656] watchdog 22f0080.wdt: heartbeat 60 sec
    [ 3690.109561] keystone-crypto 20c0000.crypto: crypto accelerator enabled
    [ 3690.116411] usbcore: registered new interface driver usbhid
    [ 3690.122000] usbhid: USB HID core driver
    [ 3690.126204] remoteproc0: 2620040.dsp0 is available
    [ 3690.131097] remoteproc0: Note: remoteproc is still under development and considered experimental.
    [ 3690.140085] remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.150493] remoteproc0: no firmware found
    [ 3690.154818] rproc-user 2620040.dsp0: registered misc device dsp0
    [ 3690.161111] remoteproc1: 2620044.dsp1 is available
    [ 3690.166003] remoteproc1: Note: remoteproc is still under development and considered experimental.
    [ 3690.174992] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.185401] remoteproc1: no firmware found
    [ 3690.189711] rproc-user 2620044.dsp1: registered misc device dsp1
    [ 3690.195976] remoteproc2: 2620048.dsp2 is available
    [ 3690.200867] remoteproc2: Note: remoteproc is still under development and considered experimental.
    [ 3690.209856] remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.220264] remoteproc2: no firmware found
    [ 3690.224578] rproc-user 2620048.dsp2: registered misc device dsp2
    [ 3690.230840] remoteproc3: 262004c.dsp3 is available
    [ 3690.235732] remoteproc3: Note: remoteproc is still under development and considered experimental.
    [ 3690.244722] remoteproc3: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.255129] remoteproc3: no firmware found
    [ 3690.259434] rproc-user 262004c.dsp3: registered misc device dsp3
    [ 3690.265705] remoteproc4: 2620050.dsp4 is available
    [ 3690.270596] remoteproc4: Note: remoteproc is still under development and considered experimental.
    [ 3690.279585] remoteproc4: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.289996] remoteproc4: no firmware found
    [ 3690.294305] rproc-user 2620050.dsp4: registered misc device dsp4
    [ 3690.300568] remoteproc5: 2620054.dsp5 is available
    [ 3690.305459] remoteproc5: Note: remoteproc is still under development and considered experimental.
    [ 3690.314449] remoteproc5: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.324856] remoteproc5: no firmware found
    [ 3690.329172] rproc-user 2620054.dsp5: registered misc device dsp5
    [ 3690.335439] remoteproc6: 2620058.dsp6 is available
    [ 3690.340330] remoteproc6: Note: remoteproc is still under development and considered experimental.
    [ 3690.349319] remoteproc6: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.359726] remoteproc6: no firmware found
    [ 3690.364032] rproc-user 2620058.dsp6: registered misc device dsp6
    [ 3690.370298] remoteproc7: 262005c.dsp7 is available
    [ 3690.375190] remoteproc7: Note: remoteproc is still under development and considered experimental.
    [ 3690.384179] remoteproc7: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 3690.394585] remoteproc7: no firmware found
    [ 3690.398891] rproc-user 262005c.dsp7: registered misc device dsp7
    [ 3690.404934] rproc-user dspmem.38: kick gpio
    [ 3690.409241] rproc-user dspmem.38: registered misc device dspmem
    [ 3690.415369] ipip: IPv4 over IPv4 tunneling driver
    [ 3690.420476] gre: GRE over IPv4 demultiplexor driver
    [ 3690.425368] ip_gre: GRE over IPv4 tunneling driver
    [ 3690.430905] TCP: cubic registered
    [ 3690.434226] Initializing XFRM netlink socket
    [ 3690.439037] NET: Registered protocol family 10
    [ 3690.444112] NET: Registered protocol family 17
    [ 3690.448580] NET: Registered protocol family 15
    [ 3690.453036] NET: Registered protocol family 41
    [ 3690.457612] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
    [ 3690.465311] Registering SWP/SWPB emulation handler
    [ 3690.672242] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    [ 3690.677753] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
    [ 3690.686053] xhci-hcd xhci-hcd.0.auto: irq 425, io mem 0x02690000
    [ 3690.692114] usb usb1: default language 0x0409
    [ 3690.692135] usb usb1: udev 1, busnum 1, minor = 0
    [ 3690.692141] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [ 3690.698951] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [ 3690.706198] usb usb1: Product: xHCI Host Controller
    [ 3690.711091] usb usb1: Manufacturer: Linux 3.10.72-rt77-gdfe5ac2 xhci-hcd
    [ 3690.717813] usb usb1: SerialNumber: xhci-hcd.0.auto
    [ 3690.722947] usb usb1: usb_probe_device
    [ 3690.722955] usb usb1: configuration #1 chosen from 1 choice
    [ 3690.722963] xHCI xhci_add_endpoint called for root hub
    [ 3690.722968] xHCI xhci_check_bandwidth called for root hub
    [ 3690.722983] usb usb1: adding 1-0:1.0 (config #1, interface 0)
    [ 3690.723089] hub 1-0:1.0: usb_probe_interface
    [ 3690.723095] hub 1-0:1.0: usb_probe_interface - got id
    [ 3690.723103] hub 1-0:1.0: USB hub found
    [ 3690.726868] hub 1-0:1.0: 1 port detected
    [ 3690.730800] hub 1-0:1.0: standalone hub
    [ 3690.730805] hub 1-0:1.0: individual port power switching
    [ 3690.730810] hub 1-0:1.0: individual port over-current protection
    [ 3690.730815] hub 1-0:1.0: Single TT
    [ 3690.730820] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
    [ 3690.730825] hub 1-0:1.0: power on to power good time: 20ms
    [ 3690.730839] hub 1-0:1.0: local power source is good
    [ 3690.730874] hub 1-0:1.0: enabling power on all ports
    [ 3690.730968] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    [ 3690.736476] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
    [ 3690.744188] usb usb2: skipped 1 descriptor after endpoint
    [ 3690.744198] usb usb2: default language 0x0409
    [ 3690.744217] usb usb2: udev 1, busnum 2, minor = 128
    [ 3690.744223] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
    [ 3690.751034] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [ 3690.758280] usb usb2: Product: xHCI Host Controller
    [ 3690.763171] usb usb2: Manufacturer: Linux 3.10.72-rt77-gdfe5ac2 xhci-hcd
    [ 3690.769893] usb usb2: SerialNumber: xhci-hcd.0.auto
    [ 3690.775005] usb usb2: usb_probe_device
    [ 3690.775012] usb usb2: configuration #1 chosen from 1 choice
    [ 3690.775019] xHCI xhci_add_endpoint called for root hub
    [ 3690.775023] xHCI xhci_check_bandwidth called for root hub
    [ 3690.775040] usb usb2: adding 2-0:1.0 (config #1, interface 0)
    [ 3690.775138] hub 2-0:1.0: usb_probe_interface
    [ 3690.775143] hub 2-0:1.0: usb_probe_interface - got id
    [ 3690.775151] hub 2-0:1.0: USB hub found
    [ 3690.778913] hub 2-0:1.0: 1 port detected
    [ 3690.782846] hub 2-0:1.0: standalone hub
    [ 3690.782851] hub 2-0:1.0: individual port power switching
    [ 3690.782856] hub 2-0:1.0: individual port over-current protection
    [ 3690.782861] hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
    [ 3690.782866] hub 2-0:1.0: power on to power good time: 20ms
    [ 3690.782879] hub 2-0:1.0: local power source is good
    [ 3690.782912] hub 2-0:1.0: enabling power on all ports
    [ 3690.783219] UBI: attaching mtd2 to ubi0
    [ 3690.821040] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
    [ 3690.821086] hub 1-0:1.0: hub_suspend
    [ 3690.821102] usb usb1: bus auto-suspend, wakeup 1
    [ 3690.881031] hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0000
    [ 3690.881069] hub 2-0:1.0: hub_suspend
    [ 3690.881084] usb usb2: bus auto-suspend, wakeup 1
    [ 3692.383673] UBI: scanning is finished
    [ 3692.394052] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 40, need 74
    [ 3692.406435] UBI: attached mtd2 (name "ubifs", size 510 MiB) to ubi0
    [ 3692.412723] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    [ 3692.419532] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    [ 3692.426254] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
    [ 3692.433151] UBI: good PEBs: 4078, bad PEBs: 6, corrupted PEBs: 0
    [ 3692.439175] UBI: user volume: 5, internal volumes: 1, max. volumes count: 128
    [ 3692.446334] UBI: max/mean erase counter: 3/0, WL threshold: 4096, image sequence number: 406925177
    [ 3692.455324] UBI: available PEBs: 0, total reserved PEBs: 4078, PEBs reserved for bad PEB handling: 40
    [ 3692.464581] UBI: background thread "ubi_bgt0d" started, PID 1370
    [ 3692.471250] UBIFS: parse sync
    [ 3692.474715] UBIFS: background thread "ubifs_bgt0_2" started, PID 1374
    [ 3692.519706] UBIFS: mounted UBI device 0, volume 2, name "rootfs"
    [ 3692.525733] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
    [ 3692.534898] UBIFS: FS size: 468541440 bytes (446 MiB, 3690 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
    [ 3692.544847] UBIFS: reserved for root: 0 bytes (0 KiB)
    [ 3692.549913] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C2A09440-5091-4FB5-B26B-2B5F69B72D77, small LPT model
    [ 3692.561340] VFS: Mounted root (ubifs filesystem) on device 0:12.
    [ 3692.568399] devtmpfs: mounted
    [ 3692.571487] Freeing unused kernel memory: 240K (c068e000 - c06ca000)
    [ 3693.177451] udevd[1405]: starting version 182
    [ 3693.621992] temperature_kmodule: Unknown symbol hwmon_device_register (err 0)
    [ 3693.629356] temperature_kmodule: Unknown symbol hwmon_device_unregister (err 0)
    [ 3693.651495] uio_module_drv mpax.4: registered misc device mpax
    [ 3693.664435] temperature_kmodule: Unknown symbol hwmon_device_register (err 0)
    [ 3693.671672] temperature_kmodule: Unknown symbol hwmon_device_unregister (err 0)
    [ 3693.683200] uio_module_drv edma3.5: registered misc device edma3
    [ 3693.693066] CMEMK module: built on Sep 30 2015 at 05:09:19
    [ 3693.698569] Reference Linux version 3.10.72
    [ 3693.705243] uio_module_drv secmgr.6: registered misc device secmgr
    [ 3693.718140] no physical memory specified
    [ 3693.722373] cmemk initialized
    [ 3693.724580] uio_module_drv qmss.7: registered misc device qmss
    [ 3693.795935] uio_module_drv hyperlink0.41: registered misc device hyperlink0
    [ 3693.810634] uio_module_drv hyperlink1.42: registered misc device hyperlink1
    [ 3693.864308] uio_module_drv srio.43: registered misc device srio
    [ 3694.389879] keystone-netcp 2090000.netcp: initializing cpsw version 1.3 (1) SGMII identification value 0x4ed1
    [ 3694.400071] keystone-netcp 2090000.netcp: Created a cpsw ale engine
    [ 3694.581264] pps pps0: new PPS source ptp0
    [ 3694.585300] cpts rftclk rate(600000000 HZ),mult(5120),shift(10),div(3)
    [ 3694.626869] keystone-netcp 2090000.netcp: Using Packet Accelerator Firmware version 0x03000105
    [ 3694.635517] keystone-netcp 2090000.netcp: pa_clk_rate(163840000 HZ),mult(25000),shift(12)
    [ 3694.891384] net eth0: netcp device eth0 opened
    [ 3696.611988] cmemk unregistered
    [ 3696.618805] CMEMK module: built on Sep 30 2015 at 05:09:19
    [ 3696.624311] Reference Linux version 3.10.72
    [ 3696.628779] CMEMK Error: Failed to request_mem_region(0x829000000, 0x57000000)
    [ 3696.902362] uio_module_drv edma3.5: offset 0x2500100 is outside the allowed range
    [ 3698.180324] temperature_kmodule: Unknown symbol hwmon_device_register (err 0)
    [ 3698.187531] temperature_kmodule: Unknown symbol hwmon_device_unregister (err 0)




    root@k2hk-evm:~# lspci -xxx
    00:00.0 PCI bridge: Texas Instruments Device 8888 (rev ff)
    00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

    01:00.0 RAM memory: Xilinx Corporation Device 7011 (rev ff)
    00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  • I found a way while playing around with the application registers, when i disable and re enable the LTSSM_EN bit in the Command Status Register, i.e CMD_STATUS, the configuration space for the PCI bridge seems to be re configured, however the Configuration space for the End point, picozed in this case contains all zeros, any ideas that can help me configure that as well?

    i am sharing the console commands and results below.



    root@k2hk-evm:~# lspci -xxx
    00:00.0 PCI bridge: Texas Instruments Device 8888 (rev ff)
    00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

    01:00.0 RAM memory: Xilinx Corporation Device 7011 (rev ff)
    00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

    root@k2hk-evm:~# devmem2 0x21800004 w 0x00000006
    /dev/mem opened.
    Memory mapped at address 0xb6fb1000.
    Read at address 0x21800004 (0xb6fb1004): 0x00000006
    Write at address 0x21800004 (0xb6fb1004): 0x00000006, readback 0x00000006
    root@k2hk-evm:~# devmem2 0x21800004 w 0x00000007
    /dev/mem opened.
    Memory mapped at address 0xb6fc5000.
    Read at address 0x21800004 (0xb6fc5004): 0x00000006
    Write at address 0x21800004 (0xb6fc5004): 0x00000007, readback 0x00000007
    root@k2hk-evm:~# lspci -xxx
    00:00.0 PCI bridge: Texas Instruments Device 8888 (rev 01)
    00: 4c 10 88 88 47 01 10 00 01 00 04 06 10 00 01 00
    10: 00 00 80 21 08 00 00 80 00 01 01 00 f0 00 00 00
    20: 00 50 00 50 f0 ff 00 00 00 00 00 00 00 00 00 00
    30: 00 00 00 00 40 00 00 00 00 00 00 00 3c 01 01 00
    40: 01 50 03 00 00 00 00 00 00 00 00 00 00 00 00 00
    50: 05 70 80 00 00 00 00 00 00 00 00 00 00 00 00 00
    60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    70: 10 00 42 00 01 80 00 00 10 18 05 00 22 34 13 00
    80: 48 00 11 30 40 00 00 00 c0 03 40 00 00 00 00 00
    90: 00 00 00 00 1f 00 00 00 00 00 00 00 06 00 00 00
    a0: 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
    b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    01:00.0 RAM memory: Xilinx Corporation Device 7011
    00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    root@k2hk-evm:~#
  • Hi,

    We're looking into this.

    Best Regards,
    Yordan
  • looking forward to your response

    Best Regards
    Sheraz Javaid
  • Hi, Sheraz,

    I don't believe current kernel code does rescan. From the logs, it doesn't seem that the PCie driver is restarted either, but I'll need to try it.

    Rex
  • Hi Rex,
    What do you suggest i should do?

    Best Regards
    Sheraz Javaid
  • Hi, Sheraz,

    The soft reset is not supported. The RC expects EP being up first. A soft reset requires RC to rescan which involves kernel driver modification.

    Rex