• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 197 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.

EZSDK 5.3.1.15 Incompatibility between V4L2 and Syslink examples

A Marchini
Intellectual 630 points

From reading DM816x_EZ_Software_Developers_Guide.pdf , you need to cut down the firmware execution before you can use the syslink examples. This means , it appears, that I can not develop a V4L2 merged with a syslink example program.

What specifically is not compatible between the two?

What kind of work needs to be done on my part to make them operate together?

Is it a limitation of the firmware, at which point I am just not able to do what I want , or is it just a configuration issue?

Sincerely,

Anthony Marchini 

  • 0
    TI__Expert 4245 points

    Hi Anthony,

    The limitation is only a configuration item. The Syslink Sample applications use a different memory map than the fully integrated EZSDK. Hence those examples specifically cannot be run simultaneously with video. When creating your own application, there is no such limitation.

    Please see the EZSDK memory map at http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map

  • 0 in reply to Siddharth Heroor
    Intellectual 630 points

    I have examined the Default 1GB System and I see where everthing has its place. Great

    You say that syslink uses a different memory map, which isn't referenced at all on this page, OK so this information is somewhere else.

    Where is the syslink memory map? I realize that linux is requested to be smaller for the syslink examples, but what is being lost when the load firmware script is being executed. The issue must be that there is a piece of memory being used by something that is the same address the example DSP programs are being loaded to. What is it? Were is the collision of space?

    The only thing that seems an issue is the DSP_CODE and IPC_SR_MC_HDVICP2_HDVPSS being assigned  the same beginning address. 

     Tony M.

  • 0 in reply to A Marchini
    Intellectual 630 points

    Maybe I am not asking this correctly. 

    • What specified the memory that the syslink example programs will use? 
    • Is it dynamically allocated in some way?
    • a basic low level question but I just need to be sure, IS the DSP binary being loaded into a reserved area of DDR3 memory space?  
    I just need to figure out how to move these things and I feel if I can find the specific define or build option to change I can move forward here.
    Thanks
    Tony M.