[EXT_EP-9367] ETB Trace on ARM9 fails to decode Created: 20/May/19 Updated: 19/Feb/20 Resolved: 20/May/19 |
|
| Status: | Fixed |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | Debug and Trace |
| Internal ID: | DBGTRC-4943 |
| Forum URL: | https://e2e.ti.com/support/tools/ccs/f/81/t/802900 |
| Found In Release: | EMU19_M02 |
| Fix In Release: | EMU19_M08 |
| Workaround: | N/A. Use Windows instaed. |
| Release Notes: | In Linux, collecting ETB Trace data from the ARM9 cores of both the OMAPL137 or OMAPL138 causes CCS to collapse at the end of the data collection. Basically the CCS application vanishes when the target is halted and the ETB trace data starts to be gathered from the target. In Windows, the same operation does not decode any data on the Trace view. |
| Description |
|
ETB Trace on ARM9 fails to decode |