qbvset, qbvget doesn't work on LS1028ardb

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

qbvset, qbvget doesn't work on LS1028ardb

ソリューションへジャンプ
4,419件の閲覧回数
JE-KIM
Contributor I

Hi

I'm using LS1028ARDB and I tested tsntool on LS1028ardb.

I didn't build or configure linux, I just installed LSDK 21.08 using flex-installer.

I connected two NVIDIA jetson agx xavier boards to the swp0, swp1 port to test tsn on LS1028ardb. (xavier 1-swp0 , xavier 2-swp1) And xavier 1 send packets to xavier 2.

I configured switch through the command below.

INTERFACES="swp0 swp1 swp2 swp3"

ip link set eno2 up
ip link add name br0 type bridge
for if in $INTERFACES;
do
ip link set dev $if master br0
ip link set $if up
done
ip link set br0 up

bridge link show

 

5: swp0@eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 4
6: swp1@eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 4
7: swp2@eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100
8: swp3@eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br0 state disabled priority 32 cost 100
10: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 master virbr0 state disabled priority 32 cost 100

 

And I tested qbvset using tsntool command referring to qbv test . But it doesn't work.

tsntool> qbvset --device swp1 --entryfile qbv0.txt

echo reply:swp1

echo reply:-19

 

The same goes for qbvget.

tsntool> qbvget --device swp1

echo reply:swp1

echo reply:-19

 

But it works to 'eno2' port. If I set the address 192.168.1.2 in br0 interface and ping 192.168.1.2 in xavier 1, the packet is not sent. (qbv0.txt "t0 00000000b 20000")

Why doesn't qbvset and qbvget work on the swpX port?

Is this a problem with tsntool? Or is it because the kernel was not built by setting up the TSN-related configuration? 

 

0 件の賞賛
返信
1 解決策
4,412件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

You need to enable "MSCC_FELIX_SWITCH_TSN" in Linux Kernel configuration file, which is not enabled by default.

You could refer to section "8.8.1.2 Kernel configuration" in LSDK 21.08 user guide.

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
4,413件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

You need to enable "MSCC_FELIX_SWITCH_TSN" in Linux Kernel configuration file, which is not enabled by default.

You could refer to section "8.8.1.2 Kernel configuration" in LSDK 21.08 user guide.

0 件の賞賛
返信
4,378件の閲覧回数
JE-KIM
Contributor I

I built linux kernel (4.19) using flex-builder and config file and qbvset, qbvget worked for swpX ports. (I attached the used config file.)

However, although the switch configuration was performed by referring to Switch Configuration , packets between the boards(connected to swp0, swp1) are not transmitted.

When checked with the $ ip link show as below, it seems that there is no connection between the swpX ports and eno2 port unlike Felix interfaces.

$ ip link show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 22:79:ea:65:b1:bd brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether ba:ec:d4:e0:c3:22 brd ff:ff:ff:ff:ff:ff
4: swp0: <BROADCAST,MULTICAST> mtu 1468 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether aa:bc:77:9d:eb:a0 brd ff:ff:ff:ff:ff:ff
5: swp1: <BROADCAST,MULTICAST> mtu 1468 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether aa:bc:77:9d:eb:a1 brd ff:ff:ff:ff:ff:ff
6: swp2: <BROADCAST,MULTICAST> mtu 1468 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether aa:bc:77:9d:eb:a2 brd ff:ff:ff:ff:ff:ff
7: swp3: <BROADCAST,MULTICAST> mtu 1468 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether aa:bc:77:9d:eb:a3 brd ff:ff:ff:ff:ff:ff
8: swp4: <BROADCAST,MULTICAST> mtu 1468 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether aa:bc:77:9d:eb:a4 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
10: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group
default qlen 1000
link/ether 52:54:00:44:42:04 brd ff:ff:ff:ff:ff:ff
11: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:44:42:04 brd ff:ff:ff:ff:ff:ff
12: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group
default
link/ether 02:42:ec:cf:65:08 brd ff:ff:ff:ff:ff:ff

 

root@localhost:~# brctl show
bridge name  bridge id                       STP enabled       interfaces
br0                 8000.aabc779deba0       no                    swp0
                                                                                      swp1
                                                                                      swp2
                                                                                      swp3
docker0         8000.0242eccf6508         no
virbr0             8000.525400444204      yes                    virbr0-nic

 

Is the kernel build wrong?...

0 件の賞賛
返信