This shows you the differences between two versions of the page.
ass:laboratoare:02:tasks:03 [2023/07/18 12:35] radu.mantu |
ass:laboratoare:02:tasks:03 [2024/08/06 20:33] (current) florin.stancu [03. Booting Linux from the FIT image] |
||
---|---|---|---|
Line 38: | Line 38: | ||
=== Task B - 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> | ||
Line 86: | Line 86: | ||
=== Task D - Boot Linux from the FIT image === | === Task D - Boot Linux from the FIT image === | ||
- | Use the ''bootm'' command, passing it the starting address of the FIT image. \\ | + | Use the ''bootm <your_itb_addres>'' command, passing it the starting address of the FIT image. \\ |
And now things get interesting... | And now things get interesting... | ||