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.

816X EVM dsp_benchmark example

I am trying to build the dsp_benchmark example that comes with the 816X EVM.

The ReadMe.txt file gives no instructions for building or running the example; it simply says there is a Makefile to build the package.

After I have set appropriate - I believe - paths in the various Rules.make files, the Makefile fails because it cannot find things from the../soc/... directory.

I have gone to the soc directory and found no help information, so I tried executing the Makefile found there, but this also fails, giving the message:

"ti/c6accel/ce/C6ACCEL.xdc", line 17: can't resolve name (ti.sdo.ce.universal.IUNIVERSAL)

It seems that the examples have not been set up to work without a great deal of knowledgeable user intervention.

I would imagine that this example should run on the board it came with  (816X EVM).

 

Can anyone provide simple instructions for getting this example to run or at least, point me at such instructions?

 

 

  • For clarification, I have been following the DSP Benchmark demo User Guide from the docs folder. Essentially this just says to run the makefile.

    There are clearly many dependencies that are not stated clearly.

     

     

  • Peter,

    What is the version of SDK, you are using. The DSP benchmark demo is provided in source and the Release notes and the ReadMe text included provides description and details of the dependencies for the demo.

    Regards

    Rahul

  • I have just found the problem. It was a typo in one of the many edits that seem to be needed to do anything with the standard installation.

    I find it surprising that the power of the processor isn't used to set up most of these definitions, either during installation or by means of a fairly trivial exploration program.

    Instead, the assumption is that users must go in and edit files manually, leading to opportunities for obscure errors such as I am perpetually hitting.

     

  • Peter,

    You should not have to do any hand edits with the EZSDK 5.0x. The installation process will create the Rules.mak file at the top level of the ezsdk - eg /ti-ezsdk_dm816x-evm_5_02_02_60/Rules.mak

    All components are then designed to be built from this top level directoryusing the Rules.mak that has been configured. In case of c6accel use

    $cd  ti-ezsdk_dm816x-evm_5_02_02_60

    $make c6accel

    Iain

     

     

  • I was forced down the road of using different versions of various components - and then having to make manual adjustments - because nothing worked

    out of the box and I was told I had to use different versions of various components.

     

    I seem to have gone full-circle on this particular merry-go-round.