RT1015 ETM trace data mux configuration

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

RT1015 ETM trace data mux configuration

1,415 Views
bert_downing
Contributor I

I'm wondering if there is some information missing in the RT1015 reference manual in regards to mux configuration for ETM trace support?  

The 4 data pins needed for ETM trace support are listed as being on pads GPIO_B0_12, 13, 14, and 15 according to page 1083 of the reference manual.  First, I'm assuming that this is supposed to be GPIO_AD_B0_12, 13, 14, and 15?  

Second, the mux control register description on page 355 does not list an ALT6 mux mode that should be used to select ETM trace data (trace0).  Is this just a mistake in the reference manual, or does the RT1015 not support this mode?  The other registers (B0_13, 14, and 15) also do not list ALT6 as an option to select trace data for these pads.  

I do see this information in the RT1020 reference manual register descriptions, so I'm assuming this is a misprint in the RT1015 manual, but I wanted to confirm.  I did verify that I'm using the latest rev (Rev 0) of the RT1015 reference manual.  Thanks.

Labels (1)
0 Kudos
Reply
4 Replies

1,308 Views
bert_downing
Contributor I

Any update on this?  I have downloaded MCUXpresso Config Tools and when I select the ARM pins for the RT1015, it does not give me the option to select the ETM data trace pins.  When I do this for the RT1021 it does have those pins as an option.  Does this mean the RT1015 does not support this?  

0 Kudos
Reply

1,308 Views
jeremyzhou
NXP Employee
NXP Employee

Hi Bert Downing,

Thanks for your reply.
I'm still waiting for the reply from the AE team, please be patient.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply

1,308 Views
jeremyzhou
NXP Employee
NXP Employee

Hi Bert Downing,

There's the reply from the AE team.

There are a couple of documentation errors that need to be fixed.
First, the table on p1083 should be referencing the GPIO_AD_B0 signals (_AD_ part of the signal name is missing). Then the mux options need to be added into the IOMUXC.

https___community.nxp.com_servlet_JiveServlet_showImage_2-1171235-270874_pastedImage_1.png

Have a great day,
TIC

 

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply

1,308 Views
jeremyzhou
NXP Employee
NXP Employee

Hi Bert Downing,

Thank you for your interest in NXP Semiconductor products and
for the opportunity to serve you.
Yes, I've confirmed this phenomenon, and I'll contact with the AE for confirmation and inform you later.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply