TI E2E Community
it seems to be so obvious that no one writes about it or I can't find it. So here is the question: if I run SysLink examples in console, where is the output of Log_print0() commands used on DSP side?
What device are you using?
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?
The most straight-forward way to view the log data is to have a CCS connection. Then use Tools->ROV to view the LoggerBuf output.
You can use LoggerSM (instead of LoggerBuf) in the UIA product and have the log data go into shared memory and be displayed by the ARM (assuming it is running linux).
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 workedfine. 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 withOMAP3530. I am not sure whether this is a problem with the integration with syslink oris 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 useI use uia_1_01_01_14bios_6_34_03_19xdctools_3_23_02_47ipc_1_24_00_16I modified the memory map as you can see in the attached files to allocate more memoryfor the logger, the shared region etc.., but that didn't make a difference. Still programsthat used bios and xdctools worked and programs that used Ipc didn't work.I have attached the modified Dsp.cfg and the shared/config.bldThanksHazem
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.