-
Notifications
You must be signed in to change notification settings - Fork 178
Create itm.md #413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create itm.md #413
Changes from 4 commits
c78bcd7
adab5a4
0ac6a71
fdb4638
4eb983d
e3df420
9f098e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
### Instrumented Trace Macrocell | ||
|
||
For targets with Arm CoreSight (for example, Cortex-M3 and Cortex-M4), the Instrumented Trace Macrocell provides a lightweight, nonintrusive way to collect debug trace output. | ||
|
||
#### Assumptions | ||
|
||
##### Defined behavior | ||
|
||
When initialized, writing data to the ITM stimulus registers results in the data being transmitted over the SWO line. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Query: When what is initialized, by whom or by what? |
||
|
||
##### Undefined behavior | ||
|
||
- The debug clock frequency is left undefined because the most optimal frequency varies from target to target. It is up to each target's owner to choose a frequency that doesn't interfere with normal operation and that the owner's preferred debug monitor supports. | ||
- If another peripheral tries to take control of the SWO pin, it is undefined whether that operation succeeds. | ||
|
||
##### Note | ||
|
||
Some SWO viewers do not allow an arbitrary frequency to be set. Make sure that the development tools you expect your users to use support the chosen frequency. | ||
|
||
#### Dependencies | ||
|
||
- The target supports Arm CoreSight. | ||
- The target has SWO connected either to a compatible interface chip or exposed as a debug pin. | ||
|
||
#### Implementing the ITM API | ||
|
||
- You must implement the function `itm_init`. When the function is called: | ||
- The debug clock for the ITM must be initialized. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Query: Do you, the user initialize the debug clock for the ITM? |
||
- The SWO pin must be configured for debug output. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Query: Do you, the user, configure the SWO pin for debug output? |
||
- You must add `ITM` to the `device_has` section in `target.json`. | ||
|
||
It is not necessary to modify any of the ITM registers in `itm_init`, except for the one related to the clock prescaling, `TPI->ACPR`. The helper function `mbed_itm_init` is responsible for calling `itm_init` and initializing the generic ITM registers. `mbed_itm_init` only calls the function `itm_init` once, making it unnecessary to protect `itm_init` against multiple initializations. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Query: Why are there no notes, dependencies or implementations? Please complete these sections. |
||
#### Testing | ||
|
||
You can use the `SerialWireOutput` to send `stdout` to the SWO stimulus port on the ITM by including this override function: | ||
|
||
``` | ||
#include "SerialWireOutput.h" | ||
|
||
FileHandle* mbed::mbed_override_console(int fd) | ||
{ | ||
static SerialWireOutput swo; | ||
return &swo; | ||
} | ||
``` | ||
|
||
You can place the function in any C++ compilation unit, including `main.cpp`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this API have spaces in it, or does it follow the same formatting as the others ("InstrumentedTraceMacrocell")?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the question. Instrumented Trace Macrocell is the name of the module like Low Power Ticker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have the ResetReason API, which is has no space and both Rs capitalized because we're referring to the class. Is it the same with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, no. This is a physical component defined in the architecture: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0314h/Chdegecg.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marcuschangarm - Looks good, it would be great if you can add that ITM link in the documentation itself. Its not a blocker though, so I'll approve.