• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 598 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DM6467 arm968 boot

tie
Prodigy 130 points

Hi, how can i boot arm968 in Codec Engine Framework? We have succssfully boot it from ARM side,and we just don't know how to use it in Codec Engine Framework.It seems TI has no user guide on this subject.Thanks & regards

  • 0
    TI__Mastermind 37340 points

    I am not sure I understand the question.  Codec Engine framework is software layer that runs on both ARM (at user level) and DSP.  In ARM side, the kernel has to load before any user level application; booting ARM requires boot-loader (e.g. u-boot) and Linux Kernel (uImage), both which are provided with DVSDK software.

    If this does not help, please feel free to post additional questions and we will be happy to answer them. 

  • 0 in reply to Juan Gonzales
    TI__Genius 17355 points

    The arm968 cores in the DM6467 are part of the accelerator blocks that are used by the codecs.  In general, these aren't parts of the system that you would want to load with your own code, particularly if you are planning on using the codec engine framework.  Codecs that make use of the accelerators would be responsible for handling that.

  • 0 in reply to Daniel Allred
    Prodigy 130 points

    do you mean the codec should boot up arm968 when we do codec initialization ? i just wonder if it fits the Codec Endigne Framework.

  • 0 in reply to tie
    TI__Mastermind 37340 points

    I believe he meant that the XDM compliant codecs that are consumed by codec engine (requires codecs be XDM compliant) will initialize the arm968.  This is initialization is outside of codec engine framework.

  • 0 in reply to Juan Gonzales
    TI__Genius 17355 points

    Right.  Any codec which makes use the accelerator blocks, whether it is used with the CE framework or some other framework, will have to be responsible for setting up those accelerators in an appropriate fashion.  To my knowledge, that would include loading any necessary code to run on the ARM968 core, which sits at the heart of that accelerator.

  • 0 in reply to tie
    TI__Mastermind 41665 points

    In general as a DM6467 user you should not be concerned with the ARM968, the use of this core is beyond the scope of what we typically support on the device. The only case where you would be dealing with booting the ARM968 is if you were a third party codec developer, which is a limited group who would typically have local support directly from TI. If you look at the DM6467 documentation (datasheet, user's guides, etc.) you will find that the ARM968 is not discussed anywhere for this reason, from a typical user perspective you should consider it to not exist, as far as I know the only place I have seen it publicly is the CCS configuration for DM6467, which has the ARM968 cores mapped on the JTAG scan chain.

    So in general if you are having an issue with a DM6467 codec using the ARM968 than you will want to work with the codec provider. If you are developing a codec for the DM6467 that uses the ARM968 you will want to work with your local TI contacts.