06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

t_create pSOS+ <strong>System</strong> <strong>Calls</strong><br />

Return Value<br />

Error Codes<br />

Notes<br />

ARM<br />

960<br />

x86<br />

On ARM processors, the stack is extended by 100 bytes.<br />

On 960 processors, the stack is extended by 48 bytes.<br />

On 486 processors, and on 386 processors used with an 80387 FPU,<br />

the stack size is extended by 108 bytes.<br />

This system call returns 0 on success, or an error code on failure.<br />

Hex Mnemonic Description<br />

0x08 ERR_OBJTFULL Node’s object table full.<br />

0x0E ERR_NOTCB Exceeds node's maximum number of tasks. The<br />

maximum number of tasks that can be<br />

simultaneously active is defined by the<br />

kc_ntask entry in the pSOS+ Configuration<br />

Table.<br />

0x0F ERR_NOSTK Insufficient space in Region 0 to create stack.<br />

0x10 ERR_TINYSTK Stack size too small.<br />

0x11 ERR_PRIOR Priority out of range.<br />

1. Internally, the pSOS+ kernel treats a task name as a 32-bit integer. However,<br />

when the application calls the kernel through the pSOS+ C language API, it<br />

passes the task name as a four-byte character array.<br />

2. A null name (for example, 32-bit binary 0) should not be used, because it may<br />

be used elsewhere as an alias for the running task.<br />

3. The pSOS+ kernel does not check for duplicate task names. If duplicate names<br />

exist, a t_ident() call can return the tid of any task with the duplicate name.<br />

1-136 <strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!