Hi Michael,
Here is a uTca message and kernel version information.
[root@amc725 opt]#dmesg
Event Receiver PCI/PCIe driver init.
pci_mrfevr 0000:0e:01.0: enabling device (0140 -> 0142)
mrfevr:BAR0 start fda10000 end fda1007f, mmap 02866000
mrfevr:BAR2 start fda00000 end fda0ffff, mmap 135a0000
var(devPCIDebug, 5)
mrmEvrSetupPCI("PMCEVR",0xe,1,0)
linuxDevPCIInit found 0000:00:00.0
as pri 8086:0104 sub 8086:0104 cls 060000
linuxDevPCIInit found 0000:00:01.0
as pri 8086:0101 sub 8086:0101 cls 060400
linuxDevPCIInit found 0000:00:06.0
as pri 8086:010d sub 8086:010d cls 060400
linuxDevPCIInit found 0000:00:1d.0
as pri 8086:2334 sub 8086:2334 cls 0c0320
linuxDevPCIInit found 0000:00:1f.0
as pri 8086:2310 sub 8086:2310 cls 060100
linuxDevPCIInit found 0000:00:1f.2
as pri 8086:2323 sub 8086:2321 cls 010601
linuxDevPCIInit found 0000:00:1f.3
as pri 8086:2330 sub 8086:2330 cls 0c0500
linuxDevPCIInit found 0000:00:1f.6
as pri 8086:2332 sub 8086:2332 cls 118000
linuxDevPCIInit found 0000:00:1f.7
as pri 8086:2360 sub a910:8e10 cls 088000
linuxDevPCIInit found 0000:01:00.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:04.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:05.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:08.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:09.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:0a.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:0b.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:02:0c.0
as pri 10b5:8764 sub 10b5:8764 cls 060400
linuxDevPCIInit found 0000:05:00.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:00.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:01.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:02.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:10.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:11.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:12.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:13.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:14.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:15.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:16.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:06:17.0
as pri 10b5:8649 sub 10b5:8649 cls 060400
linuxDevPCIInit found 0000:14:00.0
as pri 1b4b:9230 sub 1b4b:9230 cls 010601
linuxDevPCIInit found 0000:15:00.0
as pri 126f:0750 sub 126f:0750 cls 030000
linuxDevPCIInit found 0000:16:00.0
as pri 8086:0434 sub 8086:0000 cls 0b4000
linuxDevPCIInit found 0000:16:00.1
as pri 8086:043c sub 8086:0000 cls 020000
linuxDevPCIInit found 0000:16:00.2
as pri 8086:043c sub 8086:0000 cls 020000
linuxDevPCIInit found 0000:16:00.3
as pri 8086:0438 sub 8086:0000 cls 020000
linuxDevPCIInit found 0000:16:00.4
as pri 8086:0438 sub 8086:0000 cls 020000
linuxDevPCIInit found 0000:17:00.0
as pri 8086:10fb sub ffff:ffff cls 020000
linuxDevPCIInit found 0000:17:00.1
as pri 8086:10fb sub ffff:ffff cls 020000
linuxDevPCIInit found 0000:0c:00.0
as pri abcd:7028 sub abcd:7523 cls 058000
linuxDevPCIInit found 0000:0d:00.0
as pri abcd:4105 sub 0000:0000 cls 060400
linuxDevPCIInit found 0000:0e:01.0
as pri 10b5:9030 sub 1a3e:11e6 cls 118000
Consider 0:0.0
0 mismatch device 9030 104
1 mismatch device 9030 104
2 mismatch device 9056 104
Consider 0:1.0
0 mismatch device 9030 101
1 mismatch device 9030 101
2 mismatch device 9056 101
Consider 0:6.0
0 mismatch device 9030 10d
1 mismatch device 9030 10d
2 mismatch device 9056 10d
Consider 0:29.0
0 mismatch device 9030 2334
1 mismatch device 9030 2334
2 mismatch device 9056 2334
Consider 0:31.0
0 mismatch device 9030 2310
1 mismatch device 9030 2310
2 mismatch device 9056 2310
Consider 0:31.2
0 mismatch device 9030 2323
1 mismatch device 9030 2323
2 mismatch device 9056 2323
Consider 0:31.3
0 mismatch device 9030 2330
1 mismatch device 9030 2330
2 mismatch device 9056 2330
Consider 0:31.6
0 mismatch device 9030 2332
1 mismatch device 9030 2332
2 mismatch device 9056 2332
Consider 0:31.7
0 mismatch device 9030 2360
1 mismatch device 9030 2360
2 mismatch device 9056 2360
Consider 1:0.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:4.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:5.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:8.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:9.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:10.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:11.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 2:12.0
0 mismatch device 9030 8764
1 mismatch device 9030 8764
2 mismatch device 9056 8764
Consider 5:0.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:0.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:1.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:2.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:16.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:17.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:18.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:19.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:20.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:21.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:22.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 6:23.0
0 mismatch device 9030 8649
1 mismatch device 9030 8649
2 mismatch device 9056 8649
Consider 20:0.0
0 mismatch device 9030 9230
1 mismatch device 9030 9230
2 mismatch device 9056 9230
Consider 21:0.0
0 mismatch device 9030 750
1 mismatch device 9030 750
2 mismatch device 9056 750
Consider 22:0.0
0 mismatch device 9030 434
1 mismatch device 9030 434
2 mismatch device 9056 434
Consider 22:0.1
0 mismatch device 9030 43c
1 mismatch device 9030 43c
2 mismatch device 9056 43c
Consider 22:0.2
0 mismatch device 9030 43c
1 mismatch device 9030 43c
2 mismatch device 9056 43c
Consider 22:0.3
0 mismatch device 9030 438
1 mismatch device 9030 438
2 mismatch device 9056 438
Consider 22:0.4
0 mismatch device 9030 438
1 mismatch device 9030 438
2 mismatch device 9056 438
Consider 23:0.0
0 mismatch device 9030 10fb
1 mismatch device 9030 10fb
2 mismatch device 9056 10fb
Consider 23:0.1
0 mismatch device 9030 10fb
1 mismatch device 9030 10fb
2 mismatch device 9056 10fb
Consider 12:0.0
0 mismatch device 9030 7028
1 mismatch device 9030 7028
2 mismatch device 9056 7028
Consider 13:0.0
0 mismatch device 9030 4105
1 mismatch device 9030 4105
2 mismatch device 9056 4105
Consider 14:1.0
0 Match
Device PMCEVR 14:1.0
Using IRQ 16
Looking for UIO dir in /sys/bus/pci/devices/0000:0e:01.0/ with uio:uio%u
Check . gives 0 32766
Check .. gives 0 32766
Check irq gives 0 32766
Check vpd gives 0 32766
Check subsystem_vendor gives 0 32766
Check broken_parity_status gives 0 32766
Check class gives 0 32766
Check power gives 0 32766
Check reset gives 0 32766
Check resource gives 0 32766
Check consistent_dma_mask_bits gives 0 32766
Check modalias gives 0 32766
Check dma_mask_bits gives 0 32766
Check local_cpus gives 0 32766
Check config gives 0 32766
Check device gives 0 32766
Check driver gives 0 32766
Check enable gives 0 32766
Check subsystem gives 0 32766
Check msi_bus gives 0 32766
Check local_cpulist gives 0 32766
Check remove gives 0 32766
Check rescan gives 0 32766
Check uevent gives 0 32766
Check vendor gives 0 32766
Check resource0 gives 0 32766
Check resource2 gives 0 32766
Check subsystem_device gives 0 32766
Check numa_node gives 0 32766
Check d3cold_allowed gives 0 32766
Looking for UIO dir in /sys/bus/pci/devices/0000:0e:01.0/uio/ with uio%u
Failed to open uio device for PCI device 0000:0e:01.0: No such file or directory
Failed to enable interrupt
[root@amc725 0000:0e:01.0]# cd /sys/bus/pci/devices/0000:0e:01.0/uio/
-bash: cd: /sys/bus/pci/devices/0000:0e:01.0/uio/: No such file or directory
[root@amc725 0000:0e:01.0]# cd /sys/bus/pci/devices/0000:0e:01.0/
[root@amc725 0000:0e:01.0]# ls
broken_parity_status device local_cpulist power resource0 uevent
class dma_mask_bits local_cpus remove resource2 vendor
config driver modalias rescan subsystem vpd
consistent_dma_mask_bits enable msi_bus reset subsystem_device
d3cold_allowed irq numa_node resource subsystem_vendor
[root@amc725 0000:0e:01.0]#
-Jihwa
________________________________________
보낸 사람: Michael Davidsaver <[email protected]>
보낸 날짜: 2016년 3월 10일 목요일 오전 10:01
받는 사람: 김지화(빔라인장치팀); [email protected]; [email protected]
제목: Re: mrfioc2 error at uTCA platform
Before calling mrmEvrSetupPCI(), set the devPCIDebug variable to 5 (or
greater) to give some more output.
> var(devPCIDebug, 5)
What is the version of the Linux kernel you are running?
In order to make the association between the PCI device ID and /dev/uio#
device file, devlib2 follows of a symlink under /sys/. The location of
this symlink has already changed once between 2.6.28 and 2.6.32. It may
have changed again.
Look in "/sys/bus/pci/devices/0000:0e:01.0/" for "uio:uio0" or "uio/uio0".
https://github.com/epics-modules/devlib2/blob/master/pciApp/os/Linux/devLibPCIOSD.c#L266
Finally, does the kernel log (dmesg) give any messages when the mrfioc2
kernel module is loaded?
On 03/08/2016 09:55 PM, 김지화(빔라인장치팀) wrote:
> Hi Martin and Michael,
>
> I've attached error message.
>
>>> If the file '/dev/era3' exists
> Yes, I've been hard rebooted and there is not installed '/dev/era3'
>
>>> So you should see some file like '/dev/uio0'.
> Yes, I can see uio0 driver at /dev
>
>>> mrfioc2 and devlib2 are you using?
> I used mrfioc2 2.04 and devlib2.6, again it worked before but some reason it caused error.
>
> -Jihwa
>
> ________________________________________
> 보낸 사람: [email protected] <[email protected]> 대신 Michael Davidsaver <[email protected]>
> 보낸 날짜: 2016년 3월 8일 화요일 오후 12:05
> 받는 사람: [email protected]
> 제목: Re: mrfioc2 error at uTCA platform
>
> What version of mrfioc2 are you using?
>
>> Interesting is the SLAC evr version is correctly working.
>>
>> evrIocTest_registerRecordDeviceDriver(pdbbase)
>>
>> ErConfigure(0, 0, 0, 0, 1)
>>
>> EvrOpen, device = /dev/era3
> If the file '/dev/era3' exists then you don't have the correct linux kernel module loaded. mrfioc2 comes with it's own, which uses the UIO interface. So you should see some file like '/dev/uio0'.
>
>
> On 03/07/2016 03:21 PM, 김지화(빔라인장치팀) wrote:
>> Hi Martin,
>>
>>>> PMC EVR on a PMC carrier card, right?
>> Yes, right! Vadatech PMC Carier board.
>>
>>
>>>> What does "lspci" say? Maybe you've plugged the card into a different AMC slot?
>> I think slot is correct slot number because it worked before.
>>
>> Here is a PMC-EVR-230 with VID:DID 10b5:9030 and subvendor ID 1a3e
>> and subvendor device ID 11e6. (JUkka already confirmed )
>>
>> [root@amc725 mrf_pci_driver]# lspci -nn -x
>>
>> 0e:01.0 Signal processing controller [1180]: PLX Technology, Inc. PCI9030 32-bit 33MHz PCI <-> IOBus Bridge [10b5:9030] (rev 01)
>>
>> 00: b5 10 30 90 02 00 90 02 01 00 80 11 08 00 00 00
>>
>> 10: 00 00 a1 fd 00 00 00 00 00 00 a0 fd 00 00 00 00
>>
>> 20: 00 00 00 00 00 00 00 00 00 00 00 00 3e 1a e6 11
>>
>> 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 00 00
>>
>>
>>
>> Interesting is the SLAC evr version is correctly working.
>>
>> evrIocTest_registerRecordDeviceDriver(pdbbase)
>>
>> ErConfigure(0, 0, 0, 0, 1)
>>
>> EvrOpen, device = /dev/era3
>>
>> EVR Found with Firmware Revision 0x11000007
>>
>> Found a PMC_EVR /dev/era3
>>
>>
>> Jihwa
>>
>> ________________________________________
>> 보낸 사람: Konrad, Martin <[email protected]>
>> 보낸 날짜: 2016년 3월 7일 월요일 오후 1:37
>> 받는 사람: 김지화(빔라인장치팀); [email protected]
>> 제목: Re: mrfioc2 error at uTCA platform
>>
>> Hi Jihwa,
>> > Dose any one has experience of mrfioc2 evr driver for uTCA platform?
>>> PMC-EVR-230 firmware version: PMC-EVR-230-11000007.bit
>> I guess you are not using the native uTCA card but a PMC EVR on a PMC
>> carrier card, right?
>>
>>> mrmEvrSetupPCI("PMCEVR",0xe,1,0)
>>> Device PMCEVR 14:1.0
>>> Using IRQ 16
>>> Failed to open uio device for PCI device 0000:0e:01.0: No such file or
>>> directory
>>> Failed to enable interrupt
>> What does "lspci" say? Maybe you've plugged the card into a different
>> AMC slot?
>>
>> -Martin
>>
>> --
>> Martin Konrad
>> Control System Engineer
>> Facility for Rare Isotope Beams
>> Michigan State University
>> 640 South Shaw Lane
>> East Lansing, MI 48824-1321, USA
>> Tel. 517-908-7253
>> Email: [email protected]
>>
>
- Replies:
- Re: mrfioc2 error at uTCA platform Michael Davidsaver
- References:
- Re: mrfioc2 error at uTCA platform Konrad, Martin
- RE: mrfioc2 error at uTCA platform 김지화(빔라인장치팀)
- Re: mrfioc2 error at uTCA platform Michael Davidsaver
- RE: mrfioc2 error at uTCA platform 김지화(빔라인장치팀)
- Re: mrfioc2 error at uTCA platform Michael Davidsaver
- Navigate by Date:
- Prev:
Re: mrfioc2 error at uTCA platform Michael Davidsaver
- Next:
mbbo/mbbi and bits subset [email protected]
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: mrfioc2 error at uTCA platform Michael Davidsaver
- Next:
Re: mrfioc2 error at uTCA platform Michael Davidsaver
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|