Posts by SEGGER - Nino

Hello,

Thank you for your inquiry.

For buffer tracing the MIPI10 connector is typically sufficient.
However your target device has to meet certain requirements for buffer tracing to work:
https://kb.segger.com/Arm_trace_tech…race_components

If your target device meets these requirements it is typically sufficient to set the trace source in Ozone to "Trace Buffer".

With some multi core target devices it may be additionally needed to set the base addresses for the Coresight components that the J-Trace Pro could not autodetect:
https://kb.segger.com/Arm_trace_tech…mponents_failed

Regarding SWO. On more complex devices is it usually required to init the device/board specific SWO pin via a .JLinkScript.
https://kb.segger.com/SWO

In Ozone currently only SWO/ITM printf via stimulus ports is available.
Instruction tracing via SWO pin is on our wish list but without a fix timeschedule.

Best regards,
Nino

Hello,

Thank you for your inquiry.
We have the following example project for a related eval board:
https://kb.segger.com/Tracing_on_Atmel_ATSAME70

As you can see there in section Specifics/Limitations there is some functional overlap of the trace pins that might interfere with signal quality.
I assume it is similarly done on the Ultra board.

General information about signal issue troubleshooting with J-Trace Pro can be found here:
https://kb.segger.com/Adjusting_trac…troubleshooting

I hope that helps.

Best regards,
Nino

Hello,

Thank you for your inquiry.
You can find an example project for the STM32U575 EVAL Board here:
https://kb.segger.com/ST_STM32U5#Tracing_on_ST_STM32U5

So generally that should be working on custom boards as well, you might just need to adapt the trace pin init.

Best regards,
Nino

Hello,

Thank you for your inquiry.

The described behaviour is expected. The debugger has to initialize ETB trace to be able to use it. For this a defined system state is needed e.g. after reset or target halt.
After continuing after such defined system state you should see trace data.

For such post-mortem analysis that you describe you have to take care of initialization yourself and dump the data in ETB buffer manually as it was not set up through our software so we do not know the trace settings which is required to know to be able to analyze the trace data afterwards.

Best regards,
Nino

Note: Moved to J-Link forum as this is more a J-Link question.
As soon as J-Link support is added for the aforementioned devices Embedded Studio is automatically also available.

Depending on the target devices complexity it might also be sufficeint to simply select generic RV32 as target device.

Best regards,
Nino

We received the following solution for this issue from TESSY Support Team:

"Message Box in Keil uVision from JLink:
The debugger has set two breakpoints at the same address

If you click OK fast enough, the test will still be executed successfully.
However, the correct solution is found in the Debugger Settings in Keil:
Options for Target -> Debug -> JLink -> Settings -> DISABLE Reset after Connect"

Hello,

Thank you for your inquiry.
SystemView is Core architecture independent and can always be used.
So RISC-V is also supported.

Best regards,
Nino

Hello,

Please note that thread bumping is against forum rules.
This will be the only and last warning as you have violated that rule twice already..

Additionally this is not a support forum so there is no guarantee that you will receive an answer. If you require support from SEGGER please use our official channels as mentioned below.

Best regards,
Nino

Hello,

here you can find an overview of the different trace types and what they can do:
https://wiki.segger.com/General_information_about_tracing

The exception tracing you are referencing is most likely ITM trace. Currently ITM tracing is only partially available within Ozone and is joined with the ETM trace data received via the trace parallel port from target.
That way we have a gapless instruction trace recording with periodic timestamps.

However user generated ITM data and events will currently not be displayed in Ozone, but it is on our wishlist.

One of the reasons why this is not yet available with Ozone is because most of the use cases that the ITM solves is already solved by our tool SystemView, but better:
https://www.segger.com/products/devel…ols/systemview/

From your descriptions I think SystemView would be the better tool choice for your use case where you only want a high level view of your application.

Best regards,
Nino

Hello,

Thank you for your inquiry.
If your chip features multiple possible sets of trace pins you can generally use any combination you want. You just have to make sure that the chosen trace pins fit the ones that you are initializing in your .JLinkScript file.
In the linked example project you will find an example script that sets up PE2-PE6.
The example script will limit the trace data pins to 1 pin though to make the pictured setup possbile with the flying wires.
If you plan on using all 4 trace pins make sure the line where variable "JLINK_TRACE_PortWidth" is set is commented out or that value is set to 4 instead.

A general guide on how to setup trace pin inits is explained here:
https://wiki.segger.com/How_to_configu…_enable_tracing

Best regards,
Nino

Hello,

Thank you for your feedback.
Correct there was a mistake in how the suspended state was masked. Will be fixed in the next release.

Best regards,
Nino

Hello,

Thank you for your inquiry.
As Frank stated the file is one way or another in your project under that path.
If I had to guess you moved the project from one PC to another. So if you use absolute paths for your files that pup up will appear.

To avoid this either use relative paths in your projects or un-check the "Show this dialog the next time" in the pop up. Then the warning message should no longer show up for this file.

Best regards,
Nino

Hello,

Thank you for your inquiry.
See the following documentation for reference:
https://studio.segger.com/mkpkg.htm
https://studio.segger.com/ide_package_de…file_format.htm

Best regards,
Nino

Hello,

Thank you for your inquiry.
Such an issue is not known to us.
Do you see the same behaviour with the latest Embedded Studio v8.10d?
If yes, could you provide an example project for reproduction?

Best regards,
Nino

Hello,

Thank you for your inquiry.
Do you see the same behaviour with the latest Embedded Studio V8.10d?

If yes, could you provide a setup for reproduction that shows this behaviour?

Best regards,
Nino

Hello,

Thank you for your inquiry.
The J-Trace Pro models can't be "sidegraded" to different variants of the J-Trace Pro family.

But you can always use our trade in program to get a discount on a new one:
https://www.segger.com/purchase/trade-in-program/

We also have a new flagship model available that can do both Arm and RISC-V:
https://www.segger.com/products/debug…ls/j-trace-pro/

Best regards,
Nino

Hello,

Thank you for your inquiry.
For the SAMD51 we do not have a script available due to lack of public trace capable eval boards.
But we can provide you with the script sources for the SAME54 eval board.

As stated in the SAME54 Wiki article, please contact our support channel for this:

Quote from Wiki

Note: The example is shipped with a compiled .JLinkScriptfile, should you need the original source, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
To create your own .JLinkScriptfile you can use the following guide as reference: How_to_configure_JLinkScript_files_to_enable_tracing

Also they are not more or less the same, they should be identical from trace perspective which is why the SAMD51 is referencing the SAME54 example project.
We recommend to give the SAME54 pex file from the example project a try. Trace should work out of the box. Should you be using a different trace pin config than the eval board does we can provide you with the script source for adaptation as mentioned above.

Best regards,
Nino

Hello,

Thank you for your inquiry.
Please note that this is a community forum, you appear to have a new J-Trace Pro which is in valid support period. In that case we recommend to contact us via our official support channels as explained in my signature as answers are not guaranteed in our community forum.

Generally regarding your inquiry. The Nucleo Boards typically do not support pin tracing out of the box as they do not have a trace header. But on some of the larger Nucleo boards the trace pins are routed to the outer sockets so you could try flying wires (see the board manual for more info), however for proper testing of pin tracing we recommend to use a proper trace header to avoid having to troubleshoot unstable flying wires.

To get started quickly we recommend to use the Cortex-M Trace Reference Board that you got with your J-Trace Pro so you can try out the trace features immediately and get a feeling for it as the same features will be available for the STM32H723:
https://www.segger.com/products/devel…trace-tutorial/

We also have a STM32H7 trace reference board which can be purchased or used as design refrence for own trace capable boards:
https://www.segger.com/products/debug…reference-board

The H7 series also has an embedded trace buffer. So to try out that feature you do not even need trace pins. Simply get any example project for the Nucleo Board from any Toolchain and simply debug it with Ozone:
https://www.segger.com/products/devel…-link-debugger/

Then in Ozone under Tools->Trace Settings->Trace Source, select Trace Buffer.

Now you should see some trace data once the target device is halted.
However the amount of information is limited by the buffer size.
For more information about the different trace types see here:
https://wiki.segger.com/General_information_about_tracing

For pin tracing you will have to somehow connect your boards trace pins to the J-Trace Pro and add a J-Link Script file to your setup which initializes the trace pins and clock:
https://wiki.segger.com/How_to_configu…_enable_tracing

We can send you the STM32H743 script source for reference if you want. For that please open a ticket via our support system as explained in my signature.

If you are interested in some of our embedded software components we could also see if a BSP could be created as baseline:
https://www.segger.com/products/rtos-embedded-software/

Let us know if this would be of interest to you.

Best regards,
Nino

Hello,

Thank you for your inquiry.

It is expected that in trace buffer mode you will only see a small fraction of code in the timeline as the buffer is usually only ~4 kB in size. Also there are no timestamps in buffer trace available.
With pin tracing you get timestamps and can do the analysis you mentioned to see how long which thread took etc. Just make sure to enable RTOS awareness in Ozone. For more information see the Ozone manual.
Also make sure that you set the correct CPU Frequency in Ozone trace settings under Tools->Trace Settings->CPU Frequency. Otherwise the timline will be inaccurate.

Quote from GokhanAkkaya

Also, when I set the trace source as trace pins, I saw nothing in timeline windows which I set the related pins for tracing in board.

Here is an example project for the mentioned eval board:
https://wiki.segger.com/Renesas_RA6M5#…Renesas_R7FA6M5

Does pin tracing work if you use this example project?
If yes, simply reuse the pex file from the example in your own custom setup. The pex file will handle all trace related settings that are necessary for pin tracing to work on this chip.

Quote from GokhanAkkaya

I only see that kind of outputs which took only 900 microsec yet I want to see is it in real time.

The timeline is only generated when the target is halted as the incoming data stream is simply to fast to be displayed in real time.

If you require live performance analysis tools that can measure code execution time we recommend to use software tracing e.g. with SystemView:
https://www.segger.com/products/devel…ols/systemview/
Here less data is transferred so you can display the timeline live.

Best regards,
Nino

Hello,

Thank you for your inquiry.
External memory support for ST-Link is currently not available in Embedded Studio.
But it is on our feature wishlist.

To get notified automatically when the feature gets available you can subscribe here:
https://www.segger.com/notification/subscribe.php?prodid=196

Best regards,
Nino