OFDPA System Intialization failed on Accton AS5712-54x

[Saurabh Jain]

Hello all,

we are trying to obtain OpenFlow support in the AS5712-54x.

We are planning to integrate OFDPA in Accton switch.
We run the binaries in https://github.com/opennetworklinux/ofdpa-2.0-closed-accton which are supposed to fulfill (Indigo, OF-DPA).

ONL version used:
Linux onl-x86 3.2.65-1+deb7u2-OpenNetworkLinux #1 SMP Wed Dec 2 20:05:49 UTC 2015 x86_64 GNU/Linux

Then I have run:

./ofdpa-2.0-ea2-x86-64-as5712-54x-r0

But I get below error:
============================================================

root@onl-x86:~/ofdpa# ./ofdpa-2.0-ea2-x86-64-as5712-54x-r0 
 
version 0.0.0.0 -- Built on Tue Jul 14 2015 at 20:41:22 CST
 
Initializing the system.
DMA pool size: 16777216
PCI unit 0: Dev 0xb854, Rev 0x03, Chip BCM56854_A2, Driver BCM56850_A0
 
Found board: as5710_54x/as5712_54x
SOC unit 0 attached to PCI device BCM56854_A2
rc: unit 0 device BCM56854_A2
MiimTimeOut:soc_miim_write, timeout (id=0x1da addr=0x1f data=0x8630)
INIT: Unable to initialize device: 0
sdkCustomInit: initialization command "init soc" failed, rc = -1 (Internal error).
SchanTimeOut:soc_schan_op operation timed out
  HDR[CPU=0 COS=0 EBIT=0 ECODE=0 L=4 ACC_TYPE=0 DST=3 OP=11=READ_REG_CMD]
  DW[ 0]=0x2c300200 DW[ 1]=0x32000000
INIT: Unable to initialize misc for device 0: Operation timed out
sdkCustomInit: initialization command "init misc" failed, rc = -9 (Operation timed out).
SchanTimeOut:soc_schan_op operation timed out
  HDR[CPU=0 COS=0 EBIT=0 ECODE=0 L=4 ACC_TYPE=0 DST=3 OP=13=WRITE_REG_CMD]
  DW[ 0]=0x34300200 DW[ 1]=0x1e000200 DW[ 2]=0x0000fda0
INIT: Unable to initialize MMU for device: Operation timed out
sdkCustomInit: initialization command "init mmu" failed, rc = -1 (Internal error).
rc: MMU initialized
SchanTimeOut:soc_schan_op operation timed out
  HDR[CPU=0 COS=0 EBIT=0 ECODE=0 L=8 ACC_TYPE=3 DST=2 OP=9=WRITE_MEM_CMD]
  DW[ 0]=0x2420c400 DW[ 1]=0x041c0000 DW[ 2]=0x00000000 DW[ 3]=0x00000000
soc_mem_clear: write EGR_MAC_DA_PROFILE.epipe0[0] failed: Operation timed out
INIT: Unable to initialize BCM driver on unit 0: Operation timed out
sdkCustomInit: initialization command "init bcm" failed, rc = -1 (Internal error).
rc: L2 Table shadowing enabled
LINKscan: Error: bcm ports not initialized
sdkCustomInit: initialization command "linkscan 250000" failed, rc = -1 (Internal error).
PORT: Error: bcm ports not initialized
sdkCustomInit: initialization command "port ge linkscan=on autoneg=on speed=0 fullduplex=true txpause=true rxpause=true enable=false" failed, rc = -1 (Internal error).
PORT: Error: bcm ports not initialized
sdkCustomInit: initialization command "port xe linkscan=on autoneg=off speed=0 fullduplex=true txpause=true rxpause=true enable=false" failed, rc = -1 (Internal error).
rc: Port modes initialized
sdkCustomInit: initialization command "stg stp 1 all forward" failed, rc = -3 (Invalid unit).
CounTeR: Error: Could not sync counters: Operation disabled
sdkCustomInit: initialization command "counter sync" failed, rc = -1 (Internal error).
rc: common SDK init complete
PORT: Error: bcm ports not initialized
sdkCustomInit: initialization command "port xe sp=10000 if=SFI" failed, rc = -1 (Internal error).
PORT: Error: bcm ports not initialized
sdkCustomInit: initialization command "port 49,53,57,61,65,69 sp=40000 if=CR4" failed, rc = -1 (Internal error).
PORT: Error: bcm ports not initialized
sdkCustomInit: initialization command "port xe enable=no" failed, rc = -1 (Internal error).
PORT: Error: bcm ports not initialized
sdkCustomInit: initialization command "port xe enable=yes" failed, rc = -1 (Internal error).
SchanTimeOut:soc_schan_op operation timed out
  HDR[CPU=0 COS=0 EBIT=0 ECODE=0 L=8 ACC_TYPE=3 DST=1 OP=11=READ_REG_CMD]
  DW[ 0]=0x2c10c400 DW[ 1]=0x06000000
