Other Parts Discussed in Thread: OMAP-L138, OMAP-L137
This is a follow up to the following answered question: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/219596/773871.aspx#773871
We have been able to modify loadti (http://processors.wiki.ti.com/index.php/Loadti) to capture the output we need from the ARM core of our OMAP-L138 for the ARM unit tests, but it does not seem to capture the output of the DSP CIO, which we need for our DSP unit tests.
Is there some configuration to the loadti script we can make to capture both DSP and ARM CIO (like the console window of CCS5 does by default). Barring that, is there some way to specify which core to get the CIO output from?
I guess I should note that our current process does some minimal DDR and PLL setup and then loads code both for the DSP and ARM, runs the ARM which does the rest of the initilization and then wakes up and runs the DSP code. I suspect we could do something with a specialized GEL file that just connected to the DSP and bypassed the ARM to capture DSP CIO, but that would mean we would have less of a guarantee that our DSP unit tests were running in the "same" setup as our production code, and we would have to manually maintain consistency between the GEL file and the ARM initialization code. We'd much rather just have the same initialization process in test mode as in production and capture CIO from both cores as the CCS5 console window does.
Thanks,
Jay
P.S. is it better forum ettiquette to post a followup question as a separate post, or to reopen a thread for a question that has been answered validly?
