Log_print0() output

Hi Valdez.

What device are you using?

Todd

Hi Todd,

I use OMAP3530 on Beagleboard.

I see in Dsp.cfg these lines:

/* create a logger instance */
var LoggerBuf = xdc.useModule('xdc.runtime.LoggerBuf');
var loggerBufP = new LoggerBuf.Params();
loggerBufP.numEntries = 128;  /* 128 entries = 4 KB of memory */
loggerBufP.bufType = LoggerBuf.BufType_FIXED;

var appLogger = LoggerBuf.create(loggerBufP);
appLogger.instance.name = "AppLog_Core1";
Defaults.common$.logger = appLogger;

But how to see that logs? Do I need JTAG connection? If yes, so it is not possible to see it outside of CCS?

Thank you for the answer. Now I have to learn how to make connection between CCS and DSP core in OMAP3530 via XDC100v2.

Dear Sir


 I have tried to get LoggerSM from UIA to work with the examples shipped with syslink
but it didn't work. When I removed all calls to Ipc and SysLink API's, everything worked
fine. I mean I just left bios tasks and calls to xdctools modules. So I did
./loggerSMDump.out 0x8D000000 0x200000 dsp
and I can see all the logs fine. This was done on BeagleBoard and overoboard both with
OMAP3530.  I am not sure whether this is a problem with the integration with syslink or
is it a configuration problem from me. I use the Notify example with syslink_2_20_00_14.
I updated bios, xdctools, ipc to the latest releases so I use

I use uia_1_01_01_14
bios_6_34_03_19
xdctools_3_23_02_47
ipc_1_24_00_16


I modified the memory map as you can see in the attached files to allocate more memory
for the logger, the shared region etc.., but that didn't make a difference. Still programs
that used bios and xdctools worked and programs that used Ipc didn't work.
I have attached the modified Dsp.cfg and the shared/config.bld
Thanks

Hazem