A fast and easily customised operating system
for ARM devices
OS_FSControl 2
Programmer's Reference Manuals
» Part 15 – SWI Calls
» OS
» OS_FSControl
» OS_FSControl 2
OS_ FSControl 2
(SWI &29)
| Entry | |
|---|---|
| R0 | 2 |
| R1 | pointer to command tail |
| R2 | currently active object pointer to write |
| R3 | pointer to command name |
| Exit | |
|---|---|
| R0 | Preserved |
| R1 | Preserved |
| R2 | Preserved |
| R3 | Preserved |
Use
The purpose of this call is to inform the Operating System and current application, that a new application is starting.
Notes
Although registers are preserved, the call may not return.
This SWI allows you to fake starting an application. It
- Issues OS_UpCall 256 to inform the current application – if the upcall is claimed then the error “Unable to start application”.
- Issues Service_NewApplication to inform modules. If the service is claimed, then the error cannot be returned to you (as your application will now have been killed) so the error Unable to start application" is passed to [[OS_GenerateError?, which results in the error being sent to your parent’s "error handler]].
- Unless the exit handler is below memory limit? then all handlers below memory limit are reset to their defaults (OS_ReadDefaultHandler).
- The currently active object pointer is set; the current time and command tail are set (OS_WriteEnv).
See also
- Currently Active Object Pointer
- Error Handler?
- Exit Handler
- Memory Limit Handler?
- OS_FSControl
- OS_GenerateError
- OS_ReadDefaultHandler
- OS_UpCall 256
- Service_NewApplication