CCS/SM320F28335-HT: Invalid UIA Configuration, EventTransport Undefined

1.) Device is the SM320F28335-HT.  

2.) No, I cannot see log records in ROV, but I do see 6885 dropped events for the custom logger.

3.)  Notice the Transport column is empty, I'm reasonably confident this is the problem.

This message occurs after I click past the "Unable to determine instrumentation" popup.

4.) If I close the message, UIA does not launch.

5.) I used LoggerCircBuf because the closest User's Guide I can find to the UIA version I'm using is 1.1 (spruh43d), which mentions the only Loggers that can be used are those "that inherit from ti.uia.runtime.IUIATransfer", which are LoggerCircBuf and LoggerSM.    It also mentions that CircBuf is the default implementation of a logger so it made sense to use that one.

It may be quicker to clarify my understanding of UIA than to try and diagnose this issue from the ground up.  More current User's Guides mention multiple ways to configure a custom logger with a custom memory section, but it appears that most of these are unsupported in UIA 1.4.

Thanks, please let me know what else I can do to help.

Thanks for the explanation Todd.  I've previously gotten a UIA configuration working and I've used the Execution Graph, Load Analysis, etc.  I can do so with my application currently, but I need more memory than I have available for this application, so I'm trying to set up a logger to use some external memory (1MB SRAM) connected to my device.

 I've used the most recent System Analyzer User's Guide (spruh43f) and have the following to try and configure a LoggerStopMode to do what I'm looking for using the following in the .cfg.

/* System Analyzer (UIA) Setup */
var loggerParams = new LoggerStopMode.Params();
loggerParams.bufSection = "loggerBuf";
loggerParams.bufSize = 20480;

var logger = LoggerStopMode.create(loggerParams);
logger.instance.name = "BIOS Logger";
loggingSetup.sysbiosLogger = logger;

loggerBuf is allocated to the external SRAM I mentioned earlier.  After entering the code above I get an error (getting back to my mention of suspected compatibility issues) saying "XDC runtime error: ti.uia.runtime.LoggerStopMode.Params#1: no element named 'bufSize'    app.cfg"

The System Analyzer UG shows an example of doing this exact setup aside from using the above logger as the loadLogger instead of the sysbiosLogger.  Unfortunately, none of the other loggers look suitable for what I'm trying to do.

Thanks Todd.  I can now launch UIA.  I'm getting Load records, but nothing for SYS/BIOS logging aside from 1 dropped event.  Attached is a screenshot.

Several questions:

I took a look at this thread and found that I'm pulling in LoggerStopMode as mentioned, but I can't remove it without breaking UIA in this version.

I have the external memory allocated as a Data Section.  Does this have any sway on a UIA logger?

Also attached a screenshot of my current LoggingSetup configuration.  Does transferBufSize override the listed sysbiosLogger size?

Thanks.

You are correct.  The sysbios buffer works when placed in local memory.  The Load Logger buffer is also in local memory. 

Here is the mapfile entry for my buffer:

loggerBuf 
*          1    00208000    00005080     UNINITIALIZED
                  00208000    00005080     app_p28FP.o28FP (loggerBuf)

I can certainly see data at that location in the Memory Browser, and the binary file for the memory section from 0x208000 to 0x210000 is attached.  loggerBuf in xintf.zip

Hi Luke,

The header information (first 4 32-bit words) in the zip does not look correct. Can you compare it against when you have the log buffer in internal memory. I don't have access to a C28 right now (working remote today), but here is one for a 32-bit CortexM3. The first 4 words have information that CCS (and ROV) uses to figure out whether it is big or little endian, core id, length of buffer, etc. After those words, the Log records are encoded (e..g 0x50200300 -> a specific Log id and the length is 0x20 bytes. When you look at 0x20 bytes latter, there is another log record of 0x20 bytes. I cannot remember how much different this looks on the C28 with the 16 bit bytes. I'm hoping when you compare the internal verses external RAM, something pops up. Quick sanity check...do you do any type of memory tests on the external RAM?

Todd

Todd,

Yes, I run a quick bus test then a short pseudorandom test, all of which pass.  I'm observing data being written to external memory in the memory browser as well. 

I've moved the loggerBuf to on-chip memory and it works, screenshots attached.  First is evidence of the records.  I also included what appears to be two logger instances.  I've only set one up, and the second is unselectable in the XGConfig script.  Unsure if this is relevant or expected.

Next is the buffer in the Memory Browser.  (I'm using the entry in ROV for the BIOS Logger's "queueStartAdrs")  The headers don't look quite the same but the records work and fill out the execution graph beautifully so I assume they're as expected.

loggerBuf_onchip_mem.zip

Also attached a bin file of the capture. 

Hope this helps, I'll continue comparing internal vs external memory captures in the meantime.

17316.app.cfgSure thing.  Attached is a doctored .cfg