This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I am using Tornado 1.0.1 for the Hitachi SH2 with GNU compiler, linker & assembler and am having problems with the coffHexSh.exe binary utility. Using the GNU linker command file (shown below), the coffHexSh program is transferring both the PCOMMON section and the .data section from the binary COFF SH file to the HEX file. We only want the .data section to be transferred. Does anyone know how to prevent the PCOMMON section from being transferred to the HEX file? Thank you in advance for your help. /******** BEGIN GNU Linker Command File ****/ ROM_TEXT_ADRS = 0x00008050 ; RAM_LOW_ADRS = 0x00C01000 ; SRAM_START_ADRS = 0x00400000; MEMORY { /* code and constant space */ rom : o = 0x00008000, l = 928k /* data space */ sram0 : o = 0x00400000, l = 256k sram1 : o = 0x00C01000, l = 252k } SECTIONS { .apphead 0x00008000: { *(.apphead); } > rom .text (ROM_TEXT_ADRS) : { *(.text) *(.strings) *(.cksum) _etext = . ; } > rom PCOMMON (SRAM_START_ADRS) : { c:/tornado/target/config/xc/ap/ap_init.o(COMMON) } > sram0 .data (RAM_LOW_ADRS) : { *(.data) *(.ctors) *(.dtors) _edata = . ; } > sram1 .bss : { _bss_start = . ; *(.bss) *(COMMON) _end = . ; } > sram1 } /******** END GNU Linker Command File ****/ Teri McManus e-mail: mailto:teri_mcmanus@trimble.com ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |