Nexus 3 frame format

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 
1,126件の閲覧回数
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,014件の閲覧回数
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,015件の閲覧回数
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,014件の閲覧回数
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 件の賞賛