http://ocw.cs.pub.ro/courses/ 2026-05-18T08:22:33+03:00 http://ocw.cs.pub.ro/courses/ http://ocw.cs.pub.ro/courses/lib/tpl/arctic/images/favicon.ico text/html 2025-08-05T18:33:41+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2025/02/tasks/01?rev=1754408021&do=diff 01. Preparing the Linux μImage There are three vital components that are required to successfully boot Linux on ARM: * Kernel image: This should be self-evident :P * Flattened Device Tree: A blob (.dtb) of compiled hierarchical data that the kernel parses to identify hardware elements; * RootFS: A file system that can be mounted at / in order to load the init executable. Here, we will use a ramdisk image (which will be **surprise pause** stored in RAM!). text/html 2025-08-06T11:42:05+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2025/02/tasks/02?rev=1754469725&do=diff 02. Placing the FIT on the board's eMMC There are many ways to make the FIT image available to U-Boot. For this task we chose a method that may seem roundabout, but can serve as a starting point toward making our board's configuration persistent across resets (i.e.: no longer using SDP each time we restart it.) text/html 2025-08-05T13:07:40+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2025/02/tasks/03?rev=1754388460&do=diff 03. Booting Linux from the FIT image Start up your board. Use uuu to supply it with a valid firmware image package: uuu -b spl flash.bin Connect to the serial cable (the DEBUG one), then open a terminal (recall: /dev/ttyACM0 on Linux -- usually!), e.g. using picocom (don't forget to set baudrate to 115200!) and power on the board via the USB-C cable!