Miosix Processes Quick Start - Revision history

Fede.tft at 08:36, 19 May 2026

2026-05-19T08:36:11Z

← Older revision		Revision as of 08:36, 19 May 2026
Line 61:		Line 61:

	Note that the process loader depends on filesystem support, so the filesystem is a dependency of process support.		Note that the process loader depends on filesystem support, so the filesystem is a dependency of process support.
	Also note ~~that~~ if you read the [[Miosix code size optimization]] page~~, that~~ the kernel requires C++ exceptions when enabling processes, so you can't disable ~~that~~. You can, however, disable exceptions in the userspace programs (look for the ''PROC_OPT_EXCEPT'' instead of ''~~PROC_OPT_EXCEPT~~'' in ''Makefile.inc'').		Also a note if you read the [[Miosix code size optimization]] page: the kernel requires C++ exceptions when enabling processes, so you can't disable exceptions in the kernel. You can, however, disable exceptions in the userspace programs (look for the ''PROC_OPT_EXCEPT'' instead of ''OPT_EXCEPT'' in ''Makefile.inc'').

	There's one more step: select an appropriate linker script. This is done in the board-specific ''Makefile.inc'' file. This can be found in ''config/board/<your board name>/Makefile.inc''. Since this tutorial is based on the stm32f746zg_nucleo board, that would be [https://github.com/fedetft/miosix-kernel/blob/master/miosix/config/board/stm32f746zg_nucleo/Makefile.inc config/board/stm32f746zg_nucleo/Makefile.inc].		There's one more step: select an appropriate linker script. This is done in the board-specific ''Makefile.inc'' file. This can be found in ''config/board/<your board name>/Makefile.inc''. Since this tutorial is based on the stm32f746zg_nucleo board, that would be [https://github.com/fedetft/miosix-kernel/blob/master/miosix/config/board/stm32f746zg_nucleo/Makefile.inc config/board/stm32f746zg_nucleo/Makefile.inc].

Fede.tft at 08:34, 19 May 2026

2026-05-19T08:34:37Z

← Older revision		Revision as of 08:34, 19 May 2026
Line 61:		Line 61:

	Note that the process loader depends on filesystem support, so the filesystem is a dependency of process support.		Note that the process loader depends on filesystem support, so the filesystem is a dependency of process support.
			Also note that if you read the [[Miosix code size optimization]] page, that the kernel requires C++ exceptions when enabling processes, so you can't disable that. You can, however, disable exceptions in the userspace programs (look for the ''PROC_OPT_EXCEPT'' instead of ''PROC_OPT_EXCEPT'' in ''Makefile.inc'').

	There's one more step: select an appropriate linker script. This is done in the board-specific ''Makefile.inc'' file. This can be found in ''config/board/<your board name>/Makefile.inc''. Since this tutorial is based on the stm32f746zg_nucleo board, that would be [https://github.com/fedetft/miosix-kernel/blob/master/miosix/config/board/stm32f746zg_nucleo/Makefile.inc config/board/stm32f746zg_nucleo/Makefile.inc].		There's one more step: select an appropriate linker script. This is done in the board-specific ''Makefile.inc'' file. This can be found in ''config/board/<your board name>/Makefile.inc''. Since this tutorial is based on the stm32f746zg_nucleo board, that would be [https://github.com/fedetft/miosix-kernel/blob/master/miosix/config/board/stm32f746zg_nucleo/Makefile.inc config/board/stm32f746zg_nucleo/Makefile.inc].
	In this file, you should uncomment ~~whatver~~ linker script is selected, and uncomment the linker script whose name ends with processes:		In this file, you should uncomment whatever linker script is selected, and uncomment the linker script whose name ends with processes:

	<source lang="bash">		<source lang="bash">

Fede.tft at 21:51, 17 May 2026

2026-05-17T21:51:25Z

← Older revision		Revision as of 21:51, 17 May 2026
Line 1:		Line 1:
	This tutorial assumes you just completed the quick start guide either for [[Linux Quick Start\|Linux]], [[Windows Quick Start\|Windows]] or [[MacOS Quick Start\|MacOS]]. The screenshots in this tutorial are taken from a Linux computer, but the procedure is the same regardless of your host OS.		This tutorial assumes you just completed the unikernel quick start guide either for [[Linux Quick Start\|Linux]], [[Windows Quick Start\|Windows]] or [[MacOS Quick Start\|MacOS]]. The screenshots in this tutorial are taken from a Linux computer, but the procedure is the same regardless of your host OS.

	In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of our hello world example application in a userspace process.		In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of our hello world example application in a userspace process.

Fede.tft at 21:48, 17 May 2026

2026-05-17T21:48:14Z

← Older revision		Revision as of 21:48, 17 May 2026
Line 2:		Line 2:

	In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of our hello world example application in a userspace process.		In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of our hello world example application in a userspace process.

			In this tutorial we'll break the previous example program that blinked an LED and printed ''Hello world'' in two parts: we'll blink the LED in kernelspace form a kernel thread, while we'll print ''Hello world'' in userspace form a proccess.

	= Starting from a template =		= Starting from a template =

Fede.tft at 21:45, 17 May 2026

2026-05-17T21:45:59Z

Show changes

Fede.tft: Created page with "This tutorial assumes you just completed the quick start guide either for Linux, Windows or MacOS. The screenshots in this tutorial are taken from a Linux computer, but the procedure is the same regardless of your host OS. In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of..."

2026-05-17T21:02:08Z

Created page with "This tutorial assumes you just completed the quick start guide either for Linux, Windows or MacOS. The screenshots in this tutorial are taken from a Linux computer, but the procedure is the same regardless of your host OS. In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of..."

New page

This tutorial assumes you just completed the quick start guide either for [[Linux Quick Start|Linux]], [[Windows Quick Start|Windows]] or [[MacOS Quick Start|MacOS]]. The screenshots in this tutorial are taken from a Linux computer, but the procedure is the same regardless of your host OS.

In the quick start you just followed, you used Miosix as a unikernel, thus writing your application in kernelspace. To use Miosix as a fluid kernel, we'll see how we can move part of our hello world example application in a userspace process.

= Starting from a template =

In a directory of your choice, create a ''hello_processes'' directory and download a copy of the Miosix kernel as a subdirectory using git. As a refresher, on Linux that would be:

<source lang="bash">
mkdir hello_processes
cd hello_processes
git clone https://github.com/fedetft/miosix-kernel.git
</source>

This time, however, we won't use the perl script ''init_project_out_of_git_tree.pl'' and instead manually copy '''the content of''' the ''miosix-kernel/templates/processes'' in our propject directory.