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.

Migrating from DM365 to DM6467



Hi E2E Community,

I have some questions in regards to transitioning from the DM365 to the DM6467.  Any help would be appreciated.


1. This is a bit of an imprecise, qualitative question, but with codec engine abstractions, how much more complicated would it be to get a demo app up and running on a DM6467 eval  board vs. DM365 eval board?  I have worked extensively on the DM6446, so I am familiar with many of the issues of working with the dual core processors (CMEM, DSP/LINK, etc.), but there are a few gaps in my understanding of the total software package that TI or third parties provide, especially with regard to the differences between the ARM processors of the DM6467 and DM365.


2. How much portability do the tools provide between the ARM926 of the DM6467 and the ARM Cortex of the DM365, should we decide down the road to jump over?


3. Are there any RTP streaming libraries ported to the DM6467 like the appro (IPNC) kits provide?  I remember hearing some whispers a couple of years ago that an engineer at TI had ported the live555.com stack to the ARM; does TI provide or support this port in any official capacity?


4. Would the software tool requirements change if we went with the DM6467 (other than the LSP, for instance), keeping in mind that we won't be doing any DSP-side development this time around?

 

  • 1) From a Linux user-application point of view, DM365, DM6446, and DM6467 should be very similar (90%); major differences in hardware capabilities (resizer, osd...) should be ancapsulated by drivers and almost transparent to user application.  Also, all Codec Engine and related software (framework components, xdctools....) should be compatible across the three platforms and evolves over time (new software versions)

    2) Please note that DM365 has an ARM9 as well (not a Cortex core), hence tools should be compatible

    3) These solutions are nornally offered by third parties; I can say RTP streaming solutions have been ported, including live555 by customers in the past; but these solutions are not directly included in the TI software stack

    4) Tools should be compatible across both ARM and DSP