Robotic & Microcontroller Educational Knowledgepage - Network of Excellence

ARM 9: Creating dynamic libraries

at312466 (at312466@undisclosed.example.com) — 2026-10-12T21:29:36+00:00

ARM 9: Creating dynamic libraries As shown in ARM 2: Calling C functions from Assembly, one can link object files from assembly sources against the C standard library in order to use some common functions. It is also possible to create custom dynamic libraries (shared objects) from both C and assembly sources.

ARM 6: Reading current time from system

at312466 (at312466@undisclosed.example.com) — 2026-10-12T21:05:06+00:00

ARM 6: Reading current time from system In this scenario, you will ask the operating system for the current time using a syscall, passing it a pointer to a structure allocated on the stack. Prerequisites Know about UNIX time format. Scenario

ARM 4: Conditionally Executed Instructions

at312466 (at312466@undisclosed.example.com) — 2026-10-12T21:02:11+00:00

ARM 4: Conditionally Executed Instructions While technically conditional branches are a subset of all conditionally executed instructions, they will be omitted in this scenario. Instead, emphasis will be laid on conditional set, select and compare.

ARM 2: Calling C functions from Assembly

at312466 (at312466@undisclosed.example.com) — 2026-10-12T20:56:09+00:00

ARM 2: Calling C functions from Assembly Programs written entirely in assembly are rarely seen today. For the sake of convenience, external libraries written in other languages can be linked against your assembly sources. Similarly, it is also possible to create a library from your assembly files so that you can use it in other languages as well.

Programming for ARM in GNU assembly prerequisites and introduction - [Debugging]

at312466 (at312466@undisclosed.example.com) — 2026-10-12T20:43:15+00:00

Programming for ARM in GNU assembly prerequisites and introduction Sections Program in assembly consists as usually of sections, which are pieces of code or data that are then managed by the linker during ELF executable creation, and by the OS loader during program startup. Program may consist of multiple sections, they are defined with:

screenshotgdb.png - created

at312466 (at312466@undisclosed.example.com) — 2026-10-12T19:52:00+00:00

Kiirstardi juhend - [Ühenduse kontrollimine]

karllall (karllall@undisclosed.example.com) — 2026-10-12T13:01:25+00:00

Kiirstardi juhend Arenduskeskkonna seadistamine Laadige alla ja installige VS Code siit Python'i installimine Windowsi Laadige alla Python siit Enne installimist veenduge, et Add Python to PATH valik oleks märgitud Python'i installimine Linuxi Avage terminal ja kontrollige, kas teil on Python 3 installitud.

Quickstart guide - [Verifying the connection]

karllall (karllall@undisclosed.example.com) — 2026-10-12T13:00:31+00:00

Quickstart guide Configuring the development environment Download and install VS Code from here Install Python on Windows Download Python from here Before installing check the Add Python to PATH Install Python on Linux Open terminal and check if you have Python 3 installed.

MultiASM - Exercises and Laboratory Book

pczekalski (pczekalski@undisclosed.example.com) — 2026-10-12T10:07:23+00:00

MultiASM - Exercises and Laboratory Book Current version of PDF Book Generate new PDF document! Writing rules ToDo list for an orange book Versions Authors Basic information: * Project Information * Introduction Exercises, laboratories and scenarios: * Programming in Assembler for Embedded Systems * VREL NextGen Management and IoT Developer Software * User's Guide * Introduction to the Arduino Uno programming in Assembler * SUT AVR Assembler Laboratory Node Hardwar…

- Moved to en:multiasm:exercisesbook:arm:sut:start

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:38:34+00:00

RTU's ARM laboratory - Laboratory route: scenario links show their titles (ARM10-ARM21) automatically

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:34:06+00:00

RTU's ARM laboratory This chapter provides a progressive laboratory course in AArch64 assembly using Raspberry Pi 5 and 64-bit Raspberry Pi OS. It accompanies Programming in Assembler for Mobiles and ARM in the MultiASM coursebook. The core labs need only a Pi and a terminal; GPIO is an optional extension.

