• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 998 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.

errors in code when adding f28m35h52c1_c28.cmd

pradeep kumar ama
Intellectual 705 points

hi,

i m pradeep and i m working on pwm. my problem is i m getting error when i m adding f28m35h52c1_c28.cmd  (running code from flash not from ram ) file in to my code because my code size is very big so i m erasing some flash sector. i now this from piccolo i worked this same problem on piccolo so i added f28069.cmd and in that i changed the flash sector  its working proper but in concerto i m getting 60+ errors like

Description Resource Path Location Type
BEGIN memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 62 C/C++ Problem
BEGIN memory range overlaps existing memory range BEGIN F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 62 C/C++ Problem
BOOT_RSVD memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 80 C/C++ Problem
BOOT_RSVD memory range overlaps existing memory range BOOT_RSVD F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 80 C/C++ Problem
BOOTROM memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 72 C/C++ Problem
BOOTROM memory range overlaps existing memory range BOOTROM F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 72 C/C++ Problem
CSM_PWL_P0 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 65 C/C++ Problem
CSM_PWL_P0 memory range overlaps existing memory range CSM_PWL_P0 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 65 C/C++ Problem
CSM_RSVD memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 61 C/C++ Problem
CSM_RSVD memory range overlaps existing memory range CSM_RSVD F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 61 C/C++ Problem
CTOMRAM memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 94 C/C++ Problem
CTOMRAM memory range overlaps existing memory range CTOMRAM F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 94 C/C++ Problem
ECSL_PWL_P0 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 64 C/C++ Problem
ECSL_PWL_P0 memory range overlaps existing memory range ECSL_PWL_P0 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 64 C/C++ Problem
errors encountered during linking; "epwm_updown_aq_c28.out" not built epwm_updown_aq_c28 C/C++ Problem
FLASH_EXE_ONLY_P0 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 63 C/C++ Problem
FLASH_EXE_ONLY_P0 memory range overlaps existing memory range FLASH_EXE_ONLY_P0 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 63 C/C++ Problem
FLASHA memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 59 C/C++ Problem
FLASHA memory range overlaps existing memory range FLASHA F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 59 C/C++ Problem
FLASHB memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 97 C/C++ Problem
FLASHB memory range overlaps existing memory range FLASHB F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 97 C/C++ Problem
FLASHC memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 58 C/C++ Problem
FLASHC memory range overlaps existing memory range FLASHC F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 58 C/C++ Problem
FLASHD memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 57 C/C++ Problem
FLASHD memory range overlaps existing memory range FLASHD F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 57 C/C++ Problem
FLASHE memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 56 C/C++ Problem
FLASHE memory range overlaps existing memory range FLASHE F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 56 C/C++ Problem
FLASHF memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 55 C/C++ Problem
FLASHF memory range overlaps existing memory range FLASHF F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 55 C/C++ Problem
FLASHG memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 54 C/C++ Problem
FLASHG memory range overlaps existing memory range FLASHG F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 54 C/C++ Problem
FPUTABLES memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 67 C/C++ Problem
FPUTABLES memory range overlaps existing memory range FPUTABLES F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 67 C/C++ Problem
IQTABLES memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 68 C/C++ Problem
IQTABLES memory range overlaps existing memory range IQTABLES F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 68 C/C++ Problem
IQTABLES2 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 69 C/C++ Problem
IQTABLES2 memory range overlaps existing memory range IQTABLES2 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 69 C/C++ Problem
IQTABLES3 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 70 C/C++ Problem
IQTABLES3 memory range overlaps existing memory range IQTABLES3 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 70 C/C++ Problem
MTOCRAM memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 95 C/C++ Problem
MTOCRAM memory range overlaps existing memory range MTOCRAM F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 95 C/C++ Problem
PIEMISHNDLR memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 73 C/C++ Problem
PIEMISHNDLR memory range overlaps existing memory range PIEMISHNDLR F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 73 C/C++ Problem
RAML0 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 44 C/C++ Problem
RAML0 memory range overlaps existing memory range RAML0 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 44 C/C++ Problem
RAML1 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 45 C/C++ Problem
RAML1 memory range overlaps existing memory range RAML1 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 45 C/C++ Problem
RAML2 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 83 C/C++ Problem
RAML2 memory range overlaps existing memory range RAML2 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 83 C/C++ Problem
RAML3 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 84 C/C++ Problem
RAML3 memory range overlaps existing memory range RAML3 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 84 C/C++ Problem
RAMM0 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 81 C/C++ Problem
RAMM0 memory range overlaps existing memory range RAMM0 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 81 C/C++ Problem
RAMM1 memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 82 C/C++ Problem
RAMM1 memory range overlaps existing memory range RAMM1 F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 82 C/C++ Problem
RESET memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 74 C/C++ Problem
RESET memory range overlaps existing memory range RESET F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 74 C/C++ Problem
VECTORS memory range has already been specified F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 75 C/C++ Problem
VECTORS memory range overlaps F28M35H52C1_c28.cmd /epwm_updown_aq_c28 line 75 C/C++ Problem

  • 0
    TI__Mastermind 19810 points

    Pradeep,

    pradeep kumar ama said:
    o i worked this same problem on piccolo so i added f28069.cmd and in that i changed the flash sector  its working proper but in concerto i m getting 60+ errors like

    I guess the problem is that you have two linker command files defining same sections. Instead of adding 28069 linker command file to concert project, can you do the same modifications that you did on 28069 to concerto C28 project's linker command file. Be aware of which flash sectors you are expanding and programming because there are some sectors which have CSM passwords and you don't want to program them accidentally - refer to data sheet or TRM for exact details.

    if any code/data segment is falling short of memory space, identify that and just increase the size of the memory section that the segment is linked into or link the segment into more than one defines memory sections (for ex: FLASHA|FLASHB...etc). Search the forums for the error and you will find other posts which discuss the solution.

    Best Regards

    Santosh

  • 0 in reply to Santosh Athuru
    Intellectual 705 points

    thanks santosh,

    i m not adding any piccolo file  to concerto. i meant to say that what ever procedure i m following for piccolo same following for concerto... OK . i tried to increase the flash size when i m trying like that i m getting those error and more over those error are of concerto only u can see . extension all are from  concerto......    

  • 0 in reply to pradeep kumar ama
    TI__Mastermind 19810 points

    Pradeep,

    check the boundaries and sizes of the sections in your linker comand file... if you increase the size of one section, you will have to push the start of the next section that much.

    Best Regards

    Santosh