http://ocw.cs.pub.ro/courses/ 2026-06-08T07:49:24+03:00 http://ocw.cs.pub.ro/courses/ http://ocw.cs.pub.ro/courses/lib/tpl/arctic/images/favicon.ico text/html 2025-08-03T10:11:29+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2024/02/tasks/01?rev=1754205089&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 structured binary blob of data that the kernel parses to identify hardware elements. * RootFS: A file system that can be mounted at / in order to load init. Here, we will use a ramdisk image. text/html 2025-08-03T10:11:36+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2024/02/tasks/02?rev=1754205096&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-03T10:11:41+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2024/02/tasks/03?rev=1754205101&do=diff 03. Booting Linux from the FIT image uuuuuu Task A - List eMMC partition contents First things first: let's check if the flashing process was succesful. Reload your FIP using uuu and get back into the U-Boot shell. u-boot=> # list MMC devices (or rather, the slots) u-boot=> mmc list FSL_SDHC: 0 (eMMC) FSL_SDHC: 1 u-boot=> # select MMC device 0 u-boot=> mmc dev 0 switch to partitions #0, OK mmc0(part 0) is current device u-boot=> # show partitions on currently selected MMC device u-boot=… text/html 2025-08-03T10:11:48+03:00 http://ocw.cs.pub.ro/courses/ass/labs-2024/02/tasks/04?rev=1754205108&do=diff 04. Debuging (aka. the "fun" part) If you faithfully followed the instructions up to this point, you'll be glad to know that you are precisely 3 bugs away from having a working Linux-based system. So, let's get started: Bug A - bootm decompression error After executing bootm, you may notice some successful loads of the FDT and ramdisk, but the following error during the kernel loading process: