S32G3 LLCE Can2Can Routing

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

S32G3 LLCE Can2Can Routing

Jump to solution
2,127 Views
RoseRice
Contributor II

我在使用S32G399A,LLCE版本1_0_7,RTD版本4.0.2时有两个问题:
1、我将一个网段的报文转发到多个网段后,若断开某一个网段会导致其他网段的路由报文停止路由,重新接上后其他网段的路由报文能恢复;
2、LLCE转发的报文和CanHardwareObject中配置的CanObject Payload Length长度不一致时也能正常转发,LLCE路由对报文长度是否有做检查,这个属于正常现象吗?
期待您的回复

 

I have two issues when using S32G399A, LLCE version 1_0_7, RTD version 4.0.2:
1. After forwarding a message from one network segment to multiple network segments, disconnecting one network segment will cause the routing messages of other network segments to stop. After reconnecting, the routing messages of other network segments can be restored;
2. When the message forwarded by LLCE is not consistent with the CanObject Payload Length configured in CanHardwareObject, it can still be forwarded normally. Does the LLCE router check the length of the message? Is this a normal phenomenon?
We look forward to your reply
Tags (3)
0 Kudos
Reply
1 Solution
1,976 Views
Joey_z
NXP Employee
NXP Employee

hi,RoseRice

感谢您的回复和详细的信息!

1.断开通道2和S32G直接的CAN连接后,通道2离线同时通道3转发的路由报文也停止(问题复现);

>>>根据您的描述,这是CAN2CAN中multicast routing和LLCE固件的限制,如果一个传输通道无法发送时,将一直使相应的block处于阻塞状态,直到成功传输完成,可以参考图片内容。所以根据介绍,您应该是在CAN0断开口导致了block,影响了CAN9

 

2.LLCE转发的报文和CanHardwareObject中配置的CanObject Payload Length长度不一致时也能正常转发,LLCE路由对报文长度是否有做检查,这个属于正常现象吗?

>>>默认情况下CAN frame playload的长度不作为转发的规则,CanObject Payload Length设置的是RX buffer的格式,例如是8B还是64B

BR

Joey

View solution in original post

0 Kudos
Reply
5 Replies
2,093 Views
Joey_z
NXP Employee
NXP Employee

Hi,RoseRice

感谢您联系我们!

您使用的是我们开发板还是您们的设计板子,只使用的M核做的测试吗?

1.我将一个网段的报文转发到多个网段后,若断开某一个网段会导致其他网段的路由报文停止路由,重新接上后其他网段的路由报文能恢复;

>>>请问您的具体转发操作是什么样的呢?例如LLCE_CAN0接收到外部CAN帧转发到LLCE_CAN1和LLCE_CAN2。断开某个网段您是如何做的呢?
2、LLCE转发的报文和CanHardwareObject中配置的CanObject Payload Length长度不一致时也能正常转发,LLCE路由对报文长度是否有做检查,这个属于正常现象吗?

>>>您转发的报文和CanObject Payload Length长度长度是如何设置的呢?

BR

Joey

0 Kudos
Reply
2,061 Views
RoseRice
Contributor II

您使用的是我们开发板还是您们的设计板子,只使用的M核做的测试吗?
reply:使用的是我们自己的板子,只使用M核做的测试

1.我将一个网段的报文转发到多个网段后,若断开某一个网段会导致其他网段的路由报文停止路由,重新接上后其他网段的路由报文能恢复;

>>>请问您的具体转发操作是什么样的呢?例如LLCE_CAN0接收到外部CAN帧转发到LLCE_CAN1和LLCE_CAN2。断开某个网段您是如何做的呢?
reply:我们是通过CAN11接收从上位机发送的CAN报文(0x3AD),转发到CAN0和CAN9这两路上,如附件中图片所示:
a> 通道1连接S32G的CAN11,通道2连接S32G的CAN0,通道3连接S32G的CAN9;
b> 0x300, 0x309, 0x30B是S32G周期发送的报文;0x3AD是测试用的路由报文;
c> 正常接线时,通道1/2/3周期报文和路由报文均正常;
d> 断开通道2和S32G直接的CAN连接后,通道2离线同时通道3转发的路由报文也停止(问题复现);

2、LLCE转发的报文和CanHardwareObject中配置的CanObject Payload Length长度不一致时也能正常转发,LLCE路由对报文长度是否有做检查,这个属于正常现象吗?

>>>您转发的报文和CanObject Payload Length长度长度是如何设置的呢?
reply:CanObject Payload Length长度我们在EB中没有勾选前面的使能框。问题现象如图,DLC不同长度下报文都能正常转发。针对这个问题,我想知道能否通过EB配置检查Can2Can路由时报文长度,使只有满足配置的DLC长度时才做转发

