Cannot configure tc qdisc TAPRIO on LS1021ATSN

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cannot configure tc qdisc TAPRIO on LS1021ATSN

1,036 Views
SH8Lee
Contributor I

Hello!

I am currently using LS1021ATSN-PA board, and I am using the Real-time Edge Software V2.4.

And I tried a command for configuring the tc qdisc taprio on the interface eth0 of the board.

But when I tried a command below,

tc qdisc add dev eth1 parent root taprio \
num_tc 8 \
map 0 1 2 3 4 5 6 7 \
queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \
base-time 0 \
sched-entry S 80 50000 \
sched-entry S 40 50000 \
sched-entry S 3f 300000 \
flags 2

it prints out an error "RTNETLINK answers: Operation not supported".

 

Can I know the reason why it doesn't work, and how I can fix the problem?

Thank you, all!

 

 

0 Kudos
Reply
13 Replies

790 Views
KOOBK
Contributor II

Dear NXP team,

The current issue is that the eth3, eth4, and eth5 interfaces either do not exist or are not being recognized.

Additionally, there are no related messages about these network drivers appearing during the booting process.

Could you please check the network drivers and configurations?

<4>[ 0.427007] ahci-qoriq 3200000.sata: supply target not found, using dummy regulator
<6>[ 0.427214] ahci-qoriq 3200000.sata: AHCI 0001.0300 1 slots 1 ports ? Gbps 0x1 impl platform mode
<6>[ 0.427229] ahci-qoriq 3200000.sata: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc
<4>[ 0.427256] ahci-qoriq 3200000.sata: port 0 is not capable of FBS
<6>[ 0.428971] scsi host0: ahci-qoriq
<6>[ 0.429525] ata1: SATA max UDMA/133 mmio [mem 0x03200000-0x0320ffff] port 0x100 irq 44
<6>[ 0.442840] tun: Universal TUN/TAP device driver, 1.6
<6>[ 0.443297] CAN device driver interface
<6>[ 0.448222] bgmac_bcma: Broadcom 47xx GBit MAC driver loaded
<6>[ 0.463645] fsl-gianfar soc:ethernet@2d10000: enabled errata workarounds, flags: 0x4
<6>[ 0.474714] fsl-gianfar soc:ethernet@2d10000 eth0: mac: b2:81:62:f2:95:bf
<6>[ 0.474725] fsl-gianfar soc:ethernet@2d10000 eth0: Running with NAPI enabled
<6>[ 0.474732] fsl-gianfar soc:ethernet@2d10000 eth0: RX BD ring size for Q[0]: 256
<6>[ 0.474740] fsl-gianfar soc:ethernet@2d10000 eth0: RX BD ring size for Q[1]: 256
<6>[ 0.474748] fsl-gianfar soc:ethernet@2d10000 eth0: TX BD ring size for Q[0]: 256
<6>[ 0.474755] fsl-gianfar soc:ethernet@2d10000 eth0: TX BD ring size for Q[1]: 256
<6>[ 0.475350] fsl-gianfar soc:ethernet@2d50000: enabled errata workarounds, flags: 0x4
<6>[ 0.486323] fsl-gianfar soc:ethernet@2d50000 eth1: mac: 72:df:f6:8f:1e:94
<6>[ 0.486333] fsl-gianfar soc:ethernet@2d50000 eth1: Running with NAPI enabled
<6>[ 0.486339] fsl-gianfar soc:ethernet@2d50000 eth1: RX BD ring size for Q[0]: 256
<6>[ 0.486347] fsl-gianfar soc:ethernet@2d50000 eth1: RX BD ring size for Q[1]: 256
<6>[ 0.486355] fsl-gianfar soc:ethernet@2d50000 eth1: TX BD ring size for Q[0]: 256
<6>[ 0.486362] fsl-gianfar soc:ethernet@2d50000 eth1: TX BD ring size for Q[1]: 256
<6>[ 0.487885] fsl-gianfar soc:ethernet@2d90000: enabled errata workarounds, flags: 0x4
<6>[ 0.498893] fsl-gianfar soc:ethernet@2d90000 eth2: mac: ce:b2:95:59:53:f4
<6>[ 0.498904] fsl-gianfar soc:ethernet@2d90000 eth2: Running with NAPI enabled
<6>[ 0.498910] fsl-gianfar soc:ethernet@2d90000 eth2: RX BD ring size for Q[0]: 256
<6>[ 0.498918] fsl-gianfar soc:ethernet@2d90000 eth2: RX BD ring size for Q[1]: 256
<6>[ 0.498925] fsl-gianfar soc:ethernet@2d90000 eth2: TX BD ring size for Q[0]: 256
<6>[ 0.498933] fsl-gianfar soc:ethernet@2d90000 eth2: TX BD ring size for Q[1]: 256


root@ls1021atsn:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10
link/can
3: can1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10
link/can
4: can2: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10
link/can
5: can3: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10
link/can
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 10
link/ether b2:81:62:f2:95:bf brd ff:ff:ff:ff:ff:ff
7: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default ql0
link/ether 72:df:f6:8f:1e:94 brd ff:ff:ff:ff:ff:ff
8: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether ce:b2:95:59:53:f4 brd ff:ff:ff:ff:ff:ff
9: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0

root@ls1021atsn:/proc# ethtool eth3
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
No data available
root@ls1021atsn:/proc# ethtool eth4
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
No data available
root@ls1021atsn:/proc# ethtool eth5
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device

0 Kudos
Reply

