topic Re: p4080ds rapidIO message unit application work failed in P-Series

p4080ds rapidIO message unit application work failed

gaolixing — Thu, 11 Jun 2020 09:45:42 GMT

hello:

i want to run rapidIO message unit application on p4080ds,but it work failed,the follow is the log:

root@p4080ds:~# rmu
rmu: fsl_rmu_unit_uio_init(): /dev/rmu-uio-msg0: No such file or directory
rmu: main(): rmu_unit_uio_init(): No such file or directory

i use the rcw bin file that serdes config is 0x16 from SDK2.0, i use uImage-p4080ds-usdpaa.dtb file,and i use “0b01001100” on SW3 (Serdes reference clock for bank1 is 125MHz, bank2 is 125MHz, bank3 is 125MHz).

but i can't find the item is linux menucofing:

Device Drivers --->
<*> Userspace I/O drivers --->
<*> Freescale Rapidio Message Unit support

my sdk2.0 source code is 20160527 version

the uboot log is:

Warning: SERDES8 requires banks two and three to be disabled in the RCW

SRIO1: enabled but port error

SRIO2: enabled but port error

the kernel log is:

Setting up RapidIO peer-to-peer network /rapidio@ffe0c0000
fsl-of-rio ffe0c0000.rapidio: Of-device full name /rapidio@ffe0c0000
fsl-of-rio ffe0c0000.rapidio: Regs: [mem 0xffe0c0000-0xffe0d0fff]
fsl-of-rio ffe0c0000.rapidio: bellirq: 57
fsl-of-rio ffe0c0000.rapidio: pwirq: 478
fsl-of-rio ffe0c0000.rapidio: /rapidio@ffe0c0000/port1: LAW start 0x0000000c20000000, size 0x0000000010000000.
fsl-of-rio ffe0c0000.rapidio: RapidIO PHY type: Serial
fsl-of-rio ffe0c0000.rapidio: Port 0 is not ready. Try to restart connection...
fsl-of-rio ffe0c0000.rapidio: Port 0 restart failed.
fsl-of-rio ffe0c0000.rapidio: /rapidio@ffe0c0000/port2: LAW start 0x0000000c30000000, size 0x0000000010000000.
fsl-of-rio ffe0c0000.rapidio: RapidIO PHY type: Serial
fsl-of-rio ffe0c0000.rapidio: Port 1 is not ready. Try to restart connection...
fsl-of-rio ffe0c0000.rapidio: Port 1 restart failed.
fsl-of-rio: probe of ffe0c0000.rapidio failed with error -67

please help me,thank you

Re: p4080ds rapidIO message unit application work failed

gaolixing — Thu, 11 Jun 2020 10:04:22 GMT

is that need a special ucode for Fman? i use fsl_fman_ucode_p4080_r3.0_106_2_18.bin file for fman

Re: p4080ds rapidIO message unit application work failed

ufedor — Thu, 11 Jun 2020 12:23:06 GMT

You wrote:

> i can't find the item is linux menucofing

What do you see in the:

Device Drivers --->
<*> Userspace I/O drivers --->

Assuming that the SDK was not installed properly the latest SDK version can be downloaded from:

Linux® SDK for QorIQ® Processors | NXP

Detailed description of the RMU testing on P4080DS is provided in the SDK Documentation:

USDPAA RMU User Manual

You wrote:

> is that need a special ucode for Fman?

Microcode is required for FMan, but FMan operation is not connected with RapidIO.

Re: p4080ds rapidIO message unit application work failed

gaolixing — Thu, 11 Jun 2020 13:27:56 GMT

thanks for your reply

<*> Userspace I/O drivers ---> is the follow:

i use sdk2.0 20160527 version download from Linux® SDK for QorIQ® Processors | NXP ,because SDK2.0 version 2017.3 can't be compiled due to www.freescale.com is shut down

Re: p4080ds rapidIO message unit application work failed

gaolixing — Thu, 11 Jun 2020 13:29:08 GMT

the method of download sdk2.0 20160527 is supplied by wang yiping,another NXP FAE