3: Getting Started with Assembly Language Programming
- Page ID
- 76102
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \) \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)\(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\) \(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\)\(\newcommand{\AA}{\unicode[.8,0]{x212B}}\)
Chapter 3 Getting Started with Assembly Language Programming
The first step in learning any new language is being able to create a working template program in that language, then creating a program to read input and produce output. Being able to produce I/O necessary to be able to tell if a program is working, so a properly working I/O program forms the basis for being able to implement for larger and more complex programs. This I/O program is often called a “Hello World” program, and the purpose of this chapter is to create this first program. This will involve the following steps:
- creating a template file that can be used as a starting point for any program the user will create
- writing assembly language source files using printf and scanf for a program to read input and print output for a program
- using an assembler and linker to translate their source programs into ARM executable programs
- running the programs from a shell command
- finally, using the gbdtui to view the program execution and state