Tags (3)
0 Kudos
Reply
1,977 Views
Joey_z
NXP Employee
NXP Employee

hi,RoseRice

感谢您的回复和详细的信息!

1.断开通道2和S32G直接的CAN连接后,通道2离线同时通道3转发的路由报文也停止(问题复现);

>>>根据您的描述,这是CAN2CAN中multicast routing和LLCE固件的限制,如果一个传输通道无法发送时,将一直使相应的block处于阻塞状态,直到成功传输完成,可以参考图片内容。所以根据介绍,您应该是在CAN0断开口导致了block,影响了CAN9

 

2.LLCE转发的报文和CanHardwareObject中配置的CanObject Payload Length长度不一致时也能正常转发,LLCE路由对报文长度是否有做检查,这个属于正常现象吗?

>>>默认情况下CAN frame playload的长度不作为转发的规则,CanObject Payload Length设置的是RX buffer的格式,例如是8B还是64B

BR

Joey

0 Kudos
Reply
1,944 Views
RoseRice
Contributor II
感谢,路由问题通过调大接收邮箱中的 Number of Hw objects used to implement one HOH配置问题不复现了
0 Kudos
Reply
1,938 Views
Joey_z
NXP Employee
NXP Employee

hi,RoseRice

感谢分享这些信息!

有任何问题可以随时在community或者我们support系统(Home)中提问。

BR

