Constraints

• Timing
• Cost
• Weight
• Power
• Memory
• Computation power

Organization

Course structure

Lab assignments

• Labs are done individually
• Assessment:
• Must show a working solution to one of the teachers
• Code upload on Studium => plagiarism check

Lab topics

• State machines
• RTOS Basics
• Working with external hardware
• Verification with Frama-C

Lab kits

• Distributed during first lab
• Yours for the duration of the course
• If something breaks => inform teacher/TAs
• Property of Uppsala University

Course schedule

• On TimeEdit (look for 1DT106)
• On Studium (left menu)
• For each lab => 2 sessions
• Marked as Lab X.1 and Lab X.2
• You can work individually between the sessions

Examination

• March 11th, 2024
• On INSPERA
• 60 Points in total
• [30, 39] => 3
• [40, 49] => 4
• [50, 60] => 5

Hardware

RP2040

• Dual-core ARM Cortex-M0+
• 264kB on-chip SRAM
• 2MB on-board flash
• 2x UART, 2x SPI, 2x I2C, 16x PWM
• Programmable I/O
• USB-drive bootloader

Lab software

Pico SDK

• SDK provided by Raspberry Pi Ltd.
• Consists of:
• Higher-level libraries (pico_xxx)
• Runtime support (e.g. pico_standard_link)
• Hardware support libraries (hardware_xxx)
• Hardware struct/register libraries

An example application

main.c

		#include "pico/stdlib.h"

		const static uint led_pin = 0; 

		int main() {
			gpio_init(led_pin); 
			gpio_set_dir(led_pin, GPIO_OUT); 

			for(;;){
				gpio_xor_mask(1 << led_pin); 
				sleep_ms(500); 
			}
		}
	

CMakeLists.txt

		cmake_minimum_required(VERSION 3.13)

		include(pico_sdk_import.cmake)
		project(blinky) 
		
		pico_sdk_init() 

		add_executable(blinky main.c)

		pico_add_extra_outputs(blinky) 
		target_link_libraries(blinky pico_stdlib)
	

Building the application

		$ mkdir build 
		$ cd build 
		$ cmake .. 
		$ make 
	

Going further

• Look at the recommend reading
• https://raspberrypi.github.io/pico-sdk-doxygen/index.html