Nexus 3 frame format

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

Nexus 3 frame format

跳至解决方案
2,105 次查看
manuelsaez
Contributor II

Hi,

 

trying to decode the Nexus frames I came to a question that I could not find in the reference manual.

 

In chapter "63.7 Nexus message fields" the reference manual stays that:

"A packet may contain any number of fixed length fields, but may contain at most one variable length field."

 

However in Charpter 63.3 TCODEs supported there are frame with up to 3 variable fields (like the Program Trace - Indirect Branch Messages). How can I know then what is the length of each field?

 

Best regards,

Manuel

标签 (1)
1 解答
1,993 次查看
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

there are two different things: packet and message. Message can contain more packets.

Here is nice example for Indirect Branch Message:

pastedImage_0.png

Example:

pastedImage_1.png

MSEO is used to indicate start/end of packet/message:

pastedImage_2.png

Regards,

Lukas

在原帖中查看解决方案

2 回复数
1,994 次查看
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

there are two different things: packet and message. Message can contain more packets.

Here is nice example for Indirect Branch Message:

pastedImage_0.png

Example:

pastedImage_1.png

MSEO is used to indicate start/end of packet/message:

pastedImage_2.png

Regards,

Lukas

1,993 次查看
manuelsaez
Contributor II

That's very helpful!.

Since I am accessing the nexus interface through Lauterbach I have no access to the pins and I cannot see the separation between messages and packets but that's something I have to clarify somewhere else :-).

Thank you!.

0 项奖励
回复