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: lspci shows nothings!

Tool/software: Linux

Hi. 

I most recently use from am5728-evm board and i'm trying to setup PCI module on this board also i'm trying to setup and initialize MCS9922 driver

MCS9922 => PCIe to dual serial controller => http://asix.com.tw/products.php?op=pItemdetail&PItemID=122;74;110&PLine=74

I should mention that when i connect MCS9922 (picture of this module is attached) on my PC and I enter "lspci" command in terminal i saw MCS9922 and lspci shows that one thing connect to my PC. now i want to connect MCS9922 on mu evm board and use its ability.

when i connect MCS9922 on my evm board and when enter lspci command => lspci shows nothing apart from one thing:

root@am57xx-evm:~# lspci
00:00.0 PCI bridge: Texas Instruments Device 8888 (rev 01)
root@am57xx-evm:~#

also i initialize driver of MCS9922 on my evm board and make its module on my evm board.

In other words my problem is that when i conncet any PCIe module on my board, my board did not recognize this mudule....

i do not know how can solve this problem please help me.

by the way i attached config (tisdk_am57xx-evm-rt_defconfig) file of my evm board that it is in this location => arch/arm/configs

7167.tisdk_am57xx-evm-rt_defconfig.txt

  • Hi Saman,

    It seems that the initialization of MCS9922 driver is not successful. Could you attach Linux booting log and output of "lsmod" command.

    BR
    Tsvetolin Shulev
  • Hi .
    my report:

    root@am57xx-evm:~# modprobe 99xx
    root@am57xx-evm:~# lsmod
    Module Size Used by
    99xx 27649 0
    bc_example 7206 0
    rpmsg_pru 4916 0
    rpmsg_rpc 19750 0
    xhci_plat_hcd 4955 0
    rpmsg_proto 7452 0
    xhci_hcd 108339 1 xhci_plat_hcd
    usbcore 194072 2 xhci_plat_hcd,xhci_hcd
    dwc3 61957 0
    udc_core 12083 1 dwc3
    virtio_rpmsg_bus 12890 3 rpmsg_pru,rpmsg_rpc,rpmsg_proto
    cbc 2324 0
    jitterentropy_rng 6609 0
    drbg 13510 1
    xfrm_user 23036 2
    xfrm4_tunnel 2040 0
    ipcomp 2473 0
    xfrm_ipcomp 4549 1 ipcomp
    pru_rproc 11894 4
    pruss_intc 7249 5 pru_rproc
    esp4 6529 0
    ah4 5665 0
    ecb 1909 0
    af_key 27327 0
    xfrm_algo 6989 5 ah4,esp4,af_key,xfrm_user,xfrm_ipcomp
    snd_soc_simple_card 7752 0
    sha512_generic 9903 0
    sha512_arm 12079 0
    sha256_generic 9503 1
    hmac 2735 1
    snd_soc_omap_hdmi_audio 4695 0
    md5 1897 0
    sha1_generic 2621 0
    sha1_arm_neon 6261 0
    pvrsrvkm 412813 5 bc_example
    sha1_arm 3862 1 sha1_arm_neon
    bluetooth 327071 2
    omap_aes_driver 19426 0
    pruss 10881 1 pru_rproc
    omap_sham 21158 0
    ahci_platform 3218 0
    libahci_platform 7375 1 ahci_platform
    libahci 27835 2 libahci_platform,ahci_platform
    omap_wdt 4655 0
    libata 195672 3 libahci,libahci_platform,ahci_platform
    scsi_mod 127743 1 libata
    ti_vip 35729 0
    ti_vpe 19194 0
    ti_sc 24714 2 ti_vip,ti_vpe
    ti_csc 2313 2 ti_vip,ti_vpe
    ti_vpdma 15200 2 ti_vip,ti_vpe
    dwc3_omap 4425 0
    rtc_omap 8015 0
    extcon_palmas 5808 0
    extcon 13907 3 dwc3,extcon_palmas,dwc3_omap
    rtc_palmas 5054 0
    pixcir_i2c_ts 6038 0
    mt9t11x 14855 0
    snd_soc_tlv320aic3x 48260 1
    omap_rng 4540 0
    rtc_ds1307 11342 0
    omap_des 11342 0
    rng_core 7603 1 omap_rng
    debugss_kmodule 6912 0
    omap_remoteproc 11565 4
    remoteproc 27048 5 omap_remoteproc,pruss,pru_rproc,rpmsg_rpc,rpmsg_proto
    virtio 6549 2 remoteproc,virtio_rpmsg_bus
    virtio_ring 12291 2 remoteproc,virtio_rpmsg_bus
    sch_fq_codel 8123 1
    uio_module_drv 7579 0
    uio 9302 1 uio_module_drv
    gdbserverproxy 4837 0
    cryptodev 38283 2
    cmemk 31592 0
    root@am57xx-evm:~#
  • Saman,

    Seems that the 99xx module is loaded but still it is not clear what is wrong. Could you attach in a text file Linux kernel log - 'dmesg' command output. We could search in the log for something related to MCS9922 issue.

    BR
    Tsvetolin Shulev
  • i  attached my linux kernel log here.3326.kernel-log.txt