• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1183 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSv6 C6472 stairstep example - cant get system analyzer output from DSP

Eddie3909
Guru 10385 points
Other Parts Discussed in Thread: SYSBIOS

Hi

CCSv6.0.0.00190, ti.platforms.evm6472, stairstep example, System Analyzer 1.4.0.6, CGT 7.4.8, XDX 3.25.5.94, SYS/BIOS 6.37.2.27, XDS560v2 spectrum digital.

The .cfg is unmodified and states that its defaulted to the UploadMode_JTAGSTOPMODE mode. I built the project and loaded it on core 0, ran it, set breakpoints, and I believe its doing example code is stated to do in 

http://processors.wiki.ti.com/images/7/7b/MCSA1.1_Getting_Started_Guide.pdf

I've stopped the core and go to Tools -> RTOS Analyzer -> Print and Error Logs and then the window pops up saying it "Cannot Determine" the instrumentation status

I clicked on the "Cannot Determine" and got the following

I selected OK and then Start. I then get 

After clicking OK, CCS opens up a new window with Live Session and Printf Logs tabs. Both do not contain any data.

The .cfg is attached.1581.stairstep_JTAGStopMode.cfg

Complete project attached.

7418.CCSv6_stairstepJtagStopMode.zip

So what am I doing wrong? Its an example project straight from TI's example repository loaded via the wizard. 

Is there something I must do to my ccxml emulator configuration file to make this work?

In CCSv4, the messageQue example output print logs straight out of the box. I tried CCSv6's messageQue example also but get the same "Cannot Determine" error.

Cheers2u

  • 0
    TI__Guru**** 171349 points

    Hi,

    I don't have the same board as you, but I tested it with a C6474EVM and got the exact same messages/dialog boxes as you - although in my case I got Printf data correctly.

     

    These dialogs/messages are a non-issue, in the sense they only indicate the UIA component installed with CCSv6 (1.40. 0.6) is not able to detect the capabilities of the standalone SYSBIOS/XDC components. I will verify when a standalone UIA 2.x will be available.

    The real issue in your case is the fact you are not able to get data out. I will check what types of logs can be obtained to further debug this. In the meantime, I strongly suggest following the troubleshooting procedures of the sections General IDE and Debugger of the CCSv6 Troubleshooting page.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Guru 10385 points

    Thanks Rafael

    I'll review the link you sent.

    Cheers

  • 0 in reply to Eddie3909
    TI__Guru**** 171349 points

    Eddie,

    One detail that one of the developers caught was the fact your first screenshot is indicating you are using UDP as the transport mechanism. Mine shows as Stop-mode JTAG:

    I checked and you could take a quick look at the configuration settings of the LoggingSetup component of your .cfg file. Mine is set to JTAG Stop Mode

    That said, I have no idea how the setting have changed in your .cfg file.

    Give these a try and see if that helps.

    Cheers,

    Rafael

     

  • 0 in reply to desouza
    Guru 10385 points

    Hi

    I shut down CCS, power cycled the evm and only loaded the staircase example. I could get print logs! Yay!

    I think what happened was I had previously loaded the messageQue example on all cores. That example is thinking its NDK even though I set 

    LoggingSetup.eventUploadMode = LoggingSetup.UploadMode_JTAGSTOPMODE;

    I had changed it to run UploadMode_JTAGSTOPMODE as you have shown above in your screen shot, but the presence of the following .cfg text makes the system want to use UDP. Strange.

    var ServiceMgr = xdc.useModule('ti.uia.runtime.ServiceMgr');
    ServiceMgr.topology = ServiceMgr.Topology_MULTICORE;

    /* The application is using the UIA benchmark events. */
    var UIABenchmark = xdc.useModule('ti.uia.events.UIABenchmark');

    var NdkConfig = xdc.loadPackage('ti.ndk.config');
    var Global = xdc.useModule('ti.ndk.config.Global');
    var Ip = xdc.useModule('ti.ndk.config.Ip');
    var Udp = xdc.useModule('ti.ndk.config.Udp');

    Ip.dhcpClientMode = Ip.CIS_FLG_IFIDXVALID;

    var ndkdrivers = xdc.loadPackage('ti.uia.examples.evm6472.ndkdrivers');

    b.t.w. CCS hung during the build after I removed the above NDK .cfg items. I had to restart it to finish the build.

    logs attached. 5822.CCSv6_crashWhileBuildingMessageQueExample.zip