Difference between revisions of "Developing the software for the target (DIVELK)"
(→Building the U-Boot and the Linux kernel separately) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
}} | }} | ||
| − | == | + | ==U-Boot and Linux kernel== |
| − | |||
| − | |||
| − | |||
The U-Boot and the Linux kernel are typically built without invoking the Yocto build system. | 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: | Please refer to the following links for the specific instructions describing these operations: | ||
| + | *[[Building U-Boot (DIVELK)]] | ||
| + | *[[Building Linux kernel (DIVELK)]] | ||
| − | + | ==Root file systems and SDKs== | |
| − | + | The root file systems and the associated SDKs are built with the tools provided by the Yocto build system. For more details please refer to [[Building root file systems and SDKs with Yocto (DIVELK)|this page]]. | |
Revision as of 12:52, 11 September 2017
| 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. |
U-Boot and Linux kernel[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:
Root file systems and SDKs[edit | edit source]
The root file systems and the associated SDKs are built with the tools provided by the Yocto build system. For more details please refer to this page.
