3. Assembly Language. Altium TriCore

The TASKING VX-toolset TriCore is a software development toolset for the TriCore family of microcontrollers. It includes a C compiler, an assembler, a linker, a debugger and a set of libraries. The toolset supports the ISO-C standard and adds extra possibilities to program the special functions of the TriCore architecture.

PDF

Document

Chapter 3. Assembly Language

This chapter describes the most important aspects of the TASKING assembly language for TriCore. For a complete overview of the architecture you are using, refer to the target's core Architecture Manual (for example the TriCore2 Architecture Manual [2002, Infineon]).

3.1. Assembly Syntax

An assembly program consists of statements. A statement may optionally be followed by a comment.

Any source statement can be extended to more lines by including the line continuation character (\) as the last character on the line. The length of a source statement (first line and continuation lines) is only limited by the amount of available memory.

Mnemonics and directives are case insensitive. Labels, symbols, directive arguments, and literal strings are case sensitive.

The syntax of an assembly statement is:

[label[:]] [instruction | directive | macro_call] [;comment]

label

A label is a special symbol which is assigned the value and type of the current program location counter. A label can consist of letters, digits and underscore characters (_). The first character cannot be a digit. A label which is prefixed by whitespace (spaces or tabs) has to be followed by a colon (:). The size of an identifier is only limited by the amount of available memory.

Examples:

LAB1: ; This label is followed by a colon and

; can be prefixed by whitespace

LAB1 ; This label has to start at the beginning

; of a line

instruction directive macro_call

An instruction consists of a mnemonic and zero, one or more operands. It must not start in the first column.

Operands are described in

Section 3.3, Operands of an Assembly Instruction

The instructions are described in the target's core Architecture Manual.

With directives you can control the assembler from within the assembly source.

Except for preprocessing directives, these must not start in the first column.

Directives are described in

Section 3.9, Assembler Directives and Controls

A call to a previously defined macro. It must not start in the first column. See

Section 3.10, Macro Operations .

Comment, preceded by a ; (semicolon).

comment

You can use empty lines or lines with only comments.

Key features

C compiler
C++ compiler
assembler
linker
debugger
other utilities

Frequently asked questions

The TASKING VX-toolset for TriCore is a software development toolset for the TriCore family of microcontrollers. It includes a C compiler, C++ compiler, assembler, linker, debugger and other utilities.

The TASKING VX-toolset for TriCore supports the ISO-C standard and adds extra possibilities to program the special functions of the target.

The TASKING VX-toolset for TriCore is designed to help you develop embedded applications for the TriCore architecture.

User questions

Linda N.

How can I prevent the compiler from automatically managing special function registers (SFRs)?

Use the -msfr=none compiler option to disable automatic SFR management. Alternatively, the --no-tasking-sfr option provides similar functionality.

Linda N.

How can I selectively control which SFRs the compiler manages?

Use the -msfr=list option, specifying the SFRs you want the compiler to handle. Any SFR omitted from the list will not be automatically managed.

Linda N.

What alternative methods exist for accessing SFRs without compiler-managed access?

Direct memory access using SFR addresses, inline assembly, or custom macros/functions for SFR manipulation are viable alternatives.

Linda N.

What is the syntax of the LSL?

The documentation provides structural information and elements related to LSL syntax, such as the structure of a Linker Script File, Lexical Syntax (identifiers, expressions and definitions), and LSL Definitions. For a complete understanding of the syntax, consult specific LSL documentation.

Linda N.

What are the methods to disable automatic Special Function Register (SFR) code generation?

The --no-tasking-sfr option prevents the compiler from automatically generating code that accesses Special Function Registers (SFRs). An equivalent effect can be achieved using the -msfr=none option, which instructs the compiler not to manage any SFRs automatically. Additionally, the -msfr=list option allows specifying exactly which SFRs are handled automatically, while manual access can be performed using direct memory addresses, inline assembly, or macros.