ERROR: read from register ING_CONFIG_64.ipipe0 failed: Operation timed out
sdkCustomInit: initialization command "m ING_CONFIG_64 L2DST_HIT_ENABLE=0" failed, rc = -9 (Operation timed out).
rc: platform SDK init complete
driverTermMacInit: Failed to get termination MAC table size.
driverInit: 
Error initializing flow driver, rc = -21.
systemMappingInit: Error initializing driver, rc = -21.
Initialization failed!  Aborting.

Please give your inputs.

Thanks,
Saurabh Jain

[Rob Sherwood]

Hi Saurabh,

The OF-DPA code for the AS5712 is not fully merged into ONL and is a work in progress/supported by Accton so hopefully someone from their team can reply to this (I'll poke them separately to make sure they see this).  A few things to check: please make sure you have the correct kernel module files loaded with the right options, e.g., 

insmod linux-kernel-bde_x86-64.ko dmasize=32M maxpayload=128

insmod linux-user-bde_x86-64.ko

and make sure the mknod devices are correctly created similar to what the /etc/init.d/ofdpa startup script does.

As we pull in full support for these drivers, we'll make sure this is all a bit more seamless.

- Rob

.

--
You received this message because you are subscribed to the Google Groups "opennetworklinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opennetworklin...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Saurabh Jain]

Hi Rob,

Thanks for your quick reply.
I tried with the option you suggested while inserting kernel module. But I am facing the same problem.
It will be great, if we get OFDPA run on Accton switch with some help.

Thanks & Regards,
Saurabh Jain

[Kang]

Hi Saurabh,

Do you create the following two device nodes?

 mknod /dev/linux-kernel-bde c 127 0

 mknod /dev/linux-user-bde c 126 0

Best regards,

Lewis

---

從: opennetw...@googlegroups.com [opennetw...@googlegroups.com] 代表 Saurabh Jain [saurab...@kulcloud.net]
寄件日期: 2015年12月18日 下午 05:41
至: opennetworklinux
副本: saurab...@kulcloud.net
主旨: Re: OFDPA System Intialization failed on Accton AS5712-54x

[Saurabh Jain]

Hi Lewis,

We followed the below step for running OFDPA on Accton switch.

1. git clone https://github.com/opennetworklinux/ofdpa-2.0-closed-accton.git
2. mknod /dev/linux-kernel-bde c 127 0
3. mknod /dev/linux-user-bde c 126 0
4. insmod linux-kernel-bde_x86-64.ko dmasize=32M maxpayload=128 or insmod linux-kernel-bde_x86-64.ko (tried both options).
5. insmod linux-user-bde_x86-64.ko
6. cp librpc_client_x86-64.so.1 /usr/lib/librpc_client.so.1
7. cd /usr/lib
8. ln -sf librpc_client.so.1 librpc_client.so
9. ./ofdpa-2.0-ea2-x86-64-as5712-54x-r0

Please let us know if there is any step we are missing.

Thanks & Regards,
Saurabh Jain

[lnobach]

Hello all,

I opened a related issue under https://groups.google.com/forum/#!topic/opennetworklinux/PcdxzVdi624 .

I found out that if you add "forceirq=<the irq that e.g. lspci shows for the brcm>", the kernel message 

========================================================================================

linux-kernel-bde (2848): could not request irq 0 for device 0

========================================================================================

disappears, but the rest of the error stays the same. In the next year, I will retry it with dmasize, maxpayload, AND forceirq, but currently I also do not have a solution.

I would like to contribute, but as we do not have access to the code, I can not...

Best regards,

Leo

[lnobach]

Hello all,

could this be a CPLD-related issue?

According to http://www.edge-core.com/temp/ec_download/1591/5712-54X%20Instruction.pdf,

my CPLD version is 0x06 0x06 0x06.

Is there anybody who (at least partially) got of-dpa to work with a previous version?

Best regards,

Leo

[Rob Sherwood]

Fwiw, we've had OFDPA working on many switches for many use-cases (IPv6 forwarding, OpenFlow for the Atrium project, etc.).  But, currently OFDPA support is platform by platform and different platforms have different levels of plug and play capabilities.

We're still working on how to support/answer questions about OFDPA.  Just to expose how the sausage is made, Broadcom writes the OFDPA code (multiple versions) which has a plugin for platform specific drivers.  Then either my team or the platform vendor writes those platform drivers, and then we try to publish it somewhere where people can get it.  If it's my team, then we have the legal permissions from Broadcom to distribute it built into ONL, but if a platform vendor wrote the driver, we're still working out the legal permissions to redistribute it with ONL so you have to get them separately (e.g., from Accton, IM, etc.) which may or may not replicate the start up process correctly.  

Then as you point out, there is also the CPLD compatibility.  

While my team is trying to test as much as we can, it's a best effort approach (OFDPA isn't a formally supported Big Switch product).  Any help from the community trying to understand which OFDPA version works with which platform on which CPLD version is greatly appreciated.

- Rob

.