System analizing for Piccolo

Sabina,

I can reproduce this and will submit it as a bug to the appropriate team. In the meantime, could you try changing the RTSC platform from ti.platforms.tms320x28:TMS320F28069 to ti.platforms.control28069 and confirm that it works? This built without errors for me. After changing the platform, if the F28069.cmd linker command file gets added to the project, you would need to remove it first for the build to be successful. Let us know if this works.

Hi,

I changed the platform to ti.platforms.control28069 and removed LinkerCommand file at all. Build get the following errors:

"./configPkg/linker.cmd", line 229: error #10099-D: run placement fails for
   object ".ebss", size 0x10ff6 (page 0).  Available ranges:
   L4SARAM      size: 0x2000       unused: 0x1b14       max hole: 0x1ab8   
"./configPkg/linker.cmd", line 238: error #10099-D: run placement fails for

>> Compilation failure
   object ".ebss:taskStackSection", size 0x10206 (page 0).  Available ranges:
   L03DPSARAM   size: 0x2000       unused: 0x1000       max hole: 0x1000   
error #10010: errors encountered during linking; "SysTemAnalizerTest2.out" not
   built
gmake: *** [SysTemAnalizerTest2.out] Error 1
gmake: Target `all' not remade because of errors.

Are you using one of the UIA template examples or a project with your code? If it is the UIA examples, I believe there are still some issues when using those with C2000 which will be addressed in a future release. If it is an example you are using, let me know which one and I can try to fnd workarounds required to get it to build.

For testing I am using UIA template /Single Core Example/Stairstep_probePoint. But the purpose is to use System analizing in our appliocation

Thanks, Sabina

For the UIA template Stairstep Probepoint, please do the following changes to get the program to build:

- Open stairstep_ProbePoint.cfg and go to the cfg Script tab

- Comment out lines 47 and 48 which set Memory.defaultHeapSize and Program.heap (the heap sizes there are too large and cause the sections to not fit in memory)

- Reduce the Logging buffer sizes as below:
    LoggingSetup.loadLoggerSize = 512;
    LoggingSetup.mainLoggerSize = 1024;
    LoggingSetup.sysbiosLoggerSize = 1024;

- Change the allocation of .stack to a different memory region as it does not fit in previously allocated region by adding the following line:
    Program.sectMap[".stack"] = "L56DPSARAM";

This should allow the program to build and hopefully run as expected. Sorry that these do not work out of the box. We are working on this and hope to have all these UIA templates fixed up and working well with C2000 in upcoming BIOS/XDC updates.

Hi,

Now it is building properly an I managed to run system analysing! thanks.
But I see only Live Session log and  see nothing in all analyzing options: grap, CPU Load, Task Load,...

How to run system analyzing in our Piccolo application? Have we do the same changes as in the example?

Thanks,Sabina

Sabina,

Have you tried the Stairstep JTAG StopMode example under UIA templates? If not, could you give it a try? 

I just built this example, after making the changes to .cfg posted previously, and tested it on a F28069 experimenter kit. I was able to see data in Live Session: Logs as well as the CPU load, execution graphs get updated when the program is halted.

To add System Analyzer support to your custom application, the main things to check are:
-  LoggingSetup module is enabled in your BIOS .cfg and has sufficient buffer sizes for logging (you can see how it is setup in the stairstep example as a reference) (see screenshot below for where to find this)
-  the appropriate Event Upload Mode is set (C2000 supports JTAG RunMode in addtion to Stopmode)
- System Analyzer or MCU SDK is enabled in Project Properties->RTSC tab

I also noticed in your other thread that you are using CCS 5.1.1 and MCU SDK 1.0.0.68. Did you install UIA updates over this CCS to get more recent versions?  I believe System Analyzer on C2000 has become much better in more recent versions, so I would highly advise updating to CCS 5.3.0 and MCU SDK 1.0.01.74.

Hi,

I run Stairstep JTAG StopMode example in our configuration 5.1.1 and checked all iAnalysisFeature options in LiveParameters window:

My config file is:

I Pressed Start, and after it run StairStep and Suspend it after number of seconds.
All analizys tabs are empty.

If I marked only TaskLoad line(in  LiveParameters window) , press on Start, I get the following question:
"Do you want to enable realtime mode?
Can't enter realtime mode unless debug events are enabled.
Bit 1 of ST1 must be 0." Answer  'Yes' , and run a StairStep for number of seconds.

Here I get 'live Session Logs" window with a lot of events , but all other tabs empty.

pls let me know what configuration give to see information in other tabs also. I didn't succeed to do it.

Thanks, Sabina

Sabina,

I remember seeing the realtime mode messages in earlier versions of CCS, amd maybe changes, bug fixes and improvements have been made since then. I think it would be best to first update your version of CCS to 5.3 and give it a try, and let us know if you continue to have problems.

Hi,

I installed newest ver CCS ver 5.3.0. now situation is a little bit better. I see Live session log always, but see nothing in other windows: CPU load graph, Count Analizys, Execution graph ,  Task profiler,... all of them are empty.

Do you have an example that show all windows? Could you pls send me it. Maybe I do something wrong...

Thanks, Sabina

Sabina,

I've zipped up and attached the project folder here so you can load and try out the same code.

After loading the code to target (I simply clicked the green bug button to build and load the code), I went to menu Tools->System Analyzer->Live, and enabled the check boxes for "CPU Load" and "Execution Graph", and clicked Start. Then I ran the program and halted after several seconds. I did this a few times and noticed the CPU Load graph and Execution graph being updated as expected. I have attached a screenshot along with the zip file.

0677.f28069_stairstep_stopmode.zip

I am getting the same error about locked file trying generate project on 28335 I have custom hardware as well as experimenters kit.

I picked the JTAG staircase example I will follow the suggestions and transpose to 28335 was this resolved ?

I am unable to get past the linker error work around step for the stack I used Program.sectMap[".stack"] = "L47SARAM";

Also do you recommend I use CCS5.3 as well for C2000 i HAVE Code Composer Studio Version: 5.2.1.00018?

"./stairstep.obj" -l"libc.a"
<Linking>
"./configPkg/linker.cmd", line 217: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".text" size 0x415a page 0.  Available memory ranges:
   L47SARAM     size: 0x4000       unused: 0x0          max hole: 0x0      
"./configPkg/linker.cmd", line 223: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".econst" size 0x24c8 page 0.  Available memory ranges:
   L47SARAM     size: 0x4000       unused: 0x0          max hole: 0x0      
"./configPkg/linker.cmd", line 225: error #10099-D: program will not fit into available memory.  run placement with alignment/blocking fails for section ".stack" size 0x1000 page 0.  Available memory ranges:
   L47SARAM     size: 0x4000       unused: 0x0          max hole: 0x0      
"./configPkg/linker.cmd", line 220: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".cinit" size 0x5d9 page 0.  Available memory ranges:

   L47SARAM     size: 0x4000       unused: 0x0          max hole: 0x0      
"./configPkg/linker.cmd", line 232: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".text:.bootCodeSection" size 0x1c9 page 0.  Available memory ranges:
   L47SARAM     size: 0x4000       unused: 0x0          max hole: 0x0      
"./configPkg/linker.cmd", line 218: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".switch" size 0x39 page 0.  Available memory ranges:
>> Compilation failure
   L47SARAM     size: 0x4000       unused: 0x0          max hole: 0x0      
error #10010: errors encountered during linking; "test.out" not built

mark lazarewicz1 said:

I am unable to get past the linker error work around step for the stack I used Program.sectMap[".stack"] = "L47SARAM";

Also do you recommend I use CCS5.3 as well for C2000 i HAVE Code Composer Studio Version: 5.2.1.00018?

These errors will be fixed in CCS 5.4. I expect beta releases of this version will be available soon. Rather than trying to work around the errors in CCS 5.3 or earlier I would highly recommend waiting for a beta version of CCS 5.4 and give that a try when it comes out. When it is ready it should be posted to this wiki page: http://processors.wiki.ti.com/index.php/Download_CCS

I am sorry I was not clear. the question had 2 parts

the first part was

1) for c28335 is 5.3 a highly suggested update?? I saw it had better flash handling and betterc2000 support we are writing a boot loader

2) This UIA issue can wait till later our system is simple at the moment.

we will have additional RAM on our custom board and if the linker error is RAM related not flash related then we probally do not care

My intent was to understand  what we have available for insight into SYBIOS using JTAG and UIA as our system gets more complex in the coming months we will need this

mark lazarewicz1 said:

1) for c28335 is 5.3 a highly suggested update??

Yes, whenever possible it is definitely recommended to update to the latest version (at this point CCS 5.3) as it will have several bug fixes and improvements.

I would suggest if you plan to use SYS/BIOS and UIA in the coming months as you move forward, then start with CCS 5.3 and move to CCS 5.4 when it is released in 2Q.