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

Some inquiries about MAPTools for C6678

Boll
Intellectual 340 points
I am evaluating C6678EVM, and get some questions.
  1. Can linker command file be removed from CCS project if Prelinker mode is to be used for MAPTool? 
  2. Is it possible to generate a map file to see memory allocation result when building the booting image with MAPTool in Prelinker mode?
  3. I create a led_play project with reference to the guide; LEDs will blink when .out file is loaded to Core 0.  
    However it won't flash when loaded to other cores.  What is reason?
  4. I tried MAD Utils User Guide with Prelinker mode. Basically the expected result is seen except one thing - signature[] can not be recognized.
    When perform Scripts->refresh_symbols_app1, in Expressions view, the address of signature is 0x00000004, which is an invalided memory area.
    In app_1.c, signature[] is defined uninitialized.  When I modify it as initialized, things will be OK.
    So I'd like to ask:  which section will an uninitialized structure/array/union be placed in?
    Please refer to http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/192223/693541.aspx#693541 for my detail discussion with Allen.
  5. Please explain the difference of the following items in "secNamePat" of deployment_template_xxxx.json
        -  "text"    vs    "^.text"
        -  "far"     vs    "^.far$"    vs    "^\\.far\\."
    Or where can I find documents for explanation?
  6. With reference to MAD Utils User Guide, multicore booting is successful with mcsdk_2_00_05_17. 
    But it will fail when performing the same steps with  latest mcsdk_2_00_08_20.
    Please have a check.

Thanks.


Boll

  • 0
    Intellectual 820 points

    Hello Boll,

    I am nearly in the same situation with you for the Prelinker mode problem. Waiting a response from TI. However, for your third question:

    3. You are right, Leds won't blink if you execute your application on different cores other than Core 0. Because, if you go into deep in the platform_init() function of platform library, you will see that some part of the initialization process is only executed if the running core is 0. I don't know the reason for this situation, but it is as this is. May be a TI guy may answer this confusion.  What I did for overcoming this problem is: I am initializing the platform from Core 0 (the other cores are waiting for core 0 to initialize platform), and then other cores just call platform_led() function which is a core independent function that just sends a message to the FPGA. This way I can blink the LEDs from other cores.

    Regards,
    Koray.