deac/osd-contiki
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Merge pull request #616 from hexluthor/listing

Browse source 
CC2538: Add a Makefile rule to generate a final assembly listing.
This commit is contained in:
George Oikonomou 2014-04-17 22:13:52 +01:00
parent d34ee59e97 23a3a7f004
commit 49bf7cc241
2 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
cpu/cc2538/Makefile.cc2538
View file

@ -3,6 +3,7 @@ CPP = arm-none-eabi-cpp
LD = arm-none-eabi-gcc LD = arm-none-eabi-gcc
AR = arm-none-eabi-ar AR = arm-none-eabi-ar
OBJCOPY = arm-none-eabi-objcopy OBJCOPY = arm-none-eabi-objcopy
OBJDUMP = arm-none-eabi-objdump
NM = arm-none-eabi-nm NM = arm-none-eabi-nm
ifndef SOURCE_LDSCRIPT ifndef SOURCE_LDSCRIPT
@ -19,6 +20,7 @@ LDFLAGS += -T $(LDSCRIPT)
LDFLAGS += -Wl,--gc-sections,--sort-section=alignment LDFLAGS += -Wl,--gc-sections,--sort-section=alignment
LDFLAGS += -Wl,-Map=$(@:.elf=-$(TARGET).map),--cref,--no-warn-mismatch LDFLAGS += -Wl,-Map=$(@:.elf=-$(TARGET).map),--cref,--no-warn-mismatch
OBJCOPY_FLAGS += -O binary --gap-fill 0xff OBJCOPY_FLAGS += -O binary --gap-fill 0xff
OBJDUMP_FLAGS += --disassemble --source --disassembler-options=force-thumb
### Are we building with code size optimisations? ### Are we building with code size optimisations?
ifeq ($(SMALL),1) ifeq ($(SMALL),1)
@ -82,6 +84,9 @@ CUSTOM_RULE_LINK=1
%.bin: %.elf %.bin: %.elf
$(OBJCOPY) $(OBJCOPY_FLAGS) $< $@ $(OBJCOPY) $(OBJCOPY_FLAGS) $< $@
%.lst: %.elf
$(OBJDUMP) $(OBJDUMP_FLAGS) $< > $@
### We don't really need the .hex and .bin for the .$(TARGET) but let's make ### We don't really need the .hex and .bin for the .$(TARGET) but let's make
### sure they get built ### sure they get built
%.$(TARGET): %.elf %.hex %.bin %.$(TARGET): %.elf %.hex %.bin

2
platform/cc2538dk/README.md
View file

@ -246,6 +246,8 @@ If you want to upload the compiled firmware to a node via the serial boot loader
For the `cc2538-demo`, the comments at the top of `cc2538-demo.c` describe in detail what the example does. For the `cc2538-demo`, the comments at the top of `cc2538-demo.c` describe in detail what the example does.
To generate an assembly listing of the compiled firmware, run `make cc2538-demo.lst`. This may be useful for debugging or optimizing your application code. To intersperse the C source code within the assembly listing, you must instruct the compiler to include debugging information by adding `CFLAGS += -g` to the project Makefile and rebuild by running `make clean cc2538-demo.lst`.
Node IEEE/RIME/IPv6 Addresses Node IEEE/RIME/IPv6 Addresses
----------------------------- -----------------------------