Difference between revisions of "LPC845"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "__TOC__ ==MTB Trace== For the LPC84x series, MTB support was implemented by NXP in a non-standard way so that various things like CoreSight auto-detection of MTB and its buff...")
 
(MTB Trace)
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
For the LPC84x series, MTB support was implemented by NXP in a non-standard way so that various things like CoreSight auto-detection of MTB and its buffer are not possible. The J-Link software worksaround this and still gives the user a out-of-the-box experience when using MTB trace on this device.
 
For the LPC84x series, MTB support was implemented by NXP in a non-standard way so that various things like CoreSight auto-detection of MTB and its buffer are not possible. The J-Link software worksaround this and still gives the user a out-of-the-box experience when using MTB trace on this device.
 
J-Link software V6.46 or later is required to use MTB on this device series.
 
J-Link software V6.46 or later is required to use MTB on this device series.
  +
A sample project that demonstrates MTB backtrace via Ozone on this device can be found here:
 
  +
A sample project that demonstrates MTB backtrace via Ozone on this device can be found here: [https://wiki.segger.com/Tracing_on_NXP_LPC845#MTB_trace Trace Example]

Latest revision as of 13:49, 29 April 2019

Contents

MTB Trace

For the LPC84x series, MTB support was implemented by NXP in a non-standard way so that various things like CoreSight auto-detection of MTB and its buffer are not possible. The J-Link software worksaround this and still gives the user a out-of-the-box experience when using MTB trace on this device. J-Link software V6.46 or later is required to use MTB on this device series.

A sample project that demonstrates MTB backtrace via Ozone on this device can be found here: Trace Example