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.

FFT example in MCSDK

Hello,

1. I imported the FFT_Example_66_LE_COFF project into a new workspace.

According to link settings, the coff file contains only libc.a.

But according to map file the executable contains also dsplib.

Where it is in the link settings ? (and also the path to this lib)

2. Upon boot from flash I want to load an application only to cores 1,2 (out of 8). How can I do it ?

In what configuration file it is stated ?

3. What is the advantage of creating a "Group" in the debug perspective ?

Thanks,

Zvika

 

  • Hi Zvika,

    1. If you look at the Linker command file (lnk.cmd) for this project, you will see that this is where the dsplib (dsplib.a66) is linked in via the -l option here. This is why you see that dsplib is linked in when you look at the generated .map file on compilation. 

    2. To boot from flash I believe you could use the Multicore Application Deployment (MAD) utilities to do this and configure it based on your requirements. This is part of MCSDK, which you can download from http://www.ti.com/tool/bioslinuxmcsdk The folder you want to look at is 'tools/boot_loader.' I believe the MAD tool will let you build and load the image on to flash and then boot via IBL. The guide is at http://processors.wiki.ti.com/index.php/MAD_Utils_User_Guide

    3.  "Group"ing cores in Debug view can save you time in different ways; for example it allows you to connect to all cores in the group by a single right-click on the group and a single 'connect target', as opposed to having to do this separately for each core. Similarly you could use this to load the same application on multiple cores or run/pause all cores in a group or set breakpoints for all cores in a group.

  • Dear Gurnani,

    I would like to thank you for your detailed answer.

    Best regards,

    Zvika.