Difference between revisions of "Developing the software for the target (DIVELK)"
(→Building the U-Boot and the Linux kernel separately) |
(→Building the U-Boot and the Linux kernel separately) |
||
| Line 15: | Line 15: | ||
Please refer to the following links for the specific instructions describing these operations: | Please refer to the following links for the specific instructions describing these operations: | ||
| − | {{oldid| | + | {{oldid|8318|Building_U-Boot_(DIVELK)}} |
{{oldid|6822|Building Linux kernel (DIVELK)}} | {{oldid|6822|Building Linux kernel (DIVELK)}} | ||
Latest revision as of 09:11, 2 November 2018
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
 As the DIVELK kit is based on Yocto, the implementation of the MVM follows the approach described here. As such, the reading of this section is highly recommended. |
Yocto BSP image and associated SDKs[edit | edit source]
The Yocto BSP image includes the U-Boot binary, the Linux kernel image, and the target root file system. For more information about how to build it and how to build the associated SDKs, please refer to this page.
Building the U-Boot and the Linux kernel separately[edit | edit source]
The U-Boot and the Linux kernel are typically built without invoking the Yocto build system.
Please refer to the following links for the specific instructions describing these operations:
