For specific use cases and linking the Comparator 1 winIDEA offers manual configuration of the DWT module . Use cases cover comparing values on Address or/and Data with an option Ignore LSB bits: 1. Address Compare on Address on Data Access Compare on Address Range on Data Access 2. Addres...
RH850 Software Trace (SFT) uses a small FIFO that can easily overflow when too many trace messages are generated. This can cause sampling time to decrease or overflow error messages in the Analyzer Trace window (indicated by brown colored lines). Possible solutions Increase the LPD-4 clock...
Sampling With this approach, you can periodically sample variables (data variables or program execution) via a debug port. The concept of Profiler Sampling is mainly used for statistical analysis or sampling rather slowly changing variables and cyclic program execution. Emulation Adapter A...
Analyzer Manual Hardware Trigger configurations (TRD) created in winIDEA versions 9.21.134 or above may not show when transitioning to newer winIDEA versions. Possible solution 1. Open winIDEA version 9.21.133 or below. 2. Go to File | Save as and save the TRD file. 3. Open a newer version...
When trying to run Analyzer from winIDEA, trace fails and an error message displays Disk quota exceeded . Possible solution 1. In the Analyzer window, press Options . 2. In theGeneral tab, adjust thesettings in Remaining disk quota in GB . 3. Verify how much disk space you actually have on...
In some cases, the CPU is not able to stream the trace data quickly enough, which results in overflow errors. Errors are displayed in the Analyzer Output window and indicated in theTrace window with brown colored lines. Possible solutions Limit the scope of the recorded variables (e.g. tas...
When the Analyzer stops sampling with the note Trace sampling stopped, reason: Emulator buffer full . A situation hasoccurredin which the trace RAM buffer of the BlueBox is full and no longer able to accept new data. This happens when trace data is being received faster than the BlueBox is...
With Nexus trace, which is a message-based trace, the actual trigger point (frame 0) is most likely not displayed next to the instruction that generated the trigger event. The Nexus trace port broadcasts only addresses of non-sequential branch jumps. All the sequential code in between is r...
Nexus Event Out Pin (EVTO) signal is used in winIDEA as a trace trigger, but it is not enabled. Possible solution To generate the trigger event (EVTO), enable it in the Trigger Configuration dialog. 1. Open View | Analyzer . 2. Click the Analyzer Configuration button. 3. Check the Manual H...
Devices that feature anETMv4(such as most devices of the S32K3xx family) include program trace when configured to output any data trace.winIDEA will record data and program trace even if only data trace is selected, and the complete recording will show on the Trace Window. This means that ...
In contrast to the iC5xxx BlueBox, the iC7mini only supports RH850 Software Trace(SFT) where the data is stored to the SoC on-chip trace. iC7mini doesn't support SFT where the data is streamed outside the SoC to the debugger’s hardware through the LPD debug interface. However, the iC7pro s...
If longer trace sessions are required, e.g. for coverage measurement during system tests, ensure your system is set up optimally. Optimal PC setup: Multi-core CPU (for optimal distribution of workload during profiler or coverage analysis) 4GB RAM minimum, 8GB or more RAM recommended %TEMP%...
CPUSTM32H7 runs at a max. 480 MHz. If dividing the trace, it is possible to get about 100 MHz (supported by the BlueBox) which can cause problems with Flash. For a successful Trace do not stop the Analyzer and CPU simultaneously. Possible solution Stop the Analyzer before CPU: 1. Start Ana...
Printing characters via ITM can result in all the characters not being displayed in the Terminal Window. For example, here's an ITM message ("\nTEST_12345678") and some possible outputs: Explanation Tracing (observing theTerminalWindow falls under this category), is a non-intrusive operati...
Kinetis devices encompass a range of models, each offering different levels of Embedded Trace Macrocell (ETM) capabilities and parallel trace output pins. To determine the specific features available on your target device, please consult the corresponding reference manual. Affected familie...
GPIO port selection for Energy Micro EFM32 trace initialization is configured as script arguments in the CPU Options dialog. The script is distributed with winIDEA in the SFR folder. Possible solution 1. Add the custom script TraceInit_EFM32xxxx_a.cpp to Hardware | CPU Options | Analyzer |...
Trace port settings are only applicable on devices that support parallel trace. GPIO port selection initialization is configured as script parameters. The script is included in the winIDEA SFR folder. If older workspaces are in use, ports have to be configured again. Possible solution 1. A...
Trace recording is incomplete because of the big gaps in time and trace message number, with ITM Synchronization lost messages in between.This typically happens due to the SWO clock instability, or too high of SWO data rate. Possible solution 1. Update to the latest winIDEA version . 2. Ad...
Solution After you have successfully connected hardware and selected the current range according to the shunt resistor (JB1 jumper block), and voltage range depending on your target power supply range ( JB2 jumper block ) on the Power Probe, configure the following settings in winIDEA . Mo...
Non-optimal Target PCB design(different line lengths , vias, stubs, etc.)and other hardware accessories (connectors, power supply, etc.) can degrade the electrical signals. Therefore while transferring information at high frequencies from the Target CPU to the BlueBox, signal integrity iss...
Possible solutions File size is limited Trace file size is software-limitedby the Recording Size Limit setting in theRecorder Configuration dialog. Make sure you set a large enough limit (e.g. can be specified in GB, as well as TB). Enough disk space available Ensure that the drive on whic...
On-Chip trace logic monitors the CPU execution inside the SoC. O btained data is compressed using trace protocols and either: Streamed out through the trace port, where BlueBox debugger is capturing the data on the trace port. Each sample is time-stamped by the BlueBox timer. Captured in t...
If you start tracing while a core is running, the sequential configuration of trace components might produce undesired artifacts in the trace stream (e.g. considerable amount of ITM trace before ETM messages start). Note that Cortex trace does not have a global trace switch that "turns on ...
Error message AGBT FIFO overflow indicates that TriCore’s internal FIFO overflowed, which means that in a short time too many trace messages were written into FIFO. The below steps explain in the TC3xx example how to define custom triggers, use an algorithmic approach, halving the range to...
If a Missing program code message is displayed in the trace, it means that the program was executed at addresses where no code image is available in the download file. The debugger needs a complete code image for the correct trace reconstruction. The code not reported in the download file ...
On many Arm devices, the trace clock is directly related to the CPU clock set by your application.Be aware of this dependency when using the same winIDEA workspace to trace different applications, as it is possible that values from a previously performed trace line calibration may not work...
Error message AGBT FIFO overflow indicates that TriCore’s internal FIFO overflowed, which means that in a short time too many trace messages were written into FIFO. The below steps explain on the TC3xx example how to define custom triggers and use an algorithmic approach to find two or mor...
Trace window content is not refreshed properly after the trace recording is finished and uploaded. Possible solution Scroll the results using PgUp/PgDd. More resources in winIDEA Help Trace window
This topic visualisessteps on how to define custom triggers and use an algorithmic approach to find two or more problematic functions that generate too many trace messages in a wider range which are described in the topic How to find two or more problematic functions in a wider range if AG...
CAN/LIN module enables recording CAN and LIN messages as standalone operation with or without using debug. A detailed description of the configuration is available in winIDEA Help .
ADIO module enables recording analog and digital signals as standalone operation with or without using debug. Detailed description of the configuration is available in winIDEA Help .
Specific settings should be configured for this device so the trace trigger works correctly. Possible solution 1. Open Hardware | CPU Options | CTM/CTI . 2. Check in CTM Channel 2: R5.0˜ETMTRIGGER in TRIGINs. TPIUTRIGIN in TRIGOUTs . More resources in winIDEA Help CTM/CTI
By default the fast internal RC oscillator (FIRC) is used for generating the trace clock.The resistor and capacitor values(RC components) of this oscillator show significant tolerances due to the nature of themanufacturing process and also vary upon differences in supplied voltage and work...
Trace is initialized in the user application, but the trace output does not appear on the SWO pin when the target is used in standalone mode (i.e. not connected to a BlueBox debugger). Explanation On Arm Cortex devices the SWO trace pin can only be used in combination with SWD (Serial Wire...
Errors like missing data, no trace messages shown in the terminal window, or data displayed at the wrong address in the trace recording can be a result of SWO tracing during the PLL initialization. SWO trace during the PLL ( Phase-Locked Loop) initialization is not supported by winIDEA. Po...
Solution Refer to Configure Micro Trace Buffer (MTB) trace in winIDEA Help. More resources in winIDEA Help Micro Trace Buffer (MTB) Analyzer Operation mode
When using Automatic Trace configuration (i.e., when Manual Trigger C onfiguration is not selected) and starting the recording, the Analyzer may show a warning: Cannot configure: There are no hardware resources to configure all of the requested areas. The Analyzer attempts to use one POB (...
First check, whether your CPU supports trace - refer to the topic Trace is not licensed . Possiblesolutions Trace Buffer is configured in Hardware | CPU Options | SoC. Default The option Use all available memory for trace buffer should work in most cases assuming that complete TCM memory i...
When starting a new Analyzer session, winIDEA displays an error message, although a l icense for the trace is purchased. Possible solutions Determine what trace technology is available on your target Open Hardware | CPU Options | Analyzer and check if the trace Operation mode can not be se...
In corner cases, it can happen that multiple valid regions are visible in the trace calibration diagram (shown as gaps or ‘eyes’) and a non-working setting is recommended by the Trace Line Calibration tool. When such a setting is selected, the trace session will fail to trigger and the ana...
MPC5675 K can stay in SAFE mode which disables the MCKO signal and the trace does not work. Possible solution Use the below init sequence which switches CPU from SAFE into DRUN mode: A RGM_FES W 0x4080 A ME_MCTL L 0x30005AF0 A ME_MCTL L 0x3000A50F
CPU Load is an important tool to understand the real-time behavior of an application and can be calculated by averaging over the Core Loads. Refer to the CPU Load How-to guide in winIDEA Help. More resources Understanding Linux process load compared to embedded RTOS CPU Utilization - Webin...
When encountering issues with profiling, always verify that the underlying hardware trace configuration works as intended. After recording a trace, you can use the Trace Window or Profiler Timeline Window to verify that events of interest have been recorded. If no events are visible, or if...
Coding empty or very short program loops in embedded applications can cause CPU program trace overflows. Too many branches coming in succession are overwhelming the internal CPU trace logic that just can’t keep up with a torrent of branch messages. P ossible solutions are: Snooze Halt inst...