Difference between revisions of "APT:ReceiveParameter"

From 3dbrew
Jump to navigation Jump to search
Line 65: Line 65:
 
=Description=
 
=Description=
 
This returns the current parameter data from NS state, from the source process which set the parameters. Once finished, NS will clear a flag in the NS state so that this command will return an error if this command is used again if parameters were not set again.
 
This returns the current parameter data from NS state, from the source process which set the parameters. Once finished, NS will clear a flag in the NS state so that this command will return an error if this command is used again if parameters were not set again.
 +
This is called when the second [[APTU:Initialize|Initialize]] event is triggered. It returns a signal type indicating why it was triggered.
 +
 +
{| class="wikitable" border="1"
 +
|-
 +
!  Type
 +
!  Description
 +
|-
 +
| 0x1
 +
| Application just started
 +
|-
 +
| 0x3
 +
| ?
 +
|-
 +
| 0xB
 +
| Returned to application ?
 +
|-
 +
| 0xC
 +
| Exiting application ?
 +
|-
 +
| 0xF
 +
| ?
 +
|}

Revision as of 12:14, 1 February 2014

Request

Index Word Description
0 Header code [0x000D0080]
1 AppID
2 Parameter buffer size, max size is 0x1000(this can be zero).


The following is located 0x100-bytes after the beginning of the above command buffer:

Index Word Description
0 (Size<<14) | 2
1 Output parameter buffer ptr

Response

Index Word Description
0 Header code
1 Result code
2 Unknown
3 Signal type (?)
4 Actual parameter buffer size, this is <= to the the input size.
5 Value 0x10
6 Handle from the source process which set the parameters, this handle is likely used for shared memory(this can be 0x0).
7 (Size<<14) | 2
8 Output parameter buffer ptr

Description

This returns the current parameter data from NS state, from the source process which set the parameters. Once finished, NS will clear a flag in the NS state so that this command will return an error if this command is used again if parameters were not set again. This is called when the second Initialize event is triggered. It returns a signal type indicating why it was triggered.

Type Description
0x1 Application just started
0x3 ?
0xB Returned to application ?
0xC Exiting application ?
0xF ?