The Test Menu is the screen that is first displayed when the PARTNER-CTR Debugger or CTR test unit is turned on.
It is a substitute for the HOME Menu for CTR devices and has minimal functionality.
When the HOME Button is pressed while an application is running, that application is suspended and this menu is displayed.
However, to return to the Test Menu, the application must handle a press of the HOME Button.
The following operations are possible on the Test Menu.
| Input | Feature |
|---|---|
| START | Start DevMenu. When there is a suspended application, terminate that application, and then start DevMenu. |
| A | Launches an application from a CTR Card. If you are using PARTNER-CTR Debugger and running debugger software, you cannot launch applications from CTR Cards; go to CTR > Card Control and clear Card Emulation Control. |
| X | Terminates a suspended application, if there is one. |
| B | Launches the System Settings. This operation is not available when the system mode is dev1 (text also does not appear in the lower screen). |
| L Button | When there is a suspended application, the upper and lower screens (if stereoscopic view is enabled, there will be a total of three screen images) are output to the SD Card as a set. This will have no effect if an SD Card is not inserted. The filename will be (time on system clock in yyyymmdd_hhmm format)_(Screen)_(Index).bmp. It will be saved to the Capture folder on the SD Card. Note: (Screen): UL = upper screen, left eye image; UR = upper screen, right eye image; LO = lower screen(index): A five-digit numerical sequence incremented each time a save is performed from the time the development menu is started. Each image in a set of images has the same index number. |
| HOME | Returns to a suspended application, if there is one. |
| POWER Button | Terminates a suspended application, if there is one. |
The following information is displayed on the upper screen.
The following information is displayed on the lower screen.
The development menu is a minimal implementation. Apart from its appearance, it has a number of restrictions that do not apply to the actual HOME Menu.
Its implementation for Sleep Mode differs from that of the HOME Menu, and in some places it does not properly handle situations in which timing is critical. As a result, if the system enters Sleep Mode during an application transition (this includes closing the application and returning), it may not recover.
If an application is loaded and executed while the development menu is displayed, execution will tentatively stop at the start of the application. Therefore, this allows debugging from a closer point to startup than when starting an application from the HOME Menu and using ATTACH. If the POWER Button is pressed after starting an application from the development menu, it may stop execution at the nn::applet::Enable function.
Features that cause the application to exit, such as a jump to the System Settings, are not available when loaded from or attached to the debugger. To verify such features, either start them using the A Button or run them on development hardware, rather than loading them from or attaching them to the debugger.
Application region-checking is not performed by the Test Menu.
Enable function.
CONFIDENTIAL