• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 537 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.

OpenMAX on DSP & TI8168 Memory Maps

_Ralph_
Guru 10685 points

There is a section on this webpage:

http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map

called "DSP for OMX".

1) Is this configuration of the memory map applicable for OpenMAX codecs running on the HDVICPs? The name makes me think it isn't, because the DSP isn't the same as the HDVICPs but I'd be grateful if someone could clear up my confusion as I don't know where OpenMAX gets its memory map configured otherwise (unless it's at the time of media controller firmware loading).

2) While I'm here, what does "patch release" mean? This is referred to several times in the above webpage.

3) Why in "<EZSDK>/component-sources/c6accel_2_01_00_09/soc/packages/ti/c6accel_unitservers/TI816X/serverplatforms.xs" does the memory map contradict all the other memory maps I've seen around? It states that Linux occupies 166MB whereas the "length" field in this file indicates that it actually occupies 268MB, and the link above says that Linux occupies 364MB whereas the default board kernel parameters suggest that Linux only has 256MB.

I am very confused.

Thanks,

Ralph

  • 0
    TI__Intellectual 2785 points

    Ralph,

           Below are answers to your questions.

           1. The mentioned in memory map link DSP picks is memory map configuration from $(EZSDK_INSTALL_DIR)/component-sources/omx_05_02_00_09/packages/ti/omx/build/MemSegmentDefinition.xs, refer other informations in that link for other files to be checked for memory map.

               This is not applicable for Codecs running on HDVICPs.

          2. Here the "Patch release" implies that the future releases which will fix the open issue mentioned. Please refer to any release notes for any fixes. As of now this issue is still open. Once it is fixed this we will mention the release number on which the particular issue is fixed.

        3. There are multiple DSP applications exists on the EZSDK (OMX - <EZSDK>/component-sources/omx..., C6accel - <EZSDK>/component-sources/c6accel_2_01_00_09, C6Run, etc...), each application has its own memory map configuration file. But all should use the memory map defined in the EZSDK_Memory_map link.

            This may be a bug- Please let us know which release you are using, so that we can check to fix it.

            These minor memory map differences may not be a major issue & demos would work as expected.

            - When mem=256M is set in the kernel boot args the memory from 256M to 364MB (364M -256M=108MB) is unused.

            - When c6accel is running no other demo is executed, so no conflicts here.

           you can tweak as per your system using the procedure mentioned in EZSDK_Memory_map link.

           But we will fix these in subsequent releases to avoid any confusion.

    Best Regards

    Velan

  • 0 in reply to Velan
    Guru 10685 points

    Hi Velan,

    Thanks for your decent answers. With regards the dodgy C6Accel memory map, I am using the latest EZSDK, 5.02.01.59.

    Let's be honest though, not even the release notes match the EZSDK Memory Map webpage. The release notes say Linux has 256MB while the memory map webpage has it at 364MB plus another segment for Linux further in.

    Thanks,
    Ralph

  • 0 in reply to _Ralph_
    TI__Intellectual 2785 points

    Ralph,

       Apology for this confusion, we will fix this in subsequent releases.

      Since some of these applications had rebuild capability we did not take these as priority, also we were able to run each of these applications by ensuring other applications do not run simultaneously.

    Best Reagrds

    Velan

  • 0 in reply to Velan
    Guru 10685 points

    Are you saying that if I change the memory map to the correct one myself, then build C6Accel applications against the new memory map then it will all work fine for me?

    Thanks,

    Ralph

  • 0 in reply to _Ralph_
    TI__Intellectual 2785 points

    Yes, That is right

    Best Regards

    Velan