Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

Please accept the use of cookies on our site

At PEmicro we use web browser cookies in order to provide you with an enhanced experience and in order to be able to do things like shopping cart processing and identify you when you login to our website.

Click here to accept

search inside this forum
search inside all forums
Tracelink + CodeWarrior + ColdFire v3 can not trace
Robert g. Oct 6, 2017 at 12:29 PM (12:29 hours)
Staff: Johnny N.

  • I used the Tracelink with great results on a project involving a Kinetis Cortex-M0+ recently, controlling the trace and viewing results using CodeWarrior 10.7.  For my new project, I want to trace a ColdFire v3 in the same fashion, but the trace start/trace stop options are disabled in the Debug tab of CodeWarrior.  I can control execution in normal debugger fashion, but can not trace.  I did enable tracing in the debugger configuration, and in fact checked all checkboxes on the Trace and Profile tab in the debug config.  Can I get some help tracing the ColdFire v3?  It's supposed to be supported as I understand things.


  • The ColdFire V3 should be supported. What is the exact ColdFire processor? I'm not sure why the Start/Stop Trace button is disabled yet. 

    Do you have all the PST and DDATA signals from the processor connected to the header? All the trace information is captured through the DDATA signals so you should see lots of activity on them as you are debugging your processor.

    • I didn't design the board, but I believe the PST and DDATA signals are connected. I will double check tomorrow, and maybe get a logic analyzer hooked up to sniff the connections and see what's happening on those pins.  The chip is an MCF5307.  I noticed that the Multilink/Tracelink user guide also shows the trace function greyed out in the CodeWarrior screen shot, for whatever that's worth.

      • Checked with the logic analyzer, plenty of activity happening on the DDATA pins.  Just no option to capture it in CodeWarrior.  Please advise

        • Hi Robert,

          The unitcfz api does have functions to get the trace information but they are currently unpublished. The functions only return the raw trace data from the ColdFire processor. You would have to develop your own parser if you want to make it usable.

          The design engineer of the Tracelink is currently investigating your issue with Codewarrior. I was told that you should see trace in the Software Analysis tab as long as you enabled it in the Trace and Profile tab in debug configurations.

          The only document we have on how to write ColdFire V3 algorithms is cfp.doc that is included with your PROGCFZ software. If you open a support ticket on Support Request system, I can also provide you with the assembly source for the algorithm. You would need to have a copy of our assembler for ColdFire if you want to make your own modifications.

          If you need help picking the right algorithm we have the following sources of information:


  • I had gone off to do other things but have returned to try to trace my MCF5307 ColdFire v3 chip.  I started over with a clean CodeWarrior project and defined a new debug connector for my Tracelink.  I still can't trace, but at least now I get the following error message when I start debugging: 

    Window title: Profiler Error
    "Unexpected error while enabling Trace and Profile. Profiler is disabled for current session."

    Was the Tracelink developer you mentioned in your prior post able to discover anything? I would really rather gather traces through CodeWarrior than try to right my own parser for the raw output using UNITCFZ.


  • I have not received a response, either here or in my support request.  I am now trying to debug this on my own.

    I have downloaded CW 11.0, and get the same error.

    I have explored the logs created by CodeWarrior while it runs and have discovered the following in the codewarrior_ide_01162018_135214.log file. Any ideas what could be casuing this? I'd rather not start decompiling jar files, but I need a working Trace solution.

    "14:15:38.785 ERROR [Worker-18] Error trying to load trace configuration for coldfire_demo_RAM_PnE TraceLink. The default configuration will be loaded instead.
    14:15:38.896 ERROR [Worker-18] Could not configure trace!
       at org.eclipse.debug.internal.core.LaunchConfiguration.launch(
       at org.eclipse.debug.internal.core.LaunchConfiguration.launch(
       at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(
       at org.eclipse.debug.internal.ui.DebugUIPlugin$

Add comment

   Want to comment? Please login or create a new PEMicro account.

© 2018 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement