This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR6843ISK: PC Trace Analyzer, IWR6843ISK, XDS110

Part Number: IWR6843ISK

Dear E2E Team,

I have a question about the PC Trace Analyzer.

Is it possible to use the PC Trace Analyzer.

I always get an error message. ID not found. What am I doing wrong?

I use the following components: IWR6843ISK, MMWave IC Booster (XDS110), CCS v10.

Regards

Gerhard

  • Hi Alec,

    I have read the thread and tried many things, but I had no success.

    I kept getting the following error messages.

    As described in the thread, it is possible to get PC-Trades from DSP C674X. I didn't succeed there.

    Unfortunately, many settings are not visible, such as the target configuration, initialization script xxx.gel, etc.

    I hope you can give me more information.

    Regards

    Gerhard

  • Hi Gerhard,

    Since this tool has not had any active development on it for the past few years, I do not think there is much info on it available beyond what is in the User Guide. The two cores should be usable with this trace tool, but some configuration may still be required. I will link the guide below in case you have not yet gone through it.

    https://www.ti.com/lit/ug/spruhm7b/spruhm7b.pdf

    Best Regards,
    Alec

  • Hello Alex,

    I know the document.

    What I don't understand is that the RTOS Analyzer -> Exection Analyzer works for me.

    See the following pictures.

    Only the hardware trace analyzer does not work!

    With the error as above in the  thread.

    Attached is the mss_mmw.cfg file.

    Perhaps the error is here? Can you help me ?

    Kind regards Gerhard

    mss_mmw.cfg

    /*
     *  Copyright 2011 by Texas Instruments Incorporated.
     *
     *  All rights reserved. Property of Texas Instruments Incorporated.
     *  Restricted rights to use, duplicate or disclose this code are
     *  granted through contract.
     *
     */
    environment['xdc.cfg.check.fatal'] = 'false';
    
    /********************************************************************
     ************************** BIOS Modules ****************************
     ********************************************************************/
    var Memory    = xdc.useModule('xdc.runtime.Memory');
    var BIOS      = xdc.useModule('ti.sysbios.BIOS');
    var HeapMem   = xdc.useModule('ti.sysbios.heaps.HeapMem');
    var HeapBuf   = xdc.useModule('ti.sysbios.heaps.HeapBuf');
    var Task      = xdc.useModule('ti.sysbios.knl.Task');
    var Idle      = xdc.useModule('ti.sysbios.knl.Idle');
    var SEM       = xdc.useModule('ti.sysbios.knl.Semaphore');
    var Event     = xdc.useModule('ti.sysbios.knl.Event');
    var Hwi       = xdc.useModule('ti.sysbios.family.arm.v7r.vim.Hwi');
    var System    = xdc.useModule('xdc.runtime.System');
    var SysStd    = xdc.useModule('xdc.runtime.SysStd');
    var clock     = xdc.useModule('ti.sysbios.knl.Clock');
    var Pmu       = xdc.useModule('ti.sysbios.family.arm.v7a.Pmu');
    //var LoggerMin = xdc.useModule('ti.uia.loggers.LoggerMin');  // GSH auskomentiert
    var LoggingSetup = xdc.useModule('ti.uia.sysbios.LoggingSetup'); // GSH eingeben
    var LoggerStopMode = xdc.useModule('ti.uia.loggers.LoggerStopMode');
    System.SupportProxy = SysStd;
    
    /* FIQ Stack Usage: */
    Hwi.fiqStackSize                = 4096;
    Hwi.fiqStackSection            = ".myFiqStack"
    Program.sectMap[".myFiqStack"] = "DATA_RAM";
    
    /* Default Heap Creation: Local L2 memory */
    var heapMemParams           = new HeapMem.Params();
    heapMemParams.size          = 64*1024;
    heapMemParams.sectionName   = "systemHeap";
    Program.global.heap0        = HeapMem.create(heapMemParams);
    Memory.defaultHeapInstance  = Program.global.heap0;
    
    /* Enable BIOS Task Scheduler */
    BIOS.taskEnabled			= true;
    
    Program.sectMap[".vecs"]	= "VECTORS";
    
    /* Make sure libraries are built with 32-bit enum types to be compatible with DSP enum types*/
    BIOS.includeXdcRuntime  = true;
    BIOS.libType            = BIOS.LibType_Custom;
    BIOS.customCCOpts      += " --enum_type=int ";
    LoggingSetup.loggerType = LoggingSetup.LoggerType_STOPMODE;
    LoggingSetup.loadLogging = false;
    
    

     

    Execution Graph

  • Hi, 

    When you try to run the tool, have you already set the device up for CCS debug, flashed the CCS debug image, and loaded your custom image onto the device?

    Best Regards,
    Alec

  • Hello Alec,

    I am using the IWR6843ISK with mmWave IC Booster (XDS110), CCS v10.

    I flash the IWR6843ISK with the ccsdebug.bin file using Uniflasher.

    Then I connect CCSv10 to the IWR68431ISK and start the debug.

    See PDF attachment for instructions.

    Then I start the High_Accuracy_Visualizer 1.2.0 to send the .cfg data.

    Best regards

    Gerhard

    Using CCS Debug for Development.pdf

  • Gerhard, 

    Just to be clear, the demo functions properly and you are able to debug it normally, and everything works as expected until you try to use the trace tool, correct?

    Best Regards,
    Alec

  • Hello Alec,

    yes, right.

    Best Regards

    Gerhard

  • Gerhard,

    I have done some testing on my side and see similar behavior to what you have seen. I definitely believe the issue is related to the GEL files utilized by the target configuration, but i'm afraid that I do not have much additional insight to provide since support for this tool has been discontinued for a couple of years now. Based on feedback provided in the other thread that we previously discussed, I believe this to be possible, but in that instance the user found the resolution themselves and did not share it on the forums. Let me know if you make any progress or have any other questions related to the device.

    Best Regards,
    Alec