AnsweredAssumed Answered

STM3240G-EVAL .hex and .map output discrepancy

Question asked by van_wyk.herman on Apr 9, 2013
Latest reply on Apr 9, 2013 by van_wyk.herman
Hi all,
When I build my application, the output .hex file indicates that the FLASH data footprint (.text) is 0xBB04, but according to the .map file it should only be 0xB220. How is this possible?
I am using the YAGARTO toolchain on a STM3240G-EVAL.

As seen here below, the map file indicates .text to be 0xB220
.text           0x08000000     0xb220
 *(.isr_vector)
 .isr_vector    0x08000000      0x188 startup_stm32f4xx.o
                0x08000000                __isr_vector

Here are the compiler and linker options I am using:
MCFLAGS = -mthumb -mcpu=$(MCU)
 
ASFLAGS = $(MCFLAGS) -g -Wa,-amhls=$(<:.s=.lst) $(ADEFS)
CPFLAGS = $(MCFLAGS) $(OPT) -g -Wall -ffunction-sections -Wa,-ahlms=$(<:.c=.lst) $(DEFS)
LDFLAGS = $(MCFLAGS) -pedantic -nostartfiles -T$(LDSCRIPT) -Wl,-Map=$(FULL_PRJ).map,--cref,--gc-sections,--no-warn-mismatch $(LIBDIR)
LDFLAGS +=  -Wl,--start-group $(ULIBS) -Wl,--end-group
 
# Generate dependency information
CPFLAGS += -MD -MP -MF .dep/$(@F).d

I also attached the output .hex file, .map file and makefile.

Any suggestions as to what might be wrong?

Thanks,

H

Attachments

Outcomes