[ARM bare metal program][1] ARM bare metal program development environment construction

[1] Environment Construction

Install the cross-compilation toolchain (arm-linux-gcc4.4.3)

See Bolg for details.

Cross-compilation basics

arm-linux-gcc common commands

1. Check the search path of header files and library files:

arm-linux-gcc -print-libgcc-file-name

2.arm-linux-gcc common commands

arm-linux-gcc -g -c led.S

//-c is for assembly-only operation -g adds debugging information

arm-linux-ld -Tled.lds -o led.elf led.o

//Perform link operation

arm-linux-readelf -a led.elf

//View the elf file header information

arm-linux-objdump -D -S led.elf

//Perform disassembly operations

arm-linux-objcopy -O binary led.elf led.bin

//Convert to binary file

Makefile Basics

basic structure

target: prerequisites

    command

Using variables

- Definition: obj=func1.o func2.o

- Use: $(obj)

Special variables

- $^: represents all dependent files

- $@: represents the target

- $< : represents the first dependent file

General rules (examples)

%.o : %.c

    arm-linux-gcc -o %@ -g -c %^

Linker script

SECTIONS {

        . = 0x30008000;

        . = ALGN(4);

        .text :

        {

            start.o(.text)

            *(.text)

        }

        . = ALGN(4);

        .data :

        {

            *(.data)

        }

        bss_start=.

        . = ALGN(4);

        .bss :

        {

            *(.bss)

        }

}

Set the starting link address

. = 0x30008000;

Set 4-byte alignment

. = ALGN(4);

Using variables

bss_start=.

Code snippet header file

start.o(.text)

*(.text)

Eclipse Integrated Development Environment

- arm-linux-gcc

- arm-linux-gdb

- JLink_Linux

- eclipse

Note: Environment variables are configured in /etc/profile.