CCS / TMS320F28335：#10068-D no matching section warning appears in CMD when calling Flash28335_API_V210.lib library

user3829300

Other Parts Discussed in Thread: TMS320F28335

产品编号： TMS320F28335

工具/软件： Code Composer Studio

＃10068-D调用Flash28335_API_V210.lib库时，CMD中没有匹配的部分警告

SECTIONS
{

/ *分配方案领域：* /
Flash28_API：
{
-l Flash28335_API_V210.lib（.econst）
-l Flash28335_API_V210.lib（的.text）
} LOAD = FLASHD_2，
RUN = RAML0，
LOAD_START（_Flash28_API_LoadStart），
LOAD_END（_Flash28_API_LoadEnd），
RUN_START（_Flash28_API_RunStart），
PAGE = 0

以上绿色编译将报告此错误：
＃10068-D无匹配部分 F28335.cmd / EA180_CPUA_F110第166行C / C ++问题

＃10068-D没有匹配的部分 F28335.cmd / EA180_CPUA_F110第167行C / C ++问题

我没有找到在网上查看很长时间的原因。

附加到我的CMD文件和地图文件：

2337.EA180_CPUA_F110.map.txt

8270.F28335.cmd.txt

Fullscreen

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
/*
//###########################################################################
//
// FILE:    F28335.cmd
//
// TITLE:   Linker Command File For F28335 Device
//
//###########################################################################
// $TI Release: 2833x/2823x Header Files and Peripheral Examples V133 $
// $Release Date: June 8, 2012 $
//###########################################################################
*/
/* ======================================================
// For Code Composer Studio V2.2 and later
// ---------------------------------------
// In addition to this memory linker command file, 
// add the header linker command file directly to the project. 
// The header linker command file is required to link the
// peripheral structures to the proper locations within 
// the memory map.
//
// The header linker files are found in <base>\DSP2833x_Headers\cmd
//   
// For BIOS applications add:      DSP2833x_Headers_BIOS.cmd
// For nonBIOS applications add:   DSP2833x_Headers_nonBIOS.cmd    
========================================================= */
/* ======================================================
// For Code Composer Studio prior to V2.2
// --------------------------------------
// 1) Use one of the following -l statements to include the 
// header linker command file in the project. The header linker
// file is required to link the peripheral structures to the proper 
// locations within the memory map                                    */
/* Uncomment this line to include file only for non-BIOS applications */
/* -l DSP2833x_Headers_nonBIOS.cmd */
/* Uncomment this line to include file only for BIOS applications */
/* -l DSP2833x_Headers_BIOS.cmd */
/* 2) In your project add the path to <base>\DSP2833x_headers\cmd to the
   library search path under project->build options, linker tab, 
   library search path (-i).
/*========================================================= */
/* Define the memory block start/length for the F28335  
   PAGE 0 will be used to organize program sections
   PAGE 1 will be used to organize data sections
                Table 4-1. Initialized Sections Created by the Compiler
---------+------------------------------------------------------------------+---------------------------
Name     |  Contents                                                        |   Restrictions
---------+------------------------------------------------------------------+---------------------------
.cinit   |  Tables for explicitly initialized global and static variables   |   Program
---------+------------------------------------------------------------------+---------------------------
.const   |  Global and static const variables that are explicitly           |   Low 64K
         |  initialized and contain string literals                         |
---------+------------------------------------------------------------------+---------------------------
.econst  |  Far constant variables                                          |   Anywhere in data
---------+------------------------------------------------------------------+---------------------------
.pinit   |  Table of constructors to be called at startup                   |   Program
---------+------------------------------------------------------------------+---------------------------
.switch  |  Jump tables for large switch statements                         |   Program with -mt option
         |                                                                  |   Data without -mt option
---------+------------------------------------------------------------------+---------------------------
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

/*
//###########################################################################
//
// FILE:	F28335.cmd
//
// TITLE:	Linker Command File For F28335 Device
//
//###########################################################################
// $TI Release: 2833x/2823x Header Files and Peripheral Examples V133 $
// $Release Date: June 8, 2012 $
//###########################################################################
*/

/* ======================================================
// For Code Composer Studio V2.2 and later
// ---------------------------------------
// In addition to this memory linker command file, 
// add the header linker command file directly to the project. 
// The header linker command file is required to link the
// peripheral structures to the proper locations within 
// the memory map.
//
// The header linker files are found in <base>\DSP2833x_Headers\cmd
//   
// For BIOS applications add:      DSP2833x_Headers_BIOS.cmd
// For nonBIOS applications add:   DSP2833x_Headers_nonBIOS.cmd    
========================================================= */

/* ======================================================
// For Code Composer Studio prior to V2.2
// --------------------------------------
// 1) Use one of the following -l statements to include the 
// header linker command file in the project. The header linker
// file is required to link the peripheral structures to the proper 
// locations within the memory map                                    */

/* Uncomment this line to include file only for non-BIOS applications */
/* -l DSP2833x_Headers_nonBIOS.cmd */

/* Uncomment this line to include file only for BIOS applications */
/* -l DSP2833x_Headers_BIOS.cmd */

/* 2) In your project add the path to <base>\DSP2833x_headers\cmd to the
   library search path under project->build options, linker tab, 
   library search path (-i).
/*========================================================= */

/* Define the memory block start/length for the F28335  
   PAGE 0 will be used to organize program sections
   PAGE 1 will be used to organize data sections

				Table 4-1. Initialized Sections Created by the Compiler
---------+------------------------------------------------------------------+---------------------------
Name 	 |	Contents 														|	Restrictions
---------+------------------------------------------------------------------+---------------------------
.cinit 	 |	Tables for explicitly initialized global and static variables 	|	Program
---------+------------------------------------------------------------------+---------------------------
.const 	 |	Global and static const variables that are explicitly 			|	Low 64K
		 |	initialized and contain string literals							|
---------+------------------------------------------------------------------+---------------------------
.econst  |	Far constant variables 											|	Anywhere in data
---------+------------------------------------------------------------------+---------------------------
.pinit 	 |	Table of constructors to be called at startup 					|	Program
---------+------------------------------------------------------------------+---------------------------
.switch  |	Jump tables for large switch statements							|	Program with -mt option
		 |																	|	Data without -mt option
---------+------------------------------------------------------------------+---------------------------
.text 	 |	Executable code and constants 									|	Program
---------+------------------------------------------------------------------+---------------------------

				Table 4-2. Uninitialized Sections Created by the Compiler
---------+------------------------------------------------------------------+---------------------------
Name 	 |	Contents 														|	Restrictions
---------+------------------------------------------------------------------+---------------------------
.bss 	 |	Global and static variables 									|	Low 64K
---------+------------------------------------------------------------------+---------------------------
.ebss 	 |	Far global/static variables 									|	Anywhere in data
---------+------------------------------------------------------------------+---------------------------
.stack 	 |	Stack 															|	Low 64K
---------+------------------------------------------------------------------+---------------------------
.sysmem  |	Memory for malloc functions (heap) 								|	Low 64K
---------+------------------------------------------------------------------+---------------------------
.esysmem |	Memory for far_malloc functions 								|	Anywhere in data
---------+------------------------------------------------------------------+---------------------------

    Notes: 
          Memory blocks on F28335 are uniform (ie same
          physical memory) in both PAGE 0 and PAGE 1.  
          That is the same memory region should not be
          defined for both PAGE 0 and PAGE 1.
          Doing so will result in corruption of program 
          and/or data. 
          
          L0/L1/L2 and L3 memory blocks are mirrored - that is
          they can be accessed in high memory or low memory.
          For simplicity only one instance is used in this
          linker file. 
          
          Contiguous SARAM memory blocks can be combined 
          if required to create a larger memory block. 
 */


MEMORY
{
PAGE 0:    /* Program Memory */
           /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE1 for data allocation */
   RAML0       : origin = 0x008000, length = 0x001000     /* on-chip RAM block L0 */
//   RAML1       : origin = 0x009000, length = 0x001000     /* on-chip RAM block L1 */
   ZONE6       : origin = 0x0100000, length = 0x100000    /* XINTF zone 6 */ 
   ZONE7A      : origin = 0x0200000, length = 0x00FC00    /* XINTF zone 7 - program space */ 
   FLASHH      : origin = 0x300000, length = 0x018000     /* on-chip FLASH */
//   FLASHG      : origin = 0x308000, length = 0x008000     /* on-chip FLASH */
//   FLASHF      : origin = 0x310000, length = 0x008000     /* on-chip FLASH */
//   FLASHE      : origin = 0x318000, length = 0x008000     /* on-chip FLASH */
   FLASHD_1    : origin = 0x320000, length = 0x006000     /* on-chip FLASH */
   FLASHD_2    : origin = 0x326000, length = 0x002000     /* on-chip FLASH */
   FLASHC_1    : origin = 0x328000, length = 0x002000     /* on-chip FLASH */
//   FLASHC_2    : origin = 0x330000, length = 0x007FFF     /* on-chip FLASH */
   FLASHA      : origin = 0x338000, length = 0x007F80     /* on-chip FLASH */
   CSM_RSVD    : origin = 0x33FF80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
   BEGIN       : origin = 0x33FFF6, length = 0x000002     /* Part of FLASHA.  Used for "boot to Flash" bootloader mode. */
   CSM_PWL     : origin = 0x33FFF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA */
   OTP         : origin = 0x380400, length = 0x000400     /* on-chip OTP */
   ADC_CAL     : origin = 0x380080, length = 0x000009     /* ADC_cal function in Reserved memory */
   
   IQTABLES    : origin = 0x3FE000, length = 0x000b50     /* IQ Math Tables in Boot ROM */
   IQTABLES2   : origin = 0x3FEB50, length = 0x00008c     /* IQ Math Tables in Boot ROM */  
   FPUTABLES   : origin = 0x3FEBDC, length = 0x0006A0     /* FPU Tables in Boot ROM */
   ROM         : origin = 0x3FF27C, length = 0x000D44     /* Boot ROM */        
   RESET       : origin = 0x3FFFC0, length = 0x000002     /* part of boot ROM  */
   VECTORS     : origin = 0x3FFFC2, length = 0x00003E     /* part of boot ROM  */

PAGE 1 :   /* Data Memory */
           /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE0 for program allocation */
           /* Registers remain on PAGE1                                                  */
   
   BOOT_RSVD   : origin = 0x000000, length = 0x000050     /* Part of M0, BOOT rom will use this for stack */
   RAMM0       : origin = 0x000050, length = 0x0007B0     /* on-chip RAM block M0 */
//   RAMM1       : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
   RAML2       : origin = 0x009000, length = 0x006FE0     /* on-chip RAM block L2 */
//   RAML3       : origin = 0x00B000, length = 0x001000     /* on-chip RAM block L3 */
//   RAML4       : origin = 0x00C000, length = 0x001000     /* on-chip RAM block L1 */
//   RAML5       : origin = 0x00D000, length = 0x001000     /* on-chip RAM block L1 */
//   RAML6       : origin = 0x00E000, length = 0x001000     /* on-chip RAM block L1 */
//   RAML7       : origin = 0x00F000, length = 0x000FE0     /* on-chip RAM block L1 */
   RAMADDMACH1 : origin = 0x00FFE0, length = 0x000010     /* on-chip RAM block L1 */

//PAGE 2 :/*ECam data*/
   FLASHB      : origin = 0x330000, length = 0x008000     /* on-chip FLASH */
}

/* Allocate sections to memory blocks.
   Note:
         codestart user defined section in DSP28_CodeStartBranch.asm used to redirect code 
                   execution when booting to flash
         ramfuncs  user defined section to store functions that will be copied from Flash into RAM
*/ 
 
SECTIONS
{
 
   /* Allocate program areas: */
   Flash28_API:
   {
        -l Flash28335_API_V210.lib(.econst)
        -l Flash28335_API_V210.lib(.text)
   }          LOAD = FLASHD_2,
              RUN = RAML0,
              LOAD_START(_Flash28_API_LoadStart),
              LOAD_END(_Flash28_API_LoadEnd),
              RUN_START(_Flash28_API_RunStart),
              PAGE = 0
   .cinit              : > FLASHA      PAGE = 0 //Used to initialize C global variables at startup.
   .pinit              : > FLASHA,     PAGE = 0
   .text               : > FLASHH      PAGE = 0	//Used for program code.
   codestart           : > BEGIN       PAGE = 0
   ramfuncs            : LOAD = FLASHD_2,/*RUN��LOAD��Сһ�£����������*/
                         RUN = RAML0, 
                         LOAD_START(_RamfuncsLoadStart),
                         LOAD_END(_RamfuncsLoadEnd),
                         RUN_START(_RamfuncsRunStart),
                         PAGE = 0

   csmpasswds          : > CSM_PWL     PAGE = 0
   csm_rsvd            : > CSM_RSVD    PAGE = 0
   
   /* Allocate uninitalized data sections: */
   .stack              : > RAMM0       PAGE = 1 //Used for the function call stack.
   .ebss               : > RAML2       PAGE = 1	//Used for uninitialized objects (global variables).
   .esysmem            : > RAMM0       PAGE = 1 //Used for the dynamic memory allocation pool
   .sysmem             : > RAMM0       PAGE = 1

   /* Initalized sections go in Flash */
   /* For SDFlash to program these, they must be allocated to page 0 */
   .econst             : > FLASHA      PAGE = 0 //Used for initialized const objects (string constants, variables declared const).
   .switch             : > FLASHA      PAGE = 0      

   /* Allocate IQ math areas: */
   IQmath              : > FLASHC_1    PAGE = 0                  /* Math Code */
   IQmathTables     : > IQTABLES,  PAGE = 0, TYPE = NOLOAD 

   /* Uncomment the section below if calling the IQNexp() or IQexp()
      functions from the IQMath.lib library in order to utilize the 
      relevant IQ Math table in Boot ROM (This saves space and Boot ROM 
      is 1 wait-state). If this section is not uncommented, IQmathTables2
      will be loaded into other memory (SARAM, Flash, etc.) and will take
      up space, but 0 wait-state is possible.
   */
   /*
   IQmathTables2    : > IQTABLES2, PAGE = 0, TYPE = NOLOAD 
   {
   
              IQmath.lib<IQNexpTable.obj> (IQmathTablesRam)
   
   }
   */
   
   FPUmathTables    : > FPUTABLES, PAGE = 0, TYPE = NOLOAD 
         
   /* Allocate DMA-accessible RAM sections: */
//   DMARAML4         : > RAML4,     PAGE = 1
//   DMARAML5         : > RAML5,     PAGE = 1
//   DMARAML6         : > RAML6,     PAGE = 1
//   DMARAML7         : > RAML7,     PAGE = 1
   AdbufDma         : > RAMADDMACH1,     PAGE = 1

   /* .reset is a standard section used by the compiler.  It contains the */ 
   /* the address of the start of _c_int00 for C Code.   /*
   /* When using the boot ROM this section and the CPU vector */
   /* table is not needed.  Thus the default type is set here to  */
   /* DSECT  */ 
   .reset              : > RESET,      PAGE = 0, TYPE = DSECT
   vectors             : > VECTORS     PAGE = 0, TYPE = DSECT
   
   /* Allocate ADC_cal function (pre-programmed by factory into TI reserved memory) */
   .adc_cal     : load = ADC_CAL,   PAGE = 0, TYPE = NOLOAD

   CAM_Table		   : > FLASHB      PAGE = 1                  /*CAM TABLE */
}

/*
//===========================================================================
// End of file.
//===========================================================================
*/

over 6 years ago

0 Kevin Allen18 over 6 years ago

TI__Mastermind 42936 points

Hi,

Could you please re-post your question/issue in English?

Best,
Kevin

Edit:

Also, can you provide the full text of the warning. Something may be missing or improper in your linker command file (.cmd)

0 David M. Alter over 6 years ago

TI__Guru 61235 points

user3829300,

You need to actually call a flash API function before the API section will appear in your build. The warning is saying that you have linked the section, but the section is not present in the build.

Regards,

David

0 user3829300 over 6 years ago in reply to David M. Alter

Prodigy 50 points

Thank you, this problem has been solved, but there is another problem. Please help me to look at it.

The second entry variable of Flash_Program() function is Uint16 type, 
but I want to store the int32 type, and then I get an error. 
How can I implement int32 type data to write to fixed Flash, 
thank you!


int32 Buffer1[20]={1,2,3,4,5,6,7,8,9,10,-1,-2,-3,-4,-5,-6,-7,-8,-9,-10};

Flash_ptr = Sector[1].StartAddr;
Length = 0x4;
Status = Flash_Program(Flash_ptr,Buffer1,Length,&FlashStatus);
if(Status != STATUS_SUCCESS)
{
Example_Error(Status);
}

Compile error message：

Description Resource Path Location Type
#169 argument of type "int32 *" is incompatible with parameter of type "Uint16 *" Flash_API_Func.c /EA180_CPUA_F110/SpecialFunction line 310 C/C++ Problem

0 user3829300 over 6 years ago in reply to David M. Alter

Prodigy 50 points

Thank you, this problem has been solved, 
but there is another problem. Please help me to look at it.

The second entry variable of Flash_Program() function is Uint16 type,
 but I want to store the int32 type, 
and then I get an error.
 How can I implement int32 type data to write to fixed Flash, 
thank you!


int32 Buffer1 [20] = {1,2,3,4,5,6,7,8,9,10，-1，-2，-3，-4，-5，-6，-7，-8 ，-9，-10};

Flash_ptr = Sector[1].StartAddr;
Length = 0x4;
Status = Flash_Program(Flash_ptr,Buffer1,Length,&FlashStatus);
if(Status != STATUS_SUCCESS)
{
Example_Error(Status);
}

Compile error message：

Description Resource Path Location Type
#169 argument of type "int32 *" is incompatible with parameter of type "Uint16 *" Flash_API_Func.c /EA180_CPUA_F110/SpecialFunction line 310 C/C++ Problem

0 user3829300 over 6 years ago in reply to David M. Alter

Prodigy 50 points

Dear David：
Thank you, this problem has been solved,
but there is another problem. Please help me to look at it.

The second entry variable of Flash_Program() function is Uint16 type,
but I want to store the int32 type,
and then I get an error.
How can I implement int32 type data to write to fixed Flash,
thank you!

int32 Buffer1 [20] = {1,2,3,4,5,6,7,8,9,10，-1，-2，-3，-4，-5，-6，-7，-8 ，-9，-10};

Flash_ptr = Sector[1].StartAddr;
Length = 0x4;
Status = Flash_Program(Flash_ptr,Buffer1,Length,&FlashStatus);
if(Status != STATUS_SUCCESS)
{
Example_Error(Status);
}

Compile error message：

Description Resource Path Location Type
#169 argument of type "int32 *" is incompatible with parameter of type "Uint16 *" Flash_API_Func.c /EA180_CPUA_F110/SpecialFunction line 310 C/C++ Problem

0 David M. Alter over 6 years ago in reply to user3829300

TI__Guru 61235 points

user3829300,

You can typecast the array as 16-bit unsigned in the function call.

Status = Flash_Program(Flash_ptr,(Uint16*)Buffer1,Length,&FlashStatus);

I didn't test, but I believe the above is correct.

Regards,

David

0 user3829300 over 6 years ago in reply to David M. Alter

Prodigy 50 points

Thank You Very Much!

C2000™︎ microcontrollers

C2000 microcontrollers forum

CCS / TMS320F28335：#10068-D no matching section warning appears in CMD when calling Flash28335_API_V210.lib library