[SOLVED] Unable to detect trace with J-Trace pro - STM32F7

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

  • [SOLVED] Unable to detect trace with J-Trace pro - STM32F7

    Hi.
    I'm unable to get data from the trace lines (4 bit) using J-tarce pro.
    The target IC is STM32F767IIT on a self developed board.
    In the trace status at the JLinkGDBServer I get:

    Trace clock:108 kHz
    Half-sync detection:0x00000000 (Not O.K. no half-sync pattern detected)
    Last incorrect half-sync sampled:0x00000000



    When connecting an IAR I-jet to the target (same HW, same Software running) - it works fine.
    Is this a J-Trace configuration issue?


    Thanks
    Sivan.
  • Hello Sivan,

    Thank you for your inquiry.
    Are you using custom hardware or an eval board?
    Which pins are you using for traiceing?
    According to the provided information the trace pins seem not be be initialized properly.
    For reference you can use the following example project. wiki.segger.com/Tracing_on_ST_STM32F767
    It will configure 1-bit trace for a STM32F767. 1- bit only because with the Nucleo eval board only a flying wire setup was possible as no trace port was available but 4-bit trace should work just as well.
    In the example project you will find a JLinkScript file which can be modified to use 4- bit trace.

    Does the example project work on your board with J-Trace?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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.
  • Hi,
    Enclosed the trace Pinout of the target board I use.
    <img src="C:\Users\sivan\Desktop\tmp\2018-02-08 13_58_47-OrCAD Capture CIS - [_CPU - (2-CPU _ CPU)].png" alt="C:\Users\sivan\Desktop\tmp\2018-02-08 13_58_47-OrCAD Capture CIS - [_CPU - (2-CPU _ CPU)].png" title="C:\Users\sivan\Desktop\tmp\2018-02-08 13_58_47-OrCAD Capture CIS - [_CPU - (2-CPU _ CPU)].png" style="font-size: 0.8em;" />



    The nets are corrected by a customized harness- again, it works with the J-trace device.
    Images
    • 2018-02-08 13_58_47-OrCAD Capture CIS - [_CPU - (2-CPU _ CPU)].png

      32.2 kB, 1,014×317, viewed 328 times
  • Hello,

    The picture you tried to attach did not reach the forum. To upload pictures use the "Attachments" tab under the reply text editor.
    The nets are corrected by a customized harness- again, it works with the J-trace device.

    So it works now?
    Does it work with the reference project from our wiki?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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.
  • Hi Nino,
    We have tried the project as you've suggested - and it's working with the Ozone environment.
    But we currently work with IAR design environment .

    Please help to configure the J-Trace to work with the IAR and display a 4- bit Trace.

    BR,
    Sivan.
  • Hello Sivan,

    Great to hear that trace is working with Ozone for you.
    To enable 4-bit trace in Ozone simply edit the JLinkScript in the example project and set JLINK_TRACE_PortWidth to 4.
    Also make sure you use the same GPIOs for tracing as the example script. Should you be using other pins adjust the script accordingly.

    IAR trace support is not handled by us. Please get into contact with IAR for that.
    But generally it should be enough to define the JLinkScript with the Trace pin init for IAR and you should be good to go.
    wiki.segger.com/Using_J-Link_Script_Files

    For the best trace experience we suggest using Ozone as this is the only debug software that supports all J-Trace PRO features. No other debug software does that.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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.