OCEOS/oceos kernel/initialisation - Revision history

Okhoruzhyy: /* Introduction */

2022-03-15T10:48:20Z

Introduction

← Older revision		Revision as of 10:48, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:~~Oceos initialisation graph~~.png\|518x602px\|~~frameless~~\|left\|OCEOS Initialization]]		[[File:oceos_initialisation_graph.png\|518x602px\|none\|left\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* Introduction */

2022-03-15T10:47:49Z

Introduction

← Older revision		Revision as of 10:47, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:Oceos initialisation graph.png\|518x602px\|~~frame~~\|left\|OCEOS Initialization]]		[[File:Oceos initialisation graph.png\|518x602px\|frameless\|left\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* Introduction */

2022-03-15T10:47:27Z

Introduction

← Older revision		Revision as of 10:47, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:Oceos initialisation graph.png\|518x602px\|~~none~~\|left\|OCEOS Initialization]]		[[File:Oceos initialisation graph.png\|518x602px\|frame\|left\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* Introduction */

2022-03-15T10:46:52Z

Introduction

← Older revision		Revision as of 10:46, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:Oceos initialisation graph.png\|518x602px\|~~thumb~~\|left\|OCEOS Initialization]]		[[File:Oceos initialisation graph.png\|518x602px\|none\|left\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* OCEOS Initialization */

2022-03-15T10:46:19Z

OCEOS Initialization

← Older revision		Revision as of 10:46, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:Oceos initialisation graph.png\|518x602px\|thumb\|~~center~~\|OCEOS Initialization]]		[[File:Oceos initialisation graph.png\|518x602px\|thumb\|left\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* OCEOS Initialization */

2022-03-15T10:45:58Z

OCEOS Initialization

← Older revision		Revision as of 10:45, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:Oceos initialisation graph.png\|thumb\|center\|OCEOS Initialization]]		[[File:Oceos initialisation graph.png\|518x602px\|thumb\|center\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* OCEOS Initialization */

2022-03-15T10:44:19Z

OCEOS Initialization

← Older revision		Revision as of 10:44, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
	[[File:Oceos initialisation graph.png\|thumb\|~~left~~\|OCEOS Initialization]]		[[File:Oceos initialisation graph.png\|thumb\|center\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* Introduction */

2022-03-15T10:43:42Z

Introduction

← Older revision		Revision as of 10:43, 15 March 2022
Line 20:		Line 20:

	It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.		It is suggested that these names be defined in the application header that is also used for application function declarations. To avoid possible confusion between names, it is suggested also that all task names start with 't_', all mutex names with 'm_', etc.
			[[File:Oceos initialisation graph.png\|thumb\|left\|OCEOS Initialization]]

	==<span style="color:#0000ff">API Functions</span>==		==<span style="color:#0000ff">API Functions</span>==

Okhoruzhyy: /* oceos_init() */

2022-03-14T12:21:12Z

oceos_init()

← Older revision		Revision as of 12:21, 14 March 2022
Line 54:		Line 54:
	This function sets up sysMetaPtr and init_meta_ptr and must have completed successfully before tasks etc. can be created.		This function sets up sysMetaPtr and init_meta_ptr and must have completed successfully before tasks etc. can be created.

	It disables interrupts and leaves them disabled, they will be re-enabled to the previous level after all tasks etc. have been created and oceos_init_finish() has completed successfully.<br>		It disables interrupts and leaves them disabled, they will be re-enabled to the previous level after all tasks etc. have been created and [[OCEOS/oceos kernel/initialisation#oceos_init_finish()\|oceos_init_finish()]] has completed successfully.<br>
	<span style="color:#1b7ac2">'''Prototype'''</span><br>		<span style="color:#1b7ac2">'''Prototype'''</span><br>
	<syntaxhighlight lang="C">		<syntaxhighlight lang="C">

Okhoruzhyy: /* oceos_CPU_sleep() */

2022-03-14T12:20:03Z

oceos_CPU_sleep()

← Older revision		Revision as of 12:20, 14 March 2022
Line 341:		Line 341:
	Puts CPU in sleep mode.<br>		Puts CPU in sleep mode.<br>
	User must to be sure that interrupts are enabled.		User must to be sure that interrupts are enabled.

	<span style="color:#1b7ac2">'''Prototype'''</span><br>		<span style="color:#1b7ac2">'''Prototype'''</span><br>
	<syntaxhighlight lang="C">		<syntaxhighlight lang="C">