One of my customers is seeing heavy loading on their DM365 based system which doesn't align with our expectations. I will provide more details shortly, but below is what they are running into right now.
I will provide more specifics on the individual loading they are seeing, but I wanted to get this started to see if you have recommendations on how to debug what is hogging their CPU?
Are they using the Codec Engine? There are currently some issues running a video codec + ARM audio codec on DM365 because Codec Engine does not allow to enable the cache selectively only for the ARM audio codec. There will be a new CE release that will support this.
I think that the high CPU load is explained by a disabled cache on the ARM.
I will check. Can you help move this post to the external DM36x processor forum so that I can have the customer add details?
FYI, this feature was added in CE 2.25.05.16 - recently announced here.
Details about this feature are also available at this article.
They use DVSDK version 126.96.36.199 (from UDWORKS for multi channel). The MontaVista PRO 5.0 distribution is used for the tool suite, file system, and kernel version 2.6.18+.
I will update them on the new Codec engine release, but is there they would need to know on how to integrate this as part of the DVSDK? This might be self explanatory, but I just wanted to clarify this.
Also, is there a way you can move this post to an external forum so that I can have the customer read through this?
moved to external forum per Harini's request.
PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question. Thanks!
Please see below from our customer - can you help clarify?
I've gone through our current dvsdk, and it's not at all clear how to
determine whether we have cache enabled. Could you provide more
specific instructions on how to determine whether cache is enabled?
Also, so far we have only installed full dvsdk packages as far as I
know, and we are currently using dvsdk 188.8.131.52. Your email
provides links to new Codec Engine, Framework Components, and Linux
Utils releases. Are you suggesting that we can install these three new
packages on top of our current dvsdk and there will be no compatibility
issues? I just want to make sure before we attempt this in the future.
Hi Team - Can you help with above? Thanks!!
By default the ARM cache is disabled.
You can enable the cache by adding the following to the application .cfg config file.
algSettings = xdc.useModule('ti.sdo.ce.alg.Settings');
algSettings.useCache = true;
Regarding the codec engine compatibility please read the release notes, it should provide you with compatibility breaks information
Thanks Cesar. They checked the .cfg file used by our eInfoChips application and found that the cache is already enabled (i.e. it has the two lines of code indicated in your message above).
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.