Joey

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2322930%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3ES32G3%20LLCE%20Can2Can%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2322930%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20have%20two%20problems%20when%20using%20S32G399A%2C%20LLCE%20version%201_0_7%2C%20RTD%20version%204.0.2%3A%20%3CBR%20%2F%3E1%2C%20I%20will%20forward%20the%20message%20of%20a%20network%20segment%20to%20multiple%20network%20segments%2C%20if%20I%20disconnect%20a%20network%20segment%20will%20lead%20to%20other%20network%20segments%20of%20the%20routing%20message%20to%20stop%20the%20routing%2C%20reconnect%20after%20the%20other%20network%20segments%20of%20the%20routing%20message%20can%20be%20resumed%3B%20%3CBR%20%2F%3E2%2C%20LLCE%20forwarding%20message%20and%20the%20length%20of%20CanObject%20Payload%20Length%20is%20not%20consistent%2C%20but%20also%20can%20be%20forwarded%20normally%2C%20LLCE%20routing%20on%20the%20message%20length%20whether%20to%20do%20check%2C%20this%20is%20a%20normal%20phenomenon%3F%202%2C%20the%20message%20forwarded%20by%20LLCE%20and%20the%20CanObject%20Payload%20Length%20configured%20in%20CanHardwareObject%20can%20be%20forwarded%20normally%20when%20the%20length%20of%20the%20CanObject%20Payload%20Length%20is%20not%20the%20same%2C%20does%20LLCE%20routing%20check%20the%20length%20of%20the%20message%2C%20is%20this%20a%20normal%20phenomenon%3F%20%3CBR%20%2F%3EI%20am%20looking%20forward%20to%20your%20reply.%3C%2FP%3E%3CBR%20%2F%3E%3CDIV%20class%3D%22%22%3EI%20have%20two%20issues%20when%20using%20S32G399A%2C%20LLCE%20version%201_0_7%2C%20RTD%20version%204.0.2.%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E1.%20After%20forwarding%20a%20message%20from%20one%20network%20segment%20to%20multiple%20network%20segments%2C%20disconnecting%20one%20network%20segment%20will%20cause%20the%20routing%20messages%20of%20other%20network%20segments%20to%20stop.%20After%20reconnecting%2C%20the%20routing%20messages%20of%20other%20network%20segments%20can%20be%20restored%3B%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E2.%20When%20the%20message%20forwarded%20by%20LLCE%20is%20not%20consistent%20with%20the%20CanObject%20Payload%20Length%20configured%20in%20CanHardwareObject%2C%20it%20can%20still%20be%20forwarded%20normally.%20Does%20the%20LLCE%20router%20check%20the%20length%20of%20the%20message%3F%20Is%20this%20a%20normal%20phenomenon%3F%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3EWe%20look%20forward%20to%20your%20reply%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2323539%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20LLCE%20Can2Can%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2323539%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20%3CSPAN%3E%2C%20Rose%20Rice.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20contacting%20us!%3C%2FP%3E%0A%3CP%3EAre%20you%20using%20our%20development%20boards%20or%20your%20design%20boards%20with%20only%20the%20M%20core%20for%20testing%3F%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E1.%20After%20I%20forward%20messages%20from%20one%20segment%20to%20multiple%20segments%2C%20if%20I%20disconnect%20one%20segment%2C%20it%20will%20cause%20the%20routing%20messages%20of%20other%20segments%20to%20stop%20routing%2C%20and%20the%20routing%20messages%20of%20other%20segments%20can%20be%20restored%20after%20reconnecting%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26gt%3B%26gt%3B%26gt%3BWhat%20is%20your%20specific%20forwarding%20operation%3F%20For%20example%2C%20LLCE_CAN0%20receives%20external%20CAN%20frames%20and%20forwards%20them%20to%20LLCE_CAN1%20and%20LLCE_CAN2.%20How%20do%20you%20disconnect%20a%20certain%20network%20segment%3F%20%3CBR%20%2F%3E%202%20%3CSTRONG%3E.%20If%20the%20length%20of%20the%20message%20forwarded%20by%20LLCE%20is%20not%20the%20same%20as%20the%20length%20of%20the%20CanObject%20Payload%20Length%20configured%20in%20the%20CanHardwareObject%2C%20it%20can%20be%20forwarded%20normally.%20Is%20it%20normal%20for%20the%20routing%20to%20check%20the%20length%20of%20the%20payload%3F%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26gt%3B%26gt%3B%26gt%3BHow%20are%20your%20forwarded%20messages%20and%20CanObject%20Payload%20Length%20length%20length%20set%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EBR%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EJoey.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2324598%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20LLCE%20Can2Can%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2324598%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EAre%20you%20using%20our%20development%20board%20or%20your%20own%20design%20board%2C%20and%20are%20you%20using%20only%20the%20M-core%20for%20testing%3F%20%3CBR%20%2F%3Ereply%3A%20We%20are%20using%20our%20own%20board%2C%20and%20are%20using%20only%20the%20M-core%20for%20testing.%3C%2FP%3E%3CP%3E1.%20After%20I%20forward%20messages%20from%20one%20segment%20to%20multiple%20segments%2C%20if%20I%20disconnect%20one%20segment%2C%20it%20will%20cause%20the%20routing%20messages%20of%20other%20segments%20to%20stop%20routing%2C%20and%20the%20routing%20messages%20of%20other%20segments%20can%20be%20restored%20after%20reconnecting%3B%3C%2FP%3E%3CP%3E%26gt%3B%26gt%3B%26gt%3BWhat%20is%20your%20specific%20forwarding%20operation%3F%20For%20example%2C%20LLCE_CAN0%20receives%20external%20CAN%20frames%20and%20forwards%20them%20to%20LLCE_CAN1%20and%20LLCE_CAN2.%20How%20do%20you%20do%20it%20to%20disconnect%20a%20certain%20segment%3F%20%3CBR%20%2F%3Ereply%3A%20We%20receive%20CAN%20messages%20(0x3AD)%20from%20the%20host%20computer%20via%20CAN11%20and%20forward%20them%20to%20both%20CAN0%20and%20CAN9%20as%20shown%20in%20the%20attached%20picture%3A%20%3CBR%20%2F%3Ea%20%26gt%3B%20Channel%201%20connects%20to%20CAN11%20of%20S32G.%20S32G's%20CAN11%2C%20channel%202%20connects%20to%20S32G's%20CAN0%2C%20and%20channel%203%20connects%20to%20S32G's%20CAN9%3B%20%3CBR%20%2F%3Eb%20%26gt%3B%200x300%2C%200x309%2C%200x30B%20are%20the%20messages%20sent%20by%20S32G's%20cycle%3B%200x3AD%20is%20the%20routing%20message%20for%20testing%3B%20%3CBR%20%2F%3Ec%20%26gt%3B%20When%20wired%20normally%2C%20channel%201%2F2%2F3%20cycle%20messages%20and%20routing%20messages%20are%20normal%3B%20%3CBR%20%2F%3Ed%20%26gt%3B%20After%20disconnecting%20the%20CAN%20connection%20between%20channel%202%20and%20S32G%20directly%2C%20channel%202%20goes%20offline.%20CAN%20connection%2C%20channel%202%20goes%20offline%20while%20the%20routing%20messages%20forwarded%20by%20channel%203%20stop%20(problem%20recurs)%3B%3C%2FP%3E%3CP%3E2%2C%20LLCE%20forwarded%20messages%20and%20CanHardwareObject%20configured%20in%20the%20CanObject%20Payload%20Length%20length%20is%20not%20consistent%20can%20also%20be%20forwarded%20normally%2C%20LLCE%20routing%20on%20the%20length%20of%20the%20message%20whether%20to%20do%20checks%2C%20this%20is%20a%20normal%20phenomenon%3F%3C%2FP%3E%3CP%3E%26gt%3B%26gt%3B%26gt%3BHow%20do%20you%20set%20the%20length%20of%20the%20forwarded%20messages%20and%20the%20CanObject%20Payload%20Length%20length%3F%20%3CBR%20%2F%3Ereply%3ACanObject%20Payload%20Length%20length%20we%20did%20not%20check%20the%20enable%20box%20in%20front%20of%20it%20in%20EB.%20The%20problem%20is%20as%20shown%20in%20the%20figure%2C%20the%20message%20can%20be%20forwarded%20normally%20under%20different%20lengths%20of%20DLC.%20I%20would%20like%20to%20know%20if%20it%20is%20possible%20to%20check%20the%20length%20of%20Can2Can%20routing%20message%20through%20EB%20configuration%2C%20so%20that%20the%20message%20will%20be%20forwarded%20only%20when%20it%20meets%20the%20configured%20DLC%20length.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2324816%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20LLCE%20Can2Can%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2324816%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%20Rose%20Rice.%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20your%20reply%20and%20detailed%20information!%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSTRONG%3E1.%20After%20disconnecting%20the%20direct%20CAN%20connection%20between%20channel%202%20and%20the%20S32G%2C%20channel%202%20goes%20offline%20and%20the%20routing%20messages%20forwarded%20by%20channel%203%20stop%20(the%20problem%20recurs)%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%3E%26gt%3B%26gt%3B%26gt%3B%3C%2FSPAN%3E%3CSPAN%3EAccording%20to%20your%20description%2C%20this%20is%3C%2FSPAN%3E%3CSPAN%3E%20CAN2CAN%3C%2FSPAN%3E%3CSPAN%3E%20The%20multicast%20routing%20and%3C%2FSPAN%3E%3CSPAN%3E%20LLCE%3C%2FSPAN%3E%3CSPAN%3E%20firmware%20limitations%2C%20if%20a%20transmission%20channel%20cannot%20be%20sent%2C%20it%20will%20keep%20the%20corresponding%20block%20in%20blocking%20state%20until%20the%20successful%20transmission%20is%20completed%2C%20you%20can%20refer%20to%20the%20picture%20content.%20So%20according%20to%20the%20introduction%2C%20you%20should%20be%20in%20the%3C%2FSPAN%3E%3CSPAN%3E%20C%3C%2FSPAN%3E%3CSPAN%3E%20AN0%20disconnect%20is%20causing%20the%3C%2FSPAN%3E%3CSPAN%3E%20block%3C%2FSPAN%3E%3CSPAN%3E%20that%20affects%20the%3C%2FSPAN%3E%3CSPAN%3E%20CAN9%3C%2FSPAN%3E%3CSPAN%3E%20The%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20'Microsoft%20YaHei'%3B%20font-size%3A%2011.0pt%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20'Microsoft%20YaHei'%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSTRONG%3E2.%20LLCE%20forwarded%20messages%20and%20CanHardwareObject%20configured%20in%20the%20CanObject%20Payload%20Length%20length%20is%20not%20consistent%20can%20also%20be%20forwarded%20normally%2C%20LLCE%20routing%20on%20the%20message%20length%20whether%20to%20do%20checks%2C%20this%20is%20a%20normal%20phenomenon%3F%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%3E%26gt%3B%26gt%3B%26gt%3BBy%20default%20the%20CAN%20frame%20playload%3C%2FSPAN%3E%3CSPAN%3E%20length%20is%20not%20used%20as%20a%20rule%20for%20forwarding%2C%20the%20CanObject%20Payload%20Length%20is%20set%20for%20the%3C%2FSPAN%3E%3CSPAN%3E%20RX%20buffer%3C%2FSPAN%3E%3CSPAN%3E%20format%2C%20for%20example%3C%2FSPAN%3E%3CSPAN%3E%208B%3C%2FSPAN%3E%3CSPAN%3E%20or%3C%2FSPAN%3E%3CSPAN%3E%2064B%3C%2FSPAN%3E%3CSPAN%3E%20The%20format%20of%20the%20RX%20buffer.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%3EBR%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-size%3A%2011.0pt%3B%22%3E%3CSPAN%3EJoey.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2325922%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20LLCE%20Can2Can%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2325922%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3EThank%20you%2C%20the%20routing%20issue%20is%20not%20reproduced%20by%20increasing%20the%20Number%20of%20Hw%20objects%20used%20to%20implement%20one%20HOH%20configuration%20issue%20in%20the%20receiving%20mailboxes%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2325932%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20LLCE%20Can2Can%20Routing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2325932%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20%3CSPAN%3E%2C%20Rose%20Rice.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThanks%20for%20sharing%20this%20information!%3C%2FP%3E%0A%3CP%3EFeel%20free%20to%20ask%20any%20questions%20in%20the%20community%20or%20in%20our%20support%20system%20%3CA%20href%3D%22https%3A%2F%2Fsupport.nxp.com%2Fs%2F%3Flanguage%3Dzh_CN%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E(Home%3C%2FA%3E%20).%3C%2FP%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EJoey.%3C%2FP%3E%3C%2FLINGO-BODY%3E