warning: creating output section "AdcMirrorFile" without a SECTIONS

Malcolm Windham

Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28075

I was trying out the new 5.1 CC with a 28335 experimenter's card and making the Hardware_FPU example and was successful when I included all the dependencies in the project, but when I tried to build a lib comprised of those other files and link to the main example, I got about 50 warnings creating output section "..." without a SECTIONS, and something was wrong in the debugging as it went off on its own before getting to the main two computations. How to make a good static lib? (I tried generate sections. option)

Warnings were:

Description Resource Path Location Type
#10247-D creating output section "AdcMirrorFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "AdcRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "CpuTimer0RegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "CpuTimer1RegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "CpuTimer2RegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "CsmPwlFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "CsmRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "DevEmuRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "DmaRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECanaLAMRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECanaMboxesFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECanaMOTORegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "ECanaMOTSRegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "ECanaRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECanbLAMRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECanbMboxesFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECanbMOTORegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "ECanbMOTSRegsFile" without a hw00slib   C/C++ Problem
#10247-D creating output section "ECanbRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECap1RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECap2RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECap3RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECap4RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECap5RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ECap6RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EPwm1RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EPwm2RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EPwm3RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EPwm4RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EPwm5RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EPwm6RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EQep1RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "EQep2RegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "FlashRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "GpioCtrlRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "GpioDataRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "GpioIntRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "I2caRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "McbspaRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "McbspbRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "PartIdRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "PieCtrlRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "PieVectTableFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "SciaRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ScibRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "ScicRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "SpiaRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "SysCtrlRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "XintfRegsFile" without a SECTIONS hw00slib   C/C++ Problem
#10247-D creating output section "XIntruptRegsFile" without a SECTIONS hw00slib   C/C++ Problem

over 14 years ago

0 Chuntao Song over 13 years ago

Prodigy 40 points

Meet same problem. Wait for support together.

Another problem: Register window does not change although register is changed in code. But register change can be validated in the floating window when put mouse on code.

0 Chuntao Song over 13 years ago in reply to Chuntao Song

Prodigy 40 points

I know the reason now. Register address need to be allocated in the cmd file manually one by one. And that's why register window doesn't show any change.

0 lin ji over 12 years ago in reply to Chuntao Song

Prodigy 10 points

How to allocate the register address in the cmd fiale?

0 Disona over 12 years ago in reply to lin ji

Genius 3050 points

Hello!

Usually there are spicial .cmd files in controlSuite "device_support" folders. These special .cmd files allocate registers in memory in righteous way.

They are usually named as"%MCU_MODEL%_Headers_[non]BIOS.cmd.
So, I think, you should look for a file named "F28335_Headres_BIOS.cmd". (it may named F28xx_Headers_BIOS.cmd" or else.

0 Lori Heustess over 12 years ago in reply to Disona

TI__Guru* 93800 points

Disona is correct.

The allocation of these sections is done in the header command file C:\ti\controlSUITE\device_support\f2803x\<version>\DSP2803x_headers\cmd

You will want the nonBIOS file ( ounless you are using DSP or SYS/BIOS in the application of course).

0 user4403062 over 10 years ago

Prodigy 10 points

Maybe it's two years ago, but if I got the same problem right now, i supose anyone else also might.

PROBLEM: My device is TMS320F28075. I wanted to include gpio module from controlSUITE 'blinky example', into my TI-RTOS empty project for led manipulation. I got the .c, .h files imported in my project, but while debugging registers values (GpioCtrlRegs, GpioDataRegs) didn't change values while code was executed

SOLUTION: I had to copy few lines from file F2807x_Headers_BIOS.cmd (which is located in controlSUITE/device_support/vXXX/F2807x_headerscmd/) to TMS320F28075.cmd (which is my project default linker command file). My device is TMS320F28075 :).

The exact lines:

//==============================================================================
/* MY TMS320F28075.cmd FILE */

MEMORY
{
PAGE 0 : /* Program Memory */
...

PAGE 1 : /* Data Memory */
...
...
...
RAMGS5 : origin = 0x011000, length = 0x001000
RAMGS6 : origin = 0x012000, length = 0x001000
RAMGS7 : origin = 0x013000, length = 0x001000

GPIOCTRL : origin = 0x007C00, length = 0x000180 /* GPIO control registers */ <<<<<<<<< THIS ONE
GPIODAT : origin = 0x007F00, length = 0x000030 /* GPIO data registers */ <<<<<<<<< AND THIS ONE

CLK_CFG : origin = 0x05D200, length = 0x000100 <<<<<<<<< AND THIS ONE
CPU_SYS : origin = 0x05D300, length = 0x000100 <<<<<<<<< AND THIS ONE
}

SECTIONS
{
/* Allocate program areas: */
.cinit : > FLASHA | FLASHB | FLASHC | FLASHD | FLASHE |
...
...
...

/* Allocate uninitalized data sections: */
.stack : > M01SARAM | LS05SARAM PAGE = 1
...
...
...
/* Initalized sections go in Flash */
.econst : > FLASHA | FLASHB | FLASHC | FLASHD | FLASHE |
...
...
...
.reset : > RESET, PAGE = 0, TYPE = DSECT /* not used, */

GpioCtrlRegsFile : > GPIOCTRL, PAGE = 1 <<<<<<<<<<<<< AND THIS ONE
GpioDataRegsFile : > GPIODAT, PAGE = 1 <<<<<<<<<<<<< AND THIS ONE
ClkCfgRegsFile : > CLK_CFG, PAGE = 1 <<<<<<<<<<<<< AND THIS ONE
CpuSysRegsFile : > CPU_SYS, PAGE = 1 <<<<<<<<<<<<< AND THIS ONE :)
}
//==============================================================================

After this addition, my main function contains this:
...
...
...
InitPeripheralClocks();
InitGpio();
GPIO_SetupPinMux(31, GPIO_MUX_CPU1, 0);
GPIO_SetupPinOptions(31, GPIO_OUTPUT, GPIO_PUSHPULL);
...
...
...

Then i can use this functions:
GPIO_WritePin(31, 0); // Turn on
GPIO_WritePin(31, 1); // Turn off LED
for Led manipulation.

All these functions definitions copied into my main.c file. Although I dont use other structures/regs for now. I supose it might be solution for all :
#10247-D creating output section "....." without a SECTIONS specification

//======
Answer like this would save me few days of searching (learning?) on the net, so here you have, use you time for something harder :)

Best regards!!!
Michał

// EDIT ==============================================================================

Actually you shouldn't have to edit anything.

Just include file 'F2807x_Headers_BIOS.cmd' from controlSUITE in your project, along with default 'TMS320F28075.cmd'

They works complementary.

At least in my app :)
Best regards!!!
mike

0 Devin Cottier over 10 years ago in reply to user4403062

TI__Guru 60865 points

Hi Michał,

Thank you for the information. Hopefully someone will find it useful!

C2000™︎ microcontrollers

C2000 microcontrollers forum

warning: creating output section "AdcMirrorFile" without a SECTIONS