782 Views
yipingwang
NXP TechSupport
NXP TechSupport

Would you please address your current problem in a new thread?

0 Kudos
Reply

776 Views
KOOBK
Contributor II
0 Kudos
Reply

770 Views
yipingwang
NXP TechSupport
NXP TechSupport

Got it, thanks.

0 Kudos
Reply

1,007 Views
yipingwang
NXP TechSupport
NXP TechSupport

First of all,  it is need to be clear about the ls1021atsn hardware structure. As below. See attached picture 1. LS1021 internal link to the SJA1105. Ethx shows in Linux are the ports eth0/eth1 which links to ls1021. It only supports 1 RX ring and 1 TX ring per CPU. It is not support the TSN function. We called theses ports are the ethernet port as end station.

0 Kudos
Reply

963 Views
SH8Lee
Contributor I

Thank you for your reply. Then I used the interface eth2, connected to a host. And I configured an IP address using ifconfig tool to the eth2 port, but I even couldn't ping to the host connected to the port. It printed out "Destination host unreachable". How can I fix this? I can't use the port eth2 for networking now. 

0 Kudos
Reply

959 Views
yipingwang
NXP TechSupport
NXP TechSupport

eth2 is the port connecting to SJA1105, this port only has internal connection, no external connection, the user cannot use it.

0 Kudos
Reply

956 Views
SH8Lee
Contributor I

I am not clear about your "internal connection only". The LS1021ATSN-PA switch has 6 physical ports. And I think the first 2 ports are normal ethernet ports, and the others are not But, because it is a networking device, I think an user have to be able to use all of the ports, and I want to use all of them, as well.

I wonder how I can do some TSN demonstrations by connecting some hosts to LS1021ATSN-PA switch. If I am right, you are saying that I can't use the other 4 ports for networking, and the 2 ports are for normal ethernet only, not for TSN.

If there is a way that I can do some networking with the other 4 ports, please tell me. In the picture below from the LS1021ATSN part of the Real-time Edge Software UG, it is demonstrated that the 4 ports other than normal ethernet ports, which are "SWP2 ~ SWP 5" from the picture, can be connected to external hosts and communicate.

So, please tell me how I can do this. 

 

SH8Lee_0-1722931262437.png

 

0 Kudos
Reply

918 Views
yipingwang
NXP TechSupport
NXP TechSupport

You can use swp2-swp5 to implement TSN networking features, use eth0 and eth1 to do normal networking application.

eth2 connects to sja1105 switch, there is no external PHY connecting to eth2, so it cannot be connected to the external networking.

0 Kudos
Reply

915 Views
SH8Lee
Contributor I

But there are no interfaces named "SWX" for Real-Time Edge Software v2.4 which I am using. For using those interfaces, do I have to use the OpenIL?

Also, is it possible to use the interfaces in the same way as normal ethernet ports as eth0 and eth1 with which I can do some external networking? 

0 Kudos
Reply

907 Views
yipingwang
NXP TechSupport
NXP TechSupport

Can you get similar result as the following?

[root@LS1021ATSN ~] # bridge link

6: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100

7: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100

10: swp5@eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100

11: swp2@eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100

12: swp3@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 4

13: swp4@eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100

[root@LS1021ATSN ~] # ifconfig

br0       Link encap:Ethernet  HWaddr A6:68:4A:23:E8:F5

          inet6 addr: fe80::a468:4aff:fe23:e8f5/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:26 errors:0 dropped:0 overruns:0 frame:0

          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3508 (3.4 KiB)  TX bytes:6114 (5.9 KiB)

 

eth0      Link encap:Ethernet  HWaddr 00:04:9F:EF:06:06

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Base address:0xc000

 

eth1      Link encap:Ethernet  HWaddr 00:04:9F:EF:07:07

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Base address:0xa000

 

eth2      Link encap:Ethernet  HWaddr 00:04:9F:EF:08:08

          inet addr:169.254.176.8  Bcast:169.254.255.255  Mask:255.255.0.0

          inet6 addr: fe80::204:9fff:feef:808/64 Scope:Link

          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1504  Metric:1

          RX packets:26 errors:0 dropped:0 overruns:0 frame:0

          TX packets:93 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3976 (3.8 KiB)  TX bytes:14538 (14.1 KiB)

          Base address:0xe000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:40 errors:0 dropped:0 overruns:0 frame:0

          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3040 (2.9 KiB)  TX bytes:3040 (2.9 KiB)

 

swp2      Link encap:Ethernet  HWaddr 00:04:9F:EF:08:08

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

swp3      Link encap:Ethernet  HWaddr 00:04:9F:EF:08:08

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:26 errors:0 dropped:0 overruns:0 frame:0

          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3508 (3.4 KiB)  TX bytes:6114 (5.9 KiB)

 

swp4      Link encap:Ethernet  HWaddr 00:04:9F:EF:08:08

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

swp5      Link encap:Ethernet  HWaddr 00:04:9F:EF:08:08

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

[root@LS1021ATSN ~] # ifconfig br0 1.1.1.2

[root@LS1021ATSN ~] # ping 1.1.1.1

PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.

64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.683 ms

0 Kudos
Reply

905 Views
SH8Lee
Contributor I

Thank you for your detailed reply. Let me try.

By the way are you using the Real-time Edge Software for LS1021ATSN?

0 Kudos
Reply

900 Views
yipingwang
NXP TechSupport
NXP TechSupport

Yes, please provide Linux Kernel booting up log if the problem persists.

0 Kudos
Reply