Differences
This shows you the differences between two versions of the page.
|
ass:laboratoare:02:tasks:03 [2023/07/17 18:51] radu.mantu created |
ass:laboratoare:02:tasks:03 [2024/08/06 20:33] (current) florin.stancu [03. Booting Linux from the FIT image] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== 03. [??p] Booting Linux from the FIT image ==== | + | ==== 03. Booting Linux from the FIT image ==== |
| <note important> | <note important> | ||
| Line 5: | Line 5: | ||
| </note> | </note> | ||
| - | == Step 1: List eMMC partition contents == | + | === 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. | 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. | ||
| Line 36: | Line 36: | ||
| </code> | </code> | ||
| - | == Step 2: Load the FIT image in RAM == | + | === Task B - Load the FIT image in RAM === |
| - | In order for U-Boot to parse the FIT image and extract its components at their respective ''load'' addresses, we first need to bring the entire FIT image in main memory. Choose a load address where the FIT image will not overlap with any of the three components when unpacked, or with the relocated **bl33** code. | + | In order for U-Boot to parse the FIT image and extract its components at their respective ''load'' addresses, we first need to bring the entire FIT image in main memory (use the ''load'' or ''fatload'' command for this). Choose a load address where the FIT image will not overlap with any of the three components when unpacked, or with the relocated **bl33** code, e.g. ''>= 50000000''. |
| <note tip> | <note tip> | ||
| - | If ''fatls'' listed the contents of a FAT partition's directory, what can we use to load a file from said FAT partition? Seek ''help'' if in doubt. | + | Run ''help load'' for syntax. |
| </note> | </note> | ||
| - | == Step 3: Investigate contents of FIT image == | + | === Task C - Investigate contents of FIT image === |
| This step is optional, but gives us the chance to see how U-Boot can parse a DTB file and extract its information. In the following example we assume that you've loaded the FIT image at address ''0x 8000 0000'' (i.e.: 2GB, 1GB offset in RAM): | This step is optional, but gives us the chance to see how U-Boot can parse a DTB file and extract its information. In the following example we assume that you've loaded the FIT image at address ''0x 8000 0000'' (i.e.: 2GB, 1GB offset in RAM): | ||
| Line 84: | Line 84: | ||
| </note> | </note> | ||
| - | == Step 4: Boot Linux from the FIT image == | + | === Task D - Boot Linux from the FIT image === |
| + | |||
| + | Use the ''bootm <your_itb_addres>'' command, passing it the starting address of the FIT image. \\ | ||
| - | Use the ''bootm'' command, passing it the starting address of the FIT image. \\ | ||
| And now things get interesting... | And now things get interesting... | ||
