• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 1729 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.

Unassigned segment found ERROR when using MAPtools

Allen Lee
Genius 3770 points
Other Parts Discussed in Thread: TEST2


Hi All,

It's my first time to get touch with mad_utils, so i follow the steps of Demo walkthrough at http://processors.wiki.ti.com/index.php/MAD_Utils_User_Guide to use the mad_utils tools for multicore deployment. Based on the example within mad-loader, I only make some modifications as:

STEP-1: Image Preparation :

I build two .out as the input(named test1.out and test2.out) instead of the two .exe in the example.

STEP-2: Device memory partitioning & deployment config preparation

Modify the "prelinkExe" ,"stripExe" and "ofdTool"  within maptoolCfg_C6678_windows.json file according to my local CGTools directory.

Modify the deployment_template_C6678_windows.json file ,only replace app_1.exe and app_2.exe with test1.out and test2.out, nothing else modified.

STEP-3: Invoke MAP tool

My invoke command line:

C:\Texas Instruments\mcsdk_2_00_05_17\tools\boot_loader\mad-utils\map-tool>c:\Python27\python.exe maptool.py config-files\maptoolCfg_C6678_windows.json

And the the error occurs with the output:

Info: Incompatible permissions for segment: 6  application: app1 in partition: ddr-code
Info: Incompatible permissions for segment: 8  application: app1 in partition: ddr-code
Info: Incompatible permissions for segment: 6  application: app2 in partition: ddr-code
Info: Incompatible permissions for segment: 8  application: app2 in partition: ddr-code
ERROR: Unassigned segment found: app1 :seg-idx: 2
ERROR: Unassigned segment found: app1 :seg-idx: 7
ERROR: Unassigned segment found: app2 :seg-idx: 2
ERROR: Unassigned segment found: app2 :seg-idx: 7

So the c6678-le.bin was not generated in the images directory. But the there exist one directory named "appImages" and two files within it(app1 and app2).

What's wrong with the configuration of these tools? Thanks in advanced.

Allen

  • 0
    TI__Genius 9915 points

    Allen,

    Are you changing any sections of the code before compiling or you are compiling the code we packaged in the MAD utils examples.

    Thanks,

    Arun.

  • 0 in reply to ArunMani
    Genius 3770 points

    Hi Arun,

    I have followed the instructions of this thread, http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/136955.aspx. Now I can produce the binary image smoothly. But there still some issues preventing me to boot and run the image successfully.

    For debugging convenience, I scale down the complexity of the demo and there are some notes of my operations:

    1. There is ONLY one input .out which is a simple program to blink the LED0. I have validated the function of it on EVM and it was the input to produce "app1"

    2. "app1" is ONLY allocated to Core0, other cores are empty.

    "appDeployment" : [
      "app1",
      "",
      "",
      "",
      "",
      "",
      "",
      ""
     ]

    3. --dynamic and --relocatable option was added for linker.

    4.  I am testing NAND BOOT, so some changes made in i2cConfig.gel:

    ibl.bootModes[1].u.nandBoot.bootFormat        = ibl_BOOT_FORMAT_BBLOB;

    ibl.bootModes[1].u.nandBoot.blob[0][0].startAddress  = 0x80000000;       /* Image 0 load start address in LE mode */
    ibl.bootModes[1].u.nandBoot.blob[0][0].sizeBytes     = 0xFFC000;         /* Image 0 size in LE mode */
    ibl.bootModes[1].u.nandBoot.blob[0][0].branchAddress = 0x80001040;       /* Image 0 branch address after loading in LE mode */

    P.S: Confused here, BiosMCSDK userguide told startAddress should be 0x80000000 and branchAddress as 0x80001040. But http://processors.wiki.ti.com/index.php/MAD_Utils_User_Guide said

    • startAddress = 0x9e000000.
    • branchAddress = 0x9e001040

    5. My dipswitch is configured as IBL NAND boot on image 0 Mode of http://processors.wiki.ti.com/index.php/TMDXEVM6678L_EVM_Hardware_Setup#Boot_Mode_Dip_Switch_Settings

    After all steps completed, after power cycle of EVM, the LED0 didn't blink, so it shows the program is not running correctly. Any ideas?

    Thanks all helps.

    Allen

  • 0 in reply to Allen Lee
    TI__Genius 9915 points

    Hi Allen,

    in the new version of MCSDK you are using, you should use the start address and branch address specified in the MAD loader user guide. That might be the reason you are not able to get this boot work.

    Thanks,

    Arun.

  • 0 in reply to ArunMani
    Genius 3770 points

    Hi Arun,

    It seems work when using the address of MAD UG. And just one more question, in the prelink mode, the allocation of the section is handled by the MAP tools. So does it means that the instructions of project's cmd file(i.e the SECTIONS parts) is useless since the position of one section is finally decided by the MAP's prelinker instead of the CCS linker?

    Allen

  • 0 in reply to Allen Lee
    Genius 3770 points

    Sorry for a long time delay since I can't post or reply the last week. The upgrade of the forum seems produce some stablility problems.