Digital Systems

Copyright © 2017–2023 J. M. Spivey
Revision as of 12:41, 2 May 2023 by Mike (talk | contribs) (→‎Lectures)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The micro:bit (or electronic teabag[1])

Digital systems is a course about how computers work, from logic gates and latches at the bottom, to concurrent processes at the top (running under a simple operating system), with time spent on machine-level programming in the middle. For an easy start, we will begin in the middle with small programs written in machine code.

  • In Hilary Term, we will study low-level programming with the help of a tiny computer, the BBC micro:bit, which includes an ARM-based microcontroller as its processor. Starting in assembly language and moving on to C, we will learn about the instructions that make up machine code, including arithmetic, branching, memory access, and subroutines. We will also (vitally for embedded systems) learn about controlling I/O devices, such as the buttons and lights on the micro:bit and the serial interface that allows it to talk to a host computer. Once a program reaches a certain degree of complexity, it is no longer sufficient to wait in a tight loop for an event to happen, and we will study the hardware and software aspects of solutions to this problem: using interrupts to respond to external events, and an operating system to structure the program as a family of concurrent processes, each responsible for one part of the task.
  • In Trinity Term, we will study the elements of computer hardware, building up from gates and latches to architectural elements such as registers, adders and decoders, and finally a paper model of a processor able to execute a selection of ARM instructions, supported by an architectural simulator.


Hilary Term


  • 16 lectures: Tuesdays and Thursdays at 10, Lecture Theatre B.

Although some elements of the lectures will be automatically recorded, the dynamic blend of slides, calculations on the whiteboard, software demonstrations, computer hardware shown via live video and online instrumentation, and problems solved by the lecturer and class working together means that not all elements will be captured, and the recordings may therefore be almost useless. In addition, the content of each lecture may change in response to questions from the audience. Participants who cannot attend lectures in person may find it best to follow the course by reading the extensive lecture notes available on this site.

Lab sessions

In the Software Lab on Level 6 of the Thom Building, Department of Engineering Science – the same place as you had practicals for Functional Programming. In addition to the official lab times noted above, the lecturer will be available at the same time and in the same place in weeks 3 and 4 to help those who want to get an early start with assembly language programming.

  • Informal sessions: Monday 10–12, weeks 3 and 4.
  • Official sessions: Monday 10–12, weeks 5–8.

There will be no lab sessions in Trinity Term.


Your college will organise tutorials in this subject, as in others. To support them, there are four problem sheets this term, two on machine-level programming, one on I/O devices, and one on embedded operating systems.

Trinity Term


  • 8 lectures, Tuesdays and Thursdays at 10, Lecture Theatre B.


Two more tutorials are suggested, with a problem sheet on digital design, and another on processor architecture.


Information about the course is provided on several other pages.

And last of all:

  • There's a website for my book Bare Metal micro:bit, containing expanded versions of the lab materials for the course, with explanations appended.



  1. So called because the board dangles from its USB cable like a teabag dangling from its string.