ARM 21: Integration project: a bounded sample analyser - Renumbered as ARM21, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:33:51+00:00

ARM 21: Integration project: a bounded sample analyser This project combines the skills from the preceding scenarios into a single, tested command-line tool. C handles input, allocation and printing, while the analysis itself is written in AArch64 assembly.

ARM 20: Optional hardware laboratory: an LED through Linux GPIO - Renumbered as ARM20, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:33:50+00:00

ARM 20: Optional hardware laboratory: an LED through Linux GPIO Pi 5 header GPIO is managed through RP1 and Linux drivers. Legacy Raspberry Pi GPIO register addresses and Arduino DDR/PORT code are not interchangeable with this interface. The C bridge owns a libgpiod version-2 line request; assembly implements the control loop and obeys AAPCS64. No physical-address mapping or privileged register access is needed

ARM 19: Measuring performance and avoiding busy waits - Renumbered as ARM19, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:33:07+00:00

ARM 19: Measuring performance and avoiding busy waits Wall-clock time includes interruptions by other processes. Cache state, CPU frequency and temperature affect results. An instruction-count reduction need not produce the same speedup. Correctness comes first: benchmark exactly the implementation that passed the tests. Clock readings surround many calls, and printing and result validation occur outside each timed region.

ARM 18: Neon vectorisation with a correct scalar tail - Renumbered as ARM18, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:33:06+00:00

ARM 18: Neon vectorisation with a correct scalar tail A Neon register is 128 bits: v0.4s describes four 32-bit lanes. fadd interprets those lanes as floats; add would perform integer addition on the bits. Processing four elements consumes 16 bytes. For a length not divisible by four, finish with scalar operations and never load a full vector beyond the valid range.

ARM 17: Scalar floating-point calculations - Renumbered as ARM17, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:32:29+00:00

ARM 17: Scalar floating-point calculations The AAPCS64 passes these named double arguments in d0–d2 and returns the result in d0. Scalar s and d registers are views of the vector register bank. scvtf converts a signed integer's value; fmov between general and floating-point registers can copy a bit pattern. Those operations are not interchangeable. Floating-point arithmetic rounds, and many decimal fractions are not exactly representable in binary.

ARM 16: Linux input, output and error handling - Renumbered as ARM16, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:32:28+00:00

ARM 16: Linux input, output and error handling A raw Linux system call returns a negative error number on failure; this differs from the libc convention of returning -1 and setting errno. read returns zero at end of file, or a positive byte count. A successful read need not fill the buffer and does not append a zero terminator. A write may transfer fewer bytes than requested. Advance the pointer and retry only the remaining bytes.

ARM 15: Byte strings and bounded conversion - Renumbered as ARM15, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:32:00+00:00

ARM 15: Byte strings and bounded conversion A C string ends in a zero byte. A byte buffer need not contain that terminator. bounded_len returns the first zero-byte index or capacity if no terminator exists within the readable region. It never reads when capacity is zero. Its return equal to capacity means no terminator was found, not that one exists at that address.

ARM 14: Functions, the stack and C interoperability - Renumbered as ARM14, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:31:59+00:00

ARM 14: Functions, the stack and C interoperability For these integer/pointer interfaces, x0–x7 pass arguments and x0 returns the result. Caller-saved temporaries include x0–x17; avoid x18, which has a platform-defined role. Preserve any x19–x29 registers you change.

ARM 13: Memory, arrays and addressing modes - Renumbered as ARM13, reformatted to the scenario template (Start, Steps, FAQ), lab references turned into links

mcp_agent (mcp_agent@undisclosed.example.com) — 2026-10-12T09:31:28+00:00

ARM 13: Memory, arrays and addressing modes An address identifies a byte. Consecutive 32-bit elements are four bytes apart. ldrsw loads a signed 32-bit value and extends its sign to 64 bits; ldr w3 instead clears the upper half of x3. [x0], #4 accesses the old pointer then advances it. Initialised writable data belongs in