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.

OMAP software cookbook

Hi Forum,

I'd like to post some questions regarding general software/application programming/development on OMAP3evm. Before I got this board, I had very limited knowledge on programming embedded devices. I started to play with the demo package, read docs about e.g. dmai/codec engine/dspbios/dspbioslink/..., source-code-wise, I mainly looked into the dvsdk demo.

1. TI docs are nice and well-written. However, my feeling is that the docs are limited to certain topics - I miss an overview of the SW architecture for the platform, how different components are connected. Yes, one can read those between the lines but nevertheless an overview and general flow methodology doc would be extremely helpful. Could anyone give some pointers, if any?

2. The demo's code covers the UI and the most of the CE part. It'd be great to see how the interaction with DSP goes on, e.g. dspbios/dspbios link. Is there a sort of complete barebone demo that would cover (nearly) all the components like DMAI/CE/GPU/DSPBIOS/LINK/etc? It doesn't need to be shiny, completeness and self-explanatory on relationship of the components and also the building system(!) would help a lot.

3. For DSP side, I read the DSPBIOS userguide, in order to view the analysis results (and also for many other easy-to-go dsp programming), is it necessary to use CCS? Since my working host is linux only, I'd like to poll if there're other alternatives.

Thanks a lot!

 

  • 1. I think the best bring together of the technology is the Davinci workshop, which though is focused on DM6446 follows much of the same technology and concepts that you see in the OMAP3. There was also a new Dummies book released recently that looks like it may bring things together though I have not had a chance to look at it myself.

    2. Unfortunately the low level details like BIOS/Link are relatively hidden (which can be a good thing in some ways). There is a lot of documentation out there on codec engine and BIOS, a lot of the topics you are interested in are probably discussed to some extent on the Wiki sites.

    3. To get the most out of debugging the DSP you are best off using CCS, at least that is what I see used 99% of the time for DSP work, though there are other options out there such as Green Hills Multi that you could use from Linux.