[SOLVED] SWO Trace not working after upgrade

  • [SOLVED] SWO Trace not working after upgrade

    Hi,
    I'm using the j-link base for programming/debugging an EFR32MG13P in IAR 8.22. My j-link driver and software were updated during the IAR 8 installation. I'm now using J-Link V6.30. Ever since that upgrade I have not been able to use SWO Trace or the Timeline feature. Is this a problem with the j-link software? Is there an update? Thanks for any help and let me know if I can provide any more information.

    Best,
    Steve

  • Hello Steve,

    Thank you for your inquiry.
    Such an issue is not known to us.
    Which was the last J-Link software version and IAR version working?
    What are the differences between your old project settings and the new ones, specifically regarding the SWO and CPU clock speed settings?

    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,
    Thanks for your response. Previously I was using IAR 7.80.3, but have used many prior versions. Also I have been using J-Link 6.12, and before that 6.10. The microcontroller is also new (to me), it's the EFR32MG13P. Previously I had been using the EFR32MG1P and EFM32WG.

    I'm not aware of any changes to the SWO configuration. I've attached a screenshot to show the current SWO and J-Link configurations. I've messed with the clock speed config a little to try to get this working, but to no luck. Any advice is appreciated.

    Best,
    Steve

  • Hello Steve,

    Most SiLabs devices (including the EFR32MG13P) have an extra peripheral clock for SWO and other trace clocks.
    It is called AUXHFRCO. Usually the SWO clock = CPU clock, but for some special targets as this one it is some other unrelated clock which needs to be taken into account with its different speed.
    In your case you need to find out the clock speed of the AUXHFRCO on your target and insert it in the "SWO COnfiguration" window in IAR by selecting "override project default" and setting the correct "CPU clock" which here is the AUXHFRCO clock speed and not the actual clock speed.

    For the SWO clock we suggest using autodetect if possible.

    If these settings are correct SWO should work again as before.
    We assume that IAR has changed some default behaviour here which is why it seems to no longer be working.

    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.

  • Hello Steve,

    great to hear that you are up and running again.
    We will see if we can add an example project for SiLabs devices on our Wiki for future inquires about this issue.
    This thread will now be marked as solved.

    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.