• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 395 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.

CCSv4: why is loggerBuf instance taking so much memory?

Eddie3909
Guru 10385 points
Other Parts Discussed in Thread: SYSBIOS

Hi

CCSv4.2.1

CGT 7.0.4

BIOS 6.30.03.46

XDCTools 3.20.07.86

We have instantiated a 4096 entry LoggerBuf in our system and our .map file shows a huge memory section allocated below.

00810020   _xdc_runtime_LoggerBuf_Instance_State_0_entryArr__A
00810820   _xdc_runtime_LoggerBuf_Instance_State_1_entryArr__A
00830820   _xdc_runtime_LoggerBuf_Instance_State_2_entryArr__A

It seems to be allocating 0x2000 bytes (128k Bytes) for whatever LoggerBuf Instance State-1 is. Any ideas on how we can reduce state 1 size?

(or maybe 1 entry in the logger buffer is 128k/4k = 32 bytes? - in which case I simply have to set instLoggerBuf0Params0.numEntries smaller).

Also

- The ti.sysbios.rta.Agent configureSystemLog and configureLoadLog are set to false.

- All diagnostics in xdc.runtime.Defaults are set to ALWAYS_OFF and the logger is set to null.

Cheers

 

 

  • 0
    TI__Expert 4125 points

    The numEntries config parameter specifies the number of Log events/entries, each of which is 8 32-bit words, or 32 bytes. So, the units of numEntries is "events/entries" and not bytes. See

    http://rtsc.eclipse.org/cdoc-tip/xdc/runtime/LoggerBuf.html#.Basic.View 

    and

    http://rtsc.eclipse.org/cdoc-tip/xdc/runtime/Log.html#.Event.Rec

    Mark

  • 0 in reply to MarkGrosen
    Guru 10385 points

    Thanks for the links. It also looks like I can change the location by using

    var params = new LoggerBuf.Params;

    params.bufSection = String null;

    (http://rtsc.eclipse.org/cdoc-tip/xdc/runtime/LoggerBuf.html#.Basic.View)

    Cheers