PPT Slide

Software Tool Flow

CL6x command invokes all tools

ASM6x

LNK6x

.obj

.out

.c

Link.cmd

.sa

Compiler

AsmOptimizer

Text

Editor

.asm

Previous slide

Next slide

Back to first slide

View graphic version

The software tool flow begins with source code, and the text editor from which we could either create a C source, a linear assembly source, or a regular hand assembly source, which is a .asm file.

For a C source file, the extension is .c. We pass that source code through the compiler. For linear assembly source, we use the assembly optimizer, which creates an assembly language file. The assembly language file is then passed through the ASM6x assembler to create an object or .obj file. At this point, there are no physical addresses tied to either code or data, and the code is totally portable.

At the linker stage, the physical addresses for our code and data are assigned. The linker command file consists of two sections. The first is the memory map of the system which defines the type of memories we are using and where they reside. The second part of the linker command file is where we actually place our code and data in specific sections.

After linking, a .out or output file exists which can be debugged. All of these tools, the compiler, the assembly optimizer, the assembler and the linker are invoked by the CL6x command shell.