Build problems following UIA upgrade to 2.x

Hi Vasili,

This looks like a bug that was introduced in UIA 2.0.  I will try to get a fixed LogSnapshot__epilogue.h file that you can try out.

Thanks,

    Janet

Hi Janet,

1. Thank you! I've tried the file you provided. Indeed, it fixes the build.
2. However, it does not provide a complete functionality fix. As far as I know. the System Analyzer does ti.uia.events.UIASnapshot.nameOfReference. You can find more info about it here:
   http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/331559/1161814.aspx#1161814

Best,
Vasili

Sounds great. I'm waiting to see it :-)
Any info when CCS6.1 release is planned?

Best,
Vasili

Hi Vasili,

I found this: http://processors.wiki.ti.com/index.php/TI_Development_Tools_Information which says CCS6.1 should be available in Feb 2015.

Best regards,

    Janet

Hi

I'm using CCS 6.1.2.00015 with UIA 2.0.3.43, so in theory the System Analyzer should display the task names that I provide using LogSnapshot_writeNameOfReference . Unfortunately, it does not.

I had a look at LogSnapshot__epilogue.h and found a few things that I thought looked suspicious:

1. the macro ti_uia_runtime_LogSnapshot_writeNameOfReference is defined in terms of LogSnapshot_writeStringWithIdTag, which in turn seems to post a log message of type UIASnapshot_stringOnHeap (instead of UIASnapshot_nameOfReference, which I expected).
2. the refId parameter is used as the first argument to writeStringWithIdTag while all other log message types call the parameter snapshotId and use it as the second argument.
3. the XYZWithIdTag macros all look suspicious

For example, ti_uia_runtime_LogSnapshot_writeStringWithIdTag is defined as follows:

#define ti_uia_runtime_LogSnapshot_writeStringWithIdTag(idTag, snapshotId, fmt, startAdrs, lengthInMAUs) \
    ((ti_uia_runtime_LogSnapshot_isSnapshotLoggingEnabled(ti_uia_events_UIASnapshot_stringOnHeap)) ? \
        (ti_uia_runtime_LogSnapshot_putMemoryRange(ti_uia_events_UIASnapshot_stringOnHeap, Module__MID, \
        (IArg)((((UInt32)idTag & (UInt32)LogSnapshot_IDTAG_MASK) << LogSnapshot_IDTAG_BIT_SHIFT) | \
        ((((UInt32)snapshotId) & (UInt32)LogSnapshot_SNAPSHOTID_MASK)<<LogSnapshot_SNAPSHOTID_BIT_SHIFT)),\
        (IArg)__FILE__,(IArg)__LINE__, (IArg)fmt, (IArg)startAdrs, (IArg)lengthInMAUs)) : (Void)0 \
    )

The problem is that LogSnapshot_IDTAG_MASK is defined as 0xFFFF0000 and LogSnapshot_IDTAG_BIT_SHIFT is defined as 16. Therefore, all information contained in idTag is discarded. I have no idea what the idTag and snapshotId parameters are supposed to do, but their current use doesn't look right to me.

Now I looked at an old UIA 1.x file, tried to find out what exactly LogSnapshot_writeNameOfReference SHOULD do, and came up with the following implementation (pure guesswork):

#define ti_uia_runtime_LogSnapshot_writeNameOfReferenceWithIdTag(idTag, snapshotId, fmt, startAdrs, lengthInMAUs) \
    ((ti_uia_runtime_LogSnapshot_isSnapshotLoggingEnabled(ti_uia_events_UIASnapshot_nameOfReference)) ? \
        (ti_uia_runtime_LogSnapshot_putMemoryRange(ti_uia_events_UIASnapshot_nameOfReference, Module__MID, \
        (IArg)((((UInt32)idTag & (UInt32)LogSnapshot_IDTAG_MASK)) | \
        ((((UInt32)snapshotId) & (UInt32)LogSnapshot_SNAPSHOTID_MASK))),\
        (IArg)__FILE__,(IArg)__LINE__, (IArg)fmt, (IArg)startAdrs, (IArg)lengthInMAUs)) : (Void)0 \
    )

/*
 *  ======== ti_uia_runtime_LogSnapshot_writeNameOfReference ========
 *  Log_Events need to be converted to Type_Events prior to calling Log_put;
 *  the lower 16-bits are a mask that needs to be replaced with the caller's
 *  module ID.
 */

#define ti_uia_runtime_LogSnapshot_writeNameOfReference(refId, fmt, startAdrs, lengthInMAUs) \
 (ti_uia_runtime_LogSnapshot_writeNameOfReferenceWithIdTag(refId, refId, fmt, startAdrs, lengthInMAUs))

I am using refId for both parameters so that the full 32 bits value will be reassembled (consistent with UIA 1.x).

Now I absolutely don't know what the parameters mean and how they are supposed to be used, all I can say is that this fixed the System Analyzer view and that all my task names are shown correctly.

Could somebody who knows more about the inner workings of UIA please have a look at that?

Regards

Markus

Hi Markus,

Since this thread is marked as resolved, could you please post a new thread indicating the problem you are having and what device you are using?  I will take a look at it.

Best regards,

    Janet

Hi Janet,

I opened a new thread (e2e.ti.com/.../493051)

Markus