Test Rionet driver for T4240RDB

[loveleensahni]

Hi

I am working on freescale communication server project.

I need to check the rionet driver on the two T4240rdb reference boards with SRIO interface.

I am able to do the enumeration part SRIO host is enumerating the Agent. and after this test I am getting two virtual interfaces one on host and other on agent. i.e. eth0 interface .

Host side :
[   78.555790] RIO: enumerate master port 0, RIO mport 0                                                     
[   78.559537] rio_enable_rx_tx_port(local = 1, destid = 0, hopcount = 0,port_num=0)                      
[   82.037036] rio_enable_rx_tx_port(local = 0, destid = 255, hopcount = 0, port_num = 0)                    
[   82.037092] RIO: found 00:e:0002 (vid 0002 did 0440)

mport is active
eth0: rionet Ethernet over RapidIO Version 0.3, MAC 00:01:00:01:00:00, RIO mport 0

Agent side :
[   53.182438] RIO: discovery work for mport 0 RIO mport 0                                                   
[   53.182443] RIO: discover master port 0, RIO mport 0                                                      
[   53.186097] RIO: wait for enumeration to complete...                                                      
[   72.254259] RIO: ... enumeration done                                                                     
[   72.254338] RIO: found 00:e:0001 (vid 0002 did 0440) 

mport is active
eth0: rionet Ethernet over RapidIO Version 0.3, MAC 00:01:00:01:00:01, RIO mport 0

But the issue I am facing is I am not able to ping I am not getting any packets in Tx and Rx buffers . If anyone can help me over this that RMU(Rapid IO Message unit ) will work for T4240 or not ?

[ugendreshwarkud]

I found the following errata in Netcomm software:

SRIO port#2 limitation with PAMU enabled (B4860, T4240).

SRIO port #2 cannot be operated with PAMU enabled due to configuration issue.

WORKAROUND: Use SRIO port #1, or use SRIO port #2 with PAMU disabled

From the logs looks like your are using Port 2. Right?

[loveleensahni]

Hi 

will you please tell me can i use rionet driver with T4240 processors .

[loveleensahni]

Hi Ugendreshwar,

Very sorry for replying too late to your conversation .

Actually I am using SRIO Port 1 I am not using any srio switch there is a riser card attached in between two T4240 RDB reference boards. 

I have some doubts:

1. Are you sure that rionet driver will work with T4240 the already existing driver in SDK 1.6 or it will support simple messaging i.e. RMU.

2. If it is using then why I am not able to ping .It is getting into the send_doorball type functions . If there is some addressing issues .

Thanks in advance!

[ugendreshwarkud]

Do you find the following errors also? We found this issue in P2020.

RIO: Port-Write message from 00:s:0002

RIO: 00:s:0002 Implementation Specific Port errors 0x20

RIO_PW: SP1_ERR_STS_CSR=0xe0000311

RIO_PW: Device Extraction on [00:s:0002]-P1

RIO_PW: RIO_EM_P1_ERR_DETECT=0x80000004

If yes, then you need the following changes. Hope it helps in your case.

There are some issues in FSL Linux sRIO driver,  without the following modification you may not able to get Ethernet over RapidIO work if Port2 is used. Please check the following 2 items in your Linux code

1. 1) rio_mport_send_doorbell() in drivers/rapidio/rio-access.c, mport->index should be used instead of mport->id

-res = mport->ops->dsend(mport, mport->id, destid, data);

+res = mport->ops->dsend(mport, mport->index, destid, data);

1. 2) rionet_queue_tx_msg() in drivers/net/rionet.c, the 3^rd parameter should be changed to “1” if Port2 is used. The 3^rd parameter means which mbox should be used. There is no limitation in hardware which mbox can be used, but in FSL’s driver mbox0 is for port1 and mbox1 is for port2. 

-rio_add_outb_message(rnet->mport, rdev, 0, skb->data, skb->len);

+rio_add_outb_message(rnet->mport, rdev, 1, skb->data, skb->len);

[loveleensahni]

Hi ugendreshwar ,

Thanks for the reply.

we are not getting any errors just simple ping is not working . Is that issue is from T4240RDB .Might be our current processors are not supporting simple messaging i.e. (RMU). Actually we are not using any SRIO switch so we are not getting any switch errors. Is P2020 supports RMU or RMAN?

Please guide me if you are using some different approach.