System_Printf() Messages Don't Show Up Until Execution Stops - CCS4

Hi Ed,

Are you making System_printf calls from Hwis or Swis? If you are not, you can use SysStd. The following three lines in your .cfg will make the change (and deleted the SysMin ones).

    var System = xdc.useModule('xdc.runtime.System');

    var SysStd = xdc.useModule('xdc.runtime.SysStd');

    System.SupportProxy = SysStd;

Todd

I'm using the clock example code that can be chosen under Sys Bios as an example when you create a project.  I did not create this code.  It's the built-in example code.  The System_printf() calls are within the clk0Fxn() routine that is called as a result of a system timer going off.  I added the lines you mention, above, to the bottom of the clock.cfg file, and commented out my calls to System_flush() in the clock.c file, but I still get the same error message, "ti.sysbios.gates.GateMutex: line 114: assertion failure: A_badContext: bad calling contet. See GateMutex API for details. xdc.runtime.Error.raise: terminating execution" when I run the code in debug mode in CCS4.

Which version of SYS/BIOS are you using?

I'm running Code Composer Studio 4.2.3.0004.  I downloaded and installed it LAST WEEK. It's using sys bios 6_32_04_07.

Ed --

I recommend using SysMin.

Note that System_flush() internally calls C runtime library code that needs a mutex.   So, you need to make sure that your call to System_flush() is done from Task level.  You can create a Task that simply has a loop like this:

for (;;) { 
    System_flush();
    Task_sleep(1000);  /* 1 second if 1ms tick */
}

You can also use the ROV tool (available from Tools->ROV menu) to look at SysMin buffer for every breakpoint.

Please send BIOS version and your updated .cfg and .c files.

-Karl-

The ROV tool view DOES NOT WORK! Under ROV, one can click on SysMin and then the tab Output Buffer and even click the little yellow "refresh" icon while the DSP program is running, but nothing appears in the windows except the little "task running" icon until the DSP target is either halted due to a breakpoint or it calls BIOS_exit().

In this clock example, where would I place that call to System_flush()?

And what header file do I need to include in order to get Task_sleep().  I tried adding "#include <ti/sysbios/knl/Task.h>" but I received dozens of error messages about symbols being redefined, whenever I have a call to Task_sleep() included anywhere in the clock.c file.

I have ATTEMPTED TO attached the clock.c and clock.cfg files.  This clock.cfg file is the unedited file directly from the example.  The clock.c file is from the example, but I have lengthened the timers a bit so that it is obvious that the System_printf()s don't display until after the terminating call to the bios.  i WAS NOT ABLE TO ATTACH THE FILES.  HERE IS THE ERROR I GET FROM YOUR ATTACH FILES TOOL when I attempt to attach either the clock.c or clock.cfg file:

Strangely enough, I was able to attach the image of the error message!

How would you suggest that I upload the clock.c and clock.cfg files to you?  You can get them directly from the example in CCS4.  The only change I made was to add three zeros to the  time values for the periodic timer and the one-shot.

Ed Boakes said:

I'm running Code Composer Studio 4.2.3.0004.  I downloaded and installed it LAST WEEK. It's using sys bios 6_32_04_07.

This version doesn't match any BIOS releases.  Can you please confirm your BIOS version?  Also, which device are you running on?

You can zip up the 2 files and attach as a .zip.  The attach tool allows .zip files.  Not sure why it filters others.

The latest version of the examples use SysMin by default.   The problem with the Clock example is that it doesn't have any easy place to put this call to System_flush().  System_flush() calls into the RTS library and need to acquire a mutex which is not allowed from Thread level.

I've attached updated clock.c and clock.cfg files where I added a Task that calls System_flush() every second.

2818.clock-with-flush.zip

-Karl-

Karl,

Thanks for these files.  This certainly improves things.  

The BIOS version is 6_31_04_07.  Sorry, but I mis-typed the "31" in my previous posting.  

What's particularly frustrating, is that when I had had CCS 4.2.1 installed, the clock example's System_printf()s did appear very shortly after calling them.  No System_flush() or BIOS_exit() was necessary.  Due to a different issue, I updated to CCS 4.2.3.  Since the updating process produced a lengthy list of error and warning messages, I removed the entirety of all TI tools on my PC, then downloaded (on May 11, 2011) and installed CCS4.  Would you happen to know what changed in the BIOS?  Aside from again deleting my entire CCS4 and all associated tools and re-installing from my January 4, 2011 download, how would I restore the earlier behavior?

Ed