[SOLVED] [J-Trace] Host side buffer 64Mb

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] [J-Trace] Host side buffer 64Mb

    Hello,

    Several months ago I have asked question about J-Trace buffer:
    [SOLVED] [J-Trace] What is the maximum timeline instruction buffer?

    I got answer:


    SEGGER - Fabian wrote:

    Hi,
    Thank you for your inquiry.

    Currently we have a 64Mb buffer on Host side (for legacy reasons).
    This handling will change in the near future to be unlimited.

    Stay up-to-date regarding J-Link:
    segger.com/notification/subscribe.php?prodid=7,94

    How many instructions fit into this buffer depends on the instruction packet size (between 1-4 bytes per packet).
    This is device and application dependent.

    Best regards,
    Fabian

    Does something change so it is possible to use unlimited buffer?
  • Hello,

    Thank you for your inquiry.
    Yes there were changes. You can now dump the raw unanalyzed trace data on to your hard drive.
    wiki.segger.com/J-Link_Command_Strings#TraceFile

    However you would need to write your own analyzer for this right now.
    Ozone currently does not offer an interface where this recorded raw data could be inserted for analysis.
    But that will be possible in future.
    However as this is quite the large feature rework for us we do not have a fixed timeschedule yet when it will be available from Ozone so you get the "infinite" timeline.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello,

    the dumped format is the same frame format as described in the Arm Coresight documentation for ETM and TPIU.
    The frames then contain the different trace packet types which are described in the corresponding ETM manual.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.