• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 368 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.

How to load syslink example AND hd firmware?

Markus Grunwald
Expert 2060 points

Hello,

With the help of Judah and Ramsey, I managed to convert my old xdc/test.bld buildsystem to configuro and it works great on our "old" platform wich uses syslink version 2.00.02.80. Now I've used the example that Ramsey gave me to run some tests on our new platform which uses syslink 2.00.05.85. The test itself runs very well, as long as it's the only firmware that's loaded to a subsystem. As soon as the hd firmware is loaded, my example won't load anymore - sysloader freezes.

Now, the ezsdk developers guide clearly states that the syslink samples (which I'm using for my tests) "cannot be run out with graphics or firmware loaded". I had this trouble a long time ago and back then, it was "only" a memory map problem.

I need to load the hd firmware for graphic output and I need to load firmware to the DSP. Can you please help me to change my syslink example so that it can be loaded together with the hd firmware?

Thank you very much,

Markus

  • 0
    TI__Genius 12025 points

    Markus,

    To make the example compatible with the graphics firmware, I think requires two steps: 1) adjust the DSP memory map to fit into the EZSDK memory map, and 2) configure the DSP shared regions such that SR_0 matches the config used by the EZSDK. If your DSP requires additional shared regions, you must use regions which are currently not used by the EZSDK.

    I'm guessing that you are using EZSDK 5.04.00.11. The EZSDK Memory Map page gives details about the memory map and the shared regions. In particular, Section 6.7 DSP for OMX talks about the modifying the DSP memory map. To modify the example's memory map, edit the file shared/config.bld. To modify the DSP's shared region configuration, modify dsp/Dsp.cfg.

    I don't think you need to make any other changes. You should be able to run the example on the DSP with the graphics firmware loaded. Keep in mind, that if your application crashes, or the DSP crashes, there is a risk of leaking resources in SR_0 which can compromise the integrity of the entire system. In such cases, you will need to reboot the board.

    ~Ramsey