Pandora Wiki - User contributions [en]

SuperZaxxon Knobs

2016-06-22T21:41:38Z

Notaz: ducoment some config files and stuff

This page lists various configuration file tweaks that can be done on the default Pandora's OS. Some of these can be configured through the GUI, some can't.

== General ==
* /etc/pandora/conf/cpu.conf - CPU overclocking configuration (minimum/maximum rate, etc, in MHz)
* /etc/pandora/conf/dsp.conf - DSP overclocking configuration
* /etc/pandora/conf/dss_fir/* - coefficient tables for the hardware scaler filter
* /etc/pandora/my_lid_is_broken - if this file exists, pressing any key will unblank pandora's screen (otherwise the screen won't unblank while the lid is closed)

== WiFi ==
* /etc/pandora/conf/wl1251 - sourced by the wifi init script (if exists), may contain:
** ps_rate_threshold=<number> - while this rate is exceeded (bytes/s), power saving is disabled to improve performance (default 30000)
** use_fw_ps=<Y|N> - Y - power saving is only managed by wifi firmware, N - forcefully toggled by driver (default Y)
** long_doze_mode=<1|0> - if 1, additional wifi power saving is enabled ("long doze mode") which saves ~30mW, but ping times are increased and some router compatibility is lost (default 0)

== Battery charging ==
Some things can be configured in /etc/pandora/conf/eventmap
* start_capacity - start charging when capacity falls this low. Setting this to lower values may improve battery longevity

Assembly Code Optimization

2016-04-30T17:41:51Z

Notaz: /* NEON */

== Assembly code optimization on the Cortex-A8 ==
This guide presents specific optimization techniques for the [[ARM]] Cortex-A8 processor and its dual-issue, in-order pipeline.

== Use the ARMv7 movw/movt instructions ==
Newer ARM processors allow loading 32-bit values as two 16-bit immediates. The movw instruction loads the lower 16 bits, and movt loads the upper 16 bits. The movw instruction clears the upper 16 bits, so that 16-bit values can be loaded using a single instruction. The movt instruction does not affect the lower bits.

On older ARM processors, it was common to load 32-bit values with a PC-relative load. This should be avoided because it may result in a cache miss.

== Branch Prediction ==
There is a one-cycle stall in instruction fetch when a branch is predicted taken. It is therefore preferable to structure code so that the most likely code path is the one where the branch is not taken.

Unconditional branches may be mispredicted, and load instructions which follow branches may be decoded and cause cache accesses. Avoid placing load instructions after branches unless you intend the CPU to prefetch the addresses they reference.

The branch predictor has a call/return stack for jumps which reference r14 or stack operations using r13 which load the program counter. For best performance, make sure any pop, mov pc,lr or bx lr jumps to the same location as was set by the matching bl instruction. For non-return jumps, use a register other than r14.

Although instructions are decoded in pairs, the branch predictor can only predict one branch target per cycle. If you have a conditional branch which is immediately followed by another branch, and the first branch is likely to be taken, place a no-operation instruction between the branches to prevent decoding and prediction of the second branch. Inserting NOPs is detrimental if the first branch is infrequently taken.

== Dual-Issue Restrictions ==
Only one branch instruction can issue per cycle. Only one load or store instruction can issue per cycle. Instructions which write to the same register can not issue together.

There is a one-cycle delay before any written register can be used as the address of a subsequent load or store instruction. There is a one-cycle delay before any written register can be used by an instruction which performs a shift or rotation on that register.

There is one cycle delay before the result of a load can be used. In the aforementioned cases involving subsequent shift or rotate instructions, or the address of a load or store instruction, the total delay is two cycles.

Stores occur at the end of the pipeline and store instructions can issue in the same cycle as another instruction which writes the same register. Similarly, conditional branches can issue in the same cycle as flag-setting instructions because the branch is not resolved until the following cycle. In all other cases, instructions can not issue together if the second instruction depends on the results of the first.

== Instruction pairing restrictions following a branch ==
The Cortex-A8 processor normally fetches two instructions per cycle and the branch predictor tests each against the global history buffer. However, there is only one entry in the branch target buffer for each pair of instructions. Therefore, branch instructions, and certain instructions which resemble branches, may adversely affect branch prediction when present in pairs. To reduce the risk of branch misprediction, avoid pairing branch instructions with the following:

* Branch instructions
* Load instructions, whether or not they write r15
* Arithmetic/logic instructions which do not set flags and do not have an immediate value, whether or not they write r15

Flag-setting instructions can be used to avoid this restriction. Additionally, MOV instructions that do not have immediate values can be replaced with ADD, SUB, ORR, or EOR instructions using zero as an immediate value.

== Code alignment ==
Code alignment should be used with caution. Alignment has the potential to increase performance, but may be detrimental in some circumstances.

Because the instruction decoder always fetches 64-bit aligned words from the level-1 instruction cache, aligning code can improve instruction fetch and decode. However, the global history buffer of the branch predictor is indexed by the low bits of the instruction address. Excessive code alignment can result in a suboptimal distribution of entries in the branch history tables and increase branch misprediction. Additionally, the speculative prefetch may retrieve and decode instructions used as padding, even if those instructions are never executed. The types of instructions used as padding will affect the branch predictor as stated above, and this may affect the prefetch of code into the instruction cache.

== NEON ==
As the manual states, passing data from NEON (and VFP) back to ARM takes at least 20 cycles, but there are some tricks that can be used. The vmov instruction itself that is passing the data will not cause any stalls (provided the needed NEON register is already available), the stall will actually happen on any ARM instruction that follows instead (including branches). This means that:
* Multiple "vmov.32 rX, dY[Z]" can be done back-to-back and only incur one stall after the whole sequence
* Additional NEON instructions can be issued after "vmov" without stalling (with enough instructions the stall can be completely avoided)
* Additional unrelated NEON instructions can be issued before "vmov" (to hide the latency of instruction that produces the source register data)

Even though the VFP is not pipelined, the VFP vldr instructions are. "vldr s0, [r0]" will be faster than "vld1.32 {d0[0]}, [r0]" (2 vs 3 cycles, vldr also gives more flexible addressing mode). The same can't be said about "vmov sX, sY", it waits for all previous instructions to complete before issuing.

[[Category:Development]]
[[Category:Optimization]]
[[Category:Chipset]]

Assembly Code Optimization

2016-04-30T17:39:12Z

Notaz: /* NEON */

== Assembly code optimization on the Cortex-A8 ==
This guide presents specific optimization techniques for the [[ARM]] Cortex-A8 processor and its dual-issue, in-order pipeline.

== Use the ARMv7 movw/movt instructions ==
Newer ARM processors allow loading 32-bit values as two 16-bit immediates. The movw instruction loads the lower 16 bits, and movt loads the upper 16 bits. The movw instruction clears the upper 16 bits, so that 16-bit values can be loaded using a single instruction. The movt instruction does not affect the lower bits.

On older ARM processors, it was common to load 32-bit values with a PC-relative load. This should be avoided because it may result in a cache miss.

== Branch Prediction ==
There is a one-cycle stall in instruction fetch when a branch is predicted taken. It is therefore preferable to structure code so that the most likely code path is the one where the branch is not taken.

Unconditional branches may be mispredicted, and load instructions which follow branches may be decoded and cause cache accesses. Avoid placing load instructions after branches unless you intend the CPU to prefetch the addresses they reference.

The branch predictor has a call/return stack for jumps which reference r14 or stack operations using r13 which load the program counter. For best performance, make sure any pop, mov pc,lr or bx lr jumps to the same location as was set by the matching bl instruction. For non-return jumps, use a register other than r14.

Although instructions are decoded in pairs, the branch predictor can only predict one branch target per cycle. If you have a conditional branch which is immediately followed by another branch, and the first branch is likely to be taken, place a no-operation instruction between the branches to prevent decoding and prediction of the second branch. Inserting NOPs is detrimental if the first branch is infrequently taken.

== Dual-Issue Restrictions ==
Only one branch instruction can issue per cycle. Only one load or store instruction can issue per cycle. Instructions which write to the same register can not issue together.

There is a one-cycle delay before any written register can be used as the address of a subsequent load or store instruction. There is a one-cycle delay before any written register can be used by an instruction which performs a shift or rotation on that register.

There is one cycle delay before the result of a load can be used. In the aforementioned cases involving subsequent shift or rotate instructions, or the address of a load or store instruction, the total delay is two cycles.

Stores occur at the end of the pipeline and store instructions can issue in the same cycle as another instruction which writes the same register. Similarly, conditional branches can issue in the same cycle as flag-setting instructions because the branch is not resolved until the following cycle. In all other cases, instructions can not issue together if the second instruction depends on the results of the first.

== Instruction pairing restrictions following a branch ==
The Cortex-A8 processor normally fetches two instructions per cycle and the branch predictor tests each against the global history buffer. However, there is only one entry in the branch target buffer for each pair of instructions. Therefore, branch instructions, and certain instructions which resemble branches, may adversely affect branch prediction when present in pairs. To reduce the risk of branch misprediction, avoid pairing branch instructions with the following:

* Branch instructions
* Load instructions, whether or not they write r15
* Arithmetic/logic instructions which do not set flags and do not have an immediate value, whether or not they write r15

Flag-setting instructions can be used to avoid this restriction. Additionally, MOV instructions that do not have immediate values can be replaced with ADD, SUB, ORR, or EOR instructions using zero as an immediate value.

== Code alignment ==
Code alignment should be used with caution. Alignment has the potential to increase performance, but may be detrimental in some circumstances.

Because the instruction decoder always fetches 64-bit aligned words from the level-1 instruction cache, aligning code can improve instruction fetch and decode. However, the global history buffer of the branch predictor is indexed by the low bits of the instruction address. Excessive code alignment can result in a suboptimal distribution of entries in the branch history tables and increase branch misprediction. Additionally, the speculative prefetch may retrieve and decode instructions used as padding, even if those instructions are never executed. The types of instructions used as padding will affect the branch predictor as stated above, and this may affect the prefetch of code into the instruction cache.

== NEON ==
As the manual states, passing data from NEON (and VFP) back to ARM takes at least 20 cycles, but there are some tricks that can be used. The vmov instruction itself that is passing the data will not cause any stalls (provided the needed NEON register is already available), the stall will actually happen on any ARM instruction that follows instead (including branches). This means that:
* Multiple "vmov.32 rX, dY[Z]" can be done back-to-back and only incur one stall after the whole sequence
* Additional NEON instructions can be issued after "vmov" without stalls (with enough instructions the stall can be completely avoided)
* Additional unrelated NEON instructions can be issued before "vmov" (to hide the latency of instruction that produces the source register data)

Even though the VFP is not pipelined, the VFP vldr instructions are. "vldr s0, [r0]" will be faster than "vld1.32 {d0[0]}, [r0]" (2 vs 3 cycles, vldr also gives more flexible addressing mode). The same can't be said about "vmov sX, sY", it waits for all previous instructions to complete before issuing.

[[Category:Development]]
[[Category:Optimization]]
[[Category:Chipset]]

Assembly Code Optimization

2016-04-30T17:14:08Z

Notaz:

== Assembly code optimization on the Cortex-A8 ==
This guide presents specific optimization techniques for the [[ARM]] Cortex-A8 processor and its dual-issue, in-order pipeline.

== Use the ARMv7 movw/movt instructions ==
Newer ARM processors allow loading 32-bit values as two 16-bit immediates. The movw instruction loads the lower 16 bits, and movt loads the upper 16 bits. The movw instruction clears the upper 16 bits, so that 16-bit values can be loaded using a single instruction. The movt instruction does not affect the lower bits.

On older ARM processors, it was common to load 32-bit values with a PC-relative load. This should be avoided because it may result in a cache miss.

== Branch Prediction ==
There is a one-cycle stall in instruction fetch when a branch is predicted taken. It is therefore preferable to structure code so that the most likely code path is the one where the branch is not taken.

Unconditional branches may be mispredicted, and load instructions which follow branches may be decoded and cause cache accesses. Avoid placing load instructions after branches unless you intend the CPU to prefetch the addresses they reference.

The branch predictor has a call/return stack for jumps which reference r14 or stack operations using r13 which load the program counter. For best performance, make sure any pop, mov pc,lr or bx lr jumps to the same location as was set by the matching bl instruction. For non-return jumps, use a register other than r14.

Although instructions are decoded in pairs, the branch predictor can only predict one branch target per cycle. If you have a conditional branch which is immediately followed by another branch, and the first branch is likely to be taken, place a no-operation instruction between the branches to prevent decoding and prediction of the second branch. Inserting NOPs is detrimental if the first branch is infrequently taken.

== Dual-Issue Restrictions ==
Only one branch instruction can issue per cycle. Only one load or store instruction can issue per cycle. Instructions which write to the same register can not issue together.

There is a one-cycle delay before any written register can be used as the address of a subsequent load or store instruction. There is a one-cycle delay before any written register can be used by an instruction which performs a shift or rotation on that register.

There is one cycle delay before the result of a load can be used. In the aforementioned cases involving subsequent shift or rotate instructions, or the address of a load or store instruction, the total delay is two cycles.

Stores occur at the end of the pipeline and store instructions can issue in the same cycle as another instruction which writes the same register. Similarly, conditional branches can issue in the same cycle as flag-setting instructions because the branch is not resolved until the following cycle. In all other cases, instructions can not issue together if the second instruction depends on the results of the first.

== Instruction pairing restrictions following a branch ==
The Cortex-A8 processor normally fetches two instructions per cycle and the branch predictor tests each against the global history buffer. However, there is only one entry in the branch target buffer for each pair of instructions. Therefore, branch instructions, and certain instructions which resemble branches, may adversely affect branch prediction when present in pairs. To reduce the risk of branch misprediction, avoid pairing branch instructions with the following:

* Branch instructions
* Load instructions, whether or not they write r15
* Arithmetic/logic instructions which do not set flags and do not have an immediate value, whether or not they write r15

Flag-setting instructions can be used to avoid this restriction. Additionally, MOV instructions that do not have immediate values can be replaced with ADD, SUB, ORR, or EOR instructions using zero as an immediate value.

== Code alignment ==
Code alignment should be used with caution. Alignment has the potential to increase performance, but may be detrimental in some circumstances.

Because the instruction decoder always fetches 64-bit aligned words from the level-1 instruction cache, aligning code can improve instruction fetch and decode. However, the global history buffer of the branch predictor is indexed by the low bits of the instruction address. Excessive code alignment can result in a suboptimal distribution of entries in the branch history tables and increase branch misprediction. Additionally, the speculative prefetch may retrieve and decode instructions used as padding, even if those instructions are never executed. The types of instructions used as padding will affect the branch predictor as stated above, and this may affect the prefetch of code into the instruction cache.

== NEON ==
As the manual states, passing data from NEON (and VFP) back to ARM takes at least 20 cycles, but there are some tricks that can be used. The vmov instruction itself that is passing the data will not cause any stalls (provided the needed NEON register is already available), the stall will actually happen on any ARM instruction that follows instead (including branches). This means that:
* Multiple "vmov.32 rX, dY[Z]" can be done back-to-back and only have one stall after the whole sequence
* Additional NEON instructions can be issued after "vmov" without stalls (with enough instructions the stall can be hidden completely)
* Additional unrelated NEON instructions can be issued before "vmov" (to hide the latency of instruction that produces the source register data)

Even though the VFP is not pipelined, the VFP vldr instructions are. "vldr s0, [r0]" will be faster than "vld1.32 {d0[0]}, [r0]" (2 vs 3 cycles, vldr also gives more flexible addressing mode). The same can't be said about "vmov sX, sY", it waits for all previous instructions to complete before issuing.

[[Category:Development]]
[[Category:Optimization]]
[[Category:Chipset]]

Kernel interface

2016-02-28T16:18:28Z

Notaz: line counter, minor updates

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use kernel interface. This is the recommended way to access hardware (as opposed to GP2X style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
Buttons, keypad, touchscreen and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_PAGEUP (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses ALSA, but it has OSS emulation enabled too, so GP2X code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on OMAP3 by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

OMAP3 display subsystem is controlled by a driver known as DSS2, which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

/dev/fb2 is reserved for system use and requires root to access. Programs are free to use /dev/fb0 and /dev/fb1 as they please.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDWR);
buffer = mmap(0, 800*480*2, PROT_READ | PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Triple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Some toolchains don't have FBIO_WAITFORVSYNC defined in <linux/fb.h>, in which case you can define it in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>
=====adaptive vsync=====
Standard vsync has a problem: if the program takes slightly longer that one frame to update, calling FBIO_WAITFORVSYNC will wait for the whole next frame, wasting time. In the worst case this can halve the framerate, and the CPU ends up being not fully utilized. The program can try to combat this by measuring time since the last wait, but that is not reliable because ioctl may return long after the actual vsync as Linux may need to process other drivers or system threads before giving back control.

To solve the above issue, SZ 1.74 (kernel 3.2.78) has introduced a new ioctl:
<source lang="c">
#ifndef OMAPFB_WAITFORVSYNC_FRAME
#define OMAPFB_WAITFORVSYNC_FRAME _IOWR('O', 70, unsigned int)
#endif

static unsigned int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
OMAPFB_WAITFORVSYNC_FRAME has an unsigned int arg which is the current frame number (both an input and output). The ioctl only waits if the passed arg matches the current frame number that's maintained inside the kernel, otherwise it instantly returns. It always updates the arg to the current frame number on return.

Making 'arg' static is the easiest way to make it work, but you can keep the variable anywhere else as long as it's preserved between ioctl calls.

====line counter====
Since SZ 1.74 (kernel kernel 3.2.78) it's possible to read the LCD line counter:
<source lang="c">
#ifndef OMAPFB_GET_LINE_STATUS
#define OMAPFB_GET_LINE_STATUS _IOR('O', 71, int)
#endif

int counter;
ioctl(fd, OMAPFB_GET_LINE_STATUS, &counter);
</source>
It returns the current line number (0-479) only during the active display. During VFP, vsync and VBP it returns 0, and when the screen is off (lid closed, etc) the hardware returns 2047.

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is reserved for TV-out functionality and only usable by root, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

For some example code, see how it's implemented in [http://notaz.gp2x.de/cgi-bin/gitweb.cgi?p=sdl_omap.git;a=tree;f=src/video/omapdss;hb=HEAD pandora's SDL].

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

====gamma====
Since SZ 1.52, gamma can be controlled with another script, the same way as LCD refresh:
<source lang="c">
sudo -n /usr/pandora/scripts/op_gamma.sh 1.0
</source>
where 1.0 is the gamma level. If supplied gamma level is 0, then user defaults are used (useful to set on exit). There is also an optional -b N argument (to be specified before gamma value), where N controls black level (0-255, useful to combat LCD ghosting).

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Battery==
There is bq27500 battery monitoring chip onboard, that exports various files at /sys/class/power_supply/bq27500-0/ , for example 'capacity' tells charge percenage left. See Data_provided_by_Battery_and_Power_driver for more details. 
There are also similar directories at /sys/class/power_supply/twl4030_* that provide info while charging.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Kernel interface

2016-02-28T15:46:48Z

Notaz: adaptive vsync

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use kernel interface. This is the recommended way to access hardware (as opposed to GP2X style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
Buttons, keypad, touchscreen and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_PAGEUP (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses ALSA, but it has OSS emulation enabled too, so GP2X code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on OMAP3 by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

OMAP3 display subsystem is controlled by a driver known as DSS2, which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDWR);
buffer = mmap(0, 800*480*2, PROT_READ | PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Some toolchains don't have FBIO_WAITFORVSYNC defined in <linux/fb.h>, in which case you can define it in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>
=====adaptive vsync=====
Standard vsync has a problem: if the program takes slightly longer that one frame to update, calling FBIO_WAITFORVSYNC will wait for the whole next frame, wasting time. In the worst case this can halve the framerate, and the CPU ends up being not fully utilized. The program can try to combat this by measuring time since the last wait, but that is not reliable because ioctl may return long after the actual vsync as Linux may need to process other drivers or system threads.

To solve the above issue, kernel 3.2.78 has introduced a new ioctl:
<source lang="c">
#ifndef OMAPFB_WAITFORVSYNC_FRAME
#define OMAPFB_WAITFORVSYNC_FRAME _IOWR('O', 70, unsigned int)
#endif

static unsigned int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
OMAPFB_WAITFORVSYNC_FRAME has an unsigned int arg which is the current frame number (both an input and output). The ioctl only waits if the passed arg matches the current frame number, otherwise it instantly returns. It always updates the arg to the current frame number on return.

Making 'arg' static is the easiest way to make it work, but you can keep the variable anywhere else as long as it's preserved between ioctl calls.

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

====gamma====
Since SZ 1.52, gamma can be controlled with another script, the same way as LCD refresh:
<source lang="c">
sudo -n /usr/pandora/scripts/op_gamma.sh 1.0
</source>
where 1.0 is the gamma level. If supplied gamma level is 0, then user defaults are used (useful to set on exit). There is also an optional -b N argument (to be specified before gamma value), where N controls black level (0-255, useful to combat LCD ghosting).

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Battery==
There is bq27500 battery monitoring chip onboard, that exports various files at /sys/class/power_supply/bq27500-0/ , for example 'capacity' tells charge percenage left. See Data_provided_by_Battery_and_Power_driver for more details. 
There are also similar directories at /sys/class/power_supply/twl4030_* that provide info while charging.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Hardware Hacking

2015-02-19T18:10:30Z

Notaz: link to schematics

{{introNote|About custom hardware extensions, see also [[Kernel interface]]}}

==Complete schematics==
[http://boards.openpandora.org/page/articles.html/_/development/openhardware Available on the main website]

==Official Hackers Manual==
There is a LOT of great information in this:
[http://www.openpandora.org/downloads/PANDORA_Hackers_manual_v101.pdf Pandora Hackers Manual v1.01 by MWeston]
[http://www.openpandora.org/downloads/PANDORA_Hackers_manual_v100.pdf v1.00 by MWeston]

==Labels==
*silkprint, battery label, version label etc.
[http://www.openpandora.org/downloads/files/Pandora_Labels.zip labels]

<big>* License for the Labels and Manual:</big>

* All files and documents within this ZIP archive are free for any use (commercial and non-commercial).
*
* You can do with them whatever you want - but you have to include the original ownership of them.
*
* The files are owned by
*
* OpenPandora GmbH
* Michael Mrozek
* Schäffbräustr. 11
* 85049 Ingolstadt
* Germany
*
* EvilDragon@openpandora.org
* www.openpandora.org
*
<big>* (End Of license)</big>

==Pinouts==
Here's a list of pinouts for the various connectors and boards.

Here's a pic of the board, some of the pinouts can be seen on it. [http://pandorapress.net/files/2010/02/rev5.jpg]

==Ext Connector==
[[Image:Cable_connector pinout.png|thumb|TV cable connector]]
''What does it have?''
* UART2
* UART3
* TV out
* Stereo line out
* Stereo line in
* The UART lines can also be used as GPIO (six of them) and PWM lines (four of them).

[[EXT_Connector | EXT Connector]]

[[TV-out_cable | TV-out cable]]

==Battery==
[[Image:Battery.jpg|thumb]]
* 3.7V
* Lithium polymer single cell battery
* 4000 mAH, 4 AH
* battery cover here: [http://www.openpandora.org/images/Battery2.jpg]
* reading out battery information: [[http://pandorawiki.org/Power_modes#Data_provided_by_battery_and_power_driver]]

==Internal connections==

===LCD===
* TD043MTEA1 [http://beyondinfinite.com/lcd/Library/Toppoly/TD043MTEA1.pdf datasheet]
* LTPS (8-bit parallel input for R, G and B, with separate horizontal and vertical sync)
* 3.0V

===UART===
* UART2 and 3 are available via the EXT connector, and via internal solder pads on the latest revision
** UART2 appears to support hardware flow control with RTS/CTS lines
** On the 2.6.27 Kernel UART3 is /dev/ttyS0
** On 2.6.37 or later, UART2 is accessible through /dev/ttyO1, UART3 is on /dev/ttyO2

===GPIO===
* 6 are available on the EXT connector
* 7 are internal, 2 of which can be used as extra shoulder buttons
* 1 located on the LCD cable

===JTAG===
* Yes, 1.8V 10-pin (board label JTAG)

===I2C===
* One at 1.8V from the OMAP (board label I2C3-1V8)
* One at 2.8V (board label I2C3-2V8)

=== USB ===
* No internal USB ports

===Extra LEDs===
LED7 and LED8 can be added. You need to add FETs (Q17 and Q18) and resistors (R165, R166, R167 and R168)
See the official "Pandora Hacker Guide" from Michael Weston for more details and component values.

==Breakout Board==
[[Image:Breakoutboard.jpg|thumb|alt=Developer's breakout board|Developer's breakout board]]
This is the breakout board used by Pandora team members during development. Only a small number were made, and they are not available to the public. However a similar product (or gerber files) may be released in the future. A schematic for this board is available here: http://openpandora.ca/schematic/AV_Board_schematic.pdf

==Mods==
*[http://boards.openpandora.org/topic/11741-hmc-hardware-hack-1-keyboard-led-light/ Keyboard light]
*[http://boards.openpandora.org/index.php/topic/10722-hardware-hack-pandora-rumble-edition/?hl=%2Brumble+%2Bedition Rumble]

[[Category:Hardware]]
[[Category:Hacking]]

SGX drivers

2013-10-15T22:48:27Z

Notaz: versions

==Releases==
TI has released several SGX driver versions over time, that are based on Imagination Technologies SGX DDK for Linux, hence there are two version numbers associated with single release: TI release version and Imgtech DDK version. In each release kernel driver sources are provided and precompiled libraries providing OpenGL/OpenVG functionality. 
On pandora, different driver versions can be installed using a pnd from [http://boards.openpandora.org/index.php/topic/12233-sgx-driver-installer-beta/ this page].

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse;
|- style="background: #ececec"
!TI version
!SGX DDK version
!Date
!Notes
|-
|3.00.00.08a
|1.3.13.1607
|2009-06-30
|-
|3.00.00.09
|1.3.13.1832
|2009-11-16
|-
|3.01.00.02
|1.4.14.2514
|2009-11-30
|-
|3.01.00.06
|1.4.14.2616
|2010-04-06
|ES5 introduced
|-
|3.01.00.07
|1.4.14.2616
|2010-08-18
|-
|4.00.00.01
|1.4.14.2616
|2010-09-09
|last working ES2
|-
|4.03.00.01
|1.6.16.3977
|2011-01-27
|-
|4.03.00.02
|1.6.16.3977
|2011-03-10
|-
|4.04.00.01
|1.6.16.4117
|2011-07-27
|introduces DRI2 dependency
|-
|4.04.00.02
|1.6.16.4117
|2011-08-03
|-
|4.04.00.03
|1.6.16.4117
|2011-08-30
|-
|4.04.00.04
|?
|2011-09-29
|internal only (engineering drop) release
|-
|4.05.00.01
|1.6.16.4117
|2011-10-25
|4.04 + build fixes, no more ES2 libs
|-
|4.05.00.02
|1.6.16.4117
|2011-10-27
|-
|4.05.00.03
|1.6.16.4117
|2011-12-14
|-
|4.06.00.01
|1.7.17.783851
|2012-04-03
|-
|4.06.00.02
|1.7.17.867897
|2012-05-30
|-
|4.06.00.03
|1.7.17.867897
|2012-06-18
|-
|4.07.00.01
|1.7.17.867897
|2012-09-06
|missing libs
|-
|4.08.00.01
|1.9.19.2139099
|2012-09-28
|"tested on AM parts only"
|-
|4.08.00.02
|1.9.19.2188537
|2012-12-10
|"tested on AM parts only"
|-
|4.09.00.01
|1.9.19.2188537
|2013-05-14
|"tested on AM parts only" This release is build tested only for SUPPORT_XORG=0 against 3.8 kernel
|-
|4.10.00.01
|1.10.2359475
|2013-07-16
|"tested on AM parts only" This release is build tested only against 3.8 kernel
|}

'''Android releases'''
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse;
|- style="background: #ececec"
!TI version
!SGX DDK version
|-
|3.01.00.03
|1.5.15.2766
|-
|4.03.00.01
|?
|-
|4.03.01.00
|?
|}

==Library variants==
Each TI release comes with different set of libraries for different SGX chip revisions. TI SGX drivers use weird naming of SGX chip versions which is inconsistent with OMAP chip revision or SGX chip revision names. As various pandora versions use different OMAP chip versions, this may become rather confusing, so hopefully this table can help.
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse;"
|- style="background: #ececec"
!SoC name
!SoC version
!SGX core revision
!TI diver name
!Pandora name
|-
|OMAP3530
|ES2.1
|1.0.3
|ES2.0
|CC/256M
|-
|OMAP3530
|ES3.1
|1.2.1
|ES3.0
|Rebirth
|-
|DM3730
|ES1.x
|1.2.5
|ES5.0
|1GHz
|}

==Developer info==
===Driver operation modes===
The drivers seem to have 2 modes of operation - "framebuffer mode" and "X mode". Framebuffer mode appears to be noticeably faster in some cases, presumably because in X mode the driver is rendering to offscreen buffer and then manually blitting to X window, even if it's fullscreen. Also at the time of this writing, drivers starting from 4.04.00.01 only work in framebuffer mode due to some unsolved DRI2 issues.

The mode is selected depending on how EGL is initialized, if you use EGL_DEFAULT_DISPLAY for eglGetDisplay() and NULL window for eglCreateWindowSurface(), you get framebuffer mode, else if you pass real display and window handles to those functions, you'll get X mode. Note that in framebuffer mode the driver will fight with X for display, so you need to create fullscreen window to stop X from redrawing (SDL can be used for that).

===Double buffering in GL===
It is unclear when the driver decides to use double buffering, sometimes it does, sometimes it doesn't (the later is more usual), so there is often tearing visible. It is possible to force the driver to use double buffering by using a file named powervr.ini with this content:
<source lang="ini">
[default]
WindowSystem=libpvrPVR2D_FLIPWSEGL.so
</source>
The driver is looking for this file in current working directory first, and then in /etc/ .

==Pandora 3D acceleration capabilities (PowerVR SGX)==

This is based on the specification of the OMAP 35xx chip found at [http://www.ti.com/product/omap3530]:

The main points of interest from the below list are:
* OpenGL-ES 1.1 and 2.0
* OpenVG 1.0.1 support
* Bilinear, trilinear, and anisotropic texture filtering
* Nonsquare textures
* 2048 by 2048 maximum texture / framebuffer size
* 4x multisampling
* 16x full scene anti-aliasing
* Multithreaded shader engine with 16 simultaneous threads of execution and up to 64 simultaneous data instances.

Full feature list:
* PowerVR SGX Main Features
** 2D graphics, 3D graphics, vector graphics, and programmable GPU functions
** Tile-based architecture
** Universal scalable shader engine (USSE) – multithreaded engine incorporating vertex shader and fragment shader functionality
** Advanced shader feature set – in excess of Microsoft VS3.0, PS3.0, and OGL2.0
** Industry standard API support - OpenGL-ES 1.1 and 2.0, OpenVG 1.0.1
** Fine-grained task switching, load balancing, and power management
** Advanced geometry direct memory access (DMA) driven operation for minimum CPU interaction
** Programmable high-quality image anti-aliasing
** PowerVR SGX core MMU for address translation from the core virtual address to the external physical address (up to 4GB address range)
** Fully virtualized memory addressing for OS operation in a unified memory architecture
** 2D operations via the 3D pipeline
* SGX 3D features
** Deferred pixel shading
** On-chip tile floating point depth buffer
** 8-bit stencil with on-chip tile stencil buffer
** 8 parallel depth/stencil tests per clock
** Scissor test
** Texture support:
*** Cube map
*** Projected textures
*** 2D textures
*** nonsquare textures
** Texture formats:
*** RGBA 8888,565,1555
*** Monochromatic 8, 16, 16f, 32f, 32int
*** Dual channel, 8:8, 16:16, 16f:16f
*** Compressed textures PVR-TC1, PVR-TC2, ETC1
*** Programmable support for all YUV formats
** Resolution support:
*** Frame buffer maximum size = 2048 x 2048
*** Texture maximum size = 2048 x 2048
** Texture filtering:
*** Bilinear, tri-linear, anisotropic
*** Independent minimum and maximum control
** Anti-aliasing:
*** 4x multisampling
*** Up to 16x full scene anti-aliasing
*** Programmable sample positions
** Indexed primitive list support
*** Bus mastered
** Programmable vertex DMA
** Render to texture:
*** Including twiddled formats
*** Auto MipMap generation
** Multiple on-chip render targets (MRT). Note: Performance is limited when the on-chip memory is not available.
* Universal Scalable Shader Engine – Key Features - ''The (USSE) is the engine core of the PowerVR SGX architecture and supports a broad range of instructions.''
** Single programming model:
*** Multithreaded with 16 simultaneous execution threads and up to 64 simultaneous data instances
*** Zero-cost swapping in, and out, of threads
*** Cached program execution model
*** Dedicated pixel processing instructions
*** Dedicated video encode/decode instructions
** SIMD execution unit supporting operations in:
*** 32-bit IEEE-compliant float
*** 2-way 16-bit fixed point
*** 4-way 8-bit integer
*** 32-bit bit-wise (logical only)
** Static and dynamic flow control:
*** Subroutine calls
*** Loops
*** Conditional branches
*** Zero-cost instruction predication
** Procedural geometry:
*** Allows generation of primitives
*** Effective geometry compression
*** High-order surface support
** External data access:
*** Permits reads from main memory using cache
*** Permits writes to main memory
*** Data fence facility
*** Dependent texture reads

==Useful links==
[http://processors.wiki.ti.com/index.php/OMAP35x_Graphics_SDK_Release_Notes_Archive TI release notes] 
[http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/index.html TI release downloads]

SDL

2013-04-21T16:21:15Z

Notaz: /* Using SDL with OpenGL ES */

SDL is popular library for graphics, sound and input. This page lists some things to know when using it on pandora.

==Pandora optimized mode==
The SDL library included in pandora has a special mode (SDL internal driver) to make use of OMAP's features, like hardware scaling and double buffering. This mode is disabled by default because it doesn't support windowed mode and has some compatibility problems with some games. Information about how to use it can be found in [http://notaz.gp2x.de/cgi-bin/gitweb.cgi?p=sdl_omap.git;a=blob;f=README.OMAP;hb=HEAD this readme].

==Issues with standard SDL mode on pandora==
===Cursor drift in fullscreen mode===
When cursor is hidden (after SDL_ShowCursor(0) is called), touchscreen coordinates start to drift away over time, i.e. if you touch center of the screen, SDL may start reporting you touched the right or left edge. This is because SDL switches to relative mouse mode and starts warping the cursor when it's hidden. This is supposedly intended for 3D action games where cursor should never hit edge of screen and player should be able to look at some direction by moving the mouse to single direction as much as he wants (on pandora that can be accomplished with nubs or external mouse). Because some games rely on that feature to be functional, when not needed it should be disabled manually by:
* Setting environment variable SDL_MOUSE_RELATIVE=0, which can be easily done in launch script like this:
<source lang="bash">
export SDL_MOUSE_RELATIVE=0
./yourapp
</source>
* Not calling SDL_ShowCursor(0) and setting up [http://blogs.distant-earth.com/wp/?p=293 transparent cursor].

===Using SDL with OpenGL ES===
This can be accomplished with SDL_GetWMInfo() call to get the required handles, like:
<source lang="c">
SDL_SysWMinfo sysWmInfo;
SDL_VERSION(&sysWmInfo.version);
SDL_GetWMInfo(&sysWmInfo);
eglDisplay = eglGetDisplay((EGLNativeDisplayType)sysWmInfo.info.x11.display);
...
eglSurface = eglCreateWindowSurface(eglDisplay, eglConfig, (NativeWindowType)sysWmInfo.info.x11.window, NULL);
</source>
This will allow to use GL on the window. Note that if you use fullscreen mode, because of how SGX drivers are implemented, you may get better performance if you ''don't'' specify display/window handles to run the GL driver in framebuffer mode, like this:
<source lang="c">
eglDisplay = eglGetDisplay(EGL_DEFAULT_DISPLAY);
...
eglSurface = eglCreateWindowSurface(eglDisplay, eglConfig, NULL, NULL);
</source>
You should still create fullscreen SDL window to prevent interference with Xorg and to have working input. See also [[SGX_drivers#Driver_operation_modes|SGX driver operation modes]].

Development Tools

2013-04-21T16:20:23Z

Notaz: add a link

==Official Pandora Source Code Repository==

{{Split section|All the firmware stuff}}
The official source repository is under GIT revision control; EvilDragon is the admin, but the repo has a web based browser built in.===

Minor note on [[libpnd]] in the GIT; as skeezix (me) is too lazy to install vmware-tools for date sync, the check-in times are not accurate for libpnd; they're in order of course, but the actual date is usualyl off by many days, so don't sweat it.

The actual GIT repository is here: [http://git.openpandora.org/cgi-bin/gitweb.cgi] It is recommended that you read the [[Kernel_status#openpandora.org_git_structure | git structure]] information before going too far.

===Official Firmware images===
A Pandora specific repository is work-in-progress. From 1 July 2010, you can grab the latest ''unstable'' ready-to-be-flashed ubifs-images from [http://openpandora.org/firmware/ http://openpandora.org/firmware/] or the rootfs which you can [[Creating_a_bootable_SD_card | extract on your SD Card and boot]] from there.

Be aware that these images are the most recent cutting edge. They might have some bugs, but should include any new fixes which are yet to be released as [[Hotfixes]]. Note they are also 'un-configured' so will take you through the first-boot process. You will obtain a slightly different result if you copy your existing rootfs to an SD card and boot from there.

For ''stable'' released images, see other OpenPandora support pages. E.g. official forum [http://boards.openpandora.org/index.php/forum/41-pandora-os-superzaxxon-gnulinux/ software - pandora os] news.

==Pandora Specific Libraries==

===libpnd - the Pandora Library===

[[libpnd]] is a collection of utilities that Pandora developers may find useful, as well as including the daemons and tools for creating and working with PXML.xml based applications (pnd files or unpacked application directories.)

It is hoped the '''community will continue to expand this library''' over time!

Some stubs are included as hints .. for instance, the first dev to build a clean /dev/gpio based input library should slip it into libpnd so that others may benefit as well, avoid fragmentation and application bugs.

Continue into the main [[libpnd_hub|libpnd documentation hub]].

===Notaz SDL - improved SDL for Pandora===
[[SDL]] on this wiki 
[http://boards.openpandora.org/index.php?/topic/6231-improved-sdl-for-pandora/Notaz enhanced SDL thread, on the boards]

This library is very very useful for SDL-based ports and new games / apps.

* hardware scaling support (up and down)
* doublebuffering support (can eliminate tearing)
* vsync support (can give smooth scrolling if done right)
* keymap change with a config file (porting aid)

==Tentative Library Environment==

===Information===

'''Please note, that this information is hearsay/guesswork, and is yet to be confirmed on a production unit.'''

For Pandora [http://en.wikipedia.org/wiki/Out_of_the_box (Out-Of-The-Box)]
* [http://www.gnu.org/software/libc glibc] (at a guess, version 2.6.1 or whatever is compatible with OpenEmbedded)
* [http://www.libsdl.org/ libSDL] (also a guess, latest available version of 1.2)

For those interested in creating libraries, or needing more low-level access, read about the
[[kernel interface]].

==Tools for Pandora Software Development==

* OpenEmbedded cross-compile environment (and Angstrom distro) [http://www.elinux.org/BeagleBoard#OpenEmbedded]
* CodeSourcery gcc[http://www.codesourcery.com/gnu_toolchains/arm]
** [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313] - NB: OpenEmbedded uses the CodeSourcery 2007q3 to build the kernel, but uses gcc 4.3.1 to compile everything else.
* TI CodeComposer Studio: Free Evaluation Tools[http://focus.ti.com/dsp/docs/dspsupportaut.tsp?sectionId=3&tabId=416&familyId=44&toolTypeId=30]
* TI c6x Codegen tools for Linux[https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html]; License [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/doc/c6x/TILAW-%23180394-v1-Compiler_Clickwrap_For_OS_Community-2.html]; TI account required; this is *only* for Open Source development
* Das U-boot: The Universal Bootloader[http://www.denx.de/wiki/DULG/WebHome]
* Git - Fast Version Control System [http://git-scm.com/]; Good tuto: [http://www.trinitydesktop.org/wiki/bin/view/Developers/GIT]

===Kernel Source===

* A read-only GIT repository for the [[kernel_status|kernel]] source has been made available (November 2008); the note from ED is:

<blockquote>If anybody wants to take a sneak peek at the current kernel, we've got a read-only GIT setup which features the most recent version of the MK2 OpenPandora Kernel.
The git is: [git://git.openpandora.org/pandora-kernel.git]
Use the '''pandora-27-omap1''' branch for the moment, there will soon be a 2.6.28.</blockquote>
* [[Kernel_build_instructions|Kernel build instructions]]

===OpenGL===

(See also [[OpenGLES On the Pandora]])

* [[OpenGL ES]] 2.0 emulator for PC[http://www.imgtec.com/powervr/insider/sdkdownloads/index.asp#GLES2] ''This works both on Linux and Windows. One needs to register with imgtec before downloading.''
** To build the applications a few environment variables need to be set (tested on Ubuntu Gutsy). Note that to run them, you do need an OpenGL 2.0 compliant gfx card.
*** LD_LIBRARY_PATH needs to be set to the folder holding the important libraries, such as libEGL.so ($SDK_PATH/Builds/OGLES2/LinuxPC/Lib might be enough)
*** To run the makefiles in the Training section you need to set a PLATFORM variable to either LinuxPC or LinuxGeneric. I have had success with LinuxPC.
*** See [http://pastebin.com/f3f9f159f] for a script that you can run to set these for you.
* [http://www.imgtec.com/powervr/insider/powervr-pvrtextool.asp PowerVR Texture creation tool]
** "PVRTexTool enables conversion of standard bitmap files (e.g. BMP, JPG, PNG, TGA, etc.) to any texture type supported by POWERVR MBX or POWERVR SGX hardware including PVRTC, DXT and ETC compressed formats. Both a GUI and command line version are supplied for Windows and Linux. There are also plug-ins for Autodesk 3ds Max, Maya and Adobe Photoshop." - requires imgtec registration.
** ''Note, this is part of the main SDK'' - (Linux path to it is /SDKPackage/Utilities/PVRTexTool/)

===Packaging===
(See also [[PND_quickstart#Making_PND_files|Making PND files]] and [[Libpnd_hub#PXML.xml_and_.pnd_files|the PND package format]])

*[[Libpnd_hub#pnd_make.sh|pnd_make.sh]] - a straightforward shell script to build PND files from a prepared directory. Included with libpnd and, therefore, in all Pandoras
*[http://www.gp32x.com/board/index.php?/topic/58587-pndbuilder/ PNDbuilder] - a graphical tool to build PNDs. Can be used [http://freedomdown.squarespace.com/storage/PNDbuilder.zip in Windows] or [http://freedomdown.squarespace.com/storage/pndb.pnd on the Pandora].
*[http://www.gp32x.com/board/index.php?/topic/57350-distpnd/ distPND] - an extension to [http://docs.python.org/distutils/index.html Python's Distutils] designed to make PND files from Python source quickly and easily.

===Profiling===
If you need performance analysis, you can find a compiled version of the "perf" tool there : http://boards.openpandora.org/index.php?/topic/9809-profiling/#entry181954 
Just unzip the tool somewhere and launch it with LD_LIBRARY_PATH set. 
 
See https://perf.wiki.kernel.org/index.php/Main_Page to learn how to use it and happy optimizations!

[[Category:Development]]
[[Category:Operating system]]

SDL

2013-04-21T16:19:01Z

Notaz: /* Cursor drift in fullscreen mode */

SDL is popular library for graphics, sound and input. This page lists some things to know when using it on pandora.

==Pandora optimized mode==
The SDL library included in pandora has a special mode (SDL internal driver) to make use of OMAP's features, like hardware scaling and double buffering. This mode is disabled by default because it doesn't support windowed mode and has some compatibility problems with some games. Information about how to use it can be found in [http://notaz.gp2x.de/cgi-bin/gitweb.cgi?p=sdl_omap.git;a=blob;f=README.OMAP;hb=HEAD this readme].

==Issues with standard SDL mode on pandora==
===Cursor drift in fullscreen mode===
When cursor is hidden (after SDL_ShowCursor(0) is called), touchscreen coordinates start to drift away over time, i.e. if you touch center of the screen, SDL may start reporting you touched the right or left edge. This is because SDL switches to relative mouse mode and starts warping the cursor when it's hidden. This is supposedly intended for 3D action games where cursor should never hit edge of screen and player should be able to look at some direction by moving the mouse to single direction as much as he wants (on pandora that can be accomplished with nubs or external mouse). Because some games rely on that feature to be functional, when not needed it should be disabled manually by:
* Setting environment variable SDL_MOUSE_RELATIVE=0, which can be easily done in launch script like this:
<source lang="bash">
export SDL_MOUSE_RELATIVE=0
./yourapp
</source>
* Not calling SDL_ShowCursor(0) and setting up [http://blogs.distant-earth.com/wp/?p=293 transparent cursor].

===Using SDL with OpenGL ES===
This can be accomplished with SDL_GetWMInfo() call to get the required handles, like:
<source lang="c">
SDL_SysWMinfo sysWmInfo;
SDL_VERSION(&sysWmInfo.version);
SDL_GetWMInfo(&sysWmInfo);
eglDisplay = eglGetDisplay((EGLNativeDisplayType)sysWmInfo.info.x11.display);
...
eglSurface = eglCreateWindowSurface(eglDisplay, eglConfig, (NativeWindowType)sysWmInfo.info.x11.window, NULL);
</source>
This will allow to use GL on the window. Note that if you use fullscreen mode, because of how SGX drivers are implemented, you may get better performance if you ''don't'' specify display/window handles to run the GL driver in framebuffer mode, like this:
<source lang="c">
eglDisplay = eglGetDisplay(EGL_DEFAULT_DISPLAY);
...
eglSurface = eglCreateWindowSurface(eglDisplay, eglConfig, NULL, NULL);
</source>
You should still create fullscreen SDL window to prevent interference with Xorg and to have working input. Se also [[SGX_drivers#Driver_operation_modes|SGX driver operation modes]].

SDL

2013-04-21T16:17:35Z

Notaz: Created page with "SDL is popular library for graphics, sound and input. This page lists some things to know when using it on pandora. ==Pandora optimized mode== The SDL library included in pan..."

SDL is popular library for graphics, sound and input. This page lists some things to know when using it on pandora.

==Pandora optimized mode==
The SDL library included in pandora has a special mode (SDL internal driver) to make use of OMAP's features, like hardware scaling and double buffering. This mode is disabled by default because it doesn't support windowed mode and has some compatibility problems with some games. Information about how to use it can be found in [http://notaz.gp2x.de/cgi-bin/gitweb.cgi?p=sdl_omap.git;a=blob;f=README.OMAP;hb=HEAD this readme].

==Issues with standard SDL mode on pandora==
===Cursor drift in fullscreen mode===
When cursor is hidden (after SDL_ShowCursor(0) is called), touchscreen coordinates start to drift away over time, i.e. if you touch center of the screen, SDL may start reporting you touched the right or left edge. This is because SDL switches to relative mouse mode and starts warping the cursor when it's hidden. This is supposedly intended for 3D action games where cursor should never hit edge of screen and player should be able to look at some direction by moving the mouse to single direction as much as he wants (on pandora that can be accomplished with nubs or external mouse). Because some games rely on that feature to be functional, it should be disabled manually by:
* Setting environment variable SDL_MOUSE_RELATIVE=0, which can be easily done in launch script like this:
<source lang="bash">
export SDL_MOUSE_RELATIVE=0
./yourapp
</source>
* Not calling SDL_ShowCursor(0) and setting up [http://blogs.distant-earth.com/wp/?p=293 transparent cursor].

===Using SDL with OpenGL ES===
This can be accomplished with SDL_GetWMInfo() call to get the required handles, like:
<source lang="c">
SDL_SysWMinfo sysWmInfo;
SDL_VERSION(&sysWmInfo.version);
SDL_GetWMInfo(&sysWmInfo);
eglDisplay = eglGetDisplay((EGLNativeDisplayType)sysWmInfo.info.x11.display);
...
eglSurface = eglCreateWindowSurface(eglDisplay, eglConfig, (NativeWindowType)sysWmInfo.info.x11.window, NULL);
</source>
This will allow to use GL on the window. Note that if you use fullscreen mode, because of how SGX drivers are implemented, you may get better performance if you ''don't'' specify display/window handles to run the GL driver in framebuffer mode, like this:
<source lang="c">
eglDisplay = eglGetDisplay(EGL_DEFAULT_DISPLAY);
...
eglSurface = eglCreateWindowSurface(eglDisplay, eglConfig, NULL, NULL);
</source>
You should still create fullscreen SDL window to prevent interference with Xorg and to have working input. Se also [[SGX_drivers#Driver_operation_modes|SGX driver operation modes]].

SGX drivers

2013-04-17T21:27:04Z

Notaz:

SGX drivers

2013-04-17T21:26:25Z

Notaz: link back to the forum

Hardware documentation

2013-03-26T17:05:40Z

Notaz: /* PowerVR */

{{introNote|For adding custom extensions see [[Hardware hacking]]}}

==General==
* Official Hackers Manual ([http://www.openpandora.org/downloads/PANDORA_Hackers_manual_v101.pdf v1.01]) from OpenPandora Ltd, includes warnings about damage and warranties (or loss of).

==Board==
[[image:Board_rev5.jpg|thumb|Pandora PCB rev 5]]
The Pandora is based upon a OMAP3530 System-on-a-chip, that includes a whole family of processors in one single chip:
*[[ARM]] Cortex-A8 CPU
*PowerVR SGX graphics core
*C64x+ DSP core

===OMAP3530===

* OMAP35x: Main page on TI site[http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915]

* OMAP3530 specific page[http://focus.ti.com/docs/prod/folders/print/omap3530.html] ''This lists the features of the chip and has all the applicable Technical Documents''

* [http://focus.ti.com/pdfs/wtbu/ti_omap3430.pdf speficiations]

====Other OMAP3530 Projects====
*Always Innovating Touch Book[http://www.alwaysinnovating.com/wiki/]
*Beagle Board Resources[http://beagleboard.org/resources] As it uses the same SoC, many BB resources are also relevant for the Pandora.
*Beagle Board Google Group[http://groups.google.com/group/beagleboard]

====Cortex-A8====
This processor is part of the [[ARM]] risc cpu family[http://www.arm.com/products/processors/cortex-a/cortex-a8.php] that is licensed by a lot of hardware vendors. It has multiple command extensions as [[NEON]] (similar to MMX for x86 architecture)
*r1p1[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344b/DDI0344.pdf] ''Note: OMAP3530 uses rev1p2''
*'''UPDATE''': r2p2 Documentation [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344e/index.html] ''Note: OMAP3530 uses rev1p2''
*NEON instruction set [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204h/Bcfjicfj.html]
*NEON memory hazards[http://hardwarebug.org/2008/12/31/arm-neon-memory-hazards/]

==== PowerVR ====

* [http://khronos.org/opengles/2_X/ Official site]
** OpenGL ES 2.0, several million polygons per second.
** [[OpenGL ES 1.1 Tutorial]]
** [[SGX_drivers|SGX driver info]]

====C64x+====
Digital signal processors allow to do complex calculations within only a few cycles
*CPU and Instruction Set Reference Guide[http://focus.ti.com/lit/ug/spru732h/spru732h.pdf]
*TMS320C6000 Assembly Language Tools v 6.0 Beta User's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru186p]
*TMS320C6000 Optimizing Compiler v 6.0 Beta User's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&familyId=44&abstractName=spru187n]
*TMS320C6000 Programmer's Guide[http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&tabId=409&abstractName=spru198i]

===TPS65950 power IC===
*Main page on TI site[http://focus.ti.com/docs/prod/folders/print/tps65950.html]

==Display==
*Screen datasheet (TD043MTEA1)[http://beyondinfinite.com/lcd/Library/Toppoly/TD043MTEA1.pdf] The Pandora uses the display from the Archos 605 Media Player. However, on the Archos LCD the pinout is reversed as well as the cable having a 45 degree angle which would make it fail to line up with the Pandora LCD cable in the lid. --[http://boards.openpandora.org/index.php?/topic/3114-replacement-lcds/page__p__53657#entry53657]

==Status LEDs==

Meaning of the LEDs from left to right according to [http://boards.openpandora.org/index.php?/topic/325-led-function-documented/page__view__findpost__p__5726 gfrancisdev].

Left LED group
* SD card 1
* SD card 2
* Wifi
* Bluetooth

Right LED group
* Empty (with solder pad for hardware hackers who want to use an additional LED)
* Empty (-"-)
* Charging
* Power

==Input==
===Keyboard===
[[image:Keypadmatrix.png|thumb|Keyboard Matrix Diagram (Courtesy of Neelix)]]

* The keyboard is listed on p.20 of the hackers manual, and a more readable version is shown here.
===Touchscreen===
*TSC2046: ADS7846 compatible touch screen controller[http://focus.ti.com/docs/prod/folders/print/tsc2046.html]

==See also==
*[[Nubs]]
*[[Purple Tint of Death]] (due to LCD cables)
*[[Hardware Hacking]] EXT Connectors and other info

[[Category:Chipset]]

SGX drivers

2013-03-26T16:48:20Z

Notaz: dev info

SGX drivers

2013-02-18T12:44:38Z

Notaz: /* Useful links */

Kernel interface

2013-02-17T00:38:25Z

Notaz: use "sane" permissions in an example

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_PAGEUP (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDWR);
buffer = mmap(0, 800*480*2, PROT_READ | PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Some toolchains don't have FBIO_WAITFORVSYNC defined in <linux/fb.h>, in which case you can define it in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

====gamma====
Since SZ 1.52, gamma can be controlled with another script, the same way as LCD refresh:
<source lang="c">
sudo -n /usr/pandora/scripts/op_gamma.sh 1.0
</source>
where 1.0 is the gamma level. If supplied gamma level is 0, then user defaults are used (useful to set on exit). There is also an optional -b N argument (to be specified before gamma value), where N controls black level (0-255, useful to combat LCD ghosting).

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Battery==
There is bq27500 battery monitoring chip onboard, that exports various files at /sys/class/power_supply/bq27500-0/ , for example 'capacity' tells charge percenage left. See [[Data_provided_by_Battery_and_Power_driver]] for more details. 
There are also similar directories at /sys/class/power_supply/twl4030_* that provide info while charging.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Kernel interface

2013-02-16T01:23:32Z

Notaz: battery stuff

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_PAGEUP (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDONLY);
buffer = mmap(0, 800*480*2, PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Some toolchains don't have FBIO_WAITFORVSYNC defined in <linux/fb.h>, in which case you can define it in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

====gamma====
Since SZ 1.52, gamma can be controlled with another script, the same way as LCD refresh:
<source lang="c">
sudo -n /usr/pandora/scripts/op_gamma.sh 1.0
</source>
where 1.0 is the gamma level. If supplied gamma level is 0, then user defaults are used (useful to set on exit). There is also an optional -b N argument (to be specified before gamma value), where N controls black level (0-255, useful to combat LCD ghosting).

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Battery==
There is bq27500 battery monitoring chip onboard, that exports various files at /sys/class/power_supply/bq27500-0/ , for example 'capacity' tells charge percenage left. See [[Data_provided_by_Battery_and_Power_driver]] for more details. 
There are also similar directories at /sys/class/power_supply/twl4030_* that provide info while charging.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

SGX drivers

2013-02-14T18:35:48Z

Notaz: document TI SGX driver releases a bit

Kernel interface

2012-11-27T14:36:40Z

Notaz: add gamma info

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_END (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDONLY);
buffer = mmap(0, 800*480*2, PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Some toolchains don't have FBIO_WAITFORVSYNC defined in <linux/fb.h>, in which case you can define it in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

====gamma====
Since SZ 1.52, gamma can be controlled with another script, the same way as LCD refresh:
<source lang="c">
sudo -n /usr/pandora/scripts/op_gamma.sh 1.0
</source>
where 1.0 is the gamma level. If supplied gamma level is 0, then user defaults are used (useful to set on exit). There is also an optional -b N argument (to be specified before gamma value), where N controls black level (0-255, useful to combat LCD ghosting).

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Emulator List

2012-11-25T20:09:19Z

Notaz: update my stuff

''These lists were last updated on 2012-06-13 to include the latest files from the [http://repo.openpandora.org/ Repo], the [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5 File Archive], [http://apps.open-pandora.org/cgi-bin/viewarea.pl?Emulators Pandora Apps], and the [[Emulator list#Forums|community forums]]. For other software lists on the wiki, see [[Software projects]] and [[Games]].''

If different versions of an [[emulator]] were released, the listed "release date" is from the most recent one.

Please click on the little squares to sort by different categories.

To read a usage guide for several emulators, download [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,404 this guide].

==Released emulators==

Entry colors only denote compatibility and speed; interface and features are not taken into account.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Quality
!Description
|- style="background: #81BEF7"
|Perfect
|Emulators with a '''blue''' background, for all intents and purposes, work perfectly. Virtually every game runs at full speed, and ones that don't come close. No overclocking required. Practically no compatibility issues, with the possible exception of extremely obscure hardware tricks or addons.
|- style="background: #90FF90"
|Fantastic
|Emulators with a '''green''' background work very well. A lot of games run great at or close to 500Mhz, though some issues do exist. Little overclocking is required. Compatibility issues are minimum.
|- style="background: #F3F781"
|Decent
|Emulators with a '''yellow''' background have issues. Some games are playable, and a few do run full speed, but overclocking is typically needed. Compatibility issues may be considerable. This could also represent emulators with great compatibility, but low speed (or vice versa).
|- style="background: #F7BE81"
|Bad
|Emulators with an '''orange''' background do not run well. Few games are playable. Overclocking is mandatory. There may be lots of compatibility issues as well.
|- style="background: #F78181"
|Poor
|Emulators with a '''red''' background are worthless. No games are playable at 500Mhz, and you have to overclock very high to see a difference. Full speed is out of the question. Compatibility is likely nonexistent. This is test release territory.
|-
|N/A
|Emulators with a '''white''' background do not have enough information about them. Please try them out and add to this page!
|}


''If you have tried an emulator which has an uncoloured background, please add the appropriate background colour based on the legend to reflect the status of the emulator. You may add a statement in the notes if you feel that it's necessary.''

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Emulated System
! Project Name
! Release Date (YYYY-MM-DD)
! Download
! Authored or Ported By
! C1
! CS2
! Notes
|- style="background: #90FF90"
|Various{{HideableNotes| Atari Lynx, Bandai Wonderswan, GBA, GB/C, Sega Game Gear, Sega Master System, PC Engine/CD, NES, Virtual Boy, Neo Geo Pocket Colour}}
|Mednafen 0.9.17.r3
|2011-07-13
|[http://repo.openpandora.org/?page=detail&app=package.mednafen-pandora.r3 Repo]
|pder
|
|zip, [http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://www.gp32x.com/board/index.php?/topic/59533-mednafen-0-9-17-1-wip/page__gopid__950099&#entry950099 Discussion] GBA and VB don't run fullspeed.
|- style="background: #90FF90"
|Acorn RISC-PC
|[[pandrpcemu]] ('''beta''')
|2011-05-28
|[http://www.pokenet.co.uk/misc/files.pandora/pandrpcemu.pnd Download] [http://repo.openpandora.org/?page=detail&app=pandrpcemu Repo]
|hideki
|
|None
|[http://boards.openpandora.org/index.php?/topic/3762-pandrpcemu-beta-acorn-risc-pc/ Discussion] Also available natively (32-bit RO5) under [[Software projects#Unreleased software ("Projects Under Development")|Software projects]]
|- style="background: #90FF90"
|Amiga 500 / Amiga 1200
|[[UAE4ALL]] V2.0
|2012-06-13
|[http://repo.openpandora.org/?page=detail&app=uae4all Main version]
|John4p, Pickle, Notaz, tuki_cat, et al.
|[http://spreadsheets.google.com/pub?key=0AuBR5X_s_5_idG92ZVQ5cEs4ZEhYTm5sSjFIcl83U2c&hl=en&gid=0 GD]
|gzip
|"UAE4All 2.0 only works with FAME/C core. Cyclone and UAE core are not compatible.
Thus UAE4All 2.0 replaces the old FAME/C release. The old Cyclone and UAE core releases are still available in this release (but they're still UAE4All 1.1 and won't see new features). [http://boards.openpandora.org/index.php?/topic/8770-uae4all-20/ Discussion] {{HideableNotes|}}
|- style="background: #F3F781"
|Amiga 1200
|[[P-UAE]]
|2010-06-06
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/puae.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,86 Archive]
|Gnostic
|
|
|
|- style="background: #F3F781"
|Amiga
|[[pandeuae]] ('''beta''')
|2011-05-09
|[http://www.hidnet.org.uk/pandeuae.pnd Download]
|hideki
|
|
|[http://boards.openpandora.org/index.php?/topic/3350-euae-port/ Discussion]
|- style="background: #81BEF7"
|Amstrad CPC
|[[Pandora-CAP32]]
|2010-06-27
|[http://zx81.zx81.free.fr/public/pandora/cap32/pandora-cap32-v1.1.0-bin.zip Download] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,115 Archive]
|zx-81
|
|gzip
|[http://www.gp32x.com/board/index.php?/topic/54801-pandora-cap32-v1-1-0/ Discussion]
|- style="background: #90FF90"
|Apple II
|[[LinApple]] 1.3.5.0
|2011-09-13
|[http://repo.openpandora.org/?page=detail&app=linapple-jerryblade-042011 Repo]
|JerryBlade, CFWhitman
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59229-apple-emulator-for-pandora/page__view__findpost__p__957512 GP32X] [http://boards.openpandora.org/index.php?/topic/2490-apple-ii-emulator/ OP]
|- style="background: #90FF90"
|Arcade (laserdisc)
|[[Daphne]] v1.0.0.3
|2011-08-14
|[http://repo.openpandora.org/?page=detail&app=daphne-daphne-25097 Repo]
|mcobit
|
|[http://winff.org/html_new/ Bitrate]
|[http://boards.openpandora.org/index.php?/topic/4852-daphne-wip/ Discussion] {{HideableNotes|Use [http://winff.org/html_new/ WinFF] to re-encode your video files to a lower bitrate if necessary, as doing so will improve speed and shrink the file. Faster SD cards also improve speed greatly.}}
|- style="background: #F3F781"
|Arcade
|[[MAME]] v0.106
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/mame106.pnd.inf Apps] [http://repo.openpandora.org/?page=detail&app=mame.cosam.106 Repo]
|SteveM
|
|zip
|{{HideableNotes|Runs more games than MAME4ALL, but at a slower speed.}}
|- style="background: #90FF90"
|Arcade
|[[MAME4All]] v2.5b7
|2010-09-07
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,200 Archive] [http://repo.openpandora.org/?page=detail&app=mame4all.cosam.2.5-beta7 Repo]
|SteveM, Franxis
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56188-mame4all-beta/ Discussion]
|- style="background: #xxxxxx"
|Arcade
|SDLMAME v.110
|2010-06-30
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,106 Archive]
|?
|
|zip
|Use MAME4ALL instead, this is slow.
|- style="background: #xxxxxx"
|Atari 520
|PAtari v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.4 Download]
|cpasjuste
|
|
|
|-
|Atari 800
|Atari800
|2011-08-06
|[http://ompldr.org/vOXUxYQ/atari800.pnd.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60165-atari-800-emulator-almost-final/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #xxxxxx"
|Atari 8-Bit
|Pandora-Atari
|2010-08-04
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/atari-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,173 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/55724-pandora-atari-atari-8001305200-emulator-for-pandora-v110/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #90FF90"
|Atari Lynx
|[[Handy]]
|2010-06-18
|[http://repo.openpandora.org/?page=detail&app=handy.cosam.0.5.0.0 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54220-handy/ Discussion] {{HideableNotes|Do not turn on the FPS counter, or else the emulator will slow down dramatically.}}
|- style="background: #xxxxxx"
|Atari ST
|Hatari 1.0.3.2
|2011-08-02
|[http://repo.openpandora.org/?page=detail&app=hatari.skeezix.pkg Repo]
|Skeezix
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58088-hatari-atari-st-emu-140-released/page__view__findpost__p__934671 Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2010-05-07
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/Stella312a.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,53 Archive]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 2600
|Pandora-2600 ([[Stella]])
|2010-07-11
|[http://zx81.zx81.free.fr/public/pandora/2600/pandora-2600-v1.1.0-pnd.zip Download] [http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/2600-1.1.0.inf Apps]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54934-pandora-2600-atari-2600-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2011-08-03
|[http://ompldr.org/vOXF0dQ/stella.pnd Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60123-stella-atari-2600-beta-in-pnd/ Discussion]. {{HideableNotes|PAL games don't run.}}
|-
|Atari VCS 2600
|[[Stella]] 3.4.2.2
|2011-10-06
|[http://repo.openpandora.org/?page=detail&app=stella-svn Repo]
|Lomaxx
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 7800
|Pandora-7800 v1.1.0
|2010-07-11
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,146 Archive] [http://zx81.zx81.free.fr/public/pandora/7800/pandora-7800-v1.1.0-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/55189-pandora-7800-atari-7800-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Colecovision
|[[Colem]]
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem_alpha.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,70 Archive] [http://repo.openpandora.org/?page=detail&app=colem.skeezix Repo]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Colecovision
|[[Pandora Colem]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,129 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/60164-colem-port-of-zx81-slightly-modified/ Discussion for modified version (no PND)]
|- style="background: #90FF90"
|Commodore 64
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceX64.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,46 Archive]
|Pickle
|
|
|{{HideableNotes|Very good emulation, deactivate wrap mode in speed seetings if you suffer sound problems}}
|- style="background: #xxxxxx"
|Commodore (Other)
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceMisc.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,47 Archive]
|Pickle
|
|
|{{HideableNotes|Emulates the CBM2, C128, PET, Plus4, and VIC platforms.}}
|- style="background: #90FF90"
|GPH GP2X/Wiz
|[[Ginge]]
|2010-08-16
|[http://repo.openpandora.org/?page=detail&app=package.ginge.notaz Repo]
|Notaz
|
|None
|{{HideableNotes|Not really an emulator. [http://www.gp32x.com/board/index.php?/topic/55980-ginge/page__view__findpost__p__913442 DO NOT run from root]. To get rid of the default blur filter, use [http://www.gp32x.com/board/index.php?/topic/57179-pandora-emulators-vs-gp2xwiz-emulators/page__view__findpost__p__923471 this solution].}}
|- style="background: #xxxxxx"
|HP-48
|[[Pandora-X48]]
|2010-06-17
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,113,96 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/129-HP-48 Download]
|zx-81
|
|
|Emulates a calculator. [http://www.gp32x.com/board/index.php?/topic/54482-x48/ Discussion]
|- style="background: #xxxxxx"
|Macintosh 68K
|Basilisk II
|2010-12-15
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=512 Download] [http://www.mediafire.com/?ue5eyole855fyul 2]
|dgame
|
|
|[http://www.gp32x.com/board/index.php?/topic/56900-basilisk-ii-pnd-68k-macintosh-emulator/ Discussion]
|- style="background: #xxxxxx"
|Mattel Intellivision
|[[Jzintv]]
|2010-09-02
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/jzintv.inf Apps]
|WizardStan
|
|
|[http://www.gp32x.com/board/index.php?/topic/56426-jzintv/ Discussion]
|- style="background: #xxxxxx"
|MSX
|[[Pandora-MSX]]
|2010-06-26
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/msx-1.1.1.inf Apps]
|zx-81
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/54775-pandora-msx-v1-1-0/ Discussion] {{HideableNotes|Only disk images may be gzippped, and if they are, they cannot be written to.}}
|-
|NEC PC-9801
|[[Xnp2]]
|2011-05-01
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,393 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/xnp2.inf Apps] [http://www.mediafire.com/?57qer2aud0e8p9y Download]
|quews (port)
|
|
|[http://www.youtube.com/watch?v=Bd3a-duBfdU Video]
|- style="background: #xxxxxx"
|NEC PC Engine
|[[Pandora HuGo]]
|2010-06-28
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/hugo-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,117 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54833-hugo-pandora-v1-1-0/ Discussion]
|- style="background: #xxxxxx"
|NEC PC Engine
|Temper (alpha)
|2011-07-25
|[http://exophase.devzero.co.uk/temper.pnd Download]
|Exophase
|
|[http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://boards.openpandora.org/index.php?/topic/4621-temper-split-from-other-thread/ Discussion] Also supports the SuperGrafx.
|- style="background: #81BEF7"
|NES
|[[GPFCE]] 0.81.0.r2
|2012-09-30
|[http://repo.openpandora.org/?page=detail&app=package.gpfce.notaz Repo] [http://notaz.gp2x.de/releases/gpfce/gpfce_r2.pnd mirror]
|notaz
|
|zip
|[http://boards.openpandora.org/index.php?/topic/9862-emulation-nes Discussion]
|- style="background: #81BEF7"
|NES
|[[GPFCE]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,72 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/gpfce.inf Apps]
|Notaz, Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|zip
|{{HideableNotes|Sound works if you set the rate to 44000Hz in the options. Forces a 2xsai like filter.}}
|- style="background: #xxxxxx"
|NES
|[[nesemu]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,71 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/nesemu.inf Apps]
|Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|
|[http://code.google.com/p/nesemu/ Website] Seems to only run at 40fps.
|- style="background: #F3F781"
|NES
|[[Nestopia]]
|2011-08-01
|[http://ompldr.org/vOXB2Mg/nestopia_openpandora_streak.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60112-nestopia-for-openpandora-beta/ Discussion] {{HideableNotes|Emulator focus is accuracy. Very high compatibility at a cost of speed. Not a PND.}}
|- style="background: #F3F781"
|Nintendo 64
|[[Mupen64Plus]] 1.5.r20110615.2
|2011-06-16
|[http://repo.openpandora.org/?page=detail&app=mupen64plus Repo]
|Ari64, Adventus, JayFoxRox, sebt3, et al.
|[http://tinyurl.com/6ccuqmc GD]
|zip, 7z, bzip2
|[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__951543 Discussion] Compatibility list is mostly outdated. {{HideableNotes|To get good auto-frameskip, switch to gles2n64 0.0.5, set frame render rate 2, auto frameskip 1 -[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__946705]}}
|- style="background: #F78181"
|Nintendo DS
|[[Desmume]]
|2011-08-04
|[http://www.2shared.com/file/wxnc3MRT/desmume097.html Download]
[http://www.mediafire.com/?8gvvhqz3e2zkxzj 2]
|notaz
|
|
|[http://boards.openpandora.org/index.php?/topic/4744-nintendo-ds-emulator/page__view__findpost__p__82779 Discussion] Not meant for entertainment; was ported only to shut people up.
|- style="background: #F3F781"
|Nintendo GBA/GBC/GB
|[[VisualBoyAdvance]]
|2010-12-08
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/vba-1.7.2-0.inf Apps] [http://www.mediafire.com/?7qbxlnp0h2isokf Download]
|EvilDragon, SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/57808-visualboyadvance-v1-7-2-1/page__p__929521&#entry929521 Discussion]. Runs GB/C well; GBA is slow
|- style="background: #81BEF7"
|Nintendo GBA
|[[gpSP]]
|2012-10-03
|[http://repo.openpandora.org/?page=detail&app=package.gpsp.notaz Repo]
|Exophase, notaz
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60219-gba-emulator-that-you-can-adjust-the-screen-size/page__view__findpost__p__957136 GP32X] [http://boards.openpandora.org/index.php?/topic/5226-gpsp-for-pandora-from-notaz/ OP]. Native port with fullscreen scaling.
|- style="background: #90FF90"
|Nintendo GBA
|[[gpSP]] (Ginged)
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,199 Archive]
|Exophase, notaz
|
|zip
|[http://gpsp-dev.blogspot.com/ Website]. {{HideableNotes|Runs through [[Ginge]], only zipped ROMs. [http://www.gp32x.com/board/index.php?/topic/58722-im-looking-for-a-gba-emulator-without-blurry-upscaling/ No fullscreen scaling].}}
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnuBoy]] 1.0.5Svn
|2010-11-10
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,207 Archive] [http://repo.openpandora.org/?page=detail&app=sdlgnuboy Repo]
|Pickle, EvilDragon
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/56916-gnuboy-updated/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57436-gnuboy-v1-0-5-svn-released/ 2] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnGB]] ('''beta''')
|2010-10-04
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=482 Download] [http://www.mediafire.com/?7qbxlnp0h2isokf 2]
|dgame (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/56886-gngb-pnd-game-boy-and-game-boy-color-emulator/ Discussion]
|- style="background: #xxxxxx"
|Nintendo Pokémon mini
|[[Pokémini]] 0.4.4
|2011-04-13
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/pokemini.inf Apps] [http://www.mediafire.com/?05g9s8w780mt58g Download]
|Wally
|
|
|[http://boards.openpandora.org/index.php?/topic/2898-pokemini-emulator-pokemon-mini Discussion]
|- style="background: #xxxxxx"
|Oric-1/Atmos
|[[PandOricutron]]
|2010-06-16
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/PandOricutron_108.inf Apps]
|torpor
|
|
|[http://www.gp32x.com/board/index.php?/topic/54260-pandoricutron-1-0-8/ Discussion]
|- style="background: #xxxxxx"
|PDP-11
|[[SIMH PDP-11]]
|2010-05-28
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,83 Archive] [http://repo.openpandora.org/?page=detail&app=msimh.cosam.3.8.0.0 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|Philips Odyssey 2
|[[O2EM]] 1.18-1
|2010-08-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,186 Archive] [http://repo.openpandora.org/?page=detail&app=o2em Repo]
|Hitnrun, Daniel Boris
|
|
|
|-
|SAM Coupé
|[[SimCoupe]]
|2011-08-19
|[http://ompldr.org/vOXlsaw/simcoupe.pnd.zip Download]
|StreaK
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60220-simcoupe-a-sam-coupe-emulator-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4947-simcoupe-a-sam-coupe-emulator-beta/ OP]
|- style="background: #81BEF7"
|Sega Genesis, CD, 32X, Master System
|[[PicoDrive]] 1.80
|2010-09-19
|[http://repo.openpandora.org/?page=detail&app=package.picodrive.notaz Repo]
|Notaz
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56713-picodrive-1-80/ Discussion] ([http://www.gp32x.com/board/index.php?/topic/53899-picodrive-released/ old]). {{HideableNotes|Master System support is preliminary. Not all 32X games run.}}
|- style="background: #xxxxxx"
|Sega Master System & Game Gear
|[[Dega]] v1.16-4
|2010-08-15
|[http://repo.openpandora.org/?page=detail&app=dega.cosam.1.16.0.2 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54914-dega/ Discussion]{{HideableNotes|Press R+number to save, L+number to load, Pandora key to quit}}
|- style="background: #xxxxxx"
|Sega Master System
|PSMS v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.10 Download]
|cpasjuste
|
|
|
|- style="background: #F7BE81"
|Sega Saturn
|Yabause r2660
|2011-08-06
|[http://hotfile.com/dl/126054899/6ca83f7/yabause-r2660.pnd.html Download] [http://www.mediafire.com/?fmbn5ij2t3mucjh 2]
|Ari64
|[https://spreadsheets.google.com/spreadsheet/ccc?key=0Aq4SN3wYVIxgdHB4Z2hHcE9fQ3lTaTVMelEyZVBsVFE GD]
|
|[http://boards.openpandora.org/index.php?/topic/4583-yabause/ Discussion]
|- style="background: #xxxxxx"
|Sega Genesis
|DGen/SDL 1.30 Alpha Build 2
|2012-05-25
|[http://www.sendspace.com/file/a8af4p Download]
|Kazuki
|
|
|
|- style="background: #90FF90"
|SNES
|[[SNES9X4P]] 1.39ff - v20111205-2
|2011-12-06
|[http://repo.openpandora.org/?page=detail&app=snes9x4p_ivanovic Repo]
|HideableNotes|Ivanovic, Skeezix, SiENcE (Dingoo)
|
|7z
|Dingoo Snes9x port. [http://www.gp32x.com/board/index.php?/topic/55378-snes9x4d4p-another-new-build-now-with-hi-res-and-new-rom-picker/page__view__findpost__p__958887] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|SNES
|SNES9X v0.2
|2009-04-03
|[http://www.pandorasource.de/download.php?view.7 Download]
|cpasjuste (port)
|
|
|
|- style="background: #xxxxxx"
|SNES
|[[PocketSNES]] ('''beta''') 0.1
|2010-08-08
|[http://www.rangelreale.com/pandora/pocketsnes_hack_0.1.pnd Download]
|Hitnrun (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/55796-pocketsnes-hack/ Discussion]
|- style="background: #81BEF7"
|SNK Neo Geo
|[[GnGeo]] 0.8.3
|2011-04-20
|[http://repo.openpandora.org/?page=detail&app=gngeopnd-pepone Repo]
|Pepone, Manolis
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59207-gngeo-0-8-2/page__view__findpost__p__946739 GP32X] [http://boards.openpandora.org/index.php?/topic/2936-gngeo-083/ OP]
|- style="background: #xxxxxx"
|SNK Neo Geo
|NeoGeo SDL
|2009-04-03
|[http://www.pandorasource.de/download.php?view.13 Download]
|Cpasjuste
|
|
|
|-
|SNK NeoGeo Pocket
|NeoPop
|2010-07-15
|[http://www.pdroms.de/files/1969/ Download]
|Cpasjuste
|
|
|[http://www.gp32x.com/board/index.php?/topic/58848-neopop-ngpc-emulator-released/ Discussion]
|- style="background: #xxxxxx"
|SNK Neo Geo Pocket
|[[Race]]
|2010-06-20
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/race10.inf Apps]
|Hooka
|
|
|[http://www.gp32x.com/board/index.php?/topic/54187-race-a-neo-geo-pocket-color-emulator Discussion]
|- style="background: #F7BE81"
|Sony Playstation
|[[PSX4Pandora]]
|2010-11-16
|[http://www.zodttd.com/downloads/psx4pandora10b5.pnd Download]
|ZodTTD
|[http://spreadsheets.google.com/pub?key=0AkBB6e4g1lGtdFVwODhsQzdlWVdrMTRKdDFXa1laZ2c&hl=en_GB&output=html GD]
|
|[http://www.gp32x.com/board/index.php?/topic/57522-psx4pandora-1-0b5/ Discussion]
|- style="background: #90FF90"
|Sony Playstation
|[[PCSX-ReARMed]]
|2012-11-24
|[http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz Repo] [http://notaz.gp2x.de/releases/pcsxr/pcsx_rearmed_r17.pnd mirror]
|notaz
|[https://spreadsheets.google.com/ccc?key=0ArSWWAWRjErldHZVZlFxY0tBVnRRNXM5U3ZqWFNuN0E&hl=en#gid=0 GD]
|[http://boards.openpandora.org/index.php?/topic/4046-tutorial-how-to-save-space-on-ps1-games-without-ripping-video-or-music/ pbp]
|[http://boards.openpandora.org/index.php?/topic/6546-pcsx-rearmed-r13-with-a-new-gpu/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57973-pcsx-rearmed/page__view__findpost__p__955679 old thread]
|-
|Thomson TO8D
|[[TO8_PND]]
|2011-11-15
|[http://repo.openpandora.org/?page=detail&app=TO8D_PND Repo]
|SladeCraven
|
|None
|Emulates the Thomson TO8/TO8D computer. [http://boards.openpandora.org/index.php?/topic/6076-thomson-to8-emulator-beta-version-040/page__fromsearch__1 Discussion]
|-
|TI89/TI89 Titanium / TI92/TI92+ / V200PLT
|[[TiEmu]]
|2011-09-10
|[http://repo.openpandora.org/?page=detail&app=tiemu-6232 Repo]
|Kazuki
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TI-99
|Pandora-TI99 ([[TI99Sim]])
|2010-07-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,164 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/147-TI99 Download]
|zx-81
|
|
|
|-
|TI-92
|[[XTiger]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ti92-1.1.0.inf Apps]
|zx-81
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TRS-80
|[[SDLTRS]]
|2011-08-03
|[http://www.mediafire.com/download.php?72etxpjqaosa11b Download]
|Blue Protoman
|
|
|I give no support to this! This is a hackjob port!
|- style="background: #81BEF7"
|Vectrex
|[[Pandora-Vectrex]] v1.1.1
|2011-03-06
|[http://zx81.zx81.free.fr/public/pandora/vectrex/pandora-vectrex-v1.1.1-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58846-pandora-vectrex-vectrex-emulator-for-pandora-v110/page__view__findpost__p__942010 Discussion] Download game overlays [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,355 here].
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox]] v0.74svn
|2010-11-09
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,54 Archive]
|Pickle
|[[DOSBox compatibility list|W]]
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/57424-dosbox/ GP32Xa] [http://www.gp32x.com/board/index.php?/topic/53942-post-your-dosbox-successes-here/ GP32Xb] [http://boards.openpandora.org/index.php?/topic/2346-dosbox-room-for-optimization/ OPa] [http://boards.openpandora.org/index.php?/topic/2063-dosbox/ OPb]. [http://www.dosbox.com/comp_list.php General compatibility list]
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox EX]]
|2011-08-16
|[http://ompldr.org/vOXhhMA/dosbox_ex.pnd.zip Download]
|StreaK
|
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60175-dosbox-ex-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4855-dosbox-ex/ OP]
|- style="background: #F3F781"

|x86 PC
|[[Qemu for Pandora]]
|2012-03-02
|[http://www.openpandora.org/rebirth/qemu.pnd Download]
|IngoReis, mcobit
|
|None
|Discussion: [http://boards.openpandora.org/index.php?/topic/7004-qemu-for-pandora-for-rebirth-competition OP-Boards]
|- style="background: #F3F781"
|x86 Windows 3.1 r2, r1
|[[WinBox]] ('''beta''')
|2010-12-15
|[http://repo.openpandora.org/?page=detail&app=winbox-1 Repo] [http://urjaman.dyndns.info/winbox_r2.pnd Download]
|urjaman
|
|None
|[http://www.gp32x.com/board/index.php?/topic/54985-win-3-1-via-dosbox-at-native-resolution/page__view__findpost__p__887198 Discussion] {{HideableNotes|Modified DOSBox to run Windows 3.1 at Pandora's native resolution}}
|-
|ZX-80 & ZX-81
|sz81
|2011-08-19
|[http://ompldr.org/vOXk0eA/sz81.pnd.zip Download]
|StreaK
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Fuse]]
|2010-06-24
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/fuse-0.9.0.inf Apps] [http://repo.openpandora.org/?page=detail&app=fuse.cosam.0.10.0.2 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Zx Pandy]] v3.2.1.4
|2011-04-12
|[http://repo.openpandora.org/?page=detail&app=zx_pandy.dave18.001 Repo]
|Dave18
|
|
|[http://www.gp32x.com/board/index.php?/topic/58536-zx-pandy-released/ Discussion]
|}

1 "C" is short for compatibility list.
FT = Forum Topic
GD = Google Docs
W = Wiki page

2 "CS" is short for "Compression Support". The entries denote the formats that can be used to save space on the games. A blank entry doesn't mean "none", it means there's not enough info! Please add more if you can!

==Unreleased emulators==
This section includes both emulators that are actively being worked on, as well as ones that are or may be abandoned. The latter are included for historical purposes.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
!Emulated System
!Project Name
!Last Update
!Status
!Author/Port Author
!Notes
|-
|Acorn BBC Micro
|BeebEm
|[http://boards.openpandora.org/index.php?/topic/1094-bbc-emulation-merged-thread/page__st__20#entry147214 2012-05-12]
|PND, two working builds
| [http://wiki.gp2x.org/wiki/BeebEm Authors], PND by [http://sam.nipl.net/ sswam]
|[http://pandoria.org/pnd/beebem.pnd PND] [http://repo.openpandora.org/?page=detail&app=beebem-15428 Repo] [http://boards.openpandora.org/index.php?/topic/1094-bbc-emulation-merged-thread/ Discussion] [http://www.gp32x.com/board/index.php?/topic/43489-beebem-for-gp2x-06-bbc-micro-emulator GP2X]
|-
|Amstrad PCW
|Joyce / Anne emu
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/page__view__findpost__p__85612 2011-08-18]
|Abandoned
|StreaK
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/ Discussion] Discontinued: StreaK left the community.
|-
|Sega Dreamcast
|NullDC
|[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 2011-03-28]
|On hold
|Zezu / drkIIraziel
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910] drkIIraziel says he will have time to work on it "[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 after April 10]"
|-
|Nintendo SNES
|[[PandaSNES]]
|[http://www.gp32x.com/board/index.php?/topic/43213-any-snes-fans-in-the-house/page__view__findpost__p__631020 2008-07-29]
|Abandoned
|Squidge
|[http://www.gp32x.com/board/index.php?showtopic=43213] Probably discontinued; Squidge has not been heard from for a long time.
|-
|Sony Playstation Portable
|Pandora-PSP
|[http://jannikvogel.de/2011 2011-01]
|Abandoned
|[[User:JayFoxRox|JayFoxRox]]
|[http://www.gp32x.com/board/index.php?showtopic=47270] Probably discontinued; JayFoxRox has since left the community.
|-
|}

==External links==
*[http://sebt3.openpandora.org/pnd/ Releases by sebt3]
*[http://www.hermocom.com/en/downloads/openpandora/ Releases by Hermocom]
*[http://rebirthofxeen.com/files/pandora/ Releases by WizardStan]
*[http://www.stuckiegamez.co.uk/apps/pandora/ Releases by StuckieGamez]

===Forums===
The following community forums are checked when updating this page:
*From GP32X: [http://www.gp32x.com/board/index.php?/forum/63-news-zone-pandora/ News Zone], [http://www.gp32x.com/board/index.php?/forum/71-beta-testing-pandora/ Beta Testing] and [http://www.gp32x.com/board/index.php?/forum/64-developers-corner-pandora/ Developer's Corner]
*From OP: [http://boards.openpandora.org/index.php?/forum/26-software-news/ Software News] and [http://boards.openpandora.org/index.php?/forum/10-beta-testing/ Beta Testing]
*From GP2X.de: [http://forum.gp2x.de/viewforum.php?f=24 News] and [http://forum.gp2x.de/viewforum.php?f=59 Betatest]

[[Category:Emulators]]
[[Category:Software]]
[[Category:List]]

Emulator List

2012-11-25T19:40:14Z

Notaz:

''These lists were last updated on 2012-06-13 to include the latest files from the [http://repo.openpandora.org/ Repo], the [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5 File Archive], [http://apps.open-pandora.org/cgi-bin/viewarea.pl?Emulators Pandora Apps], and the [[Emulator list#Forums|community forums]]. For other software lists on the wiki, see [[Software projects]] and [[Games]].''

If different versions of an [[emulator]] were released, the listed "release date" is from the most recent one.

Please click on the little squares to sort by different categories.

To read a usage guide for several emulators, download [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,404 this guide].

==Released emulators==

Entry colors only denote compatibility and speed; interface and features are not taken into account.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Quality
!Description
|- style="background: #81BEF7"
|Perfect
|Emulators with a '''blue''' background, for all intents and purposes, work perfectly. Virtually every game runs at full speed, and ones that don't come close. No overclocking required. Practically no compatibility issues, with the possible exception of extremely obscure hardware tricks or addons.
|- style="background: #90FF90"
|Fantastic
|Emulators with a '''green''' background work very well. A lot of games run great at or close to 500Mhz, though some issues do exist. Little overclocking is required. Compatibility issues are minimum.
|- style="background: #F3F781"
|Decent
|Emulators with a '''yellow''' background have issues. Some games are playable, and a few do run full speed, but overclocking is typically needed. Compatibility issues may be considerable. This could also represent emulators with great compatibility, but low speed (or vice versa).
|- style="background: #F7BE81"
|Bad
|Emulators with an '''orange''' background do not run well. Few games are playable. Overclocking is mandatory. There may be lots of compatibility issues as well.
|- style="background: #F78181"
|Poor
|Emulators with a '''red''' background are worthless. No games are playable at 500Mhz, and you have to overclock very high to see a difference. Full speed is out of the question. Compatibility is likely nonexistent. This is test release territory.
|-
|N/A
|Emulators with a '''white''' background do not have enough information about them. Please try them out and add to this page!
|}


''If you have tried an emulator which has an uncoloured background, please add the appropriate background colour based on the legend to reflect the status of the emulator. You may add a statement in the notes if you feel that it's necessary.''

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Emulated System
! Project Name
! Release Date (YYYY-MM-DD)
! Download
! Authored or Ported By
! C1
! CS2
! Notes
|- style="background: #90FF90"
|Various{{HideableNotes| Atari Lynx, Bandai Wonderswan, GBA, GB/C, Sega Game Gear, Sega Master System, PC Engine/CD, NES, Virtual Boy, Neo Geo Pocket Colour}}
|Mednafen 0.9.17.r3
|2011-07-13
|[http://repo.openpandora.org/?page=detail&app=package.mednafen-pandora.r3 Repo]
|pder
|
|zip, [http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://www.gp32x.com/board/index.php?/topic/59533-mednafen-0-9-17-1-wip/page__gopid__950099&#entry950099 Discussion] GBA and VB don't run fullspeed.
|- style="background: #90FF90"
|Acorn RISC-PC
|[[pandrpcemu]] ('''beta''')
|2011-05-28
|[http://www.pokenet.co.uk/misc/files.pandora/pandrpcemu.pnd Download] [http://repo.openpandora.org/?page=detail&app=pandrpcemu Repo]
|hideki
|
|None
|[http://boards.openpandora.org/index.php?/topic/3762-pandrpcemu-beta-acorn-risc-pc/ Discussion] Also available natively (32-bit RO5) under [[Software projects#Unreleased software ("Projects Under Development")|Software projects]]
|- style="background: #90FF90"
|Amiga 500 / Amiga 1200
|[[UAE4ALL]] V2.0
|2012-06-13
|[http://repo.openpandora.org/?page=detail&app=uae4all Main version]
|John4p, Pickle, Notaz, tuki_cat, et al.
|[http://spreadsheets.google.com/pub?key=0AuBR5X_s_5_idG92ZVQ5cEs4ZEhYTm5sSjFIcl83U2c&hl=en&gid=0 GD]
|gzip
|"UAE4All 2.0 only works with FAME/C core. Cyclone and UAE core are not compatible.
Thus UAE4All 2.0 replaces the old FAME/C release. The old Cyclone and UAE core releases are still available in this release (but they're still UAE4All 1.1 and won't see new features). [http://boards.openpandora.org/index.php?/topic/8770-uae4all-20/ Discussion] {{HideableNotes|}}
|- style="background: #F3F781"
|Amiga 1200
|[[P-UAE]]
|2010-06-06
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/puae.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,86 Archive]
|Gnostic
|
|
|
|- style="background: #F3F781"
|Amiga
|[[pandeuae]] ('''beta''')
|2011-05-09
|[http://www.hidnet.org.uk/pandeuae.pnd Download]
|hideki
|
|
|[http://boards.openpandora.org/index.php?/topic/3350-euae-port/ Discussion]
|- style="background: #81BEF7"
|Amstrad CPC
|[[Pandora-CAP32]]
|2010-06-27
|[http://zx81.zx81.free.fr/public/pandora/cap32/pandora-cap32-v1.1.0-bin.zip Download] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,115 Archive]
|zx-81
|
|gzip
|[http://www.gp32x.com/board/index.php?/topic/54801-pandora-cap32-v1-1-0/ Discussion]
|- style="background: #90FF90"
|Apple II
|[[LinApple]] 1.3.5.0
|2011-09-13
|[http://repo.openpandora.org/?page=detail&app=linapple-jerryblade-042011 Repo]
|JerryBlade, CFWhitman
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59229-apple-emulator-for-pandora/page__view__findpost__p__957512 GP32X] [http://boards.openpandora.org/index.php?/topic/2490-apple-ii-emulator/ OP]
|- style="background: #90FF90"
|Arcade (laserdisc)
|[[Daphne]] v1.0.0.3
|2011-08-14
|[http://repo.openpandora.org/?page=detail&app=daphne-daphne-25097 Repo]
|mcobit
|
|[http://winff.org/html_new/ Bitrate]
|[http://boards.openpandora.org/index.php?/topic/4852-daphne-wip/ Discussion] {{HideableNotes|Use [http://winff.org/html_new/ WinFF] to re-encode your video files to a lower bitrate if necessary, as doing so will improve speed and shrink the file. Faster SD cards also improve speed greatly.}}
|- style="background: #F3F781"
|Arcade
|[[MAME]] v0.106
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/mame106.pnd.inf Apps] [http://repo.openpandora.org/?page=detail&app=mame.cosam.106 Repo]
|SteveM
|
|zip
|{{HideableNotes|Runs more games than MAME4ALL, but at a slower speed.}}
|- style="background: #90FF90"
|Arcade
|[[MAME4All]] v2.5b7
|2010-09-07
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,200 Archive] [http://repo.openpandora.org/?page=detail&app=mame4all.cosam.2.5-beta7 Repo]
|SteveM, Franxis
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56188-mame4all-beta/ Discussion]
|- style="background: #xxxxxx"
|Arcade
|SDLMAME v.110
|2010-06-30
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,106 Archive]
|?
|
|zip
|Use MAME4ALL instead, this is slow.
|- style="background: #xxxxxx"
|Atari 520
|PAtari v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.4 Download]
|cpasjuste
|
|
|
|-
|Atari 800
|Atari800
|2011-08-06
|[http://ompldr.org/vOXUxYQ/atari800.pnd.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60165-atari-800-emulator-almost-final/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #xxxxxx"
|Atari 8-Bit
|Pandora-Atari
|2010-08-04
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/atari-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,173 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/55724-pandora-atari-atari-8001305200-emulator-for-pandora-v110/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #90FF90"
|Atari Lynx
|[[Handy]]
|2010-06-18
|[http://repo.openpandora.org/?page=detail&app=handy.cosam.0.5.0.0 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54220-handy/ Discussion] {{HideableNotes|Do not turn on the FPS counter, or else the emulator will slow down dramatically.}}
|- style="background: #xxxxxx"
|Atari ST
|Hatari 1.0.3.2
|2011-08-02
|[http://repo.openpandora.org/?page=detail&app=hatari.skeezix.pkg Repo]
|Skeezix
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58088-hatari-atari-st-emu-140-released/page__view__findpost__p__934671 Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2010-05-07
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/Stella312a.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,53 Archive]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 2600
|Pandora-2600 ([[Stella]])
|2010-07-11
|[http://zx81.zx81.free.fr/public/pandora/2600/pandora-2600-v1.1.0-pnd.zip Download] [http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/2600-1.1.0.inf Apps]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54934-pandora-2600-atari-2600-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2011-08-03
|[http://ompldr.org/vOXF0dQ/stella.pnd Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60123-stella-atari-2600-beta-in-pnd/ Discussion]. {{HideableNotes|PAL games don't run.}}
|-
|Atari VCS 2600
|[[Stella]] 3.4.2.2
|2011-10-06
|[http://repo.openpandora.org/?page=detail&app=stella-svn Repo]
|Lomaxx
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 7800
|Pandora-7800 v1.1.0
|2010-07-11
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,146 Archive] [http://zx81.zx81.free.fr/public/pandora/7800/pandora-7800-v1.1.0-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/55189-pandora-7800-atari-7800-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Colecovision
|[[Colem]]
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem_alpha.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,70 Archive] [http://repo.openpandora.org/?page=detail&app=colem.skeezix Repo]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Colecovision
|[[Pandora Colem]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,129 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/60164-colem-port-of-zx81-slightly-modified/ Discussion for modified version (no PND)]
|- style="background: #90FF90"
|Commodore 64
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceX64.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,46 Archive]
|Pickle
|
|
|{{HideableNotes|Very good emulation, deactivate wrap mode in speed seetings if you suffer sound problems}}
|- style="background: #xxxxxx"
|Commodore (Other)
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceMisc.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,47 Archive]
|Pickle
|
|
|{{HideableNotes|Emulates the CBM2, C128, PET, Plus4, and VIC platforms.}}
|- style="background: #90FF90"
|GPH GP2X/Wiz
|[[Ginge]]
|2010-08-16
|[http://repo.openpandora.org/?page=detail&app=package.ginge.notaz Repo]
|Notaz
|
|None
|{{HideableNotes|Not really an emulator. [http://www.gp32x.com/board/index.php?/topic/55980-ginge/page__view__findpost__p__913442 DO NOT run from root]. To get rid of the default blur filter, use [http://www.gp32x.com/board/index.php?/topic/57179-pandora-emulators-vs-gp2xwiz-emulators/page__view__findpost__p__923471 this solution].}}
|- style="background: #xxxxxx"
|HP-48
|[[Pandora-X48]]
|2010-06-17
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,113,96 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/129-HP-48 Download]
|zx-81
|
|
|Emulates a calculator. [http://www.gp32x.com/board/index.php?/topic/54482-x48/ Discussion]
|- style="background: #xxxxxx"
|Macintosh 68K
|Basilisk II
|2010-12-15
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=512 Download] [http://www.mediafire.com/?ue5eyole855fyul 2]
|dgame
|
|
|[http://www.gp32x.com/board/index.php?/topic/56900-basilisk-ii-pnd-68k-macintosh-emulator/ Discussion]
|- style="background: #xxxxxx"
|Mattel Intellivision
|[[Jzintv]]
|2010-09-02
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/jzintv.inf Apps]
|WizardStan
|
|
|[http://www.gp32x.com/board/index.php?/topic/56426-jzintv/ Discussion]
|- style="background: #xxxxxx"
|MSX
|[[Pandora-MSX]]
|2010-06-26
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/msx-1.1.1.inf Apps]
|zx-81
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/54775-pandora-msx-v1-1-0/ Discussion] {{HideableNotes|Only disk images may be gzippped, and if they are, they cannot be written to.}}
|-
|NEC PC-9801
|[[Xnp2]]
|2011-05-01
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,393 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/xnp2.inf Apps] [http://www.mediafire.com/?57qer2aud0e8p9y Download]
|quews (port)
|
|
|[http://www.youtube.com/watch?v=Bd3a-duBfdU Video]
|- style="background: #xxxxxx"
|NEC PC Engine
|[[Pandora HuGo]]
|2010-06-28
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/hugo-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,117 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54833-hugo-pandora-v1-1-0/ Discussion]
|- style="background: #xxxxxx"
|NEC PC Engine
|Temper (alpha)
|2011-07-25
|[http://exophase.devzero.co.uk/temper.pnd Download]
|Exophase
|
|[http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://boards.openpandora.org/index.php?/topic/4621-temper-split-from-other-thread/ Discussion] Also supports the SuperGrafx.
|- style="background: #81BEF7"
|NES
|[[GPFCE-GP2X]]
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,224 Archive] [http://repo.openpandora.org/?page=detail&app=gpfcegp2x Repo]
|notaz
|
|zip
|{{HideableNotes|The GP2X version of GPFCE, packaged into a PND with Ginge.}}
|- style="background: #81BEF7"
|NES
|[[GPFCE]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,72 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/gpfce.inf Apps]
|Notaz, Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|zip
|{{HideableNotes|Sound works if you set the rate to 44000Hz in the options. Forces a 2xsai like filter.}}
|- style="background: #xxxxxx"
|NES
|[[nesemu]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,71 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/nesemu.inf Apps]
|Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|
|[http://code.google.com/p/nesemu/ Website] Seems to only run at 40fps.
|- style="background: #F3F781"
|NES
|[[Nestopia]]
|2011-08-01
|[http://ompldr.org/vOXB2Mg/nestopia_openpandora_streak.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60112-nestopia-for-openpandora-beta/ Discussion] {{HideableNotes|Emulator focus is accuracy. Very high compatibility at a cost of speed. Not a PND.}}
|- style="background: #F3F781"
|Nintendo 64
|[[Mupen64Plus]] 1.5.r20110615.2
|2011-06-16
|[http://repo.openpandora.org/?page=detail&app=mupen64plus Repo]
|Ari64, Adventus, JayFoxRox, sebt3, et al.
|[http://tinyurl.com/6ccuqmc GD]
|zip, 7z, bzip2
|[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__951543 Discussion] Compatibility list is mostly outdated. {{HideableNotes|To get good auto-frameskip, switch to gles2n64 0.0.5, set frame render rate 2, auto frameskip 1 -[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__946705]}}
|- style="background: #F78181"
|Nintendo DS
|[[Desmume]]
|2011-08-04
|[http://www.2shared.com/file/wxnc3MRT/desmume097.html Download]
[http://www.mediafire.com/?8gvvhqz3e2zkxzj 2]
|notaz
|
|
|[http://boards.openpandora.org/index.php?/topic/4744-nintendo-ds-emulator/page__view__findpost__p__82779 Discussion] Not meant for entertainment; was ported only to shut people up.
|- style="background: #F3F781"
|Nintendo GBA/GBC/GB
|[[VisualBoyAdvance]]
|2010-12-08
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/vba-1.7.2-0.inf Apps] [http://www.mediafire.com/?7qbxlnp0h2isokf Download]
|EvilDragon, SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/57808-visualboyadvance-v1-7-2-1/page__p__929521&#entry929521 Discussion]. Runs GB/C well; GBA is slow
|- style="background: #81BEF7"
|Nintendo GBA
|[[gpSP]]
|2011-09-08
|[http://repo.openpandora.org/?page=detail&app=package.gpsp.notaz Repo]
|Exophase, notaz
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60219-gba-emulator-that-you-can-adjust-the-screen-size/page__view__findpost__p__957136 GP32X] [http://boards.openpandora.org/index.php?/topic/5226-gpsp-for-pandora-from-notaz/ OP]. Zipped ROMs only. Now a native port with fullscreen scaling.
|- style="background: #90FF90"
|Nintendo GBA
|[[gpSP]] (Ginged)
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,199 Archive]
|Exophase, notaz
|
|zip
|[http://gpsp-dev.blogspot.com/ Website]. {{HideableNotes|Runs through [[Ginge]], only zipped ROMs. [http://www.gp32x.com/board/index.php?/topic/58722-im-looking-for-a-gba-emulator-without-blurry-upscaling/ No fullscreen scaling].}}
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnuBoy]] 1.0.5Svn
|2010-11-10
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,207 Archive] [http://repo.openpandora.org/?page=detail&app=sdlgnuboy Repo]
|Pickle, EvilDragon
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/56916-gnuboy-updated/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57436-gnuboy-v1-0-5-svn-released/ 2] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnGB]] ('''beta''')
|2010-10-04
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=482 Download] [http://www.mediafire.com/?7qbxlnp0h2isokf 2]
|dgame (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/56886-gngb-pnd-game-boy-and-game-boy-color-emulator/ Discussion]
|- style="background: #xxxxxx"
|Nintendo Pokémon mini
|[[Pokémini]] 0.4.4
|2011-04-13
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/pokemini.inf Apps] [http://www.mediafire.com/?05g9s8w780mt58g Download]
|Wally
|
|
|[http://boards.openpandora.org/index.php?/topic/2898-pokemini-emulator-pokemon-mini Discussion]
|- style="background: #xxxxxx"
|Oric-1/Atmos
|[[PandOricutron]]
|2010-06-16
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/PandOricutron_108.inf Apps]
|torpor
|
|
|[http://www.gp32x.com/board/index.php?/topic/54260-pandoricutron-1-0-8/ Discussion]
|- style="background: #xxxxxx"
|PDP-11
|[[SIMH PDP-11]]
|2010-05-28
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,83 Archive] [http://repo.openpandora.org/?page=detail&app=msimh.cosam.3.8.0.0 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|Philips Odyssey 2
|[[O2EM]] 1.18-1
|2010-08-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,186 Archive] [http://repo.openpandora.org/?page=detail&app=o2em Repo]
|Hitnrun, Daniel Boris
|
|
|
|-
|SAM Coupé
|[[SimCoupe]]
|2011-08-19
|[http://ompldr.org/vOXlsaw/simcoupe.pnd.zip Download]
|StreaK
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60220-simcoupe-a-sam-coupe-emulator-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4947-simcoupe-a-sam-coupe-emulator-beta/ OP]
|- style="background: #81BEF7"
|Sega Genesis, CD, 32X, Master System
|[[PicoDrive]] 1.80
|2010-09-19
|[http://repo.openpandora.org/?page=detail&app=package.picodrive.notaz Repo]
|Notaz
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56713-picodrive-1-80/ Discussion] ([http://www.gp32x.com/board/index.php?/topic/53899-picodrive-released/ old]). {{HideableNotes|Master System support is preliminary. Not all 32X games run.}}
|- style="background: #xxxxxx"
|Sega Master System & Game Gear
|[[Dega]] v1.16-4
|2010-08-15
|[http://repo.openpandora.org/?page=detail&app=dega.cosam.1.16.0.2 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54914-dega/ Discussion]{{HideableNotes|Press R+number to save, L+number to load, Pandora key to quit}}
|- style="background: #xxxxxx"
|Sega Master System
|PSMS v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.10 Download]
|cpasjuste
|
|
|
|- style="background: #F7BE81"
|Sega Saturn
|Yabause r2660
|2011-08-06
|[http://hotfile.com/dl/126054899/6ca83f7/yabause-r2660.pnd.html Download] [http://www.mediafire.com/?fmbn5ij2t3mucjh 2]
|Ari64
|[https://spreadsheets.google.com/spreadsheet/ccc?key=0Aq4SN3wYVIxgdHB4Z2hHcE9fQ3lTaTVMelEyZVBsVFE GD]
|
|[http://boards.openpandora.org/index.php?/topic/4583-yabause/ Discussion]
|- style="background: #xxxxxx"
|Sega Genesis
|DGen/SDL 1.30 Alpha Build 2
|2012-05-25
|[http://www.sendspace.com/file/a8af4p Download]
|Kazuki
|
|
|
|- style="background: #90FF90"
|SNES
|[[SNES9X4P]] 1.39ff - v20111205-2
|2011-12-06
|[http://repo.openpandora.org/?page=detail&app=snes9x4p_ivanovic Repo]
|HideableNotes|Ivanovic, Skeezix, SiENcE (Dingoo)
|
|7z
|Dingoo Snes9x port. [http://www.gp32x.com/board/index.php?/topic/55378-snes9x4d4p-another-new-build-now-with-hi-res-and-new-rom-picker/page__view__findpost__p__958887] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|SNES
|SNES9X v0.2
|2009-04-03
|[http://www.pandorasource.de/download.php?view.7 Download]
|cpasjuste (port)
|
|
|
|- style="background: #xxxxxx"
|SNES
|[[PocketSNES]] ('''beta''') 0.1
|2010-08-08
|[http://www.rangelreale.com/pandora/pocketsnes_hack_0.1.pnd Download]
|Hitnrun (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/55796-pocketsnes-hack/ Discussion]
|- style="background: #81BEF7"
|SNK Neo Geo
|[[GnGeo]] 0.8.3
|2011-04-20
|[http://repo.openpandora.org/?page=detail&app=gngeopnd-pepone Repo]
|Pepone, Manolis
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59207-gngeo-0-8-2/page__view__findpost__p__946739 GP32X] [http://boards.openpandora.org/index.php?/topic/2936-gngeo-083/ OP]
|- style="background: #xxxxxx"
|SNK Neo Geo
|NeoGeo SDL
|2009-04-03
|[http://www.pandorasource.de/download.php?view.13 Download]
|Cpasjuste
|
|
|
|-
|SNK NeoGeo Pocket
|NeoPop
|2010-07-15
|[http://www.pdroms.de/files/1969/ Download]
|Cpasjuste
|
|
|[http://www.gp32x.com/board/index.php?/topic/58848-neopop-ngpc-emulator-released/ Discussion]
|- style="background: #xxxxxx"
|SNK Neo Geo Pocket
|[[Race]]
|2010-06-20
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/race10.inf Apps]
|Hooka
|
|
|[http://www.gp32x.com/board/index.php?/topic/54187-race-a-neo-geo-pocket-color-emulator Discussion]
|- style="background: #F7BE81"
|Sony Playstation
|[[PSX4Pandora]]
|2010-11-16
|[http://www.zodttd.com/downloads/psx4pandora10b5.pnd Download]
|ZodTTD
|[http://spreadsheets.google.com/pub?key=0AkBB6e4g1lGtdFVwODhsQzdlWVdrMTRKdDFXa1laZ2c&hl=en_GB&output=html GD]
|
|[http://www.gp32x.com/board/index.php?/topic/57522-psx4pandora-1-0b5/ Discussion]
|- style="background: #90FF90"
|Sony Playstation
|[[PCSX-ReARMed]] r14
|2012-03-04
|[http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz Repo] [http://notaz.gp2x.de/releases/pcsxr/pcsx_rearmed_r14.pnd Download]
|notaz
|[https://spreadsheets.google.com/ccc?key=0ArSWWAWRjErldHZVZlFxY0tBVnRRNXM5U3ZqWFNuN0E&hl=en#gid=0 GD]
|[http://boards.openpandora.org/index.php?/topic/4046-tutorial-how-to-save-space-on-ps1-games-without-ripping-video-or-music/ pbp]
|[http://boards.openpandora.org/index.php?/topic/6546-pcsx-rearmed-r13-with-a-new-gpu/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57973-pcsx-rearmed/page__view__findpost__p__955679 old thread]
|-
|Thomson TO8D
|[[TO8_PND]]
|2011-11-15
|[http://repo.openpandora.org/?page=detail&app=TO8D_PND Repo]
|SladeCraven
|
|None
|Emulates the Thomson TO8/TO8D computer. [http://boards.openpandora.org/index.php?/topic/6076-thomson-to8-emulator-beta-version-040/page__fromsearch__1 Discussion]
|-
|TI89/TI89 Titanium / TI92/TI92+ / V200PLT
|[[TiEmu]]
|2011-09-10
|[http://repo.openpandora.org/?page=detail&app=tiemu-6232 Repo]
|Kazuki
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TI-99
|Pandora-TI99 ([[TI99Sim]])
|2010-07-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,164 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/147-TI99 Download]
|zx-81
|
|
|
|-
|TI-92
|[[XTiger]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ti92-1.1.0.inf Apps]
|zx-81
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TRS-80
|[[SDLTRS]]
|2011-08-03
|[http://www.mediafire.com/download.php?72etxpjqaosa11b Download]
|Blue Protoman
|
|
|I give no support to this! This is a hackjob port!
|- style="background: #81BEF7"
|Vectrex
|[[Pandora-Vectrex]] v1.1.1
|2011-03-06
|[http://zx81.zx81.free.fr/public/pandora/vectrex/pandora-vectrex-v1.1.1-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58846-pandora-vectrex-vectrex-emulator-for-pandora-v110/page__view__findpost__p__942010 Discussion] Download game overlays [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,355 here].
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox]] v0.74svn
|2010-11-09
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,54 Archive]
|Pickle
|[[DOSBox compatibility list|W]]
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/57424-dosbox/ GP32Xa] [http://www.gp32x.com/board/index.php?/topic/53942-post-your-dosbox-successes-here/ GP32Xb] [http://boards.openpandora.org/index.php?/topic/2346-dosbox-room-for-optimization/ OPa] [http://boards.openpandora.org/index.php?/topic/2063-dosbox/ OPb]. [http://www.dosbox.com/comp_list.php General compatibility list]
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox EX]]
|2011-08-16
|[http://ompldr.org/vOXhhMA/dosbox_ex.pnd.zip Download]
|StreaK
|
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60175-dosbox-ex-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4855-dosbox-ex/ OP]
|- style="background: #F3F781"

|x86 PC
|[[Qemu for Pandora]]
|2012-03-02
|[http://www.openpandora.org/rebirth/qemu.pnd Download]
|IngoReis, mcobit
|
|None
|Discussion: [http://boards.openpandora.org/index.php?/topic/7004-qemu-for-pandora-for-rebirth-competition OP-Boards]
|- style="background: #F3F781"
|x86 Windows 3.1 r2, r1
|[[WinBox]] ('''beta''')
|2010-12-15
|[http://repo.openpandora.org/?page=detail&app=winbox-1 Repo] [http://urjaman.dyndns.info/winbox_r2.pnd Download]
|urjaman
|
|None
|[http://www.gp32x.com/board/index.php?/topic/54985-win-3-1-via-dosbox-at-native-resolution/page__view__findpost__p__887198 Discussion] {{HideableNotes|Modified DOSBox to run Windows 3.1 at Pandora's native resolution}}
|-
|ZX-80 & ZX-81
|sz81
|2011-08-19
|[http://ompldr.org/vOXk0eA/sz81.pnd.zip Download]
|StreaK
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Fuse]]
|2010-06-24
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/fuse-0.9.0.inf Apps] [http://repo.openpandora.org/?page=detail&app=fuse.cosam.0.10.0.2 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Zx Pandy]] v3.2.1.4
|2011-04-12
|[http://repo.openpandora.org/?page=detail&app=zx_pandy.dave18.001 Repo]
|Dave18
|
|
|[http://www.gp32x.com/board/index.php?/topic/58536-zx-pandy-released/ Discussion]
|}

1 "C" is short for compatibility list.
FT = Forum Topic
GD = Google Docs
W = Wiki page

2 "CS" is short for "Compression Support". The entries denote the formats that can be used to save space on the games. A blank entry doesn't mean "none", it means there's not enough info! Please add more if you can!

==Unreleased emulators==
This section includes both emulators that are actively being worked on, as well as ones that are or may be abandoned. The latter are included for historical purposes.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
!Emulated System
!Project Name
!Last Update
!Status
!Author/Port Author
!Notes
|-
|Acorn BBC Micro
|BeebEm
|[http://boards.openpandora.org/index.php?/topic/1094-bbc-emulation-merged-thread/page__st__20#entry147214 2012-05-12]
|PND, two working builds
| [http://wiki.gp2x.org/wiki/BeebEm Authors], PND by [http://sam.nipl.net/ sswam]
|[http://pandoria.org/pnd/beebem.pnd PND] [http://repo.openpandora.org/?page=detail&app=beebem-15428 Repo] [http://boards.openpandora.org/index.php?/topic/1094-bbc-emulation-merged-thread/ Discussion] [http://www.gp32x.com/board/index.php?/topic/43489-beebem-for-gp2x-06-bbc-micro-emulator GP2X]
|-
|Amstrad PCW
|Joyce / Anne emu
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/page__view__findpost__p__85612 2011-08-18]
|Abandoned
|StreaK
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/ Discussion] Discontinued: StreaK left the community.
|-
|Sega Dreamcast
|NullDC
|[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 2011-03-28]
|On hold
|Zezu / drkIIraziel
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910] drkIIraziel says he will have time to work on it "[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 after April 10]"
|-
|Nintendo SNES
|[[PandaSNES]]
|[http://www.gp32x.com/board/index.php?/topic/43213-any-snes-fans-in-the-house/page__view__findpost__p__631020 2008-07-29]
|Abandoned
|Squidge
|[http://www.gp32x.com/board/index.php?showtopic=43213] Probably discontinued; Squidge has not been heard from for a long time.
|-
|Sony Playstation Portable
|Pandora-PSP
|[http://jannikvogel.de/2011 2011-01]
|Abandoned
|[[User:JayFoxRox|JayFoxRox]]
|[http://www.gp32x.com/board/index.php?showtopic=47270] Probably discontinued; JayFoxRox has since left the community.
|-
|}

==External links==
*[http://sebt3.openpandora.org/pnd/ Releases by sebt3]
*[http://www.hermocom.com/en/downloads/openpandora/ Releases by Hermocom]
*[http://rebirthofxeen.com/files/pandora/ Releases by WizardStan]
*[http://www.stuckiegamez.co.uk/apps/pandora/ Releases by StuckieGamez]

===Forums===
The following community forums are checked when updating this page:
*From GP32X: [http://www.gp32x.com/board/index.php?/forum/63-news-zone-pandora/ News Zone], [http://www.gp32x.com/board/index.php?/forum/71-beta-testing-pandora/ Beta Testing] and [http://www.gp32x.com/board/index.php?/forum/64-developers-corner-pandora/ Developer's Corner]
*From OP: [http://boards.openpandora.org/index.php?/forum/26-software-news/ Software News] and [http://boards.openpandora.org/index.php?/forum/10-beta-testing/ Beta Testing]
*From GP2X.de: [http://forum.gp2x.de/viewforum.php?f=24 News] and [http://forum.gp2x.de/viewforum.php?f=59 Betatest]

[[Category:Emulators]]
[[Category:Software]]
[[Category:List]]

Emulator List

2012-11-25T19:39:18Z

Notaz: sort sources by relevance

''These lists were last updated on 2012-06-13 to include the latest files from [http://repo.openpandora.org/ Repo], the [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5 File Archive], the [http://apps.open-pandora.org/cgi-bin/viewarea.pl?Emulators Pandora Apps], and the [[Emulator list#Forums|community forums]]. For other software lists on the wiki, see [[Software projects]] and [[Games]].''

If different versions of an [[emulator]] were released, the listed "release date" is from the most recent one.

Please click on the little squares to sort by different categories.

To read a usage guide for several emulators, download [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,404 this guide].

==Released emulators==

Entry colors only denote compatibility and speed; interface and features are not taken into account.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Quality
!Description
|- style="background: #81BEF7"
|Perfect
|Emulators with a '''blue''' background, for all intents and purposes, work perfectly. Virtually every game runs at full speed, and ones that don't come close. No overclocking required. Practically no compatibility issues, with the possible exception of extremely obscure hardware tricks or addons.
|- style="background: #90FF90"
|Fantastic
|Emulators with a '''green''' background work very well. A lot of games run great at or close to 500Mhz, though some issues do exist. Little overclocking is required. Compatibility issues are minimum.
|- style="background: #F3F781"
|Decent
|Emulators with a '''yellow''' background have issues. Some games are playable, and a few do run full speed, but overclocking is typically needed. Compatibility issues may be considerable. This could also represent emulators with great compatibility, but low speed (or vice versa).
|- style="background: #F7BE81"
|Bad
|Emulators with an '''orange''' background do not run well. Few games are playable. Overclocking is mandatory. There may be lots of compatibility issues as well.
|- style="background: #F78181"
|Poor
|Emulators with a '''red''' background are worthless. No games are playable at 500Mhz, and you have to overclock very high to see a difference. Full speed is out of the question. Compatibility is likely nonexistent. This is test release territory.
|-
|N/A
|Emulators with a '''white''' background do not have enough information about them. Please try them out and add to this page!
|}


''If you have tried an emulator which has an uncoloured background, please add the appropriate background colour based on the legend to reflect the status of the emulator. You may add a statement in the notes if you feel that it's necessary.''

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Emulated System
! Project Name
! Release Date (YYYY-MM-DD)
! Download
! Authored or Ported By
! C1
! CS2
! Notes
|- style="background: #90FF90"
|Various{{HideableNotes| Atari Lynx, Bandai Wonderswan, GBA, GB/C, Sega Game Gear, Sega Master System, PC Engine/CD, NES, Virtual Boy, Neo Geo Pocket Colour}}
|Mednafen 0.9.17.r3
|2011-07-13
|[http://repo.openpandora.org/?page=detail&app=package.mednafen-pandora.r3 Repo]
|pder
|
|zip, [http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://www.gp32x.com/board/index.php?/topic/59533-mednafen-0-9-17-1-wip/page__gopid__950099&#entry950099 Discussion] GBA and VB don't run fullspeed.
|- style="background: #90FF90"
|Acorn RISC-PC
|[[pandrpcemu]] ('''beta''')
|2011-05-28
|[http://www.pokenet.co.uk/misc/files.pandora/pandrpcemu.pnd Download] [http://repo.openpandora.org/?page=detail&app=pandrpcemu Repo]
|hideki
|
|None
|[http://boards.openpandora.org/index.php?/topic/3762-pandrpcemu-beta-acorn-risc-pc/ Discussion] Also available natively (32-bit RO5) under [[Software projects#Unreleased software ("Projects Under Development")|Software projects]]
|- style="background: #90FF90"
|Amiga 500 / Amiga 1200
|[[UAE4ALL]] V2.0
|2012-06-13
|[http://repo.openpandora.org/?page=detail&app=uae4all Main version]
|John4p, Pickle, Notaz, tuki_cat, et al.
|[http://spreadsheets.google.com/pub?key=0AuBR5X_s_5_idG92ZVQ5cEs4ZEhYTm5sSjFIcl83U2c&hl=en&gid=0 GD]
|gzip
|"UAE4All 2.0 only works with FAME/C core. Cyclone and UAE core are not compatible.
Thus UAE4All 2.0 replaces the old FAME/C release. The old Cyclone and UAE core releases are still available in this release (but they're still UAE4All 1.1 and won't see new features). [http://boards.openpandora.org/index.php?/topic/8770-uae4all-20/ Discussion] {{HideableNotes|}}
|- style="background: #F3F781"
|Amiga 1200
|[[P-UAE]]
|2010-06-06
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/puae.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,86 Archive]
|Gnostic
|
|
|
|- style="background: #F3F781"
|Amiga
|[[pandeuae]] ('''beta''')
|2011-05-09
|[http://www.hidnet.org.uk/pandeuae.pnd Download]
|hideki
|
|
|[http://boards.openpandora.org/index.php?/topic/3350-euae-port/ Discussion]
|- style="background: #81BEF7"
|Amstrad CPC
|[[Pandora-CAP32]]
|2010-06-27
|[http://zx81.zx81.free.fr/public/pandora/cap32/pandora-cap32-v1.1.0-bin.zip Download] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,115 Archive]
|zx-81
|
|gzip
|[http://www.gp32x.com/board/index.php?/topic/54801-pandora-cap32-v1-1-0/ Discussion]
|- style="background: #90FF90"
|Apple II
|[[LinApple]] 1.3.5.0
|2011-09-13
|[http://repo.openpandora.org/?page=detail&app=linapple-jerryblade-042011 Repo]
|JerryBlade, CFWhitman
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59229-apple-emulator-for-pandora/page__view__findpost__p__957512 GP32X] [http://boards.openpandora.org/index.php?/topic/2490-apple-ii-emulator/ OP]
|- style="background: #90FF90"
|Arcade (laserdisc)
|[[Daphne]] v1.0.0.3
|2011-08-14
|[http://repo.openpandora.org/?page=detail&app=daphne-daphne-25097 Repo]
|mcobit
|
|[http://winff.org/html_new/ Bitrate]
|[http://boards.openpandora.org/index.php?/topic/4852-daphne-wip/ Discussion] {{HideableNotes|Use [http://winff.org/html_new/ WinFF] to re-encode your video files to a lower bitrate if necessary, as doing so will improve speed and shrink the file. Faster SD cards also improve speed greatly.}}
|- style="background: #F3F781"
|Arcade
|[[MAME]] v0.106
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/mame106.pnd.inf Apps] [http://repo.openpandora.org/?page=detail&app=mame.cosam.106 Repo]
|SteveM
|
|zip
|{{HideableNotes|Runs more games than MAME4ALL, but at a slower speed.}}
|- style="background: #90FF90"
|Arcade
|[[MAME4All]] v2.5b7
|2010-09-07
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,200 Archive] [http://repo.openpandora.org/?page=detail&app=mame4all.cosam.2.5-beta7 Repo]
|SteveM, Franxis
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56188-mame4all-beta/ Discussion]
|- style="background: #xxxxxx"
|Arcade
|SDLMAME v.110
|2010-06-30
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,106 Archive]
|?
|
|zip
|Use MAME4ALL instead, this is slow.
|- style="background: #xxxxxx"
|Atari 520
|PAtari v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.4 Download]
|cpasjuste
|
|
|
|-
|Atari 800
|Atari800
|2011-08-06
|[http://ompldr.org/vOXUxYQ/atari800.pnd.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60165-atari-800-emulator-almost-final/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #xxxxxx"
|Atari 8-Bit
|Pandora-Atari
|2010-08-04
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/atari-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,173 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/55724-pandora-atari-atari-8001305200-emulator-for-pandora-v110/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #90FF90"
|Atari Lynx
|[[Handy]]
|2010-06-18
|[http://repo.openpandora.org/?page=detail&app=handy.cosam.0.5.0.0 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54220-handy/ Discussion] {{HideableNotes|Do not turn on the FPS counter, or else the emulator will slow down dramatically.}}
|- style="background: #xxxxxx"
|Atari ST
|Hatari 1.0.3.2
|2011-08-02
|[http://repo.openpandora.org/?page=detail&app=hatari.skeezix.pkg Repo]
|Skeezix
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58088-hatari-atari-st-emu-140-released/page__view__findpost__p__934671 Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2010-05-07
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/Stella312a.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,53 Archive]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 2600
|Pandora-2600 ([[Stella]])
|2010-07-11
|[http://zx81.zx81.free.fr/public/pandora/2600/pandora-2600-v1.1.0-pnd.zip Download] [http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/2600-1.1.0.inf Apps]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54934-pandora-2600-atari-2600-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2011-08-03
|[http://ompldr.org/vOXF0dQ/stella.pnd Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60123-stella-atari-2600-beta-in-pnd/ Discussion]. {{HideableNotes|PAL games don't run.}}
|-
|Atari VCS 2600
|[[Stella]] 3.4.2.2
|2011-10-06
|[http://repo.openpandora.org/?page=detail&app=stella-svn Repo]
|Lomaxx
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 7800
|Pandora-7800 v1.1.0
|2010-07-11
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,146 Archive] [http://zx81.zx81.free.fr/public/pandora/7800/pandora-7800-v1.1.0-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/55189-pandora-7800-atari-7800-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Colecovision
|[[Colem]]
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem_alpha.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,70 Archive] [http://repo.openpandora.org/?page=detail&app=colem.skeezix Repo]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Colecovision
|[[Pandora Colem]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,129 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/60164-colem-port-of-zx81-slightly-modified/ Discussion for modified version (no PND)]
|- style="background: #90FF90"
|Commodore 64
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceX64.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,46 Archive]
|Pickle
|
|
|{{HideableNotes|Very good emulation, deactivate wrap mode in speed seetings if you suffer sound problems}}
|- style="background: #xxxxxx"
|Commodore (Other)
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceMisc.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,47 Archive]
|Pickle
|
|
|{{HideableNotes|Emulates the CBM2, C128, PET, Plus4, and VIC platforms.}}
|- style="background: #90FF90"
|GPH GP2X/Wiz
|[[Ginge]]
|2010-08-16
|[http://repo.openpandora.org/?page=detail&app=package.ginge.notaz Repo]
|Notaz
|
|None
|{{HideableNotes|Not really an emulator. [http://www.gp32x.com/board/index.php?/topic/55980-ginge/page__view__findpost__p__913442 DO NOT run from root]. To get rid of the default blur filter, use [http://www.gp32x.com/board/index.php?/topic/57179-pandora-emulators-vs-gp2xwiz-emulators/page__view__findpost__p__923471 this solution].}}
|- style="background: #xxxxxx"
|HP-48
|[[Pandora-X48]]
|2010-06-17
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,113,96 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/129-HP-48 Download]
|zx-81
|
|
|Emulates a calculator. [http://www.gp32x.com/board/index.php?/topic/54482-x48/ Discussion]
|- style="background: #xxxxxx"
|Macintosh 68K
|Basilisk II
|2010-12-15
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=512 Download] [http://www.mediafire.com/?ue5eyole855fyul 2]
|dgame
|
|
|[http://www.gp32x.com/board/index.php?/topic/56900-basilisk-ii-pnd-68k-macintosh-emulator/ Discussion]
|- style="background: #xxxxxx"
|Mattel Intellivision
|[[Jzintv]]
|2010-09-02
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/jzintv.inf Apps]
|WizardStan
|
|
|[http://www.gp32x.com/board/index.php?/topic/56426-jzintv/ Discussion]
|- style="background: #xxxxxx"
|MSX
|[[Pandora-MSX]]
|2010-06-26
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/msx-1.1.1.inf Apps]
|zx-81
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/54775-pandora-msx-v1-1-0/ Discussion] {{HideableNotes|Only disk images may be gzippped, and if they are, they cannot be written to.}}
|-
|NEC PC-9801
|[[Xnp2]]
|2011-05-01
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,393 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/xnp2.inf Apps] [http://www.mediafire.com/?57qer2aud0e8p9y Download]
|quews (port)
|
|
|[http://www.youtube.com/watch?v=Bd3a-duBfdU Video]
|- style="background: #xxxxxx"
|NEC PC Engine
|[[Pandora HuGo]]
|2010-06-28
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/hugo-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,117 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54833-hugo-pandora-v1-1-0/ Discussion]
|- style="background: #xxxxxx"
|NEC PC Engine
|Temper (alpha)
|2011-07-25
|[http://exophase.devzero.co.uk/temper.pnd Download]
|Exophase
|
|[http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://boards.openpandora.org/index.php?/topic/4621-temper-split-from-other-thread/ Discussion] Also supports the SuperGrafx.
|- style="background: #81BEF7"
|NES
|[[GPFCE-GP2X]]
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,224 Archive] [http://repo.openpandora.org/?page=detail&app=gpfcegp2x Repo]
|notaz
|
|zip
|{{HideableNotes|The GP2X version of GPFCE, packaged into a PND with Ginge.}}
|- style="background: #81BEF7"
|NES
|[[GPFCE]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,72 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/gpfce.inf Apps]
|Notaz, Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|zip
|{{HideableNotes|Sound works if you set the rate to 44000Hz in the options. Forces a 2xsai like filter.}}
|- style="background: #xxxxxx"
|NES
|[[nesemu]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,71 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/nesemu.inf Apps]
|Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|
|[http://code.google.com/p/nesemu/ Website] Seems to only run at 40fps.
|- style="background: #F3F781"
|NES
|[[Nestopia]]
|2011-08-01
|[http://ompldr.org/vOXB2Mg/nestopia_openpandora_streak.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60112-nestopia-for-openpandora-beta/ Discussion] {{HideableNotes|Emulator focus is accuracy. Very high compatibility at a cost of speed. Not a PND.}}
|- style="background: #F3F781"
|Nintendo 64
|[[Mupen64Plus]] 1.5.r20110615.2
|2011-06-16
|[http://repo.openpandora.org/?page=detail&app=mupen64plus Repo]
|Ari64, Adventus, JayFoxRox, sebt3, et al.
|[http://tinyurl.com/6ccuqmc GD]
|zip, 7z, bzip2
|[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__951543 Discussion] Compatibility list is mostly outdated. {{HideableNotes|To get good auto-frameskip, switch to gles2n64 0.0.5, set frame render rate 2, auto frameskip 1 -[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__946705]}}
|- style="background: #F78181"
|Nintendo DS
|[[Desmume]]
|2011-08-04
|[http://www.2shared.com/file/wxnc3MRT/desmume097.html Download]
[http://www.mediafire.com/?8gvvhqz3e2zkxzj 2]
|notaz
|
|
|[http://boards.openpandora.org/index.php?/topic/4744-nintendo-ds-emulator/page__view__findpost__p__82779 Discussion] Not meant for entertainment; was ported only to shut people up.
|- style="background: #F3F781"
|Nintendo GBA/GBC/GB
|[[VisualBoyAdvance]]
|2010-12-08
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/vba-1.7.2-0.inf Apps] [http://www.mediafire.com/?7qbxlnp0h2isokf Download]
|EvilDragon, SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/57808-visualboyadvance-v1-7-2-1/page__p__929521&#entry929521 Discussion]. Runs GB/C well; GBA is slow
|- style="background: #81BEF7"
|Nintendo GBA
|[[gpSP]]
|2011-09-08
|[http://repo.openpandora.org/?page=detail&app=package.gpsp.notaz Repo]
|Exophase, notaz
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60219-gba-emulator-that-you-can-adjust-the-screen-size/page__view__findpost__p__957136 GP32X] [http://boards.openpandora.org/index.php?/topic/5226-gpsp-for-pandora-from-notaz/ OP]. Zipped ROMs only. Now a native port with fullscreen scaling.
|- style="background: #90FF90"
|Nintendo GBA
|[[gpSP]] (Ginged)
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,199 Archive]
|Exophase, notaz
|
|zip
|[http://gpsp-dev.blogspot.com/ Website]. {{HideableNotes|Runs through [[Ginge]], only zipped ROMs. [http://www.gp32x.com/board/index.php?/topic/58722-im-looking-for-a-gba-emulator-without-blurry-upscaling/ No fullscreen scaling].}}
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnuBoy]] 1.0.5Svn
|2010-11-10
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,207 Archive] [http://repo.openpandora.org/?page=detail&app=sdlgnuboy Repo]
|Pickle, EvilDragon
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/56916-gnuboy-updated/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57436-gnuboy-v1-0-5-svn-released/ 2] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnGB]] ('''beta''')
|2010-10-04
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=482 Download] [http://www.mediafire.com/?7qbxlnp0h2isokf 2]
|dgame (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/56886-gngb-pnd-game-boy-and-game-boy-color-emulator/ Discussion]
|- style="background: #xxxxxx"
|Nintendo Pokémon mini
|[[Pokémini]] 0.4.4
|2011-04-13
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/pokemini.inf Apps] [http://www.mediafire.com/?05g9s8w780mt58g Download]
|Wally
|
|
|[http://boards.openpandora.org/index.php?/topic/2898-pokemini-emulator-pokemon-mini Discussion]
|- style="background: #xxxxxx"
|Oric-1/Atmos
|[[PandOricutron]]
|2010-06-16
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/PandOricutron_108.inf Apps]
|torpor
|
|
|[http://www.gp32x.com/board/index.php?/topic/54260-pandoricutron-1-0-8/ Discussion]
|- style="background: #xxxxxx"
|PDP-11
|[[SIMH PDP-11]]
|2010-05-28
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,83 Archive] [http://repo.openpandora.org/?page=detail&app=msimh.cosam.3.8.0.0 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|Philips Odyssey 2
|[[O2EM]] 1.18-1
|2010-08-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,186 Archive] [http://repo.openpandora.org/?page=detail&app=o2em Repo]
|Hitnrun, Daniel Boris
|
|
|
|-
|SAM Coupé
|[[SimCoupe]]
|2011-08-19
|[http://ompldr.org/vOXlsaw/simcoupe.pnd.zip Download]
|StreaK
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60220-simcoupe-a-sam-coupe-emulator-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4947-simcoupe-a-sam-coupe-emulator-beta/ OP]
|- style="background: #81BEF7"
|Sega Genesis, CD, 32X, Master System
|[[PicoDrive]] 1.80
|2010-09-19
|[http://repo.openpandora.org/?page=detail&app=package.picodrive.notaz Repo]
|Notaz
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56713-picodrive-1-80/ Discussion] ([http://www.gp32x.com/board/index.php?/topic/53899-picodrive-released/ old]). {{HideableNotes|Master System support is preliminary. Not all 32X games run.}}
|- style="background: #xxxxxx"
|Sega Master System & Game Gear
|[[Dega]] v1.16-4
|2010-08-15
|[http://repo.openpandora.org/?page=detail&app=dega.cosam.1.16.0.2 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54914-dega/ Discussion]{{HideableNotes|Press R+number to save, L+number to load, Pandora key to quit}}
|- style="background: #xxxxxx"
|Sega Master System
|PSMS v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.10 Download]
|cpasjuste
|
|
|
|- style="background: #F7BE81"
|Sega Saturn
|Yabause r2660
|2011-08-06
|[http://hotfile.com/dl/126054899/6ca83f7/yabause-r2660.pnd.html Download] [http://www.mediafire.com/?fmbn5ij2t3mucjh 2]
|Ari64
|[https://spreadsheets.google.com/spreadsheet/ccc?key=0Aq4SN3wYVIxgdHB4Z2hHcE9fQ3lTaTVMelEyZVBsVFE GD]
|
|[http://boards.openpandora.org/index.php?/topic/4583-yabause/ Discussion]
|- style="background: #xxxxxx"
|Sega Genesis
|DGen/SDL 1.30 Alpha Build 2
|2012-05-25
|[http://www.sendspace.com/file/a8af4p Download]
|Kazuki
|
|
|
|- style="background: #90FF90"
|SNES
|[[SNES9X4P]] 1.39ff - v20111205-2
|2011-12-06
|[http://repo.openpandora.org/?page=detail&app=snes9x4p_ivanovic Repo]
|HideableNotes|Ivanovic, Skeezix, SiENcE (Dingoo)
|
|7z
|Dingoo Snes9x port. [http://www.gp32x.com/board/index.php?/topic/55378-snes9x4d4p-another-new-build-now-with-hi-res-and-new-rom-picker/page__view__findpost__p__958887] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|SNES
|SNES9X v0.2
|2009-04-03
|[http://www.pandorasource.de/download.php?view.7 Download]
|cpasjuste (port)
|
|
|
|- style="background: #xxxxxx"
|SNES
|[[PocketSNES]] ('''beta''') 0.1
|2010-08-08
|[http://www.rangelreale.com/pandora/pocketsnes_hack_0.1.pnd Download]
|Hitnrun (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/55796-pocketsnes-hack/ Discussion]
|- style="background: #81BEF7"
|SNK Neo Geo
|[[GnGeo]] 0.8.3
|2011-04-20
|[http://repo.openpandora.org/?page=detail&app=gngeopnd-pepone Repo]
|Pepone, Manolis
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59207-gngeo-0-8-2/page__view__findpost__p__946739 GP32X] [http://boards.openpandora.org/index.php?/topic/2936-gngeo-083/ OP]
|- style="background: #xxxxxx"
|SNK Neo Geo
|NeoGeo SDL
|2009-04-03
|[http://www.pandorasource.de/download.php?view.13 Download]
|Cpasjuste
|
|
|
|-
|SNK NeoGeo Pocket
|NeoPop
|2010-07-15
|[http://www.pdroms.de/files/1969/ Download]
|Cpasjuste
|
|
|[http://www.gp32x.com/board/index.php?/topic/58848-neopop-ngpc-emulator-released/ Discussion]
|- style="background: #xxxxxx"
|SNK Neo Geo Pocket
|[[Race]]
|2010-06-20
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/race10.inf Apps]
|Hooka
|
|
|[http://www.gp32x.com/board/index.php?/topic/54187-race-a-neo-geo-pocket-color-emulator Discussion]
|- style="background: #F7BE81"
|Sony Playstation
|[[PSX4Pandora]]
|2010-11-16
|[http://www.zodttd.com/downloads/psx4pandora10b5.pnd Download]
|ZodTTD
|[http://spreadsheets.google.com/pub?key=0AkBB6e4g1lGtdFVwODhsQzdlWVdrMTRKdDFXa1laZ2c&hl=en_GB&output=html GD]
|
|[http://www.gp32x.com/board/index.php?/topic/57522-psx4pandora-1-0b5/ Discussion]
|- style="background: #90FF90"
|Sony Playstation
|[[PCSX-ReARMed]] r14
|2012-03-04
|[http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz Repo] [http://notaz.gp2x.de/releases/pcsxr/pcsx_rearmed_r14.pnd Download]
|notaz
|[https://spreadsheets.google.com/ccc?key=0ArSWWAWRjErldHZVZlFxY0tBVnRRNXM5U3ZqWFNuN0E&hl=en#gid=0 GD]
|[http://boards.openpandora.org/index.php?/topic/4046-tutorial-how-to-save-space-on-ps1-games-without-ripping-video-or-music/ pbp]
|[http://boards.openpandora.org/index.php?/topic/6546-pcsx-rearmed-r13-with-a-new-gpu/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57973-pcsx-rearmed/page__view__findpost__p__955679 old thread]
|-
|Thomson TO8D
|[[TO8_PND]]
|2011-11-15
|[http://repo.openpandora.org/?page=detail&app=TO8D_PND Repo]
|SladeCraven
|
|None
|Emulates the Thomson TO8/TO8D computer. [http://boards.openpandora.org/index.php?/topic/6076-thomson-to8-emulator-beta-version-040/page__fromsearch__1 Discussion]
|-
|TI89/TI89 Titanium / TI92/TI92+ / V200PLT
|[[TiEmu]]
|2011-09-10
|[http://repo.openpandora.org/?page=detail&app=tiemu-6232 Repo]
|Kazuki
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TI-99
|Pandora-TI99 ([[TI99Sim]])
|2010-07-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,164 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/147-TI99 Download]
|zx-81
|
|
|
|-
|TI-92
|[[XTiger]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ti92-1.1.0.inf Apps]
|zx-81
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TRS-80
|[[SDLTRS]]
|2011-08-03
|[http://www.mediafire.com/download.php?72etxpjqaosa11b Download]
|Blue Protoman
|
|
|I give no support to this! This is a hackjob port!
|- style="background: #81BEF7"
|Vectrex
|[[Pandora-Vectrex]] v1.1.1
|2011-03-06
|[http://zx81.zx81.free.fr/public/pandora/vectrex/pandora-vectrex-v1.1.1-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58846-pandora-vectrex-vectrex-emulator-for-pandora-v110/page__view__findpost__p__942010 Discussion] Download game overlays [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,355 here].
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox]] v0.74svn
|2010-11-09
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,54 Archive]
|Pickle
|[[DOSBox compatibility list|W]]
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/57424-dosbox/ GP32Xa] [http://www.gp32x.com/board/index.php?/topic/53942-post-your-dosbox-successes-here/ GP32Xb] [http://boards.openpandora.org/index.php?/topic/2346-dosbox-room-for-optimization/ OPa] [http://boards.openpandora.org/index.php?/topic/2063-dosbox/ OPb]. [http://www.dosbox.com/comp_list.php General compatibility list]
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox EX]]
|2011-08-16
|[http://ompldr.org/vOXhhMA/dosbox_ex.pnd.zip Download]
|StreaK
|
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60175-dosbox-ex-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4855-dosbox-ex/ OP]
|- style="background: #F3F781"

|x86 PC
|[[Qemu for Pandora]]
|2012-03-02
|[http://www.openpandora.org/rebirth/qemu.pnd Download]
|IngoReis, mcobit
|
|None
|Discussion: [http://boards.openpandora.org/index.php?/topic/7004-qemu-for-pandora-for-rebirth-competition OP-Boards]
|- style="background: #F3F781"
|x86 Windows 3.1 r2, r1
|[[WinBox]] ('''beta''')
|2010-12-15
|[http://repo.openpandora.org/?page=detail&app=winbox-1 Repo] [http://urjaman.dyndns.info/winbox_r2.pnd Download]
|urjaman
|
|None
|[http://www.gp32x.com/board/index.php?/topic/54985-win-3-1-via-dosbox-at-native-resolution/page__view__findpost__p__887198 Discussion] {{HideableNotes|Modified DOSBox to run Windows 3.1 at Pandora's native resolution}}
|-
|ZX-80 & ZX-81
|sz81
|2011-08-19
|[http://ompldr.org/vOXk0eA/sz81.pnd.zip Download]
|StreaK
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Fuse]]
|2010-06-24
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/fuse-0.9.0.inf Apps] [http://repo.openpandora.org/?page=detail&app=fuse.cosam.0.10.0.2 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Zx Pandy]] v3.2.1.4
|2011-04-12
|[http://repo.openpandora.org/?page=detail&app=zx_pandy.dave18.001 Repo]
|Dave18
|
|
|[http://www.gp32x.com/board/index.php?/topic/58536-zx-pandy-released/ Discussion]
|}

1 "C" is short for compatibility list.
FT = Forum Topic
GD = Google Docs
W = Wiki page

2 "CS" is short for "Compression Support". The entries denote the formats that can be used to save space on the games. A blank entry doesn't mean "none", it means there's not enough info! Please add more if you can!

==Unreleased emulators==
This section includes both emulators that are actively being worked on, as well as ones that are or may be abandoned. The latter are included for historical purposes.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
!Emulated System
!Project Name
!Last Update
!Status
!Author/Port Author
!Notes
|-
|Acorn BBC Micro
|BeebEm
|[http://boards.openpandora.org/index.php?/topic/1094-bbc-emulation-merged-thread/page__st__20#entry147214 2012-05-12]
|PND, two working builds
| [http://wiki.gp2x.org/wiki/BeebEm Authors], PND by [http://sam.nipl.net/ sswam]
|[http://pandoria.org/pnd/beebem.pnd PND] [http://repo.openpandora.org/?page=detail&app=beebem-15428 Repo] [http://boards.openpandora.org/index.php?/topic/1094-bbc-emulation-merged-thread/ Discussion] [http://www.gp32x.com/board/index.php?/topic/43489-beebem-for-gp2x-06-bbc-micro-emulator GP2X]
|-
|Amstrad PCW
|Joyce / Anne emu
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/page__view__findpost__p__85612 2011-08-18]
|Abandoned
|StreaK
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/ Discussion] Discontinued: StreaK left the community.
|-
|Sega Dreamcast
|NullDC
|[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 2011-03-28]
|On hold
|Zezu / drkIIraziel
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910] drkIIraziel says he will have time to work on it "[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 after April 10]"
|-
|Nintendo SNES
|[[PandaSNES]]
|[http://www.gp32x.com/board/index.php?/topic/43213-any-snes-fans-in-the-house/page__view__findpost__p__631020 2008-07-29]
|Abandoned
|Squidge
|[http://www.gp32x.com/board/index.php?showtopic=43213] Probably discontinued; Squidge has not been heard from for a long time.
|-
|Sony Playstation Portable
|Pandora-PSP
|[http://jannikvogel.de/2011 2011-01]
|Abandoned
|[[User:JayFoxRox|JayFoxRox]]
|[http://www.gp32x.com/board/index.php?showtopic=47270] Probably discontinued; JayFoxRox has since left the community.
|-
|}

==External links==
*[http://sebt3.openpandora.org/pnd/ Releases by sebt3]
*[http://www.hermocom.com/en/downloads/openpandora/ Releases by Hermocom]
*[http://rebirthofxeen.com/files/pandora/ Releases by WizardStan]
*[http://www.stuckiegamez.co.uk/apps/pandora/ Releases by StuckieGamez]

===Forums===
The following community forums are checked when updating this page:
*From GP32X: [http://www.gp32x.com/board/index.php?/forum/63-news-zone-pandora/ News Zone], [http://www.gp32x.com/board/index.php?/forum/71-beta-testing-pandora/ Beta Testing] and [http://www.gp32x.com/board/index.php?/forum/64-developers-corner-pandora/ Developer's Corner]
*From OP: [http://boards.openpandora.org/index.php?/forum/26-software-news/ Software News] and [http://boards.openpandora.org/index.php?/forum/10-beta-testing/ Beta Testing]
*From GP2X.de: [http://forum.gp2x.de/viewforum.php?f=24 News] and [http://forum.gp2x.de/viewforum.php?f=59 Betatest]

[[Category:Emulators]]
[[Category:Software]]
[[Category:List]]

Configuring ext signals

2012-11-19T14:28:29Z

Notaz: update

=Pin functions (mux)=
By default UART2 pins are set up as GPIOs, and UART3 as an UART.

==Changing pin functions under 3.2 kernel==
Described in the [http://boards.openpandora.org/index.php?/topic/4497-talking-to-the-gpios-on-the-ext-connector/page__st__40#entry195457 following forum post]

=Power supply=
Currently always set to supply 2.8V, changing this requires patching bootloaders (xload and u-boot).

This is connected to VAUX3 supply on PMIC, with these programmable voltages (200mA max):
1.5V, 1.8V, 2.5V, 2.8V and 3.0V, with 2.8V as default.

'''warning''': at the time of this writing, both bootloaders (xload and u-boot) set this to 2.8V unconditionally, so don't rely on this providing other voltages during reboot until you patch both bootloaders.

=GPIOs=
Can be controlled using GPIO sysfs class device, as described in beagleboard tutorials [http://bbfordummies.blogspot.com/2009/07/1.html here].

=UART3=
On older firmwares, kernel messages are directed there. SuperZaxxon or later have that disabled.

On all firmwares released so far terminal with a shell is attached to UART3. The port runs at 115200 8N1 baud rate.
==Disabling kernel messages==
To disable kernel mesages, you need to edit kernel boot arguments. Probably easiest way to do it is to create autoboot.txt and place on root directory of a card in slot1 with this content:
<source lang="bash">
setenv bootargs ubi.mtd=4 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw rootflags=bulk_read
</source>
Alternatives are using u-boot environment (configure through USB or UART3 serial before system boots up) or patching and reflashing u-boot itself.
==Disabling attached terminal==
For this you need to edit /etc/inittab on pandora rootfs and comment out these lines:
<source lang="bash">
#S0:2345:once:/sbin/getty 115200 ttyS0
#O2:2345:once:/sbin/getty 115200 ttyO2
</source>

USB compatibility list

2012-10-31T23:00:55Z

Notaz: this should be "tested on pandora", as it was before rev 8739

This is a list of USB devices that have been tested on the Pandora. If the device you want to know about isn't listed here, don't worry! Just go to [[USB_reference|the USB reference page]], look up the specs of your device, and you may be able to figure out if it's compatible.

= Troubleshooting =

Each type of device will have its own unique way to troubleshoot.

But here are some general tips:

* Is USB-Host enabled?
* check <tt>lsusb</tt>
* check <tt>dmesg</tt>

When asking for help on [http://boards.openpandora.org/index.php?/forum/8-support/ the forums support board], be sure to post both your <tt>lsusb</tt> and <tt>dmesg</tt>.

Because <tt>dmesg</tt> output is very long, you need to paste it within [spoiler] tags like this:

[spoiler]
(paste your dmesg in here)
[/spoiler]

An easy way to get your <tt>dmesg</tt> so you can easily copy and paste it, is:

dmesg|leafpad

<tt>leafpad</tt> will open with the output of <tt>dmesg</tt>.

If you have no networking on your palmtop, you can send the information to a text file like this:

cd (your storage card)
dmesg>textfile.txt
sync

Then you can remove your card (if no programs are using it or PNDs are running on it) and bring it to a card reader on your desktop.

= Networking =

Please see the [[Mobile broadband]] page for tips on how to get these working, as well as [http://www.gp32x.com/board/index.php?/topic/54318-guide-mobile-broadband-usb-stick-usage/ this tutorial] from the GP32X forum.

== HSDPA (3G) Modems ==

Please note that many (if not all) USB 3G modems need modemmanager to be installed for switching from mass storage mode to serial communications mode. When first plugged in, most 3G USB modems claim to be a mass storage device and offer, on its built-in flash, drivers and connectivity software to be installed. Mostly this is only for Windows and Mac, so for the Pandora this is not useful. modemmanager instantly takes care of toggling the mode, so that when you plug in the modem, after a few seconds or maybe half a minute modemmanager has switched the modem to communications mode and NetworkManager is able to use it.

If you are using a Firmware before HF7 (or one of its Alpha/Beta versions) you have to install modemmanager. To do so, connect your Pandora to the Internet, open a terminal and, as a super user, intall it via opkg by entering the commands:

:sudo opkg update
:sudo opkg install modemmanager

'''Note:''' If you are using a firmware more recent than "Zaxxon" Hotfix 6 (starting with HF7) you do not have to follow the steps outlined above since modemmanager comes preinstalled.

'''Note 2:''' After plugging in the USB 3G modem, it may take some time until NetworkManager is able to use the modem. Wait for at least half a minute, until you give up and report that the modem doesn't work.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| ZTE K3565-Z / MF626 / MF627 / MF636
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes|Yes [http://www.gp32x.com/board/index.php?/topic/54318-guide-mobile-broadband-usb-stick-usage/page__view__findpost__p__956513] [http://boards.openpandora.org/index.php?/topic/7226-superzaxxon-beta-11-released/page__pid__127881#entry127881]}}
| A how-to by shideneyu for this modem can be found [http://www.pandorawiki.org/ZTE_K3565Z_3G_USB_Modem here]
|-
|-
| BandLuxe C270
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| A how-to by relliker for this modem can be found [http://www.pandorawiki.org/BandLuxe_C270_3G_USB_Modem here]
|-
| Huawei E156G
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes|Yes [http://www.gp32x.com/board/index.php?/topic/52827-3gumts-usb-dongle/page__view__findpost__p__835681]}}
|
|-
| Huawei E160
| Not required
| Standard-A
| USB 2.0
| 250mA
| Standard-A port
| {{Yes}}
| As the entry for Huawei E220 was wrong, this Current draw could also be wrong. This one definitely needs modemmanager. After installing modemmanager, it works flawlessly.
|-
| Huawei E160E
| Not required
| Standard-A
| USB 2.0
| 250mA
| Standard-A port
| {{Yes}}
| As the entry for Huawei E220 was wrong, this Current draw could also be wrong.
|-
| Huawei E1750
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes|Yes [http://www.gp32x.com/board/index.php?/topic/54318-guide-mobile-broadband-usb-stick-usage/page__view__findpost__p__939350]}}
|
|-
| [[wikipedia:Huawei E220|Huawei E220]]
| Not required
| Standard-A
| USB 1.1
| 500mA
| Standard-A port via High Speed hub
| {{No|Not on new kernels.}}
| The successful Pandora E220 tests were done by DJWillis on an old kernel (long before Pandora shipped). It seems that they are NOT working any more. Also tested on Linux (was it working?) This entry originally said 250mA, but there is no source and current sources say 500mA.
|-
| 4G-Systems XS Stick P14
| Not required (usbserial module)
| standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes|Yes [http://www.gp32x.com/board/index.php?/topic/54318-guide-mobile-broadband-usb-stick-usage/page__view__findpost__p__937681]}}
| Requires usbmodeswitch program.
|-
| iPhone 3GS (Probably also 1G/3G)
| ipheth
| Standard-A
| USB 2.0
| 500mA
| {{Unknown|USB A (Standard-A port?)}}
| {{Maybe|Should work in Angstrom with some work.}}
| Requires a good bit of dependencies to get working. Tested with Debian from SD, but should work in Angstrom with some work. The ipheth wwan0 device only provides a connection over the 3G modem, even if you're connected to a wifi network. I used the iproxy and SSH tunneling method with proxychains to get to the wifi network.
|-
| HTC Desire
| not required
| Standard-A
| USB 2.0
| 500mA
| {{Unknown|USB A (Standard-A port?)}}
| {{Yes}}
| Requires internet connection sharing to be enabled from the phone.
|}

== USB to Ethernet adapters ==

To enable USB Ethernet adapters on the Pandora, you may need to left-click the networking icon on the panel in Xfce, and select "Ifupdown (bnep0)".

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| Apple USB Ethernet Adapter MB442Z/A
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| Reportedly uses an ASIX AX88xxx chipset.
|-
| Apple USB Ethernet Adapter model A1277
| Not required
| Standard-A
| USB 2.0
| 250mA
| Standard-A port
| {{Yes}}
| ID 05ac:1402 Apple, Inc.
|-
| Conrad 3-Port-USB-Hub und Netzwerk-Adapter
| Not required
| Standard-A
| USB 2.0
| A lot! {{HideableNotes|50% of battery charge only brings you 2h40min (min brightness, no other devices attached)}}
| Standard-A port
| {{Yes}}
| Has a 3port USB Hub included. External power supply can (and should) be attached, not included though. ASIX Chipset. 20€ @ [http://www.conrad.de/ce/de/product/976406/NOTEBOOK-MINI-DOCKINGSTATION-USBRJ45/SHOP_AREA_32315&promotionareaSearchDetail=005 Conrad Electronics]. Not tested in Linux.
|-
| Wii USB 2.0 10/100M adapter (use [http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=86;71;101 ASIX AX 88772 USB 2.0 chip])
| Not required
| Standard-A
| USB 2.0
| 250mA
| Standard-A port
| {{Yes}}
| ID 0b95:7720 ASIX Electronics Corp. AX88772. [http://www.dealextreme.com/details.dx/sku.5926 This clone from DealExtreme] works too.
|-
| Connectland USB 2.0 10/100M Ethernet Adapter
| Not required
| Standard-A
| USB 2.0
| 250mA
| Standard-A port
| {{Yes}}
| ID 0b95:7720 ASIX Electronics Corp. AX88772 - Works fine, Sometimes a reboot is necessary (ZaxxonHF5RC1).
|-
| Belkin Gigabit USB 2.0 Network Adapter
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| The shape of it make is a bit awkward to fit if you connect it directly, but it has a short adapter cable. I only get ~95Mbit on a gigabit network, but then the pandora's cpu maxes out. (it may be that the driver/usb stack isn't very well optimized), has horribly bright blue LEDs.
|-
| MosChip MCS7830 USB 10/100 Ethernet adapter
| Not required
| Standard-A
| USB 2.0
| 250-260mA
| Standard-A port
| {{Yes}}
| ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter. Kernel module: mcs7830.
|-
| EU.MARK USB 10/100M RJ45 Ethernet Network Adapter Dongle
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| USB ID: 9710:7830 - bought from [http://www.dealextreme.com/details.dx/sku.22684 DealExtreme]
|-
| Digitus DN-10050 Fast Ethernet USB Adapter
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| MosChip MCS7830-based adapter. USB ID 9710:7830.
|-
| Edimax EU-4230 Fast Ethernet USB Adapter with 3-port USB hub [http://edimax.ie/images/Image/datasheet/USB/EU-4230/EU-4230_Datasheet.pdf]
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| Ethernet USB ID 0b95:772a ASIX Electronics Corp. 3-port USB2.0 hub USB ID 0409:005a NEC Corp. Optional power adapter for USB hub.
|-
| Peabird USB v2.0 Fast Ethernet Adapter
| Not required
| Standard-A
| USB 2.0
| 500mA
| Standard-A port
| {{Yes}}
| ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter. Consumes a lot of current. Fragile, the protective plastic cord cracked after one month. Hot. A blue light a bit too flashy. Definitely avoid this model.
|-
| SIIG JU-NE0012-S1 USB 2.0 Fast Ethernet Adapter
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{Yes}}
| Bought from [http://www.newegg.com/Product/Product.aspx?Item=N82E16812191163 Newegg]
|-
| Novatel Wireless Jetpack 4620L
| cdc_ether
| Standard-A
| USB
| High drain; 95% charge = 6:00 battery life.
| Standard-A port
| {{Yes}}
| This is a LTE/EVDO/CDMA/HSPA/UMTS/EDGE/GPRS Wifi Hotspot device; Device is registered as a USB Ethernet device when connected through USB tethered (as opposed to Wifi) connection. USB ID 1410:b008
|}

== USB to serial adapters ==
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| pl203
| usbserial
| Standard-A
| USB 1.1
| 100mA. A powered hub is needed.
| Standard-A port
| {{Yes}}
| A powered hub is needed. Plug the device, then load USB modules. ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port.
|}

== USB WiFi adapters ==

The Pandora stock kernel may not come with all wireless driver support outside of the internal WiFi chip. Sometimes, the only way you'll get wireless working is to build your own kernel with it included or try [http://wireless.kernel.org/en/users/Download compat-wireless].

As for hofix 6a4 compat-wireless seems to be present in the kernel out of the box, so one can build a USB wireless driver for Pandora following this [http://boards.openpandora.org/index.php?/topic/5140-solvedbuilding-a-usb-wifi-driver/page__view__findpost__p__89280 algorithm]

As for [[hotfix 6]] Release Candidate the kernel includes drivers for these Realtek chips: RTL8712/8188/8191/8192SU/8192CU

See also [http://boards.openpandora.org/index.php?/topic/7160-micro-wifi-dongle/ this thread] on the forums for the latest.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Tested on Pandora
! Additional comments
|-
| Advance Mini Wireless N150
| rtl8192cu
| Standard-A
| USB 2.0
| 500mA
| USB A
| {{Yes|Yes}}
| There's a little hole on it, so it's useful for attaching it to the OP.
|-
| ASUS WL-167G v2
| rt73usb + rt2x00usb + rt2x00lib
| Standard-A
| USB 2.0
| 300mA
| USB A
| {{Yes|Nothing in lsusb, nothing in dmesg :(. Have to be plugged into a non-powered (or powered) USB hub. dmesg shows "failed to request firmware error". You just have to "cp /lib/firmware/rt73.bin /your/pandora-rootfs/lib/firmware/"}}
| 0b05:1723 ASUSTek Computer, Inc. WL-167G v2 802.11g Adapter [Ralink RT73]. Works pretty fine on Linux PC.
|-
| Belkin N1 Wireless USB Adapter (F5D8051) ("Ver. 2053") (MARVELL v1021)
| N/A
| Standard-A
| USB 2.0
| {{Unknown}}
| No connection was attempted.
| {{No|No native driver support and ndiswrapper obviously won't work.}}
| There's a previous revision of this dongle which is supposed to have a Ralink chip, but they revised it and put a different chip inside. Reported (by whom?) to work with ndiswrapper and works in Linux.
|-
| Belkin Surf micro
| rtl8192cu
| Standard-A
| USB 2.0
| {{Unknown}}
| USB A
| {{Yes|Yes}}
| {{Yes|Should work out of the box since [[Hotfix 6]] Release Candidate}}
|-
| Cisco/Linksys AE1000 High Performance Wireless-N USB Adapter
| rt3572sta (RT3572USB)
| Standard-A
| USB 2.0
| {{Unknown}}
| USB A (Standard-A port?)
| {{Yes|Works with a modified driver.}}
| (Compiled module for pandora:[http://boards.openpandora.org/index.php?/topic/1992-linksys-ae1000-usb-wifi/ pandora forum]) Download the driver from [http://www.ralinktech.com/support.php?s=2 ralink's driver site], edit ./common/rtusb_dev_id.c, before "#endif // RT2870" add "{USB_DEVICE(0x13B1,0x002F)},", compile.' Reported (by whom?) to work in Linux.
|-
| D-Link WIRELESS G USB ADAPTER DWL-G122 rev.E1 F/W 5.00
| rt2870sta + rt2800usb + rt2800lib
| Standard-A
| USB 2.0
| 450mA
| USB A
| {{No|lsusb shows it, sometimes have to plug and reboot. No modules are loaded.}}
| 07d1:3c0f D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.E) [Ralink RT2870]. Works pretty fine on Linux PC.
|-
| Digitus Wireless 150N USB 2.0 Adapter
| rtl8192cu
| Standard-A
| USB 2.0
| 500mA
| USB A
| {{Yes|Yes}}
| Bundled with a non-WiFi Pandora coming from Craig's shop
|-
| Edimax EW-7811Un
| rtl8192cus
| Standard-A
| USB 2.0
| {{Unknown}}
| USB A
| {{Yes|Yes}}
| {{Yes|Should work out of the box since [[Hotfix 6]] Release Candidate}}
|-
| Netgear WNA1000M
| rtl8192cu
| Standard-A
| USB 2.0
| {{Unknown}}
| USB A
| {{Yes|Yes}}
| {{Yes|Should work out of the box since [[Hotfix 6]] Release Candidate}}
|-
| Thomson WLG-1500A
| ?
| Standard-A
| USB 2.0
| 400mA
| USB A
| {{No|Doesn't work.}}
| 0457:0163 Silicon Integrated Systems Corp. 802.11 Wireless LAN Adapter
|-
| TRENDnet TEW-424UB V2
| ?
| Standard-A
| USB 2.0
| 400mA
| USB A
| {{No|lsusb shows it, but no module is loaded}}
| 0457:0163 Silicon Integrated Systems Corp. 802.11 Wireless LAN Adapter. Same behavior on a PC.
|-
| Alfa Network AWUS036H 1000mw
| RTL8187
| IEEE 802.11b/g
| USB 2.0
| ?
| USB A
| {{Yes|Yes}}
| can be found on ebay; tested with Beta 3
|-
|}

== DVB/TNT/TDT ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Module(s)
! Firmware
! Additional comments
|-
| AVerMedia AVerTV Volar Green HD
| Standard-A
| USB 2.0
| 500mA
| Standard-A port
| Should work
| af9033 tda18218
| dvb-usb-af9035-02.fw
| ID 07ca:a835 AVerMedia Technologies, Inc.
HD/PRO (A835)
|-
| AVerMedia AVerTV Volar Video Capture
| Standard-A
| USB 2.0
| Reported as 0mA. More likely to be 500mA
| Standard-A port
| ?
| ?
| ?
| ID 07ca:4830 AVerMedia Technologies, Inc.
H830
|-
| Hauppauge WinTV aero
| Standard-A
| USB 2.0
| 100mA
| Standard-A port
| {{Yes|Yes}}
| smsmdtv
| sms1xxx-hcw-55xxx-dvbt-02.fw
| ID 2040:b900 Hauppauge
|-
| MSI Digi Vox Min
| Standard-A
| USB 2.0
| ?
| Standard-A port
| {{Yes|Yes}}
| ?
| ?
| Realtek rtl2832u chipset
|-
|}

= Storage =

== External Hard Disk Drives ==
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! style="min-width: 120px" | Works on Pandora
! Additional comments
|-
| Freecom 250GB 2.5" portable
| Not Required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
| Inside it's a Samsung Model HM251JX. {{HideableNotes|So I guess anything based on that will also work OK.}}
|-
| (Intenso)® 2.5" MEMORYSTATION 1TB
| Not Required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
|
|-
| LaCie Rikiki 250GB USB 2.0 2.5" Hard Drive
| Not required
| standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port via powered High Speed Hub
| {{Partial|Not when unpowered, needs testing with a powered hub}}
| Not only does it fail to spin up, but it causes the Pandora's screen to pulsate wildly, much like an old CRT would if you placed a speaker or a magnet near to it. Not tested with a powered hub.
|-
| Seagate Seagate® Expansion™ External Drives
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{No}}
| Tested by [http://www.gp32x.com/board/index.php?/user/14781-hitnrun/ Hitnrun]. "Isn't even detected in lsusb (drive powered by external power source)"
|-
| Verbatim 250GB Model #47580 Hard Drive
| Not required
| Direct
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
| Tested by [http://www.gp32x.com/board/index.php?/topic/54509-dont-use-lacie-25-usb-hard-disk-drives-with-a-pandora/page__view__findpost__p__877512 almatuk]. {{HideableNotes|"Watched videos directly from it at full speed, no need for powered USB hub. Had issues playing roms directly off it however as it was formatted NTFS. I'm sure if I formatted to FAT32 these would disappear."}}
|-
| Western Digital 160GB Elements External USB 2.0 2.5" Hard Drive
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| standard-A port via powered High Speed Hub
| {{Yes}}
|
|-
| Western Digital 250GB Elements Portable USB 2.0 2.5" Hard Drive
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct or standard-A port via High Speed Hub
| {{Yes}}
|
|-
| Western Digital 250GB My Passport Essential USB 2.0 2.5" Hard Drive
| Not required
| {{Unknown|Direct?}}
| USB 2.0
| {{Unknown}}
| {{Unknown|Direct?}}
| {{Partial|Maybe}}
| Tested by TheDarkSpectrum48K. The first time it [http://www.gp32x.com/board/index.php?/topic/54509-dont-use-lacie-25-usb-hard-disk-drives-with-a-pandora/page__view__findpost__p__877386 "works perfectly!"]. The second time [http://www.gp32x.com/board/index.php?/topic/54509-dont-use-lacie-25-usb-hard-disk-drives-with-a-pandora/page__view__findpost__p__882635 it didn't work].
|-
| Western Digital 400GB My Passport Essential USB 2.0 2.5" HDD model WDME4000TE
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
| Tested by [http://www.gp32x.com/board/index.php?/user/14534-peca/ Peca].
|-
| Western Digital 500GB Elements Portable External Hard Drive
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
| Tested by [[User:Esn|Esn]]. {{HideableNotes|The USB cable that came with it was bad, so I used another one.[http://www.gp32x.com/board/index.php?/topic/59494-solved-how-do-i-get-my-wd-500gb-external-hard-drive-to-work-properly/page__view__findpost__p__949863]}}
|-
| Western Digital 500GB My Passport Essential External Hard Drive
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
| Tested by [[User:Esn|Esn]]. Works fine. {{HideableNotes|Came pre-formatted in NTFS, but should work if you downloaded the community codec pack. It said 1TB on the packaging, but there was 465GB free space, so I'm pretty sure it was actually the 500GB one.}}[http://www.gp32x.com/board/index.php?/topic/59494-solved-how-do-i-get-my-wd-500gb-external-hard-drive-to-work-properly/page__view__findpost__p__949645]
|-
| Western Digital 1TB My Passport Essential SE External USB 2.0 2.5" Hard Drive
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct or through powered High Speed Hub
| {{Yes}}
| Tested by [http://http://www.gp32x.com/board/index.php?/user/19191-mycohl/ Mycohl]. {{HideableNotes|Externally powered hub recommended to conserve battery power.}}
|-
| Western Digital Elements 2TB 3.5" Hard Drive Model:WDBAAU0020HBK
| Not Required
| Standard-A
| USB 2.0
| {{Unknown}}
| Direct
| {{Yes}}
| Tested by [http://boards.openpandora.org/index.php?/user/430-kilowatt/ kilowatt].
|}

== DVD/CD Drives ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| Lite-On EZ-DUB DVD/CD Multi-Recorder (Model eZAU120)
| Not required
| Standard-A
| USB 2.0
| Powered by included mains adapter - DC 12V 1.8A
| Standard-A port
| {{No}}
| Works in Linux.
|-
| Memorex 20x Multi Format DVD Recorder External - DVD±RW (±R DL)
| Not required
| Standard-A
| USB 2.0
| Powered by included mains adapter
| Standard-A port
| {{Yes}}
|
|}

= Video display device =

== VGA DVI HDMI adapter ==

No devices have been tested yet

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Output connectors
! Works on Pandora
! Additional comments
|-
|
|
|
|
|
|
|
| No devices have been tested yet
|}

==== External graphics cards ====

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Output connectors
! Works on Pandora
! Additional comments
|-
| Tritton see2 usb 2.0 to SVGA adapter
| sisusb
| USB
| USB 2.0
| {{Unknown|High {{HideableNotes|Reduces Pandora's battery life in half (10h → 4h)}}}}
| VGA (D-SUB)
| {{Partial|Yes, but has performance issues.}}
| Needs to be integrated with preferences. {{HideableNotes|Currently I (who?) must edit xorg.conf and mess with xinerama.}} Good for presentations, dragging a window is bearable, but hi-res video is slow. Works in Linux without any issues.
|}

= Video capture devices =

== Webcams ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| Exoo No Driver/USB 2.0 Webcam (Model No.: M053)
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{No}}
| Bought from [http://www.dealextreme.com/details.dx/sku.14991 DealExtreme]. Works in Linux.
|-
| Logitech Quickcam Communicate Deluxe
| Not required
| Standard-A
| USB 2.0
| {{Unknown}}
| Standard-A port
| {{No}}
| USB ID: 046d:0992, works though [http://linux-uvc.berlios.de/ uvcvideo]. Works in Linux.
|-
| Logitech HD Webcam C270 720p
| Not required
| Standard-A
| USB 2.0
| 500mA
| Standard-A port
| {{Partial|Yes, but audio untested}}
| ID 046d:0825 Logitech, Inc. Audio recognized, but not tested. More info to come. Works in Linux.
|-
| Logitech HD Webcam Pro 9000
| Not required
| Standard-A
| USB 2.0
| 500mA
| Standard-A port
| {{Partial|Yes, but audio untested}}
| ID 046d:0990 Logitech, Inc. Audio recognized, but not tested. Great Picture! Works in Linux.
|}

= Audio devices =

== Microphones/recorders ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| [http://www.bluemic.com/yeti/] Blue Yeti
| not required
| standard-A
| unknown
| unknown
| standard-A port via High Speed USB hub
| {{unknown|Not thoroughly tested.}}
| Very roughly tested 2012-06-13 by [[user:spiralofhope|spiralofhope]] using Mumble. More testing required. {{HideableNotes|The system recognizes the Yeti, and it appears in Mumble's list of available devices, but the audio wizard doesn't show the Yeti as having input. Additional troubleshooting is required, as is checking the manual/company website for missing information.}}
|-
| [http://www.zoom.co.jp/english/products/h2/] Zoom H2 Handy Recorder
| not required
| standard-A
| USB 1.1
| 300mA
| standard-A port via High Speed USB hub
| {{Yes|Yes, needs a USB hub.}}
| Can record into Audacity, but won't be recognized unless connected through USB hub.[http://www.gp32x.com/board/index.php?/topic/59301-audacity-1-3-12/page__view__findpost__p__947602].
|}

== MIDI controllers ==

EvilDragon bundled the usb MIDI class drivers in the default firmware image, therefore ANY class-compliant MIDI device should work with the Pandora, out of the box.[http://www.gp32x.com/board/index.php?/topic/58523-zynaddsubfx/page__view__findpost__p__938432]

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| Akai LKP25
| Not required
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{Yes|Yes [http://www.gp32x.com/board/index.php?/topic/58523-zynaddsubfx/page__view__findpost__p__938432]}}
|
|-
| M-Audio MIDISPORT 2x2 Anniv
| Not required
| {{Unknown}}
| {{Unknown}}
| 400mA
| {{Unknown}}
| {{Unknown}}
| ID 0763:1050 Midiman. High current draw!
|-
|}

== USB audio controllers ==

Aka. "professional soundcard"; see [http://en.wikipedia.org/wiki/Sound_card#Professional_soundcards_.28audio_interfaces.29 definition on Wikipedia].

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| Cakewalk UA-1G
| not required
| Standard-A
| USB 2.0
| 200mA
| Standard-A port
| {{Yes}}
| ID 0582:00e9 Roland Corp. This device may be similar to older Edirol/Roland USB audio devices. Runs and record under Slackware. Jack audio server realtime recording works. Recognized but not tested under official OS. A hub, powered or not, is needed.
|}

= Input devices =

Any HID ([http://en.wikipedia.org/wiki/Human_interface_device Human Interface Device]) compliant keyboard, mouse or game controller should work on the Pandora. Most of those device are low speed or full speed USB device and will need to be connected though either a USB OTG adapter/cable or a USB2 hub in order to work on the Pandora.

== External Game Controllers ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Tested on Pandora
! Additional comments
|-
| 2-TECH SNES-to-USB adapter
| Not required
| Standard-A
| Low speed
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{Yes}}
| USB description is "HuiJia USB GamePad", <tt>lsusb</tt> calls it "0e8f:3013 GreenAsia Inc."
|-
| USB Super RetroPort (SNES-to-USB adapter)
| Not required
| Standard-A
| {{Unknown|Probably USB 1.1}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{No}}
| Bought from [http://www.retrousb.com/product_info.php?cPath=21&products_id=29 RetroZone]. Works in Linux.
|-
| USB RetroPort (NES-to-USB adapter)
| Not required
| Standard-A
| {{Unknown|Probably USB 1.1}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{No}}
| Bought from [http://www.retrousb.com/product_info.php?cPath=21&products_id=28 RetroZone]. Works in Linux.
|-
| Trio Linker Plus II (PlayStation,-GameCube,-and-Dreamcast-to-USB adapter)
| Not required
| Standard-A
| {{Unknown|Probably USB 1.1}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{No}}
| Bought from [http://www.play-asia.com/paOS-13-71-6m-49-en-70-1zfv.html Play-Asia]. Works in Linux.
|-
| NAZAR V47 USB Force Feedback Vibrating Gamepad Controller for PC
| Not required
| Standard-A
| {{Unknown|Probably USB 1.1}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{No}}
| Whether it really contains the claimed force feedback feature is unknown as this feature does not work under Linux - bought from [http://www.dealextreme.com/details.dx/sku.24551 DealExtreme]. Works in Linux.
|-
| 10-Fire-Button Double Vibration Feedback USB PC Arcade Joystick
| Not required
| Standard-A
| {{Unknown|Probably USB 1.1}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{No}}
| Whether it really contains the claimed force feedback feature is unknown as this feature does not work under Linux - bought from [http://www.dealextreme.com/details.dx/sku.27821 DealExtreme]. Works in Linux.
|-
| Official PlayStation 3 controller
| Not required
| Standard-A
| Full speed
| {{Unknown}}
| USB A To Mini B Cable via High Speed Hub
| {{No}}
| This is for USB not bluetooth compatibility. Sixaxis and DualShock not tested. Works in Linux.
|-
| Saitek PLC Cyborg Force Rumble Pad (P2500) - 06a3:ff0c
| {{unknown}}
| Standard-A
| {{unknown}}
| 5V
| Standard-A port via High Speed Hub
| {{Unknown|Not fully tested}}
| Partial test attempted 2012-06-24 by [[user:spiralofhope|spiralofhope]]. lsusb lists it. More testing required. {{HideableNotes|A gamepad testing procedure needs to be defined. See [[Joystick testing]].}}
|-
| Thrustmaster Firestorm Digital 3 Gamepad
| Not required
| Standard-A
| Low speed
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{Yes}}
| ID 07b5:0213 Mega World International, Ltd Thrustmaster Firestorm Digital 3 Gamepad.
|-
| Wired Xbox 360 Controller
| xpad module
| Standard-A
| {{Unknown|Probably USB 1.1}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{No}}
| This also includes gamepads for PC that needs the Windows Xinput driver. Such gamepads include the Logitech Chillstream. Works in Linux.
|-
| WiseGroup.,Ltd SmartJoy Dual PLUS Adapter (dual PSX to USB joypad adapter)
| Not required
| Standard-A
| USB 1
| 100mA
| Standard-A port via USB 1-compatible High Speed Hub
| {{Yes}}
| ID 6677:8802. Works in Linux.
|}

== Touchpads ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Suggested connection to Pandora
! Works on Pandora
! Additional comments
|-
| [http://www.logitech.com/en-us/mice-pointers/mice/devices/8417 Logitech Wireless Touchpad]
| Not required
| Standard-A
| {{Unknown}}
| {{Unknown}}
| Standard-A port via High Speed Hub
| {{Yes}}
| Left and right four-finger swipes aren't mapped to anything by default in XFCE. They can be mapped as keyboard shortcuts.
|}

== Graphics tablets ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Driver
! Connector
! Supported standard
! Current draw
! Works on Pandora
! Additional comments
|-
| Bamboo Multitouch
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{No|No [http://www.gp32x.com/board/index.php?/topic/54728-pandora-owners-tried-tablet/page__view__findpost__p__881806]}}
| It's not known if this works in Linux.
|-
| Genius Tablet
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{Yes|Yes, [http://www.gp32x.com/board/index.php?/topic/54728-pandora-owners-tried-tablet/page__view__findpost__p__883140 via USB hub]}}
| It's not known if this works in Linux.
|-
| Wacom CTH-460
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{Unknown}}
| {{No|No [http://www.gp32x.com/board/index.php?/topic/54728-pandora-owners-tried-tablet/page__view__findpost__p__924422]}}
| Would need a patched driver to work. It's not known if this works in Linux.
|-
| Wacom Volito2 Tablet (Model: CTF-420)
| Not required
| Standard-A
| Low speed
| 40mA [http://www.my-volito.com/volito/specs.asp?lang=en]
| {{No}}
| USB ID: 056a:0062
|}

== Mice ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Connector
! Works on Pandora
! Additional comments
|-
| Apple Mouse (M5769)
| USB
| {{No}}
| Seems to disable USB port, reboot afterwards required
|-
| Apple Mouse with Scroll Ball (A1152)
| USB
| {{Yes|Yes, needs a USB hub.}}
|
|}

= Connectors, adapters, and hubs =

This section is intended as a general guide. Items in this section are standard USB accessories, so drivers are not required. Compatibility with Pandora is assumed. Please note that any external product links are provided for reference only, and are not an endorsement.

== OTG (On The Go) Adapters ==

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Works on Pandora
! Additional comments
|-
| Generic adapter
| {{No}}
| [http://shop.ebay.com/?_from=R40&_trksid=p3907.m38.l1313&_nkw=usb+otg+host+cable&_sacat=See-All-Categories Find on eBay] [http://www.amazon.co.uk/s/ref=nb_ss_ce?url=search-alias%3Delectronics&field-keywords=OTG+Cable+Adapter&x=3&y=23 Find on Amazon] These links are not 100% accurate. Check for `mini-a`, and on eBay, the price is higher by about $8.
|-
|Hama 00074214
| {{Yes}}
|[http://www.hama.de/00074214/hama-mini-usb-adapter-mini-usb-a-plug-usb-a-socket-015-m Manufacturer Page]
|-
| Nokia USB OTG adapter
| {{Yes}}
| [http://www.electronicproductonline.com/catalog/product_info.php?cPath=35_67&products_id=2043 Electronic Product Online]
|}

== Compact USB Hubs ==

Be sure to enable USB-host!

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Device
! Works on Pandora
! Additional comments
|-
| Griffin SmartShare USB [http://www.griffintechnology.com/products/smartshare-usb]
| {{No}}
|
|-
| Belkin F5U415 4 Port USB 2.0 Swivel Hub [http://catalog.belkin.com/IWCatProductPage.process?Product_Id=377085]
| {{No}}
| Comes with an optional power adapter.
|-
| Belkin F5U700 USB 2.0 7-Port Lighted Hub [http://www.belkin.com/uk/support/article/?lid=enu&pid=F5U700ea&aid=10289&scid=947]
| {{Yes}}
| Tested 2012-06-16 by [[user:spiralofhope|spiralofhope]] both with and without its power adapter.
|-
| Belkin F5U701 USB 2.0 7 Port Mobile Hub [http://www.belkin.com/IWCatProductPage.process?Product_Id=369788]
| {{Yes}}
| Tested by pabloh. Comes with an optional power adapter.
|-
| ID 0e8f:0016 GreenAsia Inc.
| {{No}}
| Tested by tsh. Labeled as high speed. Bought from ebay.
|-
| ID 05e3:0608 Targus with Genesys Logic 4 Port USB 2.0 Hub
| {{Yes}}
| Tested by Kazuki. Works.
|-
|Trust 4 port netbook hub ID 05e3:0608
| {{Yes}}
| Tested by tsh. Bought from [http://www.amazon.co.uk/gp/product/B0025X16AS Amazon].
|-
| High Speed 4 Port Mini USB 2.0 Hub for Laptop PC (non powered)
| {{Yes}}
| Octopus-style small cheap unpowered USB hub. Bought from [http://cgi.benl.ebay.be/ws/eBayISAPI.dll?ViewItem&item=270538502843 ebay]
|-
| Keeptech USB 2.0 Hub (7 Ports) with Power Adapter, KT-UH703 [http://www.keeptech.com/books_show.php?id=144]
| {{Yes}}
| Tested by [[User:Esn|Esn]]. Works powered or unpowered.
|-
| Logitech Premium 4-Port USB Hub [http://www.logitech.com/en-in/notebook-products/usb-hubs/devices/3048]
| {{Yes}}
|
|-
| LUPO 7-port USB 2.0 Hub (cheap octopus type which can be powered as there is dc socket)
| {{Partial|Yes. {{HideableNotes|Can use a power supply but wasn't tested with one.}}}}
| Tested by kilowatt. Bought from [http://www.amazon.co.uk/gp/product/B003BVDABG/ref=oss_product from amazon uk]
|-
| LogiLink USB 2.0 Hub 4-Port UA0086 [http://www.logilink.eu/showproduct/UA0086.htm]
| {{Yes}}
| Tested by Jones. Comes with an optional power adapter.
|-
| Rosewill RHB-220 4-port USB 2.0 Hub
| {{Yes}}
| Tested by Tyrant1919. Unpowered. Bought from [http://www.newegg.com/Product/Product.aspx?Item=N82E16817182168 Newegg].
|-
| i-rocks SLEEK HUB USB 2.0 4 Ports Hub [http://www.i-rocks.com/Product_detail.aspx?CLASS_ID=1036&PRODUCT_ID=1080]
| {{Yes}}
| Comes with an ac adapter, but can be used without. USB 1 devices works perfectly.
|}

[[Category:USB]]
[[Category:List]]

Kernel interface

2012-10-03T09:33:08Z

Notaz: /* vertical sync */

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_END (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDONLY);
buffer = mmap(0, 800*480*2, PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Some toolchains don't have FBIO_WAITFORVSYNC defined in <linux/fb.h>, in which case you can define it in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

PND nub modes

2012-09-27T16:30:22Z

Notaz: update

{{IntroNote | This page is a work in progress, the instructions in here may or may not work for you. They were copied from several forum posts (see inline references). For an introduction to PNDs, see [[PND quickstart]]. }}

If you want a different nub behavior for certain PND applications, you can achieve this by using one of the presented methods here.

== Rationale ==

Why would you want to do this? Simple; at least one person has reported that, when playing a natively-ported FPS (like Duke Nukem or Quake, but not GoldenEye) on the Pandora, using the right nub as the mouse has proven to be more comfortable and less awkward. But switching nub modes manually is annoying; so let's have Linux do it for you!

== Presented methods ONLY apply per PND, do not affect general behavior ==

The methods below are crash save, as the nub behavior is changed by the process pnd_run.sh, which runs before AND after a PND is running. Thus even in the event that your PND application crashes, your nub configuration WILL be the same as before you started the PND with the custom nub behavior. (Source: [http://boards.openpandora.org/index.php?/topic/2860-tutorial-how-to-have-your-nubs-change-modes-upon-launching-of-a-pnd/page__view__findpost__p__118299 sebt3 forum post])

== Method: Switch left/right nub unix devices ==

Hint from: [http://boards.openpandora.org/index.php?/topic/2860-tutorial-how-to-have-your-nubs-change-modes-upon-launching-of-a-pnd/page__view__findpost__p__49157 Blue Protoman]

=== Step 1 ===
You must download sebt3's new [[pnd_run.sh]] installer and run it. Get it [http://sebt3.openpandora.org/pnd/pnd_run_installer.pnd here]. 
'''Note: This step is no longer required as of Hotfix 6 Alpha 1.'''

=== Step 2 ===
Open a text editor and copy/paste this:

<source lang="bash">cat /proc/pandora/nub0/mode > /tmp/nub0mode_before
cat /proc/pandora/nub1/mode > /tmp/nub1mode_before

/usr/pandora/scripts/op_nubchange.sh mbuttons mouse</source>

This will back up your current nub modes, then switch them; the left will act as the mouse buttons, the right will act as the mouse. If you'd like, you can substitute "scroll" or "absolute" (joystick) in, depending on how you like your nubs. But you must save this as '''PND_pre_script.sh'''. Save it wherever you'd like, you will be moving it elsewhere later.

Note: op_nubchange.sh script might not available in older firmwares. See [[Kernel_interface#Nubs|Kernel interface]] page for more information.

=== Step 3 ===
Copy/paste this into the editor again. Different file this time.

<source lang="bash">nub0mode=`cat /tmp/nub0mode_before`
nub1mode=`cat /tmp/nub1mode_before`
/usr/pandora/scripts/op_nubchange.sh $nub0mode $nub1mode

rm /tmp/nub0mode_before /tmp/nub1mode_before</source>

This will restore your nub modes to what they were before, and delete the temporary files used to store them. You must save it as '''PND_post_script.sh'''.

=== Step 4 ===
Simply copy these files into the appdata folder of your program of choice! Now you're done. If you want to test it, drag these files into the appdata of a program that runs windowed (like [[Comix|Comix]] or [[Deadbeef|Deadbeef]]), so you can test with the mouse. Simply delete the files if you no longer desire their effects.

== Method: Switch between nub configurator presets ==

Hint from: [http://boards.openpandora.org/index.php?/topic/2860-tutorial-how-to-have-your-nubs-change-modes-upon-launching-of-a-pnd/page__view__findpost__p__118405 Caine]

=== Steps ===
* Start the nub configurator
* Create a profile for the setup you wish your application to use.
* Below, I'll assume a profile is created which is called joysticks which places both nubs in joystick mode.
* Create a file PND_pre_script.sh with this content:
** /usr/pandora/scripts/op_nubmode.py -s temp_profile -p joysticks
** This will store the current configuration in a profile called temp_profile and next will load the joysticks profile.
* Create a file PND_post_script.sh with this content:
** /usr/pandora/scripts/op_nubmode.py -p temp_profile -d temp_profile
** This will load the previously created profile temp_profile and will remove it afterwards.
* Simply copy the files PND_pre_script.sh and PND_post_script.sh into the appdata folder of your program of choice!

=== Advantage ===

Uses the GUI to easily create custom profiles without having to know where values are written to.

=== Disadvantages ===

* It is slower, uses some memory and writes profiles to NAND.
* If you want to avoid NAND-writes per launch and you always revert back to the same profile after launch then you can use static profiles without having to save and remove the current. E.g. something like:
** Before: /usr/pandora/scripts/op_nubmode.py -p joysticks
** After: /usr/pandora/scripts/op_nubmode.py -p Default

[[Category:PND]]
[[Category:Development]]
[[Category:Keyboard]]

PND nub modes

2012-09-27T16:25:57Z

Notaz: /* Step 2 */

{{IntroNote | This page is a work in progress, the instructions in here may or may not work for you. They were copied from several forum posts (see inline references). For an introduction to PNDs, see [[PND quickstart]]. }}

If you want a different nub behavior for certain PND applications, you can achieve this by using one of the presented methods here.

== Rationale ==

Why would you want to do this? Simple; at least one person has reported that, when playing a natively-ported FPS (like Duke Nukem or Quake, but not GoldenEye) on the Pandora, using the right nub as the mouse has proven to be more comfortable and less awkward. But switching nub modes manually is annoying; so let's have Linux do it for you!

== Presented methods ONLY apply per PND, do not affect general behavior ==

The methods below are crash save, as the nub behavior is changed by the process pnd_run.sh, which runs before AND after a PND is running. Thus even in the event that your PND application crashes, your nub configuration WILL be the same as before you started the PND with the custom nub behavior. (Source: [http://boards.openpandora.org/index.php?/topic/2860-tutorial-how-to-have-your-nubs-change-modes-upon-launching-of-a-pnd/page__view__findpost__p__118299 sebt3 forum post])

== Method: Switch left/right nub unix devices ==

Hint from: [http://boards.openpandora.org/index.php?/topic/2860-tutorial-how-to-have-your-nubs-change-modes-upon-launching-of-a-pnd/page__view__findpost__p__49157 Blue Protoman]

=== Step 1 ===
You must download sebt3's new [[pnd_run.sh]] installer and run it. Get it [http://sebt3.openpandora.org/pnd/pnd_run_installer.pnd here]. 
'''Note: This step is no longer required as of Hotfix 6 Alpha 1.'''

=== Step 2 ===
Open a text editor and copy/paste this:

<source lang="bash">cat /proc/pandora/nub0/mode > /tmp/nub0mode_before
cat /proc/pandora/nub1/mode > /tmp/nub1mode_before

/usr/pandora/scripts/op_nubchange.sh mbuttons mouse</source>

This will back up your current nub modes, then switch them; the left will act as the mouse buttons, the right will act as the mouse. If you'd like, you can substitute "scroll" or "absolute" (joystick) in, depending on how you like your nubs. But you must save this as '''PND_pre_script.sh'''. Save it wherever you'd like, you will be moving it elsewhere later.

Note: op_nubchange.sh script might not available in older firmwares. See [[Kernel_interface#Nubs|Kernel interface]] page for more information.

=== Step 3 ===
Copy/paste this into the editor again. Different file this time.

<source lang="bash">cat /tmp/nub0mode_before > /proc/pandora/nub0/mode
cat /tmp/nub1mode_before > /proc/pandora/nub1/mode

rm /tmp/nub0mode_before /tmp/nub1mode_before</source>

This will restore your nub modes to what they were before, and delete the temporary files used to store them. You must save it as '''PND_post_script.sh'''.

=== Step 4 ===
Simply copy these files into the appdata folder of your program of choice! Now you're done. If you want to test it, drag these files into the appdata of a program that runs windowed (like [[Comix|Comix]] or [[Deadbeef|Deadbeef]]), so you can test with the mouse. Simply delete the files if you no longer desire their effects.

== Method: Switch between nub configurator presets ==

Hint from: [http://boards.openpandora.org/index.php?/topic/2860-tutorial-how-to-have-your-nubs-change-modes-upon-launching-of-a-pnd/page__view__findpost__p__118405 Caine]

=== Steps ===
* Start the nub configurator
* Create a profile for the setup you wish your application to use.
* Below, I'll assume a profile is created which is called joysticks which places both nubs in joystick mode.
* Create a file PND_pre_script.sh with this content:
** /usr/pandora/scripts/op_nubmode.py -s temp_profile -p joysticks
** This will store the current configuration in a profile called temp_profile and next will load the joysticks profile.
* Create a file PND_post_script.sh with this content:
** /usr/pandora/scripts/op_nubmode.py -p temp_profile -d temp_profile
** This will load the previously created profile temp_profile and will remove it afterwards.
* Simply copy the files PND_pre_script.sh and PND_post_script.sh into the appdata folder of your program of choice!

=== Advantage ===

Uses the GUI to easily create custom profiles without having to know where values are written to.

=== Disadvantages ===

* It is slower, uses some memory and writes profiles to NAND.
* If you want to avoid NAND-writes per launch and you always revert back to the same profile after launch then you can use static profiles without having to save and remove the current. E.g. something like:
** Before: /usr/pandora/scripts/op_nubmode.py -p joysticks
** After: /usr/pandora/scripts/op_nubmode.py -p Default

[[Category:PND]]
[[Category:Development]]
[[Category:Keyboard]]

Kernel status

2012-08-31T16:20:28Z

Notaz: update out-of-date stuff

= Introduction =
The first [[firmware]] release was based on a heavily patched linux-2.6.27-omap1 kernel. linux-omap used to be OMAP community kernel fork, nowadays its code was either merged to mainline or dropped. Further OMAP development continues on mainline kernels, linux-omap tree is mainly used to queue developed code to mainline.

Current firmware releases are based on 3.x kernel series.

= Status =
Driver support in 3.x series is more or less complete, however not all parts are merged to mainline kernel due to various reasons.

== merged code (already in mainline as of 3.4) ==
* board support (enables UART, I2C, SPI, RTC, MMC{1,2,3}, NAND, OTG, EHCI, gpio-keys, leds-gpio, keypad, touchscreen, regulators)
* sound: [[ALSA]] ASoC machine driver
* [[bq27500]] fuel gauge
* LCD panel driver
* wl1251 [[wifi driver]] glue (portions only in 2.6.37)
* charging (partial only, 2.6.37)
* [[wl1251]] complete powerdown/suspend using runtime_pm (2.6.38).
* backlight driver (3.4)

this doesn't list various bugfix patches to get above working :)

== not merged ==
now in openpandora.org GIT (mainline merge status in brackets)
* nubs (aka vsense, needs rework for mainline)
* keypad fn handling (not allowed in mainline)
* PWM LEDs (needs rework)
* Overclocking support
* some charging bits (too many hacks)
* various random hacks that benefit pandora but may harm other devices, hence mainline incompatible

= openpandora.org git structure =
{{merge|Firmware governance}}
Support for various kernels is available in pandora-XX branches or tags, XX corresponds to last part of kernel version number. 2.6.27 is an exception, it's in pandora-27-omap1 branch.

Branches based on pre-release -rc kernels will be often rebased. This means you can't do 'git pull' on them, use 'git fetch; git reset --hard origin/pandora-XX' instead. '''Warning''': this will destroy all your changes (even if they are commited), backup them first!

See also:
* [[Firmware governance]]

= Configuring newer kernels =
When compiling mainline kernel, use
<source lang="bash">make omap2plus_defconfig</source>
for openpandora.org kernels you can use omap3_pandora_defconfig
<source lang="bash">make omap3_pandora_defconfig</source>
after either of those are run, you can tune the configuration for your needs:
<source lang="bash">make menuconfig</source>
Now you should be able to build a working kernel. More info available at [[Kernel build instructions]].

= Running =
Easiest way is to place your new uImage to root of SD ([[FAT]] or [[ext2]], ext2 may need a bootloader update) along with a file named '[[autoboot.txt]]', which contains u-boot commands such as:
fatload mmc 0 0x80300000 uImage; bootm 0x80300000
Kernel bootargs can be changed by adding 'setenv' line before fatload:
setenv bootargs debug root=...

== serial port ==
In an unlikely event that you can get serial output from EXT port, be aware that serial device has changed several times (due to the driver and port configuration changes in the kernel):
* openpandora.org 2.6.27: ttyS0
* mainline upto 2.6.36: ttyS2
* mainline/openpandora.org 2.6.37 and up: ttyO2
This is relevant for console= bootarg.

= Contributing =
Help is always welcome, usually in form of testing or writing patches. In most cases it's best to file a bug report or feature request in the [http://bugs.openpandora.org bug tracker] so that things don't get lost.

== Submitting patches ==
It's best to send formal GIT-generated patch so that you get proper credit for your work and to make applying the patch easier. You can also add 'Signed-off-by' line ('-s' on 'git commit' will do it for you), which has [http://elinux.org/Developer_Certificate_Of_Origin the same meaning as for mainline Linux].

So basic workflow would be:
<source lang="bash">
<make changes>
git config --global user.name "My Name"
git config --global user.email "myname@domain.com"
git add <changed files>
git commit
git format-patch -o /somewhere/ -1
</source>
Then create a new feature request in bugtracker and attach the generated file(s), or send them to the [[Firmware_governance#Mailing_list|mailing list]], or post them on the forums, whatever is more convenient to you.

[[Category:Official OpenPandora Development]]
[[Category:Kernel]]

Kernel status

2012-08-31T15:15:45Z

Notaz: Submitting patches

= Introduction =
The first [[firmware]] release is based on a heavily patched linux-2.6.27-omap1 kernel. linux-omap used to be OMAP community kernel fork, nowadays its code was either merged to mainline or dropped. Further OMAP development continues on mainline kernels, linux-omap tree is mainly used to queue developed code to mainline. So most of the interesting features that 2.6.27 lack (like sleep modes) are available there, but development effort is needed to port all drivers first.

= Status =
This is mostly about pandora specific support for 2.6.35 or newer. Things that are already in mainline and come "for free" (like SD card support) are not mentioned.

== merged code (already in mainline as of 2.6.36) ==
* board support (enables UART, I2C, SPI, RTC, MMC{1,2,3}, NAND, OTG, EHCI, gpio-keys, leds-gpio, keypad, touchscreen, regulators)
* sound: [[ALSA]] ASoC machine driver
* [[bq27500]] fuel gauge
* LCD panel driver
* wl1251 [[wifi driver]] glue (portions only in 2.6.37)
* charging (partial only, 2.6.37)
* [[wl1251]] complete powerdown/suspend using runtime_pm (2.6.38).

this doesn't list various bugfix patches to get above working :)

== finished code, but not merged==
now in openpandora.org GIT (mainline merge status in brackets)
* nubs (aka vsense, needs rework for mainline)
* backlight driver (needs rework)
* keypad fn handling (not allowed in mainline)
* PWM LEDs (needs rework)

== missing stuff ==
* Charging missing bits.
* Bluetooth. 2.6.27 has rather old Nokia code (not mainlined), Nokia device/maemo kernels need to be checked and later versions integrated from there. There is alternative to this: expose UART port and try to use userspace [[bluez]] drivers, but this could result in less efficient power saving (if any).
* low [[power modes]]. This requires lots of testing, support in drivers and board files.
* DSP mess: [http://elinux.org/BeagleBoard/DSP_Clarification gateway, bridge or link] ?
* more things that I forgot

= openpandora.org git structure =
{{merge|Firmware governance}}
Support for various kernels is available in pandora-XX branches or tags, XX corresponds to last part of kernel version number. 2.6.27 is an exception, it's in pandora-27-omap1 branch.

Branches based on pre-release -rc kernels will be often rebased. This means you can't do 'git pull' on them, use 'git fetch; git reset --hard origin/pandora-XX' instead. '''Warning''': this will destroy all your changes (even if they are commited), backup them first!

See also:
* [[Firmware governance]]

= Configuring newer kernels =
When compiling mainline kernel, use
<source lang="bash">make omap2plus_defconfig</source>
for openpandora.org kernels you can use omap3_pandora_defconfig
<source lang="bash">make omap3_pandora_defconfig</source>
after either of those are run, you can tune the configuration for your needs:
<source lang="bash">make menuconfig</source>
Now you should be able to build a working kernel. More info available at [[Kernel build instructions]].

= Running =
Easiest way is to place your new uImage to root of SD ([[FAT]] or [[ext2]], ext2 may need a bootloader update) along with a file named '[[autoboot.txt]]', which contains u-boot commands such as:
fatload mmc 0 0x80300000 uImage; bootm 0x80300000
Kernel bootargs can be changed by adding 'setenv' line before fatload:
setenv bootargs debug console=ttyO2,115200n8 ...

== serial port ==
In an unlikely event that you can get serial output from EXT port, be aware that serial device has changed several times (due to the driver and port configuration changes in the kernel):
* openpandora.org 2.6.27: ttyS0
* mainline upto 2.6.36: ttyS2
* mainline/openpandora.org 2.6.37 and up: ttyO2
This is relevant for console= bootarg.

= Contributing =
Help is always welcome, usually in form of testing or writing patches. In most cases it's best to file a bug report or feature request in the [http://bugs.openpandora.org bug tracker] so that things don't get lost.

== Submitting patches ==
It's best to send formal GIT-generated patch so that you get proper credit for your work and to make applying the patch easier. You can also add 'Signed-off-by' line ('-s' on 'git commit' will do it for you), which has [http://elinux.org/Developer_Certificate_Of_Origin the same meaning as for mainline Linux].

So basic workflow would be:
<source lang="bash">
<make changes>
git config --global user.name "My Name"
git config --global user.email "myname@domain.com"
git add <changed files>
git commit
git format-patch -o /somewhere/ -1
</source>
Then create a new feature request in bugtracker and attach the generated file(s), or send them to the [[Firmware_governance#Mailing_list|mailing list]], or post them on the forums, whatever is more convenient to you.

[[Category:Official OpenPandora Development]]
[[Category:Kernel]]

Boot setup

2012-08-23T23:52:18Z

Notaz: /* Set up your boot.txt */

==Introduction==

As described in the [[Introduction to firmware]] page, the Pandora is able to boot from an [[SD card]].
This tutorial explains the steps necessary to create an SD card with a copy of the Angstrom operating system which you can boot.
If you do not want to run these steps manually, there also exists a utility (as a standard [[PND]] package) which can guide you through that process: [http://www.pandorabits.org/?page=sd-installer Pandora SD installer]

{{hint
|Note: This tutorial assumes you are using Linux, and gives examples which should run on your Pandora.
}}

==Get a copy of the firmware==

There are methods you can use to get the data off your Pandora's [[NAND]], [http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball this topic] discusses them. It is easier, however, to just extract a tar file.

*Take a look [http://openpandora.org/firmware/ here] (pandora-rootfs.tar.bz2 is what you want) and get the latest version from the official Open Pandora site. Note that this firmware version may be unstable and comes untested!

*Download [http://pandora.digital52.com/downloads/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20100614-omap3-pandora.rootfs.tar.bz2 this old reference image] if you are having trouble with the first link.

*If the two above don't work, you can download an [http://www.codejedi.com/pandora/libpnd/pandora-xfce-image-omap3-pandora-20101705-image-for-checking-fixes.tar.bz2 even older image].

*You can also copy your running firmware on the NAND to the SD partition. This is shown in its own section below.

==Option 1: Use the GUI-driven SD installer tool==

Instead of installing the firmware manually on the SD card (as described further below under "Option 2"), you may use the '''GUI-driven tool sd_installer.pnd by David Boucher''', which automates the entire process.
http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10

You only need the downloaded firmware tarball, the sd_installer.pnd and a suitable SD card.

==Option 2: Manually install the OS on the SD card==

===Partition your SD card===

This is an optional step.

If you want to slice your SD card into several partitions (see [[#Setting_up_mutliple-partition_SD_cards_for_booting|Setting up mutliple-partition SD cards]]), you can use the ''cfdisk'' command-line tool on the Pandora to create a partition table. Note that - as of Zaxxon HF5 - the Pandora firmware doesn't have a command to format FAT partitions, so if you want to use the FAT/ext2/swap - scheme, you'll have to format the first partition on another system later on (under Windows, use the Disk Management tool).

Assuming your card is in the left slot:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

'''WARNING: mmcblk0 will [http://bugs.openpandora.org/index.php?do=details&task_id=237 not necessarily be the left slot]. It's the first card that the system recognizes, which is ''usually'' the left slot (but not if you inserted an SD into the left slot after you had one in the right slot, for example). Please make sure before you do anything dangerous.'''

cfdisk -z starts off with a clean partition table - if you want to see what's set up currently, use ''cfdisk /dev/mmcblk0''.

Use only primary partitions (so you're limited to four slices).

===Format SD card to ext2===

You need to format your SD card to have a single ext2 partition; [[ext3]] also works[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] and is more reliable[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page__view__findpost__p__901072]. You can have a second, swap partition, as well if you like. There are command line tools you can use as well as GUI tools.

====Using the command line====
Take care with using these command line tools, to be certain you are accessing the correct device. They will not ask you and will DESTROY any data on the device. This command will replace an existing partition with an empty EXT2 formatted filesystem (this includes the single FAT partition most SD cards come shipped with). Assuming ''/dev/mmcblk0p1'' for your SD device (left slot, first partition), ''LABELNAME'' for the partition:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
If you run into problems with formatting the SD card, try unmounting it first:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

====Using a GUI tool====
The GUI tools are simple enough that you shouldn't need someone to tell you how to use them. For now this is left as an exercise left for the reader (until someone wants to write up how to do it).

===Copy and boot===

====Copy the files to your SD card====
Navigate (cd) to the directory with the .tar.bz2 file you just downloaded (or made) and do:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

If you're doing this on your Pandora, <SD card> is something like /media/mmcblk0p1 (first SD card slot on Pandora). On Ubuntu it would be something like /media/disk if it has no label. You can also try using GUI tools for this, but I didn't have very good luck with them.

====OR copy your firmware from the NAND to the SD card====

The following will ask for your password. All the operations need root permissions so I thought it would be wasteful to sprinkle sudo to everything.
We will bind mount the root fs to an alternative location ("/mp"), under which other filesystems mounted under root (like the kernel virtual filesystems /proc and /sys, and your SD card.) wont be visible. This allows us to take a live copy of the NAND contents to the SD filesystem.

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

====Set up your boot.txt====

Create a new file called [[boot.txt]] (or autoboot.txt if you want to boot automatically) and copy and paste the text below. Copy that file to the root of the root of the SD card.

{{warning
|If you edit the file on Windows, use an advanced text editor like [http://notepad-plus-plus.org/ Notepad++] and be sure to convert to UNIX format (in NP++: Edit -> EOL Conversion -> UNIX format). If you have DOS linebreaks, ext2load will fail with an error like "file not found" as it appends an hidden character to the uImage file name.
}}

boot.txt (from the [http://openpandora.org/firmware/README.txt official firmware site])
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage-3
bootm 0x80300000
</source>
Note: depending on firmware version kernels might be at several, sometimes multiple locations, so you have to choose one:
* /boot/uImage-3 - the default 3.2 kernel (recommended)
* /lib/boot/uImage - alternative location of 3.2 kernel on certain older firmwares
* /boot/uImage - the old 2.6 kernel

Be aware though that this boot.txt assumes you have formatted your card with ext2 and loads the kernel off the SD card. It is possible to boot the kernel from NAND with following boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
However this is not recommended because kernel modules on SD card will likely be not compatible with kernel on NAND.

Both boot.txt's assume you are booting from the left SD card slot, first partition. You can change "mmcblk0p1" to "mmcblk1p1" if you want to boot from the right slot (but boot.txt must still be on a card on the left slot).
Note: If you chose ext3 instead of ext2, the second line still starts with ext2load. There is no ext3load.

====Setting up mutliple-partition SD cards for booting====

It is possible to have several partitions on the SD card and boot from one of them.
E.g. if you have three partitions on the card like this:
*Partition 1: FAT
*Partition 2: ext2 (where the rootfs should be placed)
*Partition 3: swap

How it's done:

1. Put uBoot's boot control files "boot.txt" and/or "autoboot.txt" into the root of the '''first partition''' of the card (FAT partition in this example)

2. Make "boot.txt" and "autoboot.txt" point U-Boot to the '''partition, which holds the root file system''' of your Linux system. This would be parition 2 in this example (ext2 FS).
This is done '''using the "root" parameter of setenv'''.

3. Make "boot.txt" and "autoboot.txt" point U-Boot to the correct '''location to boot your kernel from'''.
This kernel location can be any FAT or ext2/3/4 partition on the SD card.
The uBoot commands '''"fatload" and "ext2load" with their parameter "mmc x:y"''' are repsonsible for loading the kernel. Choose the command, which addresses the file system the kernel is located on and make sure to correctly adapt the values x and y.

This common example boots the kernel from the FAT partition (then this is a "boot partition"), and uses the ext2 file system as root FS:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
fatload mmc 0:1 0x80300000 uimage
bootm 0x80300000
</source>

If you put the kernel into the root file system's /boot directory, the second line would be different:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p2 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

'''Note: '''

For "root=" kernel argument, slot numbering begins at 0 (0 is left SD slot, 1 is right SD slot) and partition numbering begins at 1!

For "mmc x:y" agrument of the fatload/ext2load commands, x is the card number (0 is left slot, 1 is right slot), y is the partition number, beginning at 1(!).

'''Recommendation:'''

Put the kernel into another partition than the root FS is located.
Reason: In case the root FS partition is flagged "inconsistent" after a system crash or sudden SD card removal, uBoot won't be able to boot from that partition anymore. But the file system cleanup routines can only be run, once the kernel has been booted. Hence it's safer to put the kernel on a different partition.

==Boot the system==

As you power up the Pandora, hold the shoulder button R. A menu should appear, allowing you to boot from the SD card. (this step isn't necessary if you chose to create an autoboot.txt instead of boot.txt). Remember that this will be an un-configured image, taking a little while longer to boot, and giving the first-run dialogue.

==Access the NAND==
Once you're booted into the system from SD, you may want access to the NAND rootfs. The following will let you do that.
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==Other information==
An alternative approach to using an SD card to increase the space accessible to the system is [[Extend_Utils#OS_Extends | OS Extend]]. This allows the root filesystem to exist on more than one physical device.

==References==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x Forum Topic, "Up to date firmware tarball"]
*[http://openpandora.org/firmware/ Official firmware page]
*[http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10 The GUI-driven SD installer by David Boucher]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Overclocking

2012-08-01T11:56:01Z

Notaz: /* CLI Commands */

The Pandora's [[CPU]] can officially run at 600Mhz, but most Pandoras can also run at higher speeds. This can make CPU-intensive programs (such as an N64 emulator) run smoother. If you try a speed that's too high, your Pandora can freeze up. If this occurs, you can force a restart by holding the Pandora button and sliding the power switch to the right. If you still have problems, take out your battery for a minute before turning on your Pandora (this will discharge the backup capacitor that was designed to retain RTC while the battery is being changed [http://www.gp32x.com/board/index.php?/topic/57303-overclocking-broke-my-pandora/page__view__findpost__p__924479])

==How to Overclock==
'''Notes:'''

The [[OMAP]] core will actually adjust its speed to match the load; you are setting the ''upper limit''. On its own, reducing the clock speed has little impact on battery life.

The operating voltage is specified as an 'opp' in the range 1-5, with 3 being the default.

===GUI Tools===
The OS comes with the ability to modify the CPU speed from the GUI. Under "System" in the menu, you should find "CPU-Speed". This gives you a slider to set the desired MHz. Since [[Hot Fix 5]], the maximum and minimum values can be set by using a separate tool (previously, it was limited from 14 to 900MHz).

A second tool was introduced in [[Hot Fix 5]] which allows you to set the maximum OPP level, define the minimum/maximum clock speeds, change the way the "CPU-Speed" script warns you, and define a default clock speed. This can be found under "Settings", then "CPU-Settings".

===CLI Commands===
For anyone who likes using the terminal, here are some examples:

To set OPP5:
<source lang="bash">echo 5 > /proc/pandora/cpu_opp_max</source>

To set your CPU speed: 
see [[Kernel_interface#Overclocking|Overclocking]]

==Voltage Scaling==
{{warning|OverVolting can potentially halve the life of your Pandora}}
OverVolting can be chieved by adjusting the [[Power_modes#Opperating_Point|operating point (OPP)]]

At low frequencies, the [[OMAP]] can still work with a reduced voltage, and that causes it to drain the battery a little slower. Alternatively, you can increase the voltage and maybe get a higher overclock. '''This WILL reduce the lifetime of your Pandora.''' 3 is the default OPP.

If you reduce the CPU speed below specific thresholds, the voltage will automatically adjust downwards. If you set the OPP to 1 whilst still running at the default 500 MHz, your Pandora is very likely to crash. At 4, you may see almost as good an overclock performance as at 5.

==App-specific Speed Control==
It is possible to auto configure specific applications to increase the CPU speed whilst running. Applications can be configured to prompt with a suggested speed, and you are given the option to select a speed, making the choice persistent if desired. This is done by placing a '''cpuspeed file''' in the /pandora/appdata/{pnd_name}/ directory. Delete the file to have the app ask again next time it is run.
Some apps, such as PCSX-rearmed, also allows on-the-go overclocking thanks to the sdk.

==Warranty information==
OPP5 and 1Ghz is the maximum level that is covered by warranty.[http://boards.openpandora.org/index.php?/topic/2993-overclocking-questions/page__st__20__p__71694#entry71694]

[[Category:Tutorials]]
[[Category:Optimization]]

Kernel interface

2012-08-01T11:52:56Z

Notaz: overclocking

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_END (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDONLY);
buffer = mmap(0, 800*480*2, PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Currently FBIO_WAITFORVSYNC is not defined in <linux/fb.h>, although this is in the process of modification. For now, define in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Misc==
===Overclocking===
Can be performed by running a helper script
<source lang="bash">
sudo /usr/pandora/scripts/op_cpuspeed.sh X
</source>
In case you want to do it from another program or non-interactively, you can use system() function (or similar) with:
<source lang="bash">
sudo -n /usr/pandora/scripts/op_cpuspeed.sh -n X
</source>
* Note: you are advised not to change the clock explicitly from a program because optimal clock may differ on different pandora revisions, or somebody might want to run at different clock speed to save battery, CPU life, etc. . Let the user decide about the clock before running the program and set it using the system tools.
* Note: '-n' script argument is not available on pre-SuperZaxxon Final firmwares.

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Kernel interface

2012-07-03T12:11:37Z

Notaz: /* Nubs */

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_END (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* device reenumeration starts and files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

To solve the above problem, the OS provides a helper script that will wait for enumeration to complete:
<source lang="bash">
/usr/pandora/scripts/op_nubchange.sh <left_num_mode> <right_nub_mode>
</source>
op_nubchange.sh is not available on HF6 or earlier firmwares, to support them, something like this could be used:
<source lang="bash">
if [ -e /usr/pandora/scripts/op_nubchange.sh ]; then
/usr/pandora/scripts/op_nubchange.sh absolute absolute
else
echo absolute > /proc/pandora/nub0/mode
echo absolute > /proc/pandora/nub1/mode
fi
</source>

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDONLY);
buffer = mmap(0, 800*480*2, PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Currently FBIO_WAITFORVSYNC is not defined in <linux/fb.h>, although this is in the process of modification. For now, define in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Misc==
Some things can be controlled through files in /proc/pandora/:
* '''/proc/pandora/cpu_mhz_max''' - if [http://www.kernel.org/pub/linux/utils/kernel/cpufreq/cpufreq.html cpufreq] is enabled, sets maximum allowed cpu clock, if not, just sets CPU clock to value supplied (echo 600 > /proc/pandora/cpu_mhz_max). Might also just use cpufreq parameters themselves.
more to come..

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Quickstart

2012-05-05T14:46:53Z

Notaz: dropping hotfix part for now, new units come with SuperZaxxon and installing HF6 there will break the firmware

{{IntroNote | This Wiki is an unofficial community project, and Open Pandora Ltd. is not responsible for its content. Neither is the Wiki an official source of information about your device.}}

==Introduction==
This page provides a very simple walk-through to get you up and running with playing music and installing [[games]]. It will not confuse you by providing choices, or by giving explanations. For that, you might want to go back to the [[Main Page]] of the wiki.

==Power it up==
#You should have a power-supply, and a pandora with the [[battery]] already installed. If the battery is packed in it's shipping case, remove it and follow the printed instructions on correctly inserting it.
#Plug the [[charger]] into the mains, and into the Pandora. You might now need to wait up to 10 minutes. A green light at the right hand side should come on as the Pandora wakes up. Soon after, a red light will appear next to this.
#Whilst waiting to boot, 'write' with the [[stylus]] on some paper. This will polish the tip.

==First Run Wizard==
Some information is needed at this stage in order to set up important stuff. Make sure you keep the charger plugged in.
#After booting, a dialogue will offer to shutdown, or start the configuration. Press 'Start Now' with the [[stylus]]
#The [[first run dialogue]] will appear and ask you to enter some information. Use the pointer and touchscreen or left nub to move the pointer, move the right nub to the left to ''click''
##Name (Conventionally your full name)
##Login (Must not contain spaces)
##Password (and confirmation). Do not forget this!
##Machine Name (Again no spaces. Short is good. How your machine appears on a network.)
##Select if you want to login automatically with no password prompt
##Prefered GUI (Use [[XFCE]] for this tutorial)
##Time Zone (can be changed later)
#Once done, Pandora will reboot. From this point it is safe to unplug from the mains

==Around the XFCE screen==
[[image:Screen_layout.jpg]]

==Connect WiFi==
{{hint
|If your connection is slow, you chould try changing the channel of your WLAN to a higher value. You do this by going to your router's IP and changing the settings of your wireless network.
}}

This step is optional, you can use another PC to download apps to an [[SD card]] or [[USB]] stick.
# Click the menu buttton, click System, click Toggle [[WiFi]]
# The 3rd light on the left is red, and should come ON (WiFi)
# A popup might say networks are available.
# To the left of the battery indicator (a %charge and small run-time) is the network manager icon - A black square.
# Move the mouse with the left nub, and left click by moving the right nub to the left.
# Select your wireless connection. If you have security enabled, you will be prompted for details. You can also right click (nub to the right) to turn networking on and off. WiFi may sometimes be difficult to connect reliably.
# A spinning circle indicates the connection is in progress.
# A beacon icon shows the signal strength when connected
:[[image:Wifi_connected.jpg|Connected via WLAN]]

==Download the codec pack==
This step is necessary because of different licensing laws in different countries. Please understand that you need to take responsibility for any patent restrictions which apply in your country. The codec pack also includes a video player (not fully optimised to used the DSP yet)
Note: You must perform the previous step in order to do this one!
# If not connected to WiFi, do this on another computer
# Click the blue globe icon (3rd from left)
# type open-pandora.org into the address bar, click on Community & Support
# Click on Updates & Firmware
# Click the ''Click here to download Community Codec Pack'' link for the codec pack
# Select ''save as''
# Scroll the left hand list down, select the name of your SD card or mmcblkxxx if your card is not labeled.
# Double click on the pandora folder (right nub up once)
# Double click on the apps folder (right nub up once)
# Click ''save''
# Wait for the download to finish
# Put the [[SD card]] in your pandora if done on a PC
# Press the pandora button in between the [[nubs]] (short press)
# Use the [[D-pad]] to scroll up to ''System'' then right, and down to ''Community Codec pack installer''. Press enter
# Follow the prompts and enter your password when requested

==Play some Music==
Put your music in a folder somewhere on your [[SD card]], then open GNOME [[Mplayer]] and navigate to that folder (read [[Basic Linux Guide]] to learn about the directory structure on the Pandora).

==Download a game==
Well, no instructions for a specific game, but for a simple starting point of legaly redistributable [[games]], [[emulators]] and ROMs, check out the [[PandaPacks]] which you can download, copy to SD card and just run. Or download something you like from the [[games]] list.

==Switch to MiniMenu==

Assuming you are in [[Xfce]] and using [[Hotfix 6]]:
# Open up the Xfce menu (on the bottom-left of your screen)
# Go to ''Switch GUI''
# Highlight [[MiniMenu]] and press ''OK''

==Switch to Xfce==

Assuming you are in [[MiniMenu]]:
# Go to ''System'', then ''Switch GUI''
# Highlight ''XFCE4'' and press ''OK''

==Change the default GUI==

# If in Xfce, open up the menu by pressing the Pandora button
# Go to ''Settings'', then ''Startup''
# Highlight ''Change Default GUI for current user'' and press ''OK''
# Highlight the GUI you want and press ''OK''
The next time you log in, the chosen GUI should load.

==Fix known problems with the default installation==
It is assumed your are using Xfce for these fixes. If you wish to switch back to MiniMenu after making these changes see above.

===Take ownership of your desktop===
Your desktop is owned by root in the default installation. Until this is fixed you won't be able to write to your desktop.

# In Xfce, open up the menu by pressing the Pandora button
# Select ''Terminal'' from the menu.
# Type ''whoami'' and press [ENTER]
# Note your user-name which has just been printed to the terminal
# Type ''sudo chown {your user-name} Desktop''
# Enter your password and press [ENTER] if it is required
# Type ''sudo chgrp {your user-name) Desktop''
# Enter your password and press [ENTER] if it is required

===Fix the installer's time-zone set-up===
There appears to be a problem with Pandora's [[first-run wizard]] that incorrectly sets up your time-zone. This can cause confusing behaviour when you or a program attempts to change the system time. Instructions are taken from this [http://boards.openpandora.org/index.php?/topic/34-anki-friendly-intelligent-flashcards/] board post.

# In Xfce, open up the menu by pressing the Pandora button
# Select ''Terminal'' from the menu.
# Enter the following commands:
# ''cd /usr/share/zoneinfo''
# ''ls''
# Note the continents listed, such as ''America'' and ''Australia''
# Enter the following commands, where ''America'' is your continent:
# ''cd America''
# ''ls''
# Find a listed city in the same timezone as you
# Determine the full path of the file you have chosen. For instance for the Eastern timezone use ''/usr/share/zoneinfo/America/New_York''
# Enter the following commands, replacing ''021915402011'' with the current date in ''MMDDHHMMYYYY'' format, and ''America/New_York'' with your city:
# ''sudo ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime''
# ''export TZ=America/New_York''
# ''echo "export TZ=America/New_York" >>~/.bashrc''
# ''date 021915402011''

==Shutdown==
To really shutdown, the charger must not be plugged in. The Pandora will power up when the charger is plugged in.

From Xfce:
# Press the Pandora button for the menu.
# Select LogOut
# Select Shutdown

From MiniMenu:
# Press the Select button
# Select ''Shutdown Pandora''

If you're unable to shut down for whatever reason, try doing a [[Power_modes#Power_Off|hard shut-down]].

[[Category:Tutorials]]
[[Category:Documentation]]
[[Category:Problems]]

Ångström

2012-05-05T14:26:45Z

Notaz:

The original [[Zaxxon]] firmware has been updated with a number of Hotfixes. Since then, a newer firmware called SuperZaxxon has been released.

'''Warning:''' if you do not have Zaxxon installed (boot screen says SuperZaxxon or something else), do not attempt to install any of these hofixes, doing so will break the system.

=Hotfix 6=
*[http://boards.openpandora.org/index.php?/topic/5652-hotfix-6-final-released/ Information and discussion] (2011-10-10)
*[http://www.openpandora.org/downloads/Zaxxon-HF6.zip Full flash update] (will delete all prior user settings; useful if you've screwed something up and are not sure of how to fix it)

==Bugs and solutions==
In general, the latest information about bugs will be on the official [http://bugs.openpandora.org/ bugtracker]; that is also the best place to go report a bug.

===PNDs won't run===
So you can start Xfce, but you can no longer run any programs or switch to Minimenu since you upgraded to HF6? This can easily be solved without a reflash. To quote [http://boards.openpandora.org/index.php?app=forums&module=forums&section=findpost&pid=98627 valhalla], this problem is because of version 1.0-r58.5 of the pandora-scripts package that includes some files that it should not have included and conflicts with the new version of pandora-libpnd. That version is installed at least in HF5rc2.

#Open a terminal in the location where you put your HF6 update PND. In the default file browser, you can do this by right-clicking in the folder where the PND is, and selecting "open terminal here". For example, if you put it on your desktop (<code>/pandora/desktop</code>), the text in the terminal to the left of your cursor should look something like <code>username-openpandora:/media/pandora/mmcblk0p1/pandora/desktop$</code>
#type in <code>sudo mkdir /mnt/pnd</code> and press "enter". If it asks you for your password, type in what you use to log in to your Pandora, then press "enter".
#type in <code>sudo mount -o loop HF6-Updater.pnd /mnt/pnd</code> and press "enter"
#Now we'll go to the packages directory in the PND and reinstall a couple of packages. Type in <code>cd /mnt/pnd/packages/other/</code> and press "enter"
#Type in <code>sudo opkg install pandora-libpnd_1.0-r56.5_armv7a.ipk</code> and press "enter"
#Type in <code>sudo opkg install pandora-skel_1.0-r9.5_omap3-pandora.ipk</code> and press "enter"
#To unmount the PND, type in <code>sudo umount /mnt/pnd</code> and press "enter". If it says it can't unmount it, just restart your Pandora.
#That's it, your pandora should work again!

==Beta versions==
*[http://boards.openpandora.org/index.php?/topic/5616-hotfix-6-rc-released/ RC] (2011-10-07)
*[http://boards.openpandora.org/index.php?/topic/5320-zaxxon-hotfix-6-beta-1-released/ Beta 1] (2011-09-14)
*[http://boards.openpandora.org/index.php?/topic/4118-hotfix-6-alpha-4-released/ Alpha 4] (2011-06-21)
*[http://boards.openpandora.org/index.php?/topic/4065-hotfix-6-alpha-3-out/ Alpha 3] (2011-06-17)
*[http://boards.openpandora.org/index.php?/topic/4056-hotfix-6-alpha-2-is-out/ Alpha 2] (2011-06-16)
*[http://boards.openpandora.org/index.php?/topic/3955-hotfix-6-alpha-1-released/ Alpha 1] (2011-06-09)

=Hotfix 5=
*Information and discussion: [http://boards.openpandora.org/index.php?/topic/2080-hotfix-5-released/ OP] [http://www.gp32x.com/board/index.php?/topic/58867-hotfix-5-released/ GP32X] (2011-03-04)

==Beta versions==
*RC2: [http://boards.openpandora.org/index.php?/topic/1877-hotfix-5-rc2-last-one-before-going-final/ OP] [http://www.gp32x.com/board/index.php?/topic/58779-hotfix-5-rc2-last-one-before-going-final/ GP32X] (2011-02-22)
*RC1: [http://boards.openpandora.org/index.php?/topic/1572-hotfix-5-rc-1-ready-for-testing/ OP] [http://www.gp32x.com/board/index.php?/topic/58598-hotfix-5-rc-1-ready-for-testing/ GP32X] (2011-02-09)
*[http://boards.openpandora.org/index.php?/topic/1418-beta-test-upcoming-hf5-firmware-image-beta-4/ Beta 4] (2011-02-01)
*[http://boards.openpandora.org/index.php?/topic/1316-beta-test-upcoming-hf5-firmware-image-beta-3/ Beta 3] (2011-01-28)
*[http://boards.openpandora.org/index.php?/topic/1209-beta-test-upcoming-hf5-firmware-image-beta-2/ Beta 2] (2011-01-23)
*[http://boards.openpandora.org/index.php?/topic/1115-beta-test-upcoming-hf5-firmware-image/ Beta 1] (2011-01-17)

=Hotfix 4=
*Information and discussion: [http://boards.openpandora.org/index.php?/topic/90-pandora-hotfix-4-final-released-2010-08-31/ OP] [http://www.gp32x.com/board/index.php?/topic/56385-hotfix-4-final-released/ GP32X] (2010-08-31)

==Beta versions==
*Beta 4: [http://boards.openpandora.org/index.php?/topic/69-hotfix-4-beta-4-released/ OP] [http://www.gp32x.com/board/index.php?/topic/56361-hotfix-4-beta-4-pre-final/ GP32X] (2010-08-29)
*Beta 3: [http://boards.openpandora.org/index.php?/topic/17-hotfix-4-beta-3-released/ OP] [http://www.gp32x.com/board/index.php?/topic/56266-hotfix-4-beta-3-released/ GP32X] (2010-08-27)
*[http://www.gp32x.com/board/index.php?/topic/55965-hotfix-4-beta-2/ Beta 2] (2010-08-15)
*[http://www.gp32x.com/board/index.php?/topic/55788-hotfix-4-very-first-beta/ Beta 1] (2010-08-07)

=Hotfix 3=
*[http://www.gp32x.com/board/index.php?/topic/54933-hotfix-3-released/ Information and discussion] (2010-07-01)

==Beta versions==
*[http://www.gp32x.com/board/index.php?/topic/54852-pandora-hotfix-3-beta-2/ Beta 2] (2010-06-29)
*[http://www.gp32x.com/board/index.php?/topic/54724-pandora-hotfix-3-beta-test/ Beta 1] (2010-06-25)

=Hotfix 2=
*[http://www.gp32x.com/board/index.php?/topic/54171-hotfix-2-for-zaxxon-released/ Information and discussion] (2010-06-08)

==Beta versions==
*[http://www.gp32x.com/board/index.php?/topic/54137-pandora-hotfix-pack-2-for-zaxxon/ Beta 1] (2010-06-08)

=Hotfix 1=
*[http://www.gp32x.com/board/index.php?/topic/53580-hotfix-pack-1-and-community-codec-pack-released/ Information and discussion] (2010-05-24)

=Original firmware=
*You can download the very first release of the Pandora's [[Zaxxon]] firmware from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Software]]

Ångström

2012-05-05T14:21:17Z

Notaz: warn new users about hotfix mess

The original [[Zaxxon]] firmware has been updated with a number of Hotfixes. Since then, a newer firmware called SuperZaxxon has been released.

'''Warning:''' if you have SuperZaxxon installed, to not attempt to install any of these hofixes, doing so will break the system.

=Hotfix 6=
*[http://boards.openpandora.org/index.php?/topic/5652-hotfix-6-final-released/ Information and discussion] (2011-10-10)
*[http://www.openpandora.org/downloads/Zaxxon-HF6.zip Full flash update] (will delete all prior user settings; useful if you've screwed something up and are not sure of how to fix it)

==Bugs and solutions==
In general, the latest information about bugs will be on the official [http://bugs.openpandora.org/ bugtracker]; that is also the best place to go report a bug.

===PNDs won't run===
So you can start Xfce, but you can no longer run any programs or switch to Minimenu since you upgraded to HF6? This can easily be solved without a reflash. To quote [http://boards.openpandora.org/index.php?app=forums&module=forums&section=findpost&pid=98627 valhalla], this problem is because of version 1.0-r58.5 of the pandora-scripts package that includes some files that it should not have included and conflicts with the new version of pandora-libpnd. That version is installed at least in HF5rc2.

#Open a terminal in the location where you put your HF6 update PND. In the default file browser, you can do this by right-clicking in the folder where the PND is, and selecting "open terminal here". For example, if you put it on your desktop (<code>/pandora/desktop</code>), the text in the terminal to the left of your cursor should look something like <code>username-openpandora:/media/pandora/mmcblk0p1/pandora/desktop$</code>
#type in <code>sudo mkdir /mnt/pnd</code> and press "enter". If it asks you for your password, type in what you use to log in to your Pandora, then press "enter".
#type in <code>sudo mount -o loop HF6-Updater.pnd /mnt/pnd</code> and press "enter"
#Now we'll go to the packages directory in the PND and reinstall a couple of packages. Type in <code>cd /mnt/pnd/packages/other/</code> and press "enter"
#Type in <code>sudo opkg install pandora-libpnd_1.0-r56.5_armv7a.ipk</code> and press "enter"
#Type in <code>sudo opkg install pandora-skel_1.0-r9.5_omap3-pandora.ipk</code> and press "enter"
#To unmount the PND, type in <code>sudo umount /mnt/pnd</code> and press "enter". If it says it can't unmount it, just restart your Pandora.
#That's it, your pandora should work again!

==Beta versions==
*[http://boards.openpandora.org/index.php?/topic/5616-hotfix-6-rc-released/ RC] (2011-10-07)
*[http://boards.openpandora.org/index.php?/topic/5320-zaxxon-hotfix-6-beta-1-released/ Beta 1] (2011-09-14)
*[http://boards.openpandora.org/index.php?/topic/4118-hotfix-6-alpha-4-released/ Alpha 4] (2011-06-21)
*[http://boards.openpandora.org/index.php?/topic/4065-hotfix-6-alpha-3-out/ Alpha 3] (2011-06-17)
*[http://boards.openpandora.org/index.php?/topic/4056-hotfix-6-alpha-2-is-out/ Alpha 2] (2011-06-16)
*[http://boards.openpandora.org/index.php?/topic/3955-hotfix-6-alpha-1-released/ Alpha 1] (2011-06-09)

=Hotfix 5=
*Information and discussion: [http://boards.openpandora.org/index.php?/topic/2080-hotfix-5-released/ OP] [http://www.gp32x.com/board/index.php?/topic/58867-hotfix-5-released/ GP32X] (2011-03-04)

==Beta versions==
*RC2: [http://boards.openpandora.org/index.php?/topic/1877-hotfix-5-rc2-last-one-before-going-final/ OP] [http://www.gp32x.com/board/index.php?/topic/58779-hotfix-5-rc2-last-one-before-going-final/ GP32X] (2011-02-22)
*RC1: [http://boards.openpandora.org/index.php?/topic/1572-hotfix-5-rc-1-ready-for-testing/ OP] [http://www.gp32x.com/board/index.php?/topic/58598-hotfix-5-rc-1-ready-for-testing/ GP32X] (2011-02-09)
*[http://boards.openpandora.org/index.php?/topic/1418-beta-test-upcoming-hf5-firmware-image-beta-4/ Beta 4] (2011-02-01)
*[http://boards.openpandora.org/index.php?/topic/1316-beta-test-upcoming-hf5-firmware-image-beta-3/ Beta 3] (2011-01-28)
*[http://boards.openpandora.org/index.php?/topic/1209-beta-test-upcoming-hf5-firmware-image-beta-2/ Beta 2] (2011-01-23)
*[http://boards.openpandora.org/index.php?/topic/1115-beta-test-upcoming-hf5-firmware-image/ Beta 1] (2011-01-17)

=Hotfix 4=
*Information and discussion: [http://boards.openpandora.org/index.php?/topic/90-pandora-hotfix-4-final-released-2010-08-31/ OP] [http://www.gp32x.com/board/index.php?/topic/56385-hotfix-4-final-released/ GP32X] (2010-08-31)

==Beta versions==
*Beta 4: [http://boards.openpandora.org/index.php?/topic/69-hotfix-4-beta-4-released/ OP] [http://www.gp32x.com/board/index.php?/topic/56361-hotfix-4-beta-4-pre-final/ GP32X] (2010-08-29)
*Beta 3: [http://boards.openpandora.org/index.php?/topic/17-hotfix-4-beta-3-released/ OP] [http://www.gp32x.com/board/index.php?/topic/56266-hotfix-4-beta-3-released/ GP32X] (2010-08-27)
*[http://www.gp32x.com/board/index.php?/topic/55965-hotfix-4-beta-2/ Beta 2] (2010-08-15)
*[http://www.gp32x.com/board/index.php?/topic/55788-hotfix-4-very-first-beta/ Beta 1] (2010-08-07)

=Hotfix 3=
*[http://www.gp32x.com/board/index.php?/topic/54933-hotfix-3-released/ Information and discussion] (2010-07-01)

==Beta versions==
*[http://www.gp32x.com/board/index.php?/topic/54852-pandora-hotfix-3-beta-2/ Beta 2] (2010-06-29)
*[http://www.gp32x.com/board/index.php?/topic/54724-pandora-hotfix-3-beta-test/ Beta 1] (2010-06-25)

=Hotfix 2=
*[http://www.gp32x.com/board/index.php?/topic/54171-hotfix-2-for-zaxxon-released/ Information and discussion] (2010-06-08)

==Beta versions==
*[http://www.gp32x.com/board/index.php?/topic/54137-pandora-hotfix-pack-2-for-zaxxon/ Beta 1] (2010-06-08)

=Hotfix 1=
*[http://www.gp32x.com/board/index.php?/topic/53580-hotfix-pack-1-and-community-codec-pack-released/ Information and discussion] (2010-05-24)

=Original firmware=
*You can download the very first release of the Pandora's [[Zaxxon]] firmware from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Software]]

User manual

2012-05-05T14:13:04Z

Notaz: rm dated info

{{IntroNote | This Wiki is an unofficial community project, and Open Pandora Ltd. is not responsible for its content. Neither is the Wiki an official source of information about your device. We can always use more help, look [[Getting_involved#The_Wiki | here]] to find out how you can get involved.}}

{{split section|Page to large, bad for categories, linking topics,....}}

[[Image:PandoraFront.jpg|Right|thumb|360px|The Pandora.]]
So your Pandora just arrived after being in the post for two months. Jolly good! But now that it's actually here, what on earth do you do with it? '''Don't panic!''' Let's take a look at what's included in the box (so you don't miss anything!) and then hop on over to setting it up for that extended Ms. Pacman marathon you've been waiting for!

Also, don't forget to hit up [http://www.gp32x.com/board/index.php?/forum/61-pandora/ GP32X] for questions/info/apps/fun/discussion! Ask on the [http://boards.openpandora.org/ Official Open Pandora forum] if you want a definitive answer.

If you find a problem which is not explained after visiting the forum, be sure to report it in the [http://bugs.openpandora.org/ Bug Tracker]

== Introduction ==

The Pandora is a combination PC and game console. It has gaming controls ([[d-pad]], two analog [[nubs]], ABXY and shoulder buttons) and a 43-button QWERTY [[keyboard]].

It is fast enough run a full desktop, access the internet and play games. However, it is much smaller than a netbook -- it will fit in your pocket! It's a bit bigger than the original Nintendo DS.

== Features ==

; Outside:

* 140 x 83.4 x 27.5mm, 335g (including battery)
* "Clamshell" design
* 43 button QWERTY and numeric [[keypad]]

* Gaming controls:
** Two analog controllers ([[nubs]])
** 8-way D-pad
** A/B/X/Y and [[shoulder buttons]] for gaming.
* 800x480 resolution LTPS [[LCD]] with resistive touch screen, 4.3" widescreen, 16.7 million colors, 300 cd/m2 brightness, 450:1 contrast ratio
* Two [[SDHC card]] slots (up to 64GB of storage currently)
* Headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
* Internal microphone plus ability to connect external microphone through headset
* [[TV output]] (composite and S-Video)
* [[USB]] 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
* [[USB]] 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
* Two externally accessible [[UARTs]] and four [[PWM]] signals (for [[hardware hacking]], robot control, debugging, etc.)

; Inside:

* 4200mAh battery.
** 10+ hours of battery life, depending on usage. For example, turning Wi-Fi or the screen off would give better battery life.
* 600MHz Texas Instruments [[OMAP3530]] processor.
** Can be clocked higher or lower by software designed for the device.
* 256MB DDR-333 [[SDRAM]] (Pre-2012-units), 512MB DDR-333 [[SDRAM]] (units made in Germany, 2012)
* 512MB [[NAND]] FLASH memory
* [[IVA2+]] audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
* [[ARM]]® Cortex™-A8 superscalar microprocessor core
* PowerVR [[SGX530]] 110MHz OpenGL ES 2.0 compliant 3D hardware
* [[Wifi]] 802.11b/g (up to 18dBm output)
* [[Bluetooth]] 2.0 + EDR (3Mbps) (Class 2, + 4dBm)

; More:

* Stereo line level inputs and outputs

* Unbrickable design with integrated [[boot loader]] for safe code experimentation.
* Power and hold [[switch]] useful for "instant on" and key lockout to aid in media player applications on the go.
* Runs on the Linux [[operating system]] (currently 3.2.x and 2.6.x)
* See the [[#Applications | Applications]] section of this manual to see what applications your Pandora will come with.

== Box Contents ==

When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you should find the following items:

* The Pandora console
* [[Stylus]] (located in stylus slot on the side of the Pandora)
* [[Battery]]
* Mains power adapter ([[charger]])
* [[Battery case]]

Available separately:

* [[TV-Out Cable]]
** As of 3rd November 2010 these are not yet included in the box and will ship separately as available.
* [[Carrying Case]]
* Extra Battery

After you take those things out, you may find a sliver of Hope left over. It's best to keep it, as you never know when you could use some Hope.

== Safety Information ==

*Warning: Choking Hazard, do not let children under the age of 3 come close to your Pandora console. The Pandora contains small parts that can be eaten by those children.

*The battery of Pandora must be charged by the charger included with the Pandora (see package contents). [http://www.open-pandora.org/ Open Pandora Ltd.] will not be responsible for damage arising from the use of third party chargers. Please be aware that "cheap" third party chargers often carry fake CE logos. These can damage your Pandora or burst horribly into FLAMES.

*Keep the Pandora in normal temperatures under 140F/60C (Recommended temperatures are in the range between -10C and 40C){{Citation needed}}. The battery is a standard Lithium Polymer battery. Do not keep near fire or water. Do not disassemble, destroy or damage the battery, or it may explode! Do not short circuit external contacts! Dispose of it properly, please.

*Modifications to hardware can damage your Pandora. [http://www.open-pandora.org/ Open Pandora Ltd] cannot be held responsible for any resulting damages that occur from you modifying your Pandora.

*Malicious software can do horrible things to your Pandora. Only download Pandora software from trusted locations such as the [http://repo.openpandora.org/ Repo], the [http://apps.openpandora.org Pandora Apps] website, the [http://dl.openhandhelds.org/cgi-bin/pandora.cgi Pandora File Archive], or the websites of trusted developers.

*The Pandora has a 4.3-inch touch screen. You can touch the screen to trigger an action. That's right, a touch screen - not a stab screen, punch screen, or solid mahogany workbench. Always touch the screen gently – that is more than enough to trigger the action you want.

*The casing of the Pandora has been designed for maximum strength, making it quite hard to break. Please do not consider this a challenge. Do not drop, throw, clamp, launch, tumble dry, or drop anvils on the Pandora. This will void your warranty.

== Warranty Information ==

A one year warranty applies as required by law, and the device will be replaced/repaired if it is faulty. LCDs with numerous/excessive dead pixels will also be replaced.{{Citation needed}}

== First Time Use ==

Now that you've opened the box, let's set this thing up! Place the battery inside the battery compartment on the back of the Pandora, making sure the contacts touch(the little silvery metal bits, it's easy). Snap on the battery cover and you're all set!
If you find this [[linux]] stuff is a bit new and overwhelming, please try the [[Quickstart | quickstart page]] for a simple walk through the first steps (including downloading the codec pack) and please provide feedback on the forums about how it can be improved and still kept simple.

==== Charging ====

Fully charge your Pandora before disconnecting it from the wall [[charger]]. This can improve the lifetime of your battery. To charge the Pandora, insert the power cable end in the Pandora and the other end into your wall socket, then wait about 4 hours to reach 100%.

The [[battery]] comes pre-charged at 40%, and that level might have decreased during shipping. To be on the safe side, we recommend that you charge the Pandora before you use it. Simply plug in your wall charger into an outlet, or optionally use a mini-[[USB]] cable connected to a computer or wall adapter. For extreme silliness, plug your Pandora into an ''already charged Pandora,'' and charge it from that! But not really.

Note that if your battery shipped really discharged, you may have to way a few minutes before the Pandora power on.

To "fast charge" just put the system into "low-power" mode. You cannot charge the system while ''off''. This is currently a feature and may change in future versions of the firmware.

You can find more useful information about charging on the [[power modes]] page.

{{warning
|IF YOU POWERED THE SYSTEM WITHOUT A BATTERY, SHUT IT OFF BEFORE STICKING THE BATTERY BACK IN.
}}

Finally, don't just leave your Pandora plugged in forever. Unplug it once every couple days while using it to allow the battery to discharge from full (to around 90% or less?). If you're not going to use your Pandora for a while, discharge the [[battery]] to around 40%, remove the battery, wrap it in a plastic bag (a Ziplock-type bag?), and stick it in the fridge.

Leaving your Pandora plugged in indefinitely, even while in low-power mode, may damage the battery if you're running a firmware older than Zaxxon Hotfix 6! See the [http://boards.openpandora.org/index.php?/topic/640-warning-dont-leave-your-pandora-plugged-in-for-too-long/|the Open Pandora Boards] for more details.

==== First Boot ====
Once your Pandora is ready, turn it on. After it has booted, a series of settings dialogs will pop up in the shape of a "Boot Wizard" allowing you to alter your Pandora's settings to your liking.

There are a total of 3 parts to the [[First Boot Wizard]] guide:
===== User setup =====
After calibrating your screen, you will have to enter your full name. This is what you will see in any user selection dialogs or when the system needs to address you, so enter whatever you are most comfortable with. Then follows your username. It is recommended to choose an all-lowercase, one-word username here, since you will have to enter this name every time you log in. Once you've entered your username, a password input dialog appears. You will have to enter the password you want to use twice here. If you don't want to have a password for your device, simply leave both fields empty. If, however, you decide to enter a password, something hard to guess and between 8 and 16 characters long is preferred.

===== Network and security settings =====
You will now have to enter a name for your Pandora. This will be the Pandora's host name, so you have two options in this situation:

# If you don't have a domain you want to connect to, simply enter any name here. It should not contain any spaces.
# If you ''do'' have a domain you want to connect to, enter a name in the form of "pandoraname.domainname.tld". Note that you may never have a use for this.

Then, you'll have to choose whether you want to automatically log in on your Pandora when it boots, or if you should be given the opportunity to log in as a different user, or enter your password. It is recommended to disable auto login if you want to protect your user data, but if you're often in a hurry, then you can enable auto login here.

The final thing you will have to choose, is whether you want to use the full desktop [[Xfce]] environment or the gaming-oriented [[MiniMenu]] environment as your default environment in the Pandora. It is also possible to select the environment each time on startup (Switch GUI).
It is recommended to choose "Switch GUI" here. This option can be changed later at any point.

===== Startup / Overclocking / LCD Settings =====
Since firmware release of SuperZaxxon, you can optionally change the startup / overclocking or LCD Settings.
You can skip these settings for now, you can always change these later as well.

==== Calibrating the Analog Nubs [http://pandorawiki.org/Nubs]====

The nubs automatically [[calibrate]] with use, and do so every time the unit is freshly powered up. Calibration information is stored inside the nub RAM, so when you power down (full power off, not just low power mode) the calibration information is lost. Calibrating the nubs is as simple as just using them -- do a few left right up down moves or swoosh around, and the nub will know its boundaries and be good thereafter.

So no special effort is required to calibrate or use the nubs, but the first few motions you use of them may be erratic as they self-calibrate.

==== Calibrating the Touchscreen ====
The [[touchscreen]] in your new Pandora device isn't psychic! You have to tell it what to do, and in order to do that effectively, you need to calibrate it. Simply navigate to settings→screen→calibration wizard{{Verify credibility}} and follow the onscreen instructions. You may have to recalibrate the screen from time to time as well.

==== Mouse (stylus/pointer) settings ====
When done with the calibration and you are back in the Pandora [[Xfce]] desktop environment you might also want to change some other touch screen settings to make navigation with the stylus work according to your preferences. Two recommended settings to experiment with for easier navigation are:

# The double-click Time setting
# The double-click Distance (valid touch-screen double-click area)

In the first setting, i.e. Time, you will be setting the interval between double-clicks where such clicks will be accepted as valid.
Ex. if you set the time to 250ms, the second click (or screen-tap in our case) must occur within 250ms of the first to be valid.

In the second setting, Distance, you will be setting the radius of screen area where the second click (tap) must fall into to be considered as a valid second tap. This means that if, for example, you set the distance to 5, your second tap must fall within a circle radius of 5 pixels from the point where the first tap occurred.

These two settings can be found under: Desktop ---> Xfce menu ---> Settings ---> Desktop ---> Mouse ---> Behaviour tab.

== Basic Use ==
See the [[GUI]] page for more details on the user interfaces which can be used with the Pandora.

===minimenu / mmenu===

[[minimenu]] is designed as a fast and easy to use launcher, without a lot of fancy frills. A grid of icons to launch, and use the d-pad or touchscreen to fire one off. It is fairly configurable and skinnable and is fully featured, and very fast. If you recall the interface on the gp32, gp2x, wiz, and gmenu2x you will be right at home and then some!

=====The main grid=====

The main grid with the default [[skin]] has most of the screen realestate showing a grid of available 'auto discovered' applications, with a detail panel on the right. A list of tabs is across the top of the screen, with some short help message on the bottom.

Pressing Start or B will invoke the [[pnd]]-application. Pressing Select will switch to a basic menu, providing shutdown or some advanced options.

Pressing "Y" (think "Why?") will bring up pnd-application documentation, if that [[pnd]]-file has defined any.

The left and right shoulder triggers will switch categories of applications; by default, minimenu includes an All category and defaults to showing it.

The applications are auto-discovered in the same means as the xfce desktop and pmenu and other pnd-supporting systems, however you may add additional minimenu-specific searchpaths into the configuration should you wish to. It is likely a basic file browser will also be added, letting you launch applications manually placed on your SD cards.

The standard overrides are supported -- [[.ovr]] files for icon title, clockspeed setting and categories, as well as a [[.png]] for icon override.

=====Skinning=====

Skinning guide in gp32x forum: http://www.gp32x.com/board/index.php?/topic/53990-skinning-minimenu/

A mmskin.conf from February 2011: http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob;f=minimenu/skin/default/mmskin.conf;h=695888b3ae310d7ea04b4e682baed0c0c6fc4349;hb=98c1d081629ac9cbb3056b39097a3db968ce4055

===Desktop style environment (Xfce)===

=====On the Desktop=====

The desktop will contain icons for numerous locations (such as each mounted SD card), as well as any auto-discovered pnd-applications located on SD cards or internal [[NAND]].

=====In the menu=====
On the bottom left you have your applications menu, similar to the Windows start menu. Clicking it brings up a list of all installed applications and pnd-applications in the appropriate location on your [[SD cards]].

=====Miscellaneous=====
To the right may be some icons, these serve as shortcuts to commonly used applications. Next to that you have your taskbar which, as you might have guessed, lists all running applications in your current workspace. To the right of the taskbar you have your workspaces, think of these as multiple desktops. By default you have two to switch between. Applications running in one workspace will not be visible in the other, so you can effectively hide your Ms. Pacman game from your boss at work, because there's no way you're not going to go for the gold, even at work! Finally there are a few more icons that deal with TV-Out, network connectivity, etc. and some running applications may place an icon there as well. And to the right of THOSE, you have your time. Because time flies when you're using your Pandora! Badum tsh. And to the right of that, you have a little icon which, when clicked, displays all running applications.

Finally, I'd just like to reiterate this--EVERYTHING is customizable! We'll get to that section later on.

If a window is too tall to fit on the screen you can move it by holding down the left [[shoulder button]] and dragging the window with the [[stylus]].

===Pandora Button===

When in the desktop style environment ([[Xfce]]), the Pandora button will bring up the applications menu, letting you quickly view the available applications. If held, it allows you to [[User_manual#Killing Applications | kill]] an unresponsive application. If that doesn't work, you can do a hard-reset of the Pandora by pressing and holding the Pandora button, then flicking the power switch to the right.

===Power modes===

The [[Power modes]] page provides full details of power modes, charging and battery care and lifetime.

Without switching the device entirely off, it may be placed into low power mode or regular power mode; simply sliding the power switch to the right will toggle modes.

Consider low power mode to be akin to turning off a PDA or cellphone -- the screen is off, the CPU is clocked down and so on, but the device is still silently on, allowing for alarms to go off or it to be turned on again instantly. Regular power mode is for normal usage.

Low power mode is probably going to be used as the normal "off" for most people, with true off (device powered down entirely, unable to respond to alarms or wake up quickly) available to conserve battery power. Turning the Pandora off completely is the best option if you don't plan on using it for few hours or longer.

Closing the lid will turn off the [[display]] but otherwise leave the device operating - handy for audio playing; turning off the display reduces power consumption.

Shutdown will only occur if you are unplugged from the wall. The device can't be charged while off, to "fast charge" just switch to low power mode. See [[Power modes | power modes]] for more info.

The actual behavior of buttons and events can be customized.

=== USB Peripherals ===
You can connect USB2 High Speed peripherals directly, using the large USB connector, or a USB-OTG adaptor lead. Lower-speed USB devices will only work through a hub, the Pandora does not have the support circuitry inside to drive the interface in the correct mode.
See the [[USB_compatibility_list|the USB compatibility list]] for peripherals which have been tested so far.

=== Killing Applications ===
Killing (or forcibly closing) an unresponsive application is as simple as holding down the [[Pandora button]] (just under start and select) for a few seconds. A dialog will appear which lists the open applications and gives you the option to kill them.

=== Forcing a Restart ===
Occasionally something will happen causing your Pandora to become unresponsive (to the point that even killing a program isn't possible). When this happens it is necessary to force your Pandora to restart. The easiest way to do this is by holding the Pandora button and moving the power switch to the right.

== Configuration and Customization ==
This is just an overview of the [[customization]] and configuration you can do. Individual sections may link to their own pages.

=== Setting Up WiFi ===
If [[wifi]] is enabled, and you are in range of an access point, a dialogue should appear offering to connect to it. See the [[Wifi]] page for more detail on using wifi.

=== Setting Up Bluetooth ===
Connecting to [[Bluetooth]] devices is easy using the tool located in the Xfce taskbar.

For help with setting up a [[Bluetooth]] GPS, see [[GPS#Bluetooth_GPS | here]].

=== Adjusting Brightness/Contrast ===
Brightness can be raised by pressing Fn+I and lowered with Fn+U. A tool is included with the Pandora called "LCD-Settings" (under the "Settings" menu) which can be used to adjust the brightness and the gamma.

=== Changing Your Theme ===
Under "Settings" in the menu, you will find "Appearance" which will let you adjust the style, icon set, fonts, and a few other appearance related settings. Also, under "Window Manager" you can adjust the style of each window's title bar.

=== Minimenu Configuration and Tricks ===

[[minimenu]] has a fairly comprehensive configuration file for its minimalistic design; most options may be enabled or disabled or fiddled with, and the skin can reasonably be altered.

The All category can be removed if undesired.

Expert conf hackers can specify what categories they'd like and in what order, and have multiple app categories dumped into one tab, and other tricks.

pnd-application icons may be all loaded during the menu setup, or deferred until later and loaded in the background.

Preview pics may be loaded up front (not advised, as it can be slow), or deferred until later. (When deferred, they may load when you rest the selection, or load in background.)

You may choose to have auto-discovered applications registered into any of their 6 categories (Main, Sub1, Sub2, Alt, AltSub1, AltSub2).

Etc and so on.

Additional keys are supported: Q to quit the menu (not really useful for most people), and Space to invoke the application.

[[Minimenu Configuration Documentation]]

== Applications ==

Many applications will come preinstalled into the internal [[NAND]]; these will be regular Linux applications (not packaged into [[pnd]] files, since they do not need to be redistributed to anyone.)

Additional applications may be found as [[Introduction to PNDs | pnd-files]] (a packaged up single file representing an entire application) or as regular Linux files (an application likely being made up of many files and possibly needing installation.)

==== What Is Included? ====
* [[Ångström]] Linux: Lightweight beautiful Linux-based operating system for the Pandora.
* [[Xfce]]: A full featured window manager for Linux.
* [[Midori]]: A full featured web browser, designed to be lighter and faster than a full desktop style browser.
* Lightweight office utilities including Abiword, Gnumeric, and ClawsMail (warning: do not use ClawsMail, it will fill up your [[NAND]]. Solutions are [http://www.gp32x.com/board/index.php?/topic/56810-html-viewer-for-claws-mail/page__view__findpost__p__919458 being worked on]). '''As of [http://www.gp32x.com/board/index.php?/topic/58867-hotfix-5-released/ Hotfix 5]''', GCalcTool is also included, while Abiword, Gnumeric, Clawsmail and Pidgin have been removed (you can download them from [[software projects|here]] instead).
{{Volume needed}}

==== Where Can I Get More Apps? ====
There are many ways to get more applications onto your Pandora.

*On this wiki, we maintain up-to-date lists of [[games]], [[Emulator list|emulators]], and [[Software projects|other software]], with download links. These lists are more comprehensive than the two official sites below, because not every program is submitted to both of them.

*On [http://repo.openpandora.org repo.openpandora.org] there is a nice [[PND]]-Repository, using [[PNDstore]] you can also automatically update all your [[PND]]s or install new ones directly on the Pandora.

*The easiest way is to browse the [http://apps.open-pandora.org Open App Store], where you can download a selection of free or commercial applications. To download, navigate to an app, pay for it if you must, and hit the 'download' button. Select where you want to save it, and you're done!

*There is the good ol' [http://dl.openhandhelds.org/cgi-bin/pandora.cgi Pandora File Archive].

*To help with the massive range of applications, a member of the community has started to produce [[PandaPacks]] for some pre-packaged games, emulators and distributable ROMs in handy SD card filling torrents.

*The Pandora includes the package manager [[opkg]], which is a fork of [http://en.wikipedia.org/wiki/Ipkg ipkg]. This will install to your Pandoras [[NAND]] by default and can cause severe problems because the version of Angstrom which is used on the Pandora is too old - only use it if you know exactly what you're doing! Type "df -h" in the terminal to see how much space you have left - you shouldn't fill it completely, you might not even be able to login when it is completely full (I'm quite sure you can't, although I might be wrong). You can use the [http://www.pandorabits.org/index.php?page=opkg-installer OPKG Installer] to make things easier.

*You could also download .ipk files directly from the [http://www.angstrom-distribution.org/repo Angstrom ARM Repository], but these are actually the same as if you would install them using [[opkg]] (see above), have the same problems as if using [[opkg]] and the additional annoyance that dependencies aren't resolved automatically. There are different .ipk files for every program, the right ones are the armv7a ones from 2008.

*Also, people may upload their apps to weird crevices in the net, so be on the lookout! (or use a search engine)

{{warning|Your Pandora's internal memory (NAND) will be at close to capacity when you receive it. All new programs '''should be installed to SD card'''. Downloads from the Angstrom Repo, or use of the [[opkg]] package manager, should only be done by advanced users or when instructed by Open Pandora Ltd (for example, firmware updates will probably use a pandora specific repository in the future).''}}

==== Installing a PND file (an application) ====
[[Image:PandoraSD.png|thumb|alt=SD card folder structure|This is what the folder structure on your SD card should look like. The drive letter and card name will vary; they're not important.]]
Installation of a PND file is so easy, you can hardly even call it installing. All you need to do is copy the PND file into the appropriate folder on your SD card. The first thing you'll need to do is set up some folders that the Pandora will recognise. It's recommended that you start with a blank, freshly formatted (or freshly purchased) SD card. For the purposes of this guide we'll refer to your [[SD card]] as <SD> (Windows might call it something like G:\Removable Disk or Linux /media/something). Create a new folder on the SD card called 'pandora':
*<SD>/pandora
Then open the 'pandora' folder, and create four more inside it: apps, appdata (this one isn't really needed, [[PND]]s can save there settings and stuff there, it will automatically be created when a [[PND]] wants to save something), desktop, and menu:
*<SD>/pandora/apps
*<SD>/pandora/appdata/
*<SD>/pandora/desktop/
*<SD>/pandora/menu/
Now you're ready to install a PND file. Just copy and paste (or drag and drop; or save) the file into your folder of choice:
* Putting a PND in the /desktop folder will make it appear on the [[XFCE]] desktop
* Putting a PND in the /menu folder will make it appear in the [[XFCE]] system menu
* Putting a PND in the /apps folder will make it appear in both locations
* If you're using [[Minimenu]] instead of XFCE, it doesn't matter which of these three folders you use. You can also create a <SD>/pandora/mmenu/ folder, and anything saved there will ''only'' show up in Minimenu.
Occasionally you'll come across an application which needs additional data (for example, the data files for Quake, or ROMs for an emulator). These files goes into the appdata folder. A [[PND]] program will automatically create its own subfolder within /appdata the first time it is run; then you can add files to it. More information on this is available on the [[Introduction_to_PNDs#Where_does_my_data_go.3F_How_do_I_make_files_visible_to_the_applications.3F | introduction to PNDs]] page.

== Firmware ==
For more detail about firmware, see the [[Introduction to firmware]] page.

==== Updating The Firmware ====

Updates to the firmware are currently available as full reflash only. Check the OpenPandora official [http://www.openpandora.org/index.php?option=com_content&view=article&id=199&Itemid=40&lang=en support] page for the latest status.

==== Reinstalling the Firmware ====

There are several reasons why you might wish to take this seemingly drastic step. It is possible that the system software gets corrupted somehow (for example, a power failure whilst you are completing the 'first boot' process). Alternatively, you might wish to install a copy of the firmware on an SD card if you are experimenting with different system configurations. Regardless, the Pandora is very robust, it is always possible to download some files to the SD card, and use these to return the internal [[NAND]] to the 'factory' state without too much effort. See the [[Introduction to firmware]] page for information on how to do this.

== Pandora FAQ ==
Silly goose, go to the [[FAQ]] page for more detailed information.

==Futher reading==
* [[Basic Linux Guide]] - For those who don't know very much about Linux and want to learn more.
* [[Minimenu Configuration Documentation]] - If you want to customize or configure Minimenu.
* [[Tutorials]]
* [[Emulator list]] - See what systems you can emulate.
* [[Games]] - Take a look at the games that are available.
* [[Software projects]] - A list of all non-emulator, non-game software for Pandora.

[[Category:Documentation]]

Configuring ext signals

2012-05-05T13:41:15Z

Notaz: /* Disabling attached terminal */

=Pin functions (mux)=
Currently this needs recompiling u-boot, but some easier control is planned.

By default UART2 pins are set up as GPIOs, and UART3 as an UART.

=Power supply=
Currently requires patching bootloaders (xload and u-boot).

This is connected to VAUX3 supply on PMIC, with these programmable voltages (200mA max):
1.5V, 1.8V, 2.5V, 2.8V and 3.0V, with 2.8V as default.

'''warning''': at the time of this writing, both bootloaders (xload and u-boot) set this to 2.8V, so don't rely on this providing other voltages during reboot until you patch both bootloaders.

=GPIOs=
Can be controlled using GPIO sysfs class device, as described in beagleboard tutorials [http://bbfordummies.blogspot.com/2009/07/1.html here].

=UART3=
By default, kernel messages are directed there and a terminal with a shell is attached. The port runs at 115200 8N1 baud rate.
==Disabling kernel messages==
To disable kernel mesages, you need to edit kernel boot arguments. Probably easiest way to do it is to create autoboot.txt and place on root directory of a card in slot1 with this content:
<source lang="bash">
setenv bootargs ubi.mtd=4 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw rootflags=bulk_read
</source>
Alternatives are using u-boot environment (configure through USB or UART3 serial before system boots up) or patching and reflashing u-boot itself.
==Disabling attached terminal==
For this you need to edit /etc/inittab on pandora rootfs and comment out these lines:
<source lang="bash">
#S0:2345:once:/sbin/getty 115200 ttyS0
#O2:2345:once:/sbin/getty 115200 ttyO2
</source>

Jp:Running Linux from an SD card

2012-05-05T13:39:34Z

Notaz: remove ttyS0, breaks new kernel

==はじめに==

[[Jp:Introduction to firmware|ファームウェアの紹介]]ページで説明されているように、Pandoraは[[SD card]] [[Image:Flag_gb.png]] からのシステム起動も可能です。このチュートリアルでは、ブートできるAngstromのオペレーティングシステムのコピーを使用して、SDカードを作成するために必要な手順を説明します。

{{hint
|注記: このチュートリアルでは、Linuxを使用していることを想定し、パンドラ上で実行する必要がある例を示します。
}}

==ファームウェアのコピーを取得する==

[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball このトピック] [[Image:Flag_gb.png]] で説明された、Pandoraの[[Jp:NAND|NAMD]]からデータを取得するために使用できる方法があります。それは、単にtarファイルを抽出するだけで簡単です。

*[http://openpandora.org/firmware/ ここ] (pandora-rootfs.tar.bz2 が何をするのか) [[Image:Flag_gb.png]] を見て下さい、そして公式のOpenPandoraのサイトから最新バージョンを入手して下さい。このファームウェアのバージョンが、不安定でテストされていないかもしれないことに注意してください！

*先のリンクに障害がある場合は、[http://pandora.digital52.com/downloads/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20100614-omap3-pandora.rootfs.tar.bz2 この古いリファレンスのイメージ] [[Image:Flag_gb.png]] をダウンロードして下さい。

*上記の二つが動作しない場合は、[http://www.codejedi.com/pandora/libpnd/pandora-xfce-image-omap3-pandora-20101705-image-for-checking-fixes.tar.bz2 さらに古いイメージ] [[Image:Flag_gb.png]] をダウンロード出来ます。

*また、SDカードのパーティションに、NAND上で動作するファームウェアをコピーすることができます。これは、以下の独自のセクションに示す通りです。

==SDカードのパーティション==

このステップはオプションです。

SDカードをいくつかのパーティションに分割したい場合(見て、[[Jp:Running Linux from an SD card#ブート用マルチパーティションSDカードの作成方法|ブート用マルチパーティションSDカードの作成方法]])は、パーティションテーブルを作成するために、Pandoraの''cfdisk''コマンドラインツールを使用することができます。Pandoraのファームウェア(Zaxxon HF5のような)は、FATパーティションをフォーマットするコマンドを持っていないことに注意してください、FAT/ext2/swapを使用する場合、後で別のシステム(Windows環境下で、ディスク管理ツールを使用)で、最初のパーティションをフォーマットする必要があります。

カードが左側のスロットにある場合:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

cfdisk -z は、クリーンなパーティションテーブルから始めます - 現在設定されているかを確認したい場合は、''cfdisk /dev/mmcblk0''を使用してください。

プライマリパーティションのみを使用してください(よって4分割までに限定です)。

==ext2にSDカードをフォーマット==

あなたは単一のext2パーティションを持つように、SDカードをフォーマットする必要があります; [[ext3]] も同様[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] で、より信頼性が高い[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page__view__findpost__p__901072]です。あなたが好むなら、2番目にswapパーティションを持つことができます。GUIツールと同様に使用できるコマンドラインツールがあります。

===コマンドラインを使用===
正しいデバイスにアクセスしているのを確認してから、これらのコマンドラインツールを使用するように注意してください。あなたに尋ねることはありませんが、デバイス上のデータが破壊されます。このコマンドは、空のext2フォーマットされたファイルシステムを持つ、既存のパーティションに置き換えます(ほとんどのSDカードは、出荷時に単一のFATパーティションで設定されています)。''/dev/mmcblk0p1'' をあなたのSDカード(左のスロットで、firstパーティション)と仮定し、''LABELNAME'' をパーティション名とします:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
もしSDカードをフォーマットして問題が発生した場合、最初にそれをunmountしてみてください:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

===GUIツールを使用===
GUIツールを使用すると、誰かが使用する方法を指示する必要がないほど簡単です。今のところこれは読者のために、宿題として残しておきます（誰かが使用方法を書き込むまで）。

==コピーとブート==

===SDカードにファイルをコピー===
ダウンロードした(もしくは作成した)tar.bz2ファイルを持つディレクトリに移動(cd 実行)して次を実行:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

Pandora上でこれを行う場合、<SD card> は /media/mmcblk0p1 のようになります(Pandoraの第一(左側)SDカードスロットの場合)。ラベルがない場合、Ubuntu上では /media/disk のようになります。また、このためのGUIツールを使用して試すことができますが、私は強運を持っていませんでした。

===もしくはNANDからSDカードにファームウェアをコピー===

以下は、パスワードを聞いてきます。すべてにsudoを使うのは無駄だろうと思ったので、すべての操作はroot権限が必要です。
root下にmountされた他のファイルシステム（カーネルの仮想ファイルシステム /proc および /sys 、そしてSDカードのような）と共に、root fsを別の場所("/mp")にmountします。これにより、SDのファイルシステムにNANDの内容のライブコピーを取ることができます。

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

===boot.txtの設定===
[[boot.txt]](または、自動的にbootしたい場合はautoboot.txt)と呼ばれる新しいファイルを作成し、コピーして以下のテキストを貼り付けます。SDカードのrootのrootにそのファイルをコピーします。

{{warning
|あなたがWindows上でファイルを編集する場合、[http://notepad-plus-plus.org/ Notepad++] [[Image:Flag_gb.png]] のような高度なテキストエディタを使用し、UNIX形式に変換してください(NP++では: Edit -> EOL Conversion -> UNIX format)。DOS形式の改行がある場合は、uImageのファイル名に隠された文字を付加するので、ext2load は "file not found" のようなエラーで失敗するでしょう。
}}

boot.txt ([http://openpandora.org/firmware/README.txt 公式ファームウェアサイトより] [[Image:Flag_gb.png]] )
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage
bootm 0x80300000
</source>

この boot.txt では、カードがext2でフォーマットされ、SDカードからカーネルをロードすると仮定していることも注意してください。ext2フォーマットされたSDカードから起動したくない場合は、
次を使って下さい
boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
この場合、ブートローダーが内部NANDメモリー上のカーネルを探して教えてくれます（テストが行われないことに注意）。

両方の boot.txt は、左側のSDカードスロット、最初のパーティションからブートしていると仮定しています。右のスロットから起動する場合には、"mmcblk0p1" から "mmcblk1p1" に変更しましょう。

===ブート用マルチパーティションSDカードの作成方法===

SDカードは、複数のパーティションを持つことが可能で、それらのいずれかからブート可能です。
例えば、以下のようにカード上に3つのパーティションがある場合:
*パーティション1: FAT
*パーティション2: ext2 (rootfsを配置する場所)
*パーティション3: swap

1番目のパーティションのrootに(auto)boot.txtファイルを置き、U-Bootを2番目のパーティションからシステムをブートする正しい場所へ指示します。
これは、rootfsの場所を示すsetenvの "root" パラメータと、ext2loadの "mmc x:x" パラメータによって指示されます。
上記の例の場合は、以下のようなFATパーティションのrootにある (auto)boot.txt(Windows/ Macのコンピュータを使用して簡単に編集可能)が必要:

<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

注記: スロット番号は0（0は左のSDスロット、1は右のSDスロット）から始まり、パーティション番号は1から始まります!

おそらく同様に、FATパーティションのrootにカーネル (uImage) を置き、上記のようにブートするのに "ext2load" の代わりに "fatload" が使えます（これは、テストされていません！）:

<source lang="bash">
fatload mmc 0:1 0x80300000 uimage
</source>

===システムのBoot===

右肩ボタンを押しながらPandoraの電源を投入すると、SDカードから起動できます。(boot.txtの代わりにautoboot.txtを作成することを選択した場合、この手順は必要ありません) 。この場合未設定の画像になり、起動に少し時間がかかり、そして初回起動のダイアログが表示されることに注意してください。

==NANDへのアクセス==
一度SDからシステムを起動したあと、NANDのrootfsから起動したい場合があります。その時は以下のように行って下さい。
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==他の情報==
システムにアクセス可能な領域を増やすために、SDカードを使用する代わりの方法は、[[Extend_Utils#OS_Extends | OS Extend]] [[Image:Flag_gb.png]] です。これは、rootファイルシステムが複数の物理デバイス上に存在することができます。

==参考==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog] [[Image:Flag_gb.png]]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x フォーラムのトピック "Up to date firmware tarball"] [[Image:Flag_gb.png]]
*[http://openpandora.org/firmware/ 公式サイトのファームウェアのページ] [[Image:Flag_gb.png]]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

Jp:Running Linux from an SD card

2012-05-05T13:38:36Z

Notaz: remove ttyS0, breaks new kernel

==はじめに==

[[Jp:Introduction to firmware|ファームウェアの紹介]]ページで説明されているように、Pandoraは[[SD card]] [[Image:Flag_gb.png]] からのシステム起動も可能です。このチュートリアルでは、ブートできるAngstromのオペレーティングシステムのコピーを使用して、SDカードを作成するために必要な手順を説明します。

{{hint
|注記: このチュートリアルでは、Linuxを使用していることを想定し、パンドラ上で実行する必要がある例を示します。
}}

==ファームウェアのコピーを取得する==

[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball このトピック] [[Image:Flag_gb.png]] で説明された、Pandoraの[[Jp:NAND|NAMD]]からデータを取得するために使用できる方法があります。それは、単にtarファイルを抽出するだけで簡単です。

*[http://openpandora.org/firmware/ ここ] (pandora-rootfs.tar.bz2 が何をするのか) [[Image:Flag_gb.png]] を見て下さい、そして公式のOpenPandoraのサイトから最新バージョンを入手して下さい。このファームウェアのバージョンが、不安定でテストされていないかもしれないことに注意してください！

*先のリンクに障害がある場合は、[http://pandora.digital52.com/downloads/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20100614-omap3-pandora.rootfs.tar.bz2 この古いリファレンスのイメージ] [[Image:Flag_gb.png]] をダウンロードして下さい。

*上記の二つが動作しない場合は、[http://www.codejedi.com/pandora/libpnd/pandora-xfce-image-omap3-pandora-20101705-image-for-checking-fixes.tar.bz2 さらに古いイメージ] [[Image:Flag_gb.png]] をダウンロード出来ます。

*また、SDカードのパーティションに、NAND上で動作するファームウェアをコピーすることができます。これは、以下の独自のセクションに示す通りです。

==SDカードのパーティション==

このステップはオプションです。

SDカードをいくつかのパーティションに分割したい場合(見て、[[Jp:Running Linux from an SD card#ブート用マルチパーティションSDカードの作成方法|ブート用マルチパーティションSDカードの作成方法]])は、パーティションテーブルを作成するために、Pandoraの''cfdisk''コマンドラインツールを使用することができます。Pandoraのファームウェア(Zaxxon HF5のような)は、FATパーティションをフォーマットするコマンドを持っていないことに注意してください、FAT/ext2/swapを使用する場合、後で別のシステム(Windows環境下で、ディスク管理ツールを使用)で、最初のパーティションをフォーマットする必要があります。

カードが左側のスロットにある場合:

<source lang="bash">sudo cfdisk -z /dev/mmcblk0</source>

cfdisk -z は、クリーンなパーティションテーブルから始めます - 現在設定されているかを確認したい場合は、''cfdisk /dev/mmcblk0''を使用してください。

プライマリパーティションのみを使用してください(よって4分割までに限定です)。

==ext2にSDカードをフォーマット==

あなたは単一のext2パーティションを持つように、SDカードをフォーマットする必要があります; [[ext3]] も同様[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/] で、より信頼性が高い[http://www.gp32x.com/board/index.php?/topic/54928-64gb-sdxc-cards/page__view__findpost__p__901072]です。あなたが好むなら、2番目にswapパーティションを持つことができます。GUIツールと同様に使用できるコマンドラインツールがあります。

===コマンドラインを使用===
正しいデバイスにアクセスしているのを確認してから、これらのコマンドラインツールを使用するように注意してください。あなたに尋ねることはありませんが、デバイス上のデータが破壊されます。このコマンドは、空のext2フォーマットされたファイルシステムを持つ、既存のパーティションに置き換えます(ほとんどのSDカードは、出荷時に単一のFATパーティションで設定されています)。''/dev/mmcblk0p1'' をあなたのSDカード(左のスロットで、firstパーティション)と仮定し、''LABELNAME'' をパーティション名とします:
<source lang="bash">
mkfs.ext2 -L LABELNAME /dev/mmcblk0p1
</source>
もしSDカードをフォーマットして問題が発生した場合、最初にそれをunmountしてみてください:
<source lang="bash">
sudo umount /media/[LABELNAME of SD card]
</source>

===GUIツールを使用===
GUIツールを使用すると、誰かが使用する方法を指示する必要がないほど簡単です。今のところこれは読者のために、宿題として残しておきます（誰かが使用方法を書き込むまで）。

==コピーとブート==

===SDカードにファイルをコピー===
ダウンロードした(もしくは作成した)tar.bz2ファイルを持つディレクトリに移動(cd 実行)して次を実行:

<source lang="bash">
sudo tar -xvjf <tarfile>.tar.bz2 -C <SD card>
</source>

Pandora上でこれを行う場合、<SD card> は /media/mmcblk0p1 のようになります(Pandoraの第一(左側)SDカードスロットの場合)。ラベルがない場合、Ubuntu上では /media/disk のようになります。また、このためのGUIツールを使用して試すことができますが、私は強運を持っていませんでした。

===もしくはNANDからSDカードにファームウェアをコピー===

以下は、パスワードを聞いてきます。すべてにsudoを使うのは無駄だろうと思ったので、すべての操作はroot権限が必要です。
root下にmountされた他のファイルシステム（カーネルの仮想ファイルシステム /proc および /sys 、そしてSDカードのような）と共に、root fsを別の場所("/mp")にmountします。これにより、SDのファイルシステムにNANDの内容のライブコピーを取ることができます。

<source lang="bash">
sudo su
mkdir /mp
mount --bind / /mp
cp -va /mp/* /media/<SD card>
umount /mp
rmdir /mp
exit
</source>

===boot.txtの設定===
[[boot.txt]](または、自動的にbootしたい場合はautoboot.txt)と呼ばれる新しいファイルを作成し、コピーして以下のテキストを貼り付けます。SDカードのrootのrootにそのファイルをコピーします。

{{warning
|あなたがWindows上でファイルを編集する場合、[http://notepad-plus-plus.org/ Notepad++] [[Image:Flag_gb.png]] のような高度なテキストエディタを使用し、UNIX形式に変換してください(NP++では: Edit -> EOL Conversion -> UNIX format)。DOS形式の改行がある場合は、uImageのファイル名に隠された文字を付加するので、ext2load は "file not found" のようなエラーで失敗するでしょう。
}}

boot.txt ([http://openpandora.org/firmware/README.txt 公式ファームウェアサイトより] [[Image:Flag_gb.png]] )
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage
bootm 0x80300000
</source>

この boot.txt では、カードがext2でフォーマットされ、SDカードからカーネルをロードすると仮定していることも注意してください。ext2フォーマットされたSDカードから起動したくない場合は、
次を使って下さい
boot.txt
<source lang="bash">
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr} && boot
</source>
この場合、ブートローダーが内部NANDメモリー上のカーネルを探して教えてくれます（テストが行われないことに注意）。

両方の boot.txt は、左側のSDカードスロット、最初のパーティションからブートしていると仮定しています。右のスロットから起動する場合には、"mmcblk0p1" から "mmcblk1p1" に変更しましょう。

===ブート用マルチパーティションSDカードの作成方法===

SDカードは、複数のパーティションを持つことが可能で、それらのいずれかからブート可能です。
例えば、以下のようにカード上に3つのパーティションがある場合:
*パーティション1: FAT
*パーティション2: ext2 (rootfsを配置する場所)
*パーティション3: swap

1番目のパーティションのrootに(auto)boot.txtファイルを置き、U-Bootを2番目のパーティションからシステムをブートする正しい場所へ指示します。
これは、rootfsの場所を示すsetenvの "root" パラメータと、ext2loadの "mmc x:x" パラメータによって指示されます。
上記の例の場合は、以下のようなFATパーティションのrootにある (auto)boot.txt(Windows/ Macのコンピュータを使用して簡単に編集可能)が必要:

<source lang="bash">
setenv bootargs debug root=/dev/mmcblk0p2 rw rootdelay=2 console=ttyS0,115200n8 vram=6272K omapfb.vram=0:3000K
ext2load mmc 0:2 0x80300000 /boot/uImage
bootm 0x80300000
</source>

注記: スロット番号は0（0は左のSDスロット、1は右のSDスロット）から始まり、パーティション番号は1から始まります!

おそらく同様に、FATパーティションのrootにカーネル (uImage) を置き、上記のようにブートするのに "ext2load" の代わりに "fatload" が使えます（これは、テストされていません！）:

<source lang="bash">
fatload mmc 0:1 0x80300000 uimage
</source>

===システムのBoot===

右肩ボタンを押しながらPandoraの電源を投入すると、SDカードから起動できます。(boot.txtの代わりにautoboot.txtを作成することを選択した場合、この手順は必要ありません) 。この場合未設定の画像になり、起動に少し時間がかかり、そして初回起動のダイアログが表示されることに注意してください。

==NANDへのアクセス==
一度SDからシステムを起動したあと、NANDのrootfsから起動したい場合があります。その時は以下のように行って下さい。
<source lang="bash">
sudo mkdir /mnt/nand
sudo ubiattach /dev/ubi_ctrl -m 4
sudo mount -t ubifs ubi0:rootfs /mnt/nand
</source>

==他の情報==
システムにアクセス可能な領域を増やすために、SDカードを使用する代わりの方法は、[[Extend_Utils#OS_Extends | OS Extend]] [[Image:Flag_gb.png]] です。これは、rootファイルシステムが複数の物理デバイス上に存在することができます。

==参考==
*[http://www.rjmitchell.ca/~jeff/blog2009/2010/06/07/pandora-running-firmware-from-sd-card-instead-of-nand-flash/ Skeezix's blog] [[Image:Flag_gb.png]]
*[http://www.gp32x.com/board/index.php?/topic/54290-up-to-date-firmware-tarball GP32x フォーラムのトピック "Up to date firmware tarball"] [[Image:Flag_gb.png]]
*[http://openpandora.org/firmware/ 公式サイトのファームウェアのページ] [[Image:Flag_gb.png]]

[[Category:Tutorials]]
[[Category:Booting]]
[[Category:Storage card]]
[[Category:Operating system]]

GLESGAE

2012-05-05T13:35:31Z

Notaz: remove ttyS0, breaks new kernel

= GLESGAE - GL ES Game Application Engine =

GLESGAE is a vehicle for a series of tutorials on building a game engine for the Pandora console from scratch. 
These will be written when I have time.. the uncreated ones below being an indicator of what's to come. 
Unwritten parts may be split up, moved, or otherwise manipulated before actually going live, so don't take the following as set in stone till the link turns blue!

== Table of Contents ==
Part One - Setup Stuff!
* [http://pandorawiki.org/index.php?title=GLESGAE#GLESGAE_Overview GLESGAE Overview]
* [http://pandorawiki.org/index.php?title=GLESGAE#Engine_Design_Overview Engine Design Overview]
* [http://pandorawiki.org/index.php?title=GLESGAE#Environment_Setup Environment Setup]
* [[GLESGAE:Setting Up A Window and Context]]
* [[GLESGAE:The Event and Input Systems]]
Part Two - Show me Stuff!
* [[GLESGAE:Making a Mesh]]
* [[GLESGAE:Fixed Function Rendering Contexts]]
* [[GLESGAE:Shader Based Contexts]]
* [[GLESGAE:The Transform Stack]]
* [[GLESGAE:Fixed Function Transformations]]
* [[GLESGAE:Shader Based Transformations]]
* [[GLESGAE:Dealing with Textures]]
* [[GLESGAE:Making another Mesh with Vertex Buffers]]
Part Three - Manage my Stuff!
* [[GLESGAE:Managing Resources Overview]]
* [[GLESGAE:The Resource Manager]]
* [[GLESGAE:State Management Overview]]
* [[GLESGAE:Implementing The Game States]]
Part Four - The First Evaluation
* [[GLESGAE:First Evaluation Overview]]
* [[GLESGAE:First Evaluation Graphics]]
* [[GLESGAE:First Evaluation Resources]]
Part Five - Make it do Stuff!
* [[GLESGAE:Logic Processing Overview]]
* [[GLESGAE:Dealing with Entities]]
* [[GLESGAE:Playing with Scripts]]
Part Six - Push Stuff around!
* [[GLESGAE:Physics Processing Overview]]
* [[GLESGAE:Implementing Box2D Physics]]
* [[GLESGAE:Implementing Bullet Physics]]
Part Seven - Make Stuff squeak!
* [[GLESGAE:Sound Processing Overview]]
* [[GLESGAE:Implementing OpenAL]]
Part Eight - The Second Evaluation
* [[GLESGAE:Second Evaluation Overview]]
* [[GLESGAE:Second Evaluation Logic]]
* [[GLESGAE:Second Evaluation Physics]]
* [[GLESGAE:Second Evaluation Sound]]
Part Nine - Poke Stuff from afar!
* [[GLESGAE:Networking Overview]]
* [[GLESGAE:A Basic Networking System]]
Part Ten - Advanced Stuff!
* [[GLESGAE:Library Stubs]]
Part Eleven - Tool Stuff!
* [[GLESGAE:Tools Overview]]
* [[GLESGAE:Mesh Converter]]

= GLESGAE Overview =
To try not spam the wiki to death, I'll include the first two parts here, but subsequent parts will be in their own pages as they're more to deal with actual development problems rather than general overview stuff. 
Where possible, I'll also combine things if they're related to the last part that I did - IE: generating a window, and then adding ES contexts.

Originally, I was going to attempt to take part in the Platformer Homebrew Competition over on the OpenPandora boards. However, with free time being very limited, no engine to speak of, the need to do assets and that it's already been going a month so I'm a bit behind, I've decided to tackle a somewhat different challenge - build and document an engine, originally for Pandora and spawning out elsewhere later.

Yes, another engine.

I've been dragging my old SGZEngine around for quite a while now.. though it's never really got much further than it has, and it's full of weird quirks and bugs that with each project, I spend more time working around than writing actual logic. 
I did start another engine - SGEngine ( dropped the Z ) - however this was highly experimental in fobbing off every subsystem to a dynamically runtime loadable DLL to facilitate mix and matching bits and pieces. Especially useful for testing OpenGL and D3D renderers and a neat hack, but not much use as it was becoming highly complicated to do anything. 
This brings us to GLESGAE. The name being chosen due to me being Scottish, and it being an amusing mnemoic to begin with.

Recently, I've been doing a lot of Android programming. 
This involved writing a custom renderer for GLES1 and then onto GLES2. 
With my previous experience of writing such low level GL code being glBegin(); ... glEnd(); I effectively got thrown in at the deep end and had to fight a bit to stay afloat. However, I pulled through, and while furthering the work engine is always going to be appreciated by them; there's already a defined system of how things work, and I wanted to change a bit too much of that.. so a new personal engine it is; using the new found knowledge I've just gained.

So, with the introduction out of the way, this ( weekly, with any luck ) set of tutorials, guides and random gibberings on building an engine while I continue GLESGAE shall begin.

= Engine Design Overview =

Game Engines are somewhat of a necessary evil these days if you have any inclination of producing more than one game on a system, or one game on many systems.
However, there is also a very real danger of writing a solution for a non-existing problem - an engine without a game.
As such, I will be writing a game alongside this as well, to make sure that the engine does in fact have useful features.

The danger of writing an engine without a game in mind, is that you keep adding bits and pieces and end up not really getting anywhere. Which is exactly what happened with SGEngine. Lots of neat hacks, but it never really got anywhere, and it's a right pig to try and get working for anything serious now.
It was still a useful educational experience, as I learned how to deal with dynamic runtime libraries across Windows and *nix systems, as well as a more saner route for platform independent modules - SGZEngine essentially had a platform folder where all the code went, and interfaces and objects everywhere else. It wasn't particularly clean, even though it sounds like it should've been.

So what is an Engine? 
In the purest sense, it's a collection of generic functions that when wired up can help you create code much quicker. Generally, a Game Engine can pull in other Engines such as Rendering Engines, Audio Engines and Physics Engines - all tailor made for their own specific domains. 
As programmers we do tend to have the habit of being a bit ego-centric with an "I can rewrite the wheel better!" attitude. This can get us in to trouble at times! While I specifically want to deal with GL ES rendering on my own, I'll be pulling in OpenAL for audio and bullet or perhaps box2d for Physics; while trying to leave things open to be able to switch these out for something else at a later date.

This is therefore going to be a set of tutorials on building a Game Engine with a custom Graphics Engine in particular. 
However, a Game Engine isn't just Audio, Graphics and Physics - though these are by far the most interesting parts of a Game Engine.
You'll also generally need a set of utility functions that range from file I/O, input handling, event handling, memory management, resource management, and much more. 
You may also want to abstract logic out to a scripting engine; something I've a lot of experience with and quite fond of, so shall be pulling in Lua as well for this purpose.

While on PC development ( and by extension, Pandora ) you can generally get away with just new/malloc random things at any point and free/delete when necessary all over the place, certain consoles don't particularly like that and you're generally better off managing your own heap and memory pages so you know exactly where your memory is at any time, and can cache things yourself, rather than relying on anything that may or may not do what you expect.

File Management can also catch you unaware on other platforms. Android, for example, has a rather strict permission system whereby you only really have access to your own package, and the contents of the sdcard. Granted, Android 2.3 gives you more control, but if you're writing NDK apps for <2.3 you'll have to jump back and forth between Java and C where file management becomes a whole new game of fun.

And what about input? The Pandora has those nubs! those lovely lovely nubs, dpad, face buttons, shoulder buttons, touchscreen and a full keyboard! You've also got the possibility of godknows what connected via USB - game pads, mice, full-sized keyboards...

I won't even start about threading and the chaos that can bring... then there's networking, which is even worse!

Finally, there's the thought of how you organize data and feed it to your engine. 
These days, most engines follow a very data-driven design - and for good reason! You don't want to have to recompile half your codebase just for changing some NPC text, repositioning a graphic, loading a new model, etc.. GLESGAE is going to be data driven - and that also means tools that will be able to create the data to feed it, in the format that works best for the target platform. 
We shall be building these tools along the way too, and where possible, also having them run on the Pandora itself.

I'll cover more bits as we get to them.. for now, we'll get the Environment Setup.

= Environment Setup =

== I'm Lazy, Give Me A Pre-Configured Thing! ==
Here you go: http://www.stuckiegamez.co.uk/apps/pandora/SimpleDev/zaxxon-premade-dev.tar.bz2 ~250mb

Extract to an ext2/3 formatted SD card, and boot. Simple!

'''NOTE:''''' This is a bit old, now.. and may have somewhat dodgy WiFi, but I'll get round to fixing this soon ( hopefully by 13th May. )'''''

== Tell Me What You Did ==
This weekend is essentially the overview and setup phase, so it's a bit boring I'm afraid. 
To keep everyone on the same page, I'm going to assume you're using Angstrom from an SD card, that you've installed GCC et al on it, and you'll be booting from it for development purposes.

This gives us a few benefits; 
* We are developing on the target hardware and can test things immediately.
* We can keep the NAND in a near enough vanilla state to ensure we don't accidentally pull in and use random libraries that not everyone will have.
* If we do something really bad, we've only messed up an SD card and can just re-extract the tarball and start again, rather than reflash the NAND!

If you've already got an SD card setup with dev tools, then you can leave class early and I'll see you next week. 
Same for if you have a preferred development environment already.. if it works for you, there's no point changing it. 
The rest of you, pay attention!

We'll do everything on the Pandora, to save having to deal with Linux, Windows, Mac, BSD, BeOS, whatever... madness. 
I advise at least grabbing yourself a 2Gig SD card.. go for a bigger card if you like, but 2Gig is probably a good minimum and are reasonably cheap these days. 

Grab your SD card and ensure everything you want from it has been removed - we're about to sacrifice it to the Pandora Dev Gods. 
Stick it in your left slot. 
Open up a terminal. 
You'll need to manually unmount it before going near it with cfdisk to repartition. 
'''''sudo umount /dev/mmcblk0p1''''' -- and possibly p2, p3, p# depending on how many partitions it has. Generally, it'll only have the one. 
'''''sudo cfdisk /dev/mmcblk0''''' -- this'll launch cfdisk on your card.. if you see more than one partition and you've only unmounted one partition, then quit and unmount them!

We want to delete all partitions on this card, so press right and then return to delete the current partition. 
Press up and down to move the selector if need be to remove the rest of them if you've more than one. 
Now we want to create a new partition, so with the Free Space selected, press right to highlight '''[ New ]''' and hit return, select '''[ Primary ]''', and let it use the full card ( just hit return. ) 
Press Left to highlight '''[ Write ]''' and press return. Type "yes" and hit return to confirm the changes, then '''[ Quit ]''' 
You could have added swap if you wanted.. it's up to you really. 

Now we have to format it. 
'''''sudo mkfs.ext2 /dev/mmcblk0p1'''''

Remove the card and reinsert so that the system re-reads the partition table correctly and gives you access to your newly formatted partition.

Now, we download the latest rootfs from OpenPandora.org and extract it to the card. We shall be lazy and stay in the terminal for this so... 
'''''cd /media/mmcblk0p1''''' 
'''''sudo su''''' -- we'll need to be root for this, as we'll have no permission by default to touch this card. 
'''''wget -c http://openpandora.org/firmware/pandora-rootfs.tar.bz2''''' - this grabs us the latest rootfs - though lately, these appear to be very out of sync between Pandora OE and Angstrom OE so be careful! 
'''''tar -xjpf pandora-rootfs.tar.bz2'''' -- you could add v to the arguments if you like.. it'll let you see what it's extracting and is slightly more exciting than just waiting for it to finish! The p is for preserving permissions, x to extract, j for bz2 support and f for file. 
'''''rm pandora-rootfs.tar.bz2'''''

We want the system to autoboot this when the card is inserted, so let's create autoboot.txt 
'''''nano autoboot.txt''''' 
Fill it with the following: 
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0 0x80300000 /boot/uImage-2.6.27.46-omap1
bootm 0x80300000

That's us.. reboot and run through the First Time Configuration stuff, being sure to choose XFCE over MiniMenu, and then feel free to configure the look as you see fit.

Now the fun bit.

'''Warning''' - ''This is potentially dangerous as Angstrom and Pandora libraries may have gone off at tangents at this point... this is why we're doing this on an SD card rather than the NAND so if we stuff it up, we only need to reformat an SD card and not reflash the NAND!''

Make sure your Pandora is connected to the net by whatever means you have. 
Open up a terminal 
'''''sudo opkg update''''' 
'''''sudo opkg install gcc g++ make binutils-dev cpp cpp-symlinks g++-symlinks gcc-symlinks libstdc++-dev libgles-omap3-dev subversion''''' - You could install sdl etc.. too if you want, but that's all we'll be using for now; and you'll be needing subversion later to keep up with the project.

Now the ever popular Hello World. 
'''''mkdir Projects''''' 
'''''cd Projects''''' 
'''''nano main.cpp''''' 
#include <cstdio>

int main(void)
{
printf("Hello World!\n");

return 0;
}

'''''g++ -o main main.cpp''''' 
'''''./main''''' 

''' Interesting Gotcha ''' - '' In the rootfs I downloaded (HF5 RC1), ncurses hadn't been installed... '''sudo opkg install libncurses5''' if you get "cannot open shared object file libncurses.so.5" when invoking nano.''

That's all for this week.. course you could go and install Geany, or whatever code editor you prefer. 
Next time, we shall be opening up a window via badgering X11 directly, and getting a GL ES context up and running.

[[Category:GLESGAE]]
[[Category:Tutorials]]

Debian On SD

2012-05-05T13:32:21Z

Notaz: rm blank line

= Debian On SD =

I'm going to split this into three chunks now... standard Desktop Debian on SD using Squeeze/Lenny/Sid ( choose your poison, though only Squeeze is officially tested to work by myself, ) Emdebian GRIP install, and NAND install.

You can post feedback, bugs, etc.. on the following topics:
GP32X: http://www.gp32x.com/board/index.php?/topic/57097-debian-on-an-sd-card/
OpenPandora Boards: http://boards.openpandora.org/index.php?/topic/1819-debian-on-sd/

I'd prefer the GP32X boards as I'm slightly more active there.

= Little Note to Wiki Editors =
I change this a lot offline and then plaster the changes on during a new release. 
If you're going to go changing this page, please contact me first so I don't accidentally obliterate your changes, or that you do changes to the style I've set out that I don't agree with! 
This may well be against the "wiki spirit" .. but I spend days/weeks typing up these changes and testing them.. so a little consideration please :)

== Desktop Debian ==
This is split into three main sections - Building from Scratch, Maintenance and Upgrades, Common Things To Do.

''' This documents the final 1.0.3 and 1.0.4 "brute force" releases. The 1.1 "debianized" release will take a while and not involve this process at all. '''

* Building From Scratch lets you customise everything from the outset, and lets you create your very own tailor-made distribution, rather than a pre-created one.
It does require a bit of Linux knowledge before diving in.. so if unsure, ask!

* Maintenance and Upgrades covers standard Debian maintenance if you're not usually a Debian user.
It'll also ( in the future ) cover how to upgrade your pre-built distribution with new drivers as the official OS gets updated.

* Common/Fun Things To Do will give you ideas on what to try in your new Debian installation.
Remember, this is a full desktop OS you now have squeezed into your hands, and feel free to share your cool ideas!

If you don't want to build from scratch, you have two choices;
* Grab a Minimal Install and continue from [http://pandorawiki.org/index.php?title=Debian_On_SD#Desktop_Environment Desktop Environment]
* Grab a full build.

The latest minimal is available here: http://www.stuckiegamez.co.uk/apps/pandora/Debian/pandora-squeeze-minimal-1.0.2.tar.bz2 
The latest full builds are:
* LXDE - http://www.stuckiegamez.co.uk/apps/pandora/Debian/pandora-squeeze-1.0.4-grip.tar.bz2
* XFCE - http://www.stuckiegamez.co.uk/apps/pandora/Debian/pandora-squeeze-1.0.5-grip.tar.bz2

Remember to untar with permissions ( include '''p''' in your arguments to tar ) on to your ext2/3 formatted SD card. 
For example: '''''tar -xvjpf pandora-squeeze*.tar.bz2 -C /media/sdcard .'''''

Default User details are: 
username: '''pandora''' 
password: '''debian'''

=== Changelog ===
==== Original Proof of Concept ====
* Released - 19th October 2010
* Based on Sid
* GDM
* GNOME
* Bit slow but workable

==== Release 1.0 ====
* Released - 20th February 2011
* First release
* libts issues
* libpnd issues
* Overly fat with stuff
* Wifi issues for some people

==== Release 1.0.1 ====
* Released - 23rd February 2011
* First documented release
* libts issues persist
* Most libpnd issues fixed
* Slimmed down to ~830mb
* Made Wifi issues worse and accidentally stripped out more than needed

==== Release 1.0.2 ====
* Released - 22nd March 2011
* Replaced libts with evdev... doesn't cause X choking.
* libpnd should behave now, though the pnd services don't seem to get kicked till a terminal is opened, and even then they turn zombie.. eh?
* Added full dev setup.. so it's fat.. it's 1.2gig extracted.
* Replaced GDM with SLIM.

==== Release 1.0.3 ====
* Released - 27th March 2011
* Effectively 1.0.2 with the WiFi and Session Management bug fixed.
* Much slimmer as it's done from scratch again without the dev setup ~805mb rootfs

==== Release 1.0.4 ====
* Released - 4th April 2011
* 1.0.3 with lots of bugs fixed and based on Grip so it's got even more and super tiny in comparision.
* Contains; LXDE, GDM, Gnome MPlayer, IceWeasel ( firefox ) and Synaptic

==== Release 1.0.5 ====
* Released - 9th April 2011
* 1.0.4 with XFCE instead of LXDE and a few bug fixes ( pandora-state's rc scripts being set correctly, and console key map .. see the relevant bits below if you need them, but other than that, it's exactly the same - just with XFCE instead of LXDE )

=== Release 1.1 Proposed ===
* Expected - May 2011 ( maybe )
* libts, amongst other libraries, using OpenPandora patched version.
* Pandora specifics wrapped as Debian archives.
* Pandora specifics repo to deal with updates to drivers from mainline.
* Perhaps an updated kernel using the patches from mainline.

== Building From Scratch ==
This isn't for the feint of heart.. if you don't understand something - stop! Ask or read up on it before continuing. While I haven't mangled my Pandora or PC in any way from doing this, it's still possible to make a mess, so be careful!

This is split into many parts.. it's advised to go through this in order.

* Getting a Minimal Install from Scratch
* Desktop Environment
* Device Drivers and PNDs
* Users, First Boot Scripts and Permissions
* Reboot and Troubleshooting

=== Getting a Minimal Install from Scratch ===

There are two options here:
* Linux PC
* On Pandora

==== Linux PC ====
On a Linux PC, run debootstrap to grab the version you want. We shall be using Squeeze today: 
'''''sudo debootstrap --arch armel --foreign squeeze /tmp/pandora-debian ftp://ftp.uk.debian.org/debian''''' 
Grab a large SD card, and repartition it to have one large ext2/ext3 partition and format as normal. 
Copy all the files from /tmp/pandora-debian over to your new SD card partition. 
Put it in your Pandora. 
'''''sudo chroot /media/mmcblk0p1''''' -- assuming it's in your first slot. 
'''''/debootstrap/deboostrap --second-stage''''' 
... this takes a while...

==== Pandora ====
Alternatively, you can run cdebootstrap on the Pandora itself, or debootstrap from within Debian... this bypasses the need of doing the second-stage madness. 
Grab it from here: http://packages.debian.org/sid/cdebootstrap-static and select the armel package. 
Download it to /tmp preferably, but your home folder will do, or anywhere you like. For now, I shall assume you downloaded it to /tmp 
'''''cd /tmp''''' -- Again, if you downloaded elsewhere, change to that directory instead. 
'''''ar xv cdebootstrap*.deb''''' -- We're using the archive tool to extract with verbosity our cdebootstrap package. 
'''''sudo tar -zxvf data.tar.gz -C /''''' -- Now we're using tar to extract, with gzip support, again with verbosity, the file data.tar.gz, changing the Current directory to / so that it extracts systemwide on our NAND. We're running this command sudo so we have write permissions. 
Now we just run cdebootstrap-static with a few parameters, and wait. 
'''''cdebootstrap-static --allow-unauthenticated -f minimal squeeze /media/mmcblk1p1''''' -- What we're doing here, is we're allowing "unauthenticated" packages to be installed. As we don't, or probably don't, have the gnupg keychain stuff configured, all packaged will be "unauthenticated" regardless of whether they are or not. We're telling it we also want a minimal install of the squeeze release, and to install to where we have the mount point of Partition 1 of the SD card in Slot 1 - which you should have already partitioned and formatted as ext2! 
This takes a while... perhaps longer than doing the first stage on the PC and second-stage on Pandora.

=== Setting up Apt ===
I've forgotten about this, as mostly it'll be set to the default Debian repository, but should you want to change it: 
'''''sudo nano /etc/apt/sources.list'''''

UK people can set this to ''deb ftp://ftp.uk.debian.org/debian main non-free contrib'' to get pretty much everything, or can pick whichever local Debian repository they like - but be warned that not all of them have an armel repo! 
By default, debootstrap will likely only get main.. adding the non-free and contrib branches are optional, but bring in more stuff.

=== Desktop Environment ===
Now you have Debian, the world is yours for the taking!
Or something like that...

Debian comes with a wide variety of desktop environments and window managers; from XFCE as you use on Angstrom by default, to KDE, GNOME, LXDE, Fluxbox, Enlightenment, etc.. 
Now's the time to choose one of them to install.. be aware that the bigger they are, the longer they'll take to install and the more resources they will eat up while in use.. as a rough guide from heavy to light: 
* KDE
* GNOME
* Enlightenment ( Squeeze has e16 .. and is faster than I expected )
* XFCE
* LXDE
* Fluxbox

Having recently tested KDE myself, it doesn't quite seem to work properly, so I'd avoid that for the moment... especially as it takes about ten hours to install!

We shall install LXDE as it's a bit more light weight than XFCE and still provides a reasonable mainstream environment. While I do prefer Fluxbox overall, it's a bit of a paradigm shift to use from your standard desktop machine.

If you haven't already, chroot into your environment.
You should already be root, so we'll get on with the installing.

'''''apt-get install lxde'''''

This may well take an age, so go do something else in the meantime. 
You may also want a login manager.. your choices are amongst XDM, GDM, KDM and SLIM to name a few. KDM is perhaps a bit heavy, whereas GDM works fairly well even though it's rather heavy too. SLIM is what you use on Pandora anyway, and XDM is rather basic but usable all the same. GDM is automatically pulled in via LXDE anyway, so we may as well just use that for now.

Additional: 
Installing LXDE via the above command pulls in GDM by default.. if you use ''lxde-core'' instead, it removes a lot of the stuff that pulls in random things, and if you additionally use '''''aptitude install --without-recommends lxde-core''''' it should strip out even more. You will need to manually install ''less'', ''zenity'', and ''xterm'' for example. Zenity is especially needed for all the Pandora config scripts.

1.0.3 has slimmed stuff down again. 
Once in the chroot jail, I've performed the following: '''''aptitude install --without-recommends lxde-core slim lxterminal zenity less xserver-xorg-video-omap3 network-manager-gnome synaptic xfce4-power-manager apmd libnotify-bin gedit epiphany-browser eject gksu gnome-bluetooth python-dbus ca-certificates xinput busybox''''' which will effectively pull in all the Debian specifics we'll be needing, gutting out a rather large amount of cruft.

Once it's done, we'll start tackling the Drivers.

=== Device Drivers and PNDs ===
We shall tackle these one at a time, as there's quite a few of them.

* X Display Driver
* SGX Drivers
* Keymap
* Nubs
* Touchscreen
* Wifi
* Bluetooth
* Kernel and Misc Bits and Pieces
* PNDs

==== X Display Driver ====
Debian has a NEON-optimised omapfb driver. We shall use this, and pinch some configuration gubbins from Angstrom.

'''''apt-get install xserver-xorg-video-omap3'''''

We now need to create an xorg.conf .. though it'll be rather minimal as we only really want to overload what graphics device setup it has, so: 
'''''nano /etc/X11/xorg.conf''''' 
Section "Module"
Load "extmod"
Load "dbe"
Disable "glx"
Disable "dri"
Load "dri2"
EndSection

Section "ServerLayout"
Identifier "DefaultLayout"
Screen "Screen0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "OMAPFB"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "800x480"
EndSubSection
EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Device"
Identifier "OMAPFB"
Driver "omapfb"
Option "fb" "/dev/fb0"
EndSection

Most of this is pinched from the Angstrom xorg.conf minus the fb Option at the bottom, as our framebuffer has a different device node.

That should be all you need for basic X though.

==== SGX Drivers ====
Most of this has been pinched from http://elinux.org/BeagleBoardDebian#SGX_Video_Acceleration - why rewrite the wheel? 
This mostly works apart from a few caveats, so I shall repeat it here for future reference and to keep all information in one place, and I've uploaded the resulting tarballs for convenience.

You can either follow the above guide - substituting the BeagleBoard for the Pandora, or use the following preconfigured packages. 
'''''cd /tmp''''' 
'''''wget -c http://www.stuckiegamez.co.uk/apps/pandora/Debian/GFX_4_00_00_01_libs.tar.gz''''' ~20MB Libraries themselves 
'''''wget -c http://www.stuckiegamez.co.uk/apps/pandora/Debian/GFX_Linux_SDK.tar.gz''''' ~220MB Demos and SDK gubbins 

Technically, you don't really need that fat 220MB GFX_Linux_SDK tarball unless you really want it, or want to test the libraries are in place. 
I'll cover installing both anyway...

===== Libraries =====
'''''tar -zxvf GFX_4_00_00_01_libs.tar.gz''''' 
'''''chmod +x ./install-SGX.sh''''' 
'''''./install-SGX.sh''''' 
'''''rm /devmem2_0.0-0ubuntu1_armel.deb''''' - this is particularly useless to us... and why it dumps it at root, I don't know! 

That package contains ES2, ES3 and ES5 libraries.. we're only really interested in ES2 ( haven't tried if ES3 or ES5 would even work! ) so: 
'''''cd /usr/lib''''' 
'''''ln -s ES2.0/* .''''' 

Not hugely clean, but it works. For the brave, you could try ES3 or ES5 but.. you're on your own!

===== Demos/SDK =====
'''''cd /tmp''''' 
'''''tar -zxvf OGLES.tar.gz''''' 
'''''tar -zxvf OGLES2.tar.gz''''' 

You can't run anything yet ( well, you might since you've chrooted in via Angstrom ) so we'll leave them in /tmp for the moment - or move them elsewhere - such as /opt if you're worried about Debian wiping out /tmp on boot.

==== Keymap ====
The keymap is actually stupidly easy, and I've missed how easy it is for quite a while now! 
We shall steal them from Angstrom.. so open up another Terminal. 
As of now, I shall prefix Angstrom commands with ''Angstrom'' and Debian commands with ''Debian'' so you know which Terminal to type them in.

''Angstrom'' '''''sudo cp /etc/keymap-extension-2.6.map /media/mmcblk0p1/etc''''' - this does assume you've got your SD card mounted in slot one, and with one ext2 partition.. adjust as necessary. 
''Angstrom'' '''''sudo cp /etc/skel/.pndXmodmap /media/mmcblk0p1/etc/skel''''' - as above. 

After some fiddling, if you stick the following into ''.xsession'' it'll actually get called...
whoami > /tmp/currentuser
killall -1 pndnotifyd &
exec startlxde

Of course, this is a bit hacky and hard-coded in that if you've chosen something other than lxde, you'll probably want to change that startlxde to something else!

1.0.2 does something really hacky and actually starts pndnotifyd and pndevmapperd as daemons directly. 
It also starts up the xfce4-power-manager for a battery meter.

1.0.3 does something else again.. it does not have the '''killall -1 pndnotifyd &''' line, instead it has the following:
sudo /etc/init.d/pndnotifyd-init restart
sudo /etc/init.d/pndevmapperd-init restart
And has edited /etc/sudoers.d/99_libpnd to add access to those two lines without being prompted for a password.

1.0.4 is again different, and doesn't HUP pndnotifyd at all as it seemed to work without much issue just by starting the service differently, also, due to use of GDM, we do the xmodmap at GDM's startup instead in the following manner: 
'''''sudo nano /etc/gdm/Init/\:0''''' - the \ is needed to use : as a character! 
#!/bin/bash
xinput set-int-prop "touchscreen" "Evdev Axis Calibration" 32 3936 125 3873 183
xmodmap /etc/skel/.pndXmodmap
loadkeys /etc/keymap-extension-2.6.map

The xinput line is for the evdev touchscreen configuration, if this is wrong, please run '''xinput_calibrator''' from a Terminal, and replace the line with what it gives you!

The loadkeys line also ensures that the console gets the correct keymap as well.

Thanks to chris_c for the GDM init hint, and mcobit for the loadkeys hint!

Should probably copy more over but, this'll do for now. 

==== Nubs ====
The nubs just require some more config stuff to be copied over, and a few rc scripts to be setup right. 
''Angstrom'' '''''sudo cp -R /etc/pandora /media/mmcblk0p1/etc''''' 
This also copies over configurations for the LCD backlight, some pmenu and mmenu stuff, and some PND configuration bits.

''Angstrom'' '''''sudo cp /etc/init.d/pandora-state /media/mmcblk0p1/etc/init.d''''' - pandora-state restores nubs and backlight settings, as well as saves them on exit.

Configuration utils come in with the PND installation below.

==== Touchscreen ====
===== Current 1.0.2/3 Release =====
1.0.2 uses evdev instead of libts for the touchscreen. This doesn't really require any configuration for the most part, but does need to be calibrated. 
You'll need a full dev setup on the Pandora for this, as you'll need to compile the xinput_calibrator - http://www.freedesktop.org/wiki/Software/xinput_calibrator however it's fairly trivial once all the libraries are installed.

My values, which you should put into .xsession, are as follows: '''''xinput set-int-prop "touchscreen" "Evdev Axis Calibration" 32 3936 125 3873 183''''' and you'll need xinput installed ( which you should've done above if following the 1.0.3 path. )

This is already done on 1.0.4 and xinput_calibrator is included should you need to re-run it.

===== libts for other releases =====
''Debian'' '''''apt-get install libxcb-dri2-0 xserver-xorg-input-tslib libts-bin''''' 
''Debian'' '''''nano /etc/profile.d/tslib.sh'''''
#!/bin/sh
TSLIB_TSDEVICE=/dev/input/event5
TSLIB_CONFFILE=/etc/ts.conf
export TSLIB_TSDEVICE TSLIB_CONFFILE

We'll do the rest of it on First Boot. 
This will be fixed properly when WiFi issues settle, so I can finalize a build system and re-do everything as packages - including libts with the OpenPandora-specific patches from the git.

==== Wifi ====
Wifi is fun... most of it will come in the kernel and modules/firmware pack when we get to it, but there's some ancillary scripts and things that lay in wait to catch you off guard! 
''Angstrom'' '''''sudo cp /etc/init.d/wl1251-init /media/mmcblk0p1/etc/init.d''''' 
''Angstrom'' '''''sudo cp /lib/udev/rules.d/50-compat_firmware.rules /media/mmcblk0p1/lib/udev/rules.d''''' 
''Angstrom'' '''''sudo cp /lib/udev/rules.d/compat_firmware.sh /media/mmcblk0p1/lib/udev/rules.d'''''

The wl1251-init script uses busybox. While you could edit the script and remove the dependency on busybox, it's probably better to just install busybox if you haven't already, so that there are less changes to deal with - seeing as it's only about 600kB. 
''Debian'' '''''apt-get install busybox'''''

While we don't necessarily need Network Manager, it's a damn sight more easier to use than battering iwconfig et al from the Terminal: 
''Debian'' '''''apt-get install network-manager-gnome''''' 
This'll take a long time as it pulls in quite a lot of stuff...

==== Bluetooth ====
Debian's bluetooth setup seems to kick in and work without issue. 
Probably need to get a clean way to toggle it on and off - as it defaults to being on.

==== Kernel and Misc Bits and Pieces ====
The kernel *should* be easy... grabbing a fresh set would've been advisable, but this doesn't seem to come with everything so we'll steal from our running system again.

''Angstrom'' '''''sudo cp -R /lib/modules/2.6.27.46-omap1 /media/mmcblk0p1/lib/modules''''' 
''Angstrom'' '''''sudo cp -R /lib/firmware /media/mmcblk0p1/lib/firmare''''' 
''Angstrom'' '''''sudo cp /boot/uImage /media/mmcblk0p1/boot/uImage'''''

==== Battery Monitor ====
You'll likely want to know how much battery power you have! 
''Debian'' '''''apt-get install apmd''''' 
''Debian'' '''''apt-get install xfce4-power-manager''''' 
Somewhat cheeky perhaps, but it does work! [http://www.gp32x.com/board/index.php?/topic/57653-a-guide-to-installing-lxde/page__view__findpost__p__928896 see this post]

If you add '''''xfce4-power-manager &''''' before '''''exec startlxde''''' in your .xsession, it'll start up automatically for you.

==== Misc Init Scripts and Things ====
There are a few random init scripts we need for things: 
''Angstrom'' '''''sudo cp /etc/init.d/led-config /media/mmcblk0p1/etc/init.d''''' - configure the LEDs properly. 
''Angstrom'' '''''sudo cp /etc/init.d/usb-gadget /media/mmcblk0p1/etc/init.d''''' - for initializing the usb gadget device - g_cdc for USB networking, for instance. 
''Angstrom'' '''''sudo cp /usr/bin/usb-gadget /media/mmcblk0p1/usr/bin''''' 
''Angstrom'' '''''sudo cp /etc/profile.d/op_env.sh /media/mmcblk0p1/etc/profile.d''''' - effectively just tells SDL to use tslib driver 
''Angstrom'' '''''sudo cp /etc/default/leds /media/mmcblk0p1/etc/default''''' 
''Angstrom'' '''''sudo cp /etc/default/usb-gadget /media/mmcblk0p1/etc/default''''' 
''Angstrom'' '''''sudo cp /etc/skel/.asoundrc /media/mmcblk0p1/etc/skel''''' 

And some more stuff to install in Debian: 
''Debian'' '''''apt-get install libnotify-bin'''''

==== PNDs ====
There are some init scripts you need for the PNDs to work. These are: 
''Angstrom'' '''''sudo cp /etc/init.d/pndevmapperd-init /media/mmcblk0p1/etc/init.d''''' 
''Angstrom'' '''''sudo cp /etc/init.d/pndnotifyd-init /media/mmcblk0p1/etc/init.d''''' 
''Angstrom'' '''''sudo cp /usr/bin/pnd* /media/mmcblk0p1/usr/bin''''' - there are a few pnd binaries, these include pnd_info, pnd_run, pndevmapperd and pndnotifyd. 
''Angstrom'' '''''sudo cp /usr/lib/libpnd.so.1.0.1 /media/mmcblk0p1/usr/lib''''' - obviously nothing'll work without the pnd libraries! 

There are a bunch of scripts and PNDs hiding in /usr/pandora.. we may as well grab them over as well. 
''Angstrom'' '''''sudo cp -R /usr/pandora /media/mmcblk0p1/usr''''' 

We need to do a symlink to the library properly now, and clean up some stuff. 
''Debian'' '''''ln -s /usr/lib/libpnd.so.1.0.1 /usr/lib/libpnd.so.1''''' 
''Debian'' '''''rm -rf /usr/pandora/mmenu''''' - these are just PNDs that call the programs installed in Angstrom from MiniMenu. We don't have these programs installed on Debian so, they're useless to us. 

==== RC Scripts ====

We also need to disable some things from running.. the first run script specifies the following: 
update-rc.d -f samba remove
update-rc.d -f xinetd remove
update-rc.d -f avahi-daemon remove
update-rc.d -f apmd remove
update-rc.d -f usb-gadget remove
update-rc.d -f banner remove
update-rc.d -f portmap remove
update-rc.d -f mountnfs remove
update-rc.d -f blueprobe remove
update-rc.d -f dropbear remove
update-rc.d -f wl1251-init remove

We'll also need to add some bits to the rc.d script set.
===== Script Fixups =====
We need to fiddle with a few of the scripts - specifically led-config to add the dummy LSB information ( just rip it out of another script, and leave Required-Start, Required-Stop, Default-Start and Default-Stop empty, ) and pndnotifyd-init, pndevmapperd-init and pandora-state where you need to blank out the #adjust marker as it causes Debian to have fits.

If you don't do this, the nub settings won't save, for instance, and some system scripts are not guaranteed to start up. 
The update-rc.d program will shout at you which ones, and essentially, it's just some tidying up that needs done.

It's now recommended to use update-rc.d to put these in rather than the old heavy handed ln calls:
update-rc.d led-config defaults 05
update-rc.d pndevmapperd-init defaults 30 40
update-rc.d pndnotifyd-init defaults 30 40
update-rc.d pandora-state defaults 05

The pandora-state is different on Angstrom than Debian as it didn't start up with it's usual bindings, which was annoying!

=== Users and Permissions ===
You may be wondering why Users haven't been done till the very end.. we've edited the /etc/skel setup which will be used to create your user details.

If you have already jumped the gun and created a user previously, all changes we've done to /etc/skel will need to be mirrored in your home folder!

''Debian'' ''''''adduser <username>''''' - obviously, replace <username> with what you want; for example ''adduser pandora''.

One interesting thing I've noticed happens, is sometimes it'll happily create your user... then not give you full permissions to your own folder.. so let's beat it a bit. 
''Debian'' '''''chown -R <username>:<username> /home/<username>''''' - replacing <username> with your actual username; for example ''chown pandora:pandora /home/pandora'' 

You'll probably want to use sudo, which will require you to be in the wheel group, which we are about to create: 
''Debian'' '''''groupadd wheel''''' 
There's also few groups you'd want to be in, so we'll do that now. 
''Debian'' '''''usermod -a -G wheel <username>''''' - you know the drill now... example; ''usermod -a -G wheel pandora'' 
''Debian'' '''''usermod -a -G adm <username>''''' 
''Debian'' '''''usermod -a -G audio <username>''''' 
''Debian'' '''''usermod -a -G video <username>''''' 
''Debian'' '''''usermod -a -G plugdev <username>''''' 
''Debian'' '''''usermod -a -G users <username>''''' 
''Debian'' '''''usermod -a -G netdev <username>''''' 

Technically, you could've done all this in the one line with adduser, but I'd rather keep it all separate so that if we end up with extra groups, we all know how to add them.

You'll also need to do the above for every new user you create for the moment.

There's a bunch of sudoers rules that are hidden as well that we need to steal ( I completely missed these twice - my thanks to sebt3 and DJWillis for pointing me to them! I thought the #includedir line was commented out due to the # ... *facepalm* ) 
''Angstrom'' '''''sudo cp /etc/sudoers.d/* /media/mmcblk0p1/etc/sudoers.d/'''''

Finally, /tmp can sometimes go mad so we shall fix that just now too. 
''Debian'' '''''chmod a+w /tmp'''''

=== Reboot and Troubleshooting ===

==== auto/boot.txt ====
We need either an autoboot.txt or a boot.txt now or we won't be able to boot up Debian. 
There's no difference between either, other than autoboot will cause the Pandora to automatically boot from SD if it finds it, whereas boot requires holding the right shoulder button as usual. 
''Debian'' '''''nano /autoboot.txt''''' - again, you could use boot.txt instead and press the right shoulder button during boot. 
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0
ext2load mmc 0:1 0x80300000 /boot/uImage
bootm 0x80300000

All that's really left now is to reboot and catch any issues that may crop up!

==== First Boot ====

===== tslib calibration =====
First Boot should bring you up to GDM in all it's splendour. But Wait! The touchscreen! IT IS MADNESS! 
If you've a USB keyboard, you can be one step ahead and do CTRL+ALT+F1 to jump to a terminal, but we're going to assume just the Pandora so we'll carry on and login.

Once LXDE has finished loading up, press FN+ALT+F2 and type "lxterminal" 
'''''sudo su''''' 
'''''export TSLIB_TSDEVICE=/dev/input/event5''''' 
'''''export TSLIB_CONFFILE=/etc/ts.conf''''' 
'''''ts_calibrate'''''

Touchscreen should behave itself now. 

===== Finish up installing any left overs =====
While root ( that's what sudo su does ) we shall finish setting up anything that didn't take during our chroot session in Angstrom ( bluetooth usually ) 
'''''apt-get -f install''''' 
'''''exit''''' - jump back to our user so we don't accidentally mess things up 

==== Cleanup ====
Potential clean-ups that should occur is packaging up the Pandora specific libraries and scripts into .deb files for maintenance purposes if nothing else. We can then either try and get them fed back into Debian, or provide our own Debian repo for Pandora.

The following should probably be stuffed into deb files for easier maintainability: 
* libpnd
* pandora specific scripts
* SGX drivers
* kernel
* modules and firmware

== Maintenance and Upgrades ==
Maintenance on Debian is very easy.. it's just a case of running '''''sudo apt-get update && sudo apt-get upgrade''''' from a console, or using Synaptic ( see below on how to install if your rootfs didn't have it. )

== Common Issues/Fun Things To Do ==
There's a wealth of power at your fingertips with Debian, so place your fun things to do here! 
Also, sometimes there are odd issues, so if you fix something odd, place it here too.

=== Networking ===
Networking should work effectively the same as on Angstrom, but here's a run down of what to do anyway:
* Click the LXDE menu up.
* Click System Tools -> Toggle Wifi
* Click the Network Manager app between the process bar and the clock.
* Click your network - or select "Connect to Hidden Wireless Network" if it's not there and fill out the details.
* Fill out the keyring for your passwords to go into - so you only need to remember the one ;)
* The Network Manager icon should spin and then give you a strength bar as normal once connected.

=== Synaptic ===
The 1.0.1 release did not include Synaptic.. it's back in 1.0.2 and 1.0.3 
To get it back for the 1.0.1 release, it's simply a case of doing: 
'''''sudo apt-get update''''' - if you haven't done so for a while ( as in, days, not hours ) 
'''''sudo apt-get install synaptic''''' 
Then wait for a while as it downloads and installs.

You'll find Synaptic under System Tools once it's done.

=== My PNDs don't work, why?! ===
Generally, it'll be because of library differences.. I'm still trying to figure out the best way to deal with this, but you've got the Debian armel repository at your disposal, so you should be fine for a while!

1.0.2 has some library compatibility with Pandora Angstrom but it's not complete. The PNDs of Wesnoth and BattleJewels will work for example, whereas SuperTux and GravityForce do not.

Library compatibility was achieved by pulling packages manually from older revisions, symlinking some libraries and pulling stuff from experimental.. it was trial and error so, is a tad iffy.

1.0.3 and 1.0.4 do not have library compatibility as it caused extra issues in 1.0.2, you'll need to either wait for 1.1 or pull in the needed libraries yourself.

=== Wifi and Session Management is broken?! ===
Pre-1.0.3 there was an issue with this.. it should now be fixed in 1.0.3 so if you don't want to update, perform the following: 
'''''sudo rm -f /etc/udev/rules.d/70-persistent-net.rules''''' 
'''''sudo chmod +x /usr/lib/dbus-1.0/dbus-daemon-launch-helper''''' 
and reboot.. everything should now work properly.

=== My PNDs don't appear immediately? ===
This is an odd one.. by rights they should.. and I also don't quite understand why pndnotifyd kicks in when you open a terminal, but it does.

Therefore, if you haven't done so already, open up a terminal and then close it.. pndnotifyd then starts up and takes care of all the PND stuff for you.

This should be fixed in 1.0.4

=== I get no notifications in 1.0.3 ===
This is actually because notification-daemon hasn't been installed.

=== Packages to add in 1.1! ===
Feel free to add packages here that I should include in the next release (1.1)
* wireless-tools
* x11-xserver-utils ( I keep forgetting this.. it's for xmodmap )
* xinput - for evdev's configuration
* console-tools - for chvt
* xterm - for failsafe console
* bash-completion - tis handy to have
* aptitude - somehow I forgot this.

= Emdebian Grip =
Most of the above can be taken for Grip, with the following changes...

Why Grip? It's much smaller and targeted for embedded devices... I originally was going to use Grip actually, but it was a bit buggered at the time, though it seems to be working now. 
Additionally, Emdebian comes in Crush and Baked flavours... Grip is compatible with Desktop Debian, so we'll use that.. Crush is smaller again, and generally requires a cross-compiler to setup packages, and Baked is effectively what we do with Angstrom.

Emdebian could also in theory be shrunk enough to actually fit on NAND... which is something I'll be looking into - if only to document another alternative process to the Angstrom OE bitbake bonanza.

== Multistrap ==
Grip's debootstrap is slightly different... it uses multistrap instead.

This allows us to use Grip's repository as the base, and Desktop Debian's repositories for anything else we might need ( omap3 drivers, for instance. ) This is also particularly useful for us when I get around to doing Pandora specifics compiled for Debian, as then we just add that repository as well.

Anyway, we need Debian running for this - be it on your Desktop ( or Ubuntu ) or on your Pandora ( recommended, as this guide assumes this is what you're doing. ) 
Install Multistrap - '''''sudo apt-get install multistrap'''''

You'll also need to mount an SD card somewhere manually.. I've mounted mine to /tmp/emdebian: '''''sudo umount /dev/mmcblk1p1 && mount /dev/mmcblk1p1 /tmp/emdebian'''''

=== Config File ===
'''''nano multistrap'''''
[General]
arch=armel
directory=/tmp/emdebian
cleanup=true
noauth=false
unpack=true
aptsources=Grip Debian
debootstrap=Grip Debian

[Debian]
packages=
source=ftp://ftp.uk.debian.org/debian
keyring=debian-archive-keyring
suite=squeeze

[Grip]
packages=
keyring=emdebian-archive-keyring
source=http://www.emdebian.org/grip
suite=squeeze

'''''sudo multistrap -f multistrap'''''

Change /tmp/multistrap to where ever you want the debootstrap to occur. 
'''Gotcha''''' I had issues with it complaining about unauthenticated packages, just add '''--no-auth''' to your command line and it'll continue happily.''

This shouldn't take too long ( was about half an hour on my Pandora ) and gives you a very sparse minimal rootfs of 192Mb.

The following multistrap config will give you what's in the 1.0.4 Grip rootfs
[General]
arch=armel
directory=/tmp/emdebian
cleanup=true
noauth=false
unpack=true
aptsources=Grip Debian
debootstrap=Grip Debian

[Debian]
packages=xserver-xorg-video-omap3 libxcb-dri2-0 libnotify-bin xinput
source=ftp://ftp.uk.debian.org/debian
keyring=debian-archive-keyring
suite=squeeze

[Grip]
packages=lxde busybox network-manager-gnome xfce4-power-manager apmd gdm less sudo nano wireless-tools iceweasel synaptic gnome-mplayer x11-xserver-utils notification-daemon gnome-keyring
keyring=emdebian-archive-keyring
source=http://www.emdebian.org/grip
suite=squeeze

You could also add packages into the Grip and Debian configuration parts, and it will automatically pull them down and install them for you, be careful with what you pull in though, as not everything has been repackaged for Grip, so it will pull down the "full fat" variants from Debian instead.

You might get errors of unconfigured packages, just chroot in and run '''''apt-get -f install''''' to finish up.. if there are warnings about proc, ignore them till you reboot into the rootfs and re-run '''''sudo apt-get -f install'''''.

== Chroot and Setup ==
Now we can just chroot in and setup as we see fit. 
'''''sudo chroot /tmp/emdebian''''' - again, you may have mounted your media elsewhere. 
'''''sudo apt-get update'''''

You can now just follow the Debian guide as above, with the added bonus of most packages will come from Grip and be pre-stripped of extra fluff. 
I would recommend to get as much stuff as possible downloaded in the initial multistrap however, as it will automatically clean stuff up for you.

= Debian On NAND =
First of all, 
'''''WARNING: DO NOT ATTEMPT THIS.''''' 
'''''NO, SERIOUSLY, DON'T! THIS IS UTTERLY HACKY AND IT IS ON YOUR OWN HEAD IF YOU MESS UP.''''' 

== Get a Debian Rootfs ==
Your NAND has about 475Mb for the rootfs to play with ( there are other partitions, remember! ), therefore Desktop Debian is a bit too large for our purposes - even 1.0.3's complete massacre still ended up too big by far; so we need to look at Emdebian, of which there are three flavours - grip, crush and baked. 
We'll be using Grip, so follow the guide above for at least getting a working system on SD before going anywhere near your NAND.

We can use compression to get your rootfs down by 40-50%, but I'd still be vary wary of a large rootfs!

If you're lazy, grab my pre-made Grip rootfs, which includes LXDE by default.

== Preparing the Rootfs ==
Boot into your rootfs for this, so we can ensure we're as up to date as we can be, then clean the apt cache, and then any crap we installed which we don't need any more, such as things which were installed as dependencies and the parent's been removed. 
'''''sudo apt-get update''''' 
'''''sudo apt-get upgrade''''' 
'''''sudo apt-get clean''''' 
'''''sudo apt-get autoclean''''' 

Additionally, you could wipe out the documentation ( if any ) and manually pull out unwanted packages. However, if you're pulling stuff out, you shouldn't have installed it in the first place! Go back to the start and do it again as punishment!

This post on the Ubuntu forums is particularly helpful: http://ubuntuforums.org/showthread.php?t=140920

Depending on your needs, you may also want to wipe out your home folder and reinstate it from /etc/skel 
You'll also want to wipe out tmp - '''''sudo rm -rf /tmp/*'''''

Now shut down and either place your SD card in your PC. You can do this on Pandora, but you will need a lot of space.

Copy your rootfs somewhere.. I suggest /tmp/pandora-debian 
'''''mkdir /tmp/pandora-debian''''' 
'''''sudo cp -p -r /media/my/sd/card/* /tmp/pandora-debian''''' - this will preserve Permissions and copy everything Recursively.

We need to edit the fstab so that it can boot properly, if you haven't done so already. 
'''''sudo nano /tmp/pandora-debian/etc/fstab'''''
# OpenPandora fstab.

rootfs / auto defaults,noatime 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
tmpfs /var/volatile tmpfs defaults 0 0
tmpfs /dev/shm tmpfs mode=0777 0 0
tmpfs /media/ram tmpfs defaults 0 0

This should look familiar, as it's effectively your stock fstab minus the boot partition ( we have a kernel in our rootfs, if you've followed the above guides... )

We should also get rid of the autoboot.txt or boot.txt; '''''sudo rm /tmp/pandora-debian/autoboot.txt'''''

== Creating the Image ==
You need mtd-utils in your Debian distro of choice. '''''sudo apt-get install mtd-utils'''''

Now, mkfs.ubifs can compress using either LZO ( by default ) or zlib and will get your rootfs about 40-50% smaller depending on what you choose. It's also possible to use a combination of both, which is what we will do later.. Of course, if your rootfs is full of pre-compressed stuff already, it's not really going to shrink a great deal. 
For a full run down on mkfs.ubifs and co, see here: http://www.linux-mtd.infradead.org/doc/ubifs.html

Download the flash kit: http://openpandora.org/firmware/pandora-flash-kit.zip and extract it to /tmp/flash. I suggest reading the README as well.

Now run these fun commands... what we're doing is we're making a ubifs image first, then making an md5 checksum. 
We're also favoring LZO compression meaning we're mixing zlib and LZO to get the best compression we can. 
'''''sudo mkfs.ubifs -r /tmp/pandora-debian -o rootfs.img -m 2048 -e 129024 -c 4042 -x favor_lzo -X 20''''' 
'''''md5sum rootfs.img > rootfs.md5'''''

'''STOP! If your rootfs.img is getting close to 480Mb, you might not want to try and flash it.. it may be fine, but I would recommend 450Mb as an absolute maximum.'''

== Flashing the Image ==
I shall repeat: 
'''''WARNING: DO NOT ATTEMPT THIS.''''' 
'''''NO, SERIOUSLY, DON'T! THIS IS UTTERLY HACKY AND IT IS ON YOUR OWN HEAD IF YOU MESS UP.''''' 

Stick the following on to a FAT32 formatted SD card: 
* '''boot.scr''' - from the flash kit.
* '''rootfs.img''' - the image you've just created.
* '''rootfs.md5''' - the checksum to the image.

Place it in slot 1 of your Pandora ( the left slot, ) reboot while holding the right trigger, select boot from SD, cross your fingers and pray to the Pandora Gods.

Once it's done.. reboot and see what mess you've made, assuming you get it to boot! 
If you haven't got it to boot, on your FAT32 flasher card, add an autoboot.txt with the following:
setenv bootargs ubi.mtd=4 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw vram=6272K omapfb.vram=0:3000K
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr};

As this will let you see what's gone wrong... I had to do this a few times, as I buggered it up myself...

Congratulations, you now have Debian on NAND rather than Angstrom. 
Also, these instructions could easily be adapted to allow you to use any other distro that boots on Pandora.

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Storage card]]
[[Category:Booting]]

Debian On SD

2012-05-05T13:31:53Z

Notaz: remove ttyS0, breaks new kernel

= Debian On SD =

I'm going to split this into three chunks now... standard Desktop Debian on SD using Squeeze/Lenny/Sid ( choose your poison, though only Squeeze is officially tested to work by myself, ) Emdebian GRIP install, and NAND install.

You can post feedback, bugs, etc.. on the following topics:
GP32X: http://www.gp32x.com/board/index.php?/topic/57097-debian-on-an-sd-card/
OpenPandora Boards: http://boards.openpandora.org/index.php?/topic/1819-debian-on-sd/

I'd prefer the GP32X boards as I'm slightly more active there.

= Little Note to Wiki Editors =
I change this a lot offline and then plaster the changes on during a new release. 
If you're going to go changing this page, please contact me first so I don't accidentally obliterate your changes, or that you do changes to the style I've set out that I don't agree with! 
This may well be against the "wiki spirit" .. but I spend days/weeks typing up these changes and testing them.. so a little consideration please :)

== Desktop Debian ==
This is split into three main sections - Building from Scratch, Maintenance and Upgrades, Common Things To Do.

''' This documents the final 1.0.3 and 1.0.4 "brute force" releases. The 1.1 "debianized" release will take a while and not involve this process at all. '''

* Building From Scratch lets you customise everything from the outset, and lets you create your very own tailor-made distribution, rather than a pre-created one.
It does require a bit of Linux knowledge before diving in.. so if unsure, ask!

* Maintenance and Upgrades covers standard Debian maintenance if you're not usually a Debian user.
It'll also ( in the future ) cover how to upgrade your pre-built distribution with new drivers as the official OS gets updated.

* Common/Fun Things To Do will give you ideas on what to try in your new Debian installation.
Remember, this is a full desktop OS you now have squeezed into your hands, and feel free to share your cool ideas!

If you don't want to build from scratch, you have two choices;
* Grab a Minimal Install and continue from [http://pandorawiki.org/index.php?title=Debian_On_SD#Desktop_Environment Desktop Environment]
* Grab a full build.

The latest minimal is available here: http://www.stuckiegamez.co.uk/apps/pandora/Debian/pandora-squeeze-minimal-1.0.2.tar.bz2 
The latest full builds are:
* LXDE - http://www.stuckiegamez.co.uk/apps/pandora/Debian/pandora-squeeze-1.0.4-grip.tar.bz2
* XFCE - http://www.stuckiegamez.co.uk/apps/pandora/Debian/pandora-squeeze-1.0.5-grip.tar.bz2

Remember to untar with permissions ( include '''p''' in your arguments to tar ) on to your ext2/3 formatted SD card. 
For example: '''''tar -xvjpf pandora-squeeze*.tar.bz2 -C /media/sdcard .'''''

Default User details are: 
username: '''pandora''' 
password: '''debian'''

=== Changelog ===
==== Original Proof of Concept ====
* Released - 19th October 2010
* Based on Sid
* GDM
* GNOME
* Bit slow but workable

==== Release 1.0 ====
* Released - 20th February 2011
* First release
* libts issues
* libpnd issues
* Overly fat with stuff
* Wifi issues for some people

==== Release 1.0.1 ====
* Released - 23rd February 2011
* First documented release
* libts issues persist
* Most libpnd issues fixed
* Slimmed down to ~830mb
* Made Wifi issues worse and accidentally stripped out more than needed

==== Release 1.0.2 ====
* Released - 22nd March 2011
* Replaced libts with evdev... doesn't cause X choking.
* libpnd should behave now, though the pnd services don't seem to get kicked till a terminal is opened, and even then they turn zombie.. eh?
* Added full dev setup.. so it's fat.. it's 1.2gig extracted.
* Replaced GDM with SLIM.

==== Release 1.0.3 ====
* Released - 27th March 2011
* Effectively 1.0.2 with the WiFi and Session Management bug fixed.
* Much slimmer as it's done from scratch again without the dev setup ~805mb rootfs

==== Release 1.0.4 ====
* Released - 4th April 2011
* 1.0.3 with lots of bugs fixed and based on Grip so it's got even more and super tiny in comparision.
* Contains; LXDE, GDM, Gnome MPlayer, IceWeasel ( firefox ) and Synaptic

==== Release 1.0.5 ====
* Released - 9th April 2011
* 1.0.4 with XFCE instead of LXDE and a few bug fixes ( pandora-state's rc scripts being set correctly, and console key map .. see the relevant bits below if you need them, but other than that, it's exactly the same - just with XFCE instead of LXDE )

=== Release 1.1 Proposed ===
* Expected - May 2011 ( maybe )
* libts, amongst other libraries, using OpenPandora patched version.
* Pandora specifics wrapped as Debian archives.
* Pandora specifics repo to deal with updates to drivers from mainline.
* Perhaps an updated kernel using the patches from mainline.

== Building From Scratch ==
This isn't for the feint of heart.. if you don't understand something - stop! Ask or read up on it before continuing. While I haven't mangled my Pandora or PC in any way from doing this, it's still possible to make a mess, so be careful!

This is split into many parts.. it's advised to go through this in order.

* Getting a Minimal Install from Scratch
* Desktop Environment
* Device Drivers and PNDs
* Users, First Boot Scripts and Permissions
* Reboot and Troubleshooting

=== Getting a Minimal Install from Scratch ===

There are two options here:
* Linux PC
* On Pandora

==== Linux PC ====
On a Linux PC, run debootstrap to grab the version you want. We shall be using Squeeze today: 
'''''sudo debootstrap --arch armel --foreign squeeze /tmp/pandora-debian ftp://ftp.uk.debian.org/debian''''' 
Grab a large SD card, and repartition it to have one large ext2/ext3 partition and format as normal. 
Copy all the files from /tmp/pandora-debian over to your new SD card partition. 
Put it in your Pandora. 
'''''sudo chroot /media/mmcblk0p1''''' -- assuming it's in your first slot. 
'''''/debootstrap/deboostrap --second-stage''''' 
... this takes a while...

==== Pandora ====
Alternatively, you can run cdebootstrap on the Pandora itself, or debootstrap from within Debian... this bypasses the need of doing the second-stage madness. 
Grab it from here: http://packages.debian.org/sid/cdebootstrap-static and select the armel package. 
Download it to /tmp preferably, but your home folder will do, or anywhere you like. For now, I shall assume you downloaded it to /tmp 
'''''cd /tmp''''' -- Again, if you downloaded elsewhere, change to that directory instead. 
'''''ar xv cdebootstrap*.deb''''' -- We're using the archive tool to extract with verbosity our cdebootstrap package. 
'''''sudo tar -zxvf data.tar.gz -C /''''' -- Now we're using tar to extract, with gzip support, again with verbosity, the file data.tar.gz, changing the Current directory to / so that it extracts systemwide on our NAND. We're running this command sudo so we have write permissions. 
Now we just run cdebootstrap-static with a few parameters, and wait. 
'''''cdebootstrap-static --allow-unauthenticated -f minimal squeeze /media/mmcblk1p1''''' -- What we're doing here, is we're allowing "unauthenticated" packages to be installed. As we don't, or probably don't, have the gnupg keychain stuff configured, all packaged will be "unauthenticated" regardless of whether they are or not. We're telling it we also want a minimal install of the squeeze release, and to install to where we have the mount point of Partition 1 of the SD card in Slot 1 - which you should have already partitioned and formatted as ext2! 
This takes a while... perhaps longer than doing the first stage on the PC and second-stage on Pandora.

=== Setting up Apt ===
I've forgotten about this, as mostly it'll be set to the default Debian repository, but should you want to change it: 
'''''sudo nano /etc/apt/sources.list'''''

UK people can set this to ''deb ftp://ftp.uk.debian.org/debian main non-free contrib'' to get pretty much everything, or can pick whichever local Debian repository they like - but be warned that not all of them have an armel repo! 
By default, debootstrap will likely only get main.. adding the non-free and contrib branches are optional, but bring in more stuff.

=== Desktop Environment ===
Now you have Debian, the world is yours for the taking!
Or something like that...

Debian comes with a wide variety of desktop environments and window managers; from XFCE as you use on Angstrom by default, to KDE, GNOME, LXDE, Fluxbox, Enlightenment, etc.. 
Now's the time to choose one of them to install.. be aware that the bigger they are, the longer they'll take to install and the more resources they will eat up while in use.. as a rough guide from heavy to light: 
* KDE
* GNOME
* Enlightenment ( Squeeze has e16 .. and is faster than I expected )
* XFCE
* LXDE
* Fluxbox

Having recently tested KDE myself, it doesn't quite seem to work properly, so I'd avoid that for the moment... especially as it takes about ten hours to install!

We shall install LXDE as it's a bit more light weight than XFCE and still provides a reasonable mainstream environment. While I do prefer Fluxbox overall, it's a bit of a paradigm shift to use from your standard desktop machine.

If you haven't already, chroot into your environment.
You should already be root, so we'll get on with the installing.

'''''apt-get install lxde'''''

This may well take an age, so go do something else in the meantime. 
You may also want a login manager.. your choices are amongst XDM, GDM, KDM and SLIM to name a few. KDM is perhaps a bit heavy, whereas GDM works fairly well even though it's rather heavy too. SLIM is what you use on Pandora anyway, and XDM is rather basic but usable all the same. GDM is automatically pulled in via LXDE anyway, so we may as well just use that for now.

Additional: 
Installing LXDE via the above command pulls in GDM by default.. if you use ''lxde-core'' instead, it removes a lot of the stuff that pulls in random things, and if you additionally use '''''aptitude install --without-recommends lxde-core''''' it should strip out even more. You will need to manually install ''less'', ''zenity'', and ''xterm'' for example. Zenity is especially needed for all the Pandora config scripts.

1.0.3 has slimmed stuff down again. 
Once in the chroot jail, I've performed the following: '''''aptitude install --without-recommends lxde-core slim lxterminal zenity less xserver-xorg-video-omap3 network-manager-gnome synaptic xfce4-power-manager apmd libnotify-bin gedit epiphany-browser eject gksu gnome-bluetooth python-dbus ca-certificates xinput busybox''''' which will effectively pull in all the Debian specifics we'll be needing, gutting out a rather large amount of cruft.

Once it's done, we'll start tackling the Drivers.

=== Device Drivers and PNDs ===
We shall tackle these one at a time, as there's quite a few of them.

* X Display Driver
* SGX Drivers
* Keymap
* Nubs
* Touchscreen
* Wifi
* Bluetooth
* Kernel and Misc Bits and Pieces
* PNDs

==== X Display Driver ====
Debian has a NEON-optimised omapfb driver. We shall use this, and pinch some configuration gubbins from Angstrom.

'''''apt-get install xserver-xorg-video-omap3'''''

We now need to create an xorg.conf .. though it'll be rather minimal as we only really want to overload what graphics device setup it has, so: 
'''''nano /etc/X11/xorg.conf''''' 
Section "Module"
Load "extmod"
Load "dbe"
Disable "glx"
Disable "dri"
Load "dri2"
EndSection

Section "ServerLayout"
Identifier "DefaultLayout"
Screen "Screen0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "OMAPFB"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "800x480"
EndSubSection
EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Device"
Identifier "OMAPFB"
Driver "omapfb"
Option "fb" "/dev/fb0"
EndSection

Most of this is pinched from the Angstrom xorg.conf minus the fb Option at the bottom, as our framebuffer has a different device node.

That should be all you need for basic X though.

==== SGX Drivers ====
Most of this has been pinched from http://elinux.org/BeagleBoardDebian#SGX_Video_Acceleration - why rewrite the wheel? 
This mostly works apart from a few caveats, so I shall repeat it here for future reference and to keep all information in one place, and I've uploaded the resulting tarballs for convenience.

You can either follow the above guide - substituting the BeagleBoard for the Pandora, or use the following preconfigured packages. 
'''''cd /tmp''''' 
'''''wget -c http://www.stuckiegamez.co.uk/apps/pandora/Debian/GFX_4_00_00_01_libs.tar.gz''''' ~20MB Libraries themselves 
'''''wget -c http://www.stuckiegamez.co.uk/apps/pandora/Debian/GFX_Linux_SDK.tar.gz''''' ~220MB Demos and SDK gubbins 

Technically, you don't really need that fat 220MB GFX_Linux_SDK tarball unless you really want it, or want to test the libraries are in place. 
I'll cover installing both anyway...

===== Libraries =====
'''''tar -zxvf GFX_4_00_00_01_libs.tar.gz''''' 
'''''chmod +x ./install-SGX.sh''''' 
'''''./install-SGX.sh''''' 
'''''rm /devmem2_0.0-0ubuntu1_armel.deb''''' - this is particularly useless to us... and why it dumps it at root, I don't know! 

That package contains ES2, ES3 and ES5 libraries.. we're only really interested in ES2 ( haven't tried if ES3 or ES5 would even work! ) so: 
'''''cd /usr/lib''''' 
'''''ln -s ES2.0/* .''''' 

Not hugely clean, but it works. For the brave, you could try ES3 or ES5 but.. you're on your own!

===== Demos/SDK =====
'''''cd /tmp''''' 
'''''tar -zxvf OGLES.tar.gz''''' 
'''''tar -zxvf OGLES2.tar.gz''''' 

You can't run anything yet ( well, you might since you've chrooted in via Angstrom ) so we'll leave them in /tmp for the moment - or move them elsewhere - such as /opt if you're worried about Debian wiping out /tmp on boot.

==== Keymap ====
The keymap is actually stupidly easy, and I've missed how easy it is for quite a while now! 
We shall steal them from Angstrom.. so open up another Terminal. 
As of now, I shall prefix Angstrom commands with ''Angstrom'' and Debian commands with ''Debian'' so you know which Terminal to type them in.

''Angstrom'' '''''sudo cp /etc/keymap-extension-2.6.map /media/mmcblk0p1/etc''''' - this does assume you've got your SD card mounted in slot one, and with one ext2 partition.. adjust as necessary. 
''Angstrom'' '''''sudo cp /etc/skel/.pndXmodmap /media/mmcblk0p1/etc/skel''''' - as above. 

After some fiddling, if you stick the following into ''.xsession'' it'll actually get called...
whoami > /tmp/currentuser
killall -1 pndnotifyd &
exec startlxde

Of course, this is a bit hacky and hard-coded in that if you've chosen something other than lxde, you'll probably want to change that startlxde to something else!

1.0.2 does something really hacky and actually starts pndnotifyd and pndevmapperd as daemons directly. 
It also starts up the xfce4-power-manager for a battery meter.

1.0.3 does something else again.. it does not have the '''killall -1 pndnotifyd &''' line, instead it has the following:
sudo /etc/init.d/pndnotifyd-init restart
sudo /etc/init.d/pndevmapperd-init restart
And has edited /etc/sudoers.d/99_libpnd to add access to those two lines without being prompted for a password.

1.0.4 is again different, and doesn't HUP pndnotifyd at all as it seemed to work without much issue just by starting the service differently, also, due to use of GDM, we do the xmodmap at GDM's startup instead in the following manner: 
'''''sudo nano /etc/gdm/Init/\:0''''' - the \ is needed to use : as a character! 
#!/bin/bash
xinput set-int-prop "touchscreen" "Evdev Axis Calibration" 32 3936 125 3873 183
xmodmap /etc/skel/.pndXmodmap
loadkeys /etc/keymap-extension-2.6.map

The xinput line is for the evdev touchscreen configuration, if this is wrong, please run '''xinput_calibrator''' from a Terminal, and replace the line with what it gives you!

The loadkeys line also ensures that the console gets the correct keymap as well.

Thanks to chris_c for the GDM init hint, and mcobit for the loadkeys hint!

Should probably copy more over but, this'll do for now. 

==== Nubs ====
The nubs just require some more config stuff to be copied over, and a few rc scripts to be setup right. 
''Angstrom'' '''''sudo cp -R /etc/pandora /media/mmcblk0p1/etc''''' 
This also copies over configurations for the LCD backlight, some pmenu and mmenu stuff, and some PND configuration bits.

''Angstrom'' '''''sudo cp /etc/init.d/pandora-state /media/mmcblk0p1/etc/init.d''''' - pandora-state restores nubs and backlight settings, as well as saves them on exit.

Configuration utils come in with the PND installation below.

==== Touchscreen ====
===== Current 1.0.2/3 Release =====
1.0.2 uses evdev instead of libts for the touchscreen. This doesn't really require any configuration for the most part, but does need to be calibrated. 
You'll need a full dev setup on the Pandora for this, as you'll need to compile the xinput_calibrator - http://www.freedesktop.org/wiki/Software/xinput_calibrator however it's fairly trivial once all the libraries are installed.

My values, which you should put into .xsession, are as follows: '''''xinput set-int-prop "touchscreen" "Evdev Axis Calibration" 32 3936 125 3873 183''''' and you'll need xinput installed ( which you should've done above if following the 1.0.3 path. )

This is already done on 1.0.4 and xinput_calibrator is included should you need to re-run it.

===== libts for other releases =====
''Debian'' '''''apt-get install libxcb-dri2-0 xserver-xorg-input-tslib libts-bin''''' 
''Debian'' '''''nano /etc/profile.d/tslib.sh'''''
#!/bin/sh
TSLIB_TSDEVICE=/dev/input/event5
TSLIB_CONFFILE=/etc/ts.conf
export TSLIB_TSDEVICE TSLIB_CONFFILE

We'll do the rest of it on First Boot. 
This will be fixed properly when WiFi issues settle, so I can finalize a build system and re-do everything as packages - including libts with the OpenPandora-specific patches from the git.

==== Wifi ====
Wifi is fun... most of it will come in the kernel and modules/firmware pack when we get to it, but there's some ancillary scripts and things that lay in wait to catch you off guard! 
''Angstrom'' '''''sudo cp /etc/init.d/wl1251-init /media/mmcblk0p1/etc/init.d''''' 
''Angstrom'' '''''sudo cp /lib/udev/rules.d/50-compat_firmware.rules /media/mmcblk0p1/lib/udev/rules.d''''' 
''Angstrom'' '''''sudo cp /lib/udev/rules.d/compat_firmware.sh /media/mmcblk0p1/lib/udev/rules.d'''''

The wl1251-init script uses busybox. While you could edit the script and remove the dependency on busybox, it's probably better to just install busybox if you haven't already, so that there are less changes to deal with - seeing as it's only about 600kB. 
''Debian'' '''''apt-get install busybox'''''

While we don't necessarily need Network Manager, it's a damn sight more easier to use than battering iwconfig et al from the Terminal: 
''Debian'' '''''apt-get install network-manager-gnome''''' 
This'll take a long time as it pulls in quite a lot of stuff...

==== Bluetooth ====
Debian's bluetooth setup seems to kick in and work without issue. 
Probably need to get a clean way to toggle it on and off - as it defaults to being on.

==== Kernel and Misc Bits and Pieces ====
The kernel *should* be easy... grabbing a fresh set would've been advisable, but this doesn't seem to come with everything so we'll steal from our running system again.

''Angstrom'' '''''sudo cp -R /lib/modules/2.6.27.46-omap1 /media/mmcblk0p1/lib/modules''''' 
''Angstrom'' '''''sudo cp -R /lib/firmware /media/mmcblk0p1/lib/firmare''''' 
''Angstrom'' '''''sudo cp /boot/uImage /media/mmcblk0p1/boot/uImage'''''

==== Battery Monitor ====
You'll likely want to know how much battery power you have! 
''Debian'' '''''apt-get install apmd''''' 
''Debian'' '''''apt-get install xfce4-power-manager''''' 
Somewhat cheeky perhaps, but it does work! [http://www.gp32x.com/board/index.php?/topic/57653-a-guide-to-installing-lxde/page__view__findpost__p__928896 see this post]

If you add '''''xfce4-power-manager &''''' before '''''exec startlxde''''' in your .xsession, it'll start up automatically for you.

==== Misc Init Scripts and Things ====
There are a few random init scripts we need for things: 
''Angstrom'' '''''sudo cp /etc/init.d/led-config /media/mmcblk0p1/etc/init.d''''' - configure the LEDs properly. 
''Angstrom'' '''''sudo cp /etc/init.d/usb-gadget /media/mmcblk0p1/etc/init.d''''' - for initializing the usb gadget device - g_cdc for USB networking, for instance. 
''Angstrom'' '''''sudo cp /usr/bin/usb-gadget /media/mmcblk0p1/usr/bin''''' 
''Angstrom'' '''''sudo cp /etc/profile.d/op_env.sh /media/mmcblk0p1/etc/profile.d''''' - effectively just tells SDL to use tslib driver 
''Angstrom'' '''''sudo cp /etc/default/leds /media/mmcblk0p1/etc/default''''' 
''Angstrom'' '''''sudo cp /etc/default/usb-gadget /media/mmcblk0p1/etc/default''''' 
''Angstrom'' '''''sudo cp /etc/skel/.asoundrc /media/mmcblk0p1/etc/skel''''' 

And some more stuff to install in Debian: 
''Debian'' '''''apt-get install libnotify-bin'''''

==== PNDs ====
There are some init scripts you need for the PNDs to work. These are: 
''Angstrom'' '''''sudo cp /etc/init.d/pndevmapperd-init /media/mmcblk0p1/etc/init.d''''' 
''Angstrom'' '''''sudo cp /etc/init.d/pndnotifyd-init /media/mmcblk0p1/etc/init.d''''' 
''Angstrom'' '''''sudo cp /usr/bin/pnd* /media/mmcblk0p1/usr/bin''''' - there are a few pnd binaries, these include pnd_info, pnd_run, pndevmapperd and pndnotifyd. 
''Angstrom'' '''''sudo cp /usr/lib/libpnd.so.1.0.1 /media/mmcblk0p1/usr/lib''''' - obviously nothing'll work without the pnd libraries! 

There are a bunch of scripts and PNDs hiding in /usr/pandora.. we may as well grab them over as well. 
''Angstrom'' '''''sudo cp -R /usr/pandora /media/mmcblk0p1/usr''''' 

We need to do a symlink to the library properly now, and clean up some stuff. 
''Debian'' '''''ln -s /usr/lib/libpnd.so.1.0.1 /usr/lib/libpnd.so.1''''' 
''Debian'' '''''rm -rf /usr/pandora/mmenu''''' - these are just PNDs that call the programs installed in Angstrom from MiniMenu. We don't have these programs installed on Debian so, they're useless to us. 

==== RC Scripts ====

We also need to disable some things from running.. the first run script specifies the following: 
update-rc.d -f samba remove
update-rc.d -f xinetd remove
update-rc.d -f avahi-daemon remove
update-rc.d -f apmd remove
update-rc.d -f usb-gadget remove
update-rc.d -f banner remove
update-rc.d -f portmap remove
update-rc.d -f mountnfs remove
update-rc.d -f blueprobe remove
update-rc.d -f dropbear remove
update-rc.d -f wl1251-init remove

We'll also need to add some bits to the rc.d script set.
===== Script Fixups =====
We need to fiddle with a few of the scripts - specifically led-config to add the dummy LSB information ( just rip it out of another script, and leave Required-Start, Required-Stop, Default-Start and Default-Stop empty, ) and pndnotifyd-init, pndevmapperd-init and pandora-state where you need to blank out the #adjust marker as it causes Debian to have fits.

If you don't do this, the nub settings won't save, for instance, and some system scripts are not guaranteed to start up. 
The update-rc.d program will shout at you which ones, and essentially, it's just some tidying up that needs done.

It's now recommended to use update-rc.d to put these in rather than the old heavy handed ln calls:
update-rc.d led-config defaults 05
update-rc.d pndevmapperd-init defaults 30 40
update-rc.d pndnotifyd-init defaults 30 40
update-rc.d pandora-state defaults 05

The pandora-state is different on Angstrom than Debian as it didn't start up with it's usual bindings, which was annoying!

=== Users and Permissions ===
You may be wondering why Users haven't been done till the very end.. we've edited the /etc/skel setup which will be used to create your user details.

If you have already jumped the gun and created a user previously, all changes we've done to /etc/skel will need to be mirrored in your home folder!

''Debian'' ''''''adduser <username>''''' - obviously, replace <username> with what you want; for example ''adduser pandora''.

One interesting thing I've noticed happens, is sometimes it'll happily create your user... then not give you full permissions to your own folder.. so let's beat it a bit. 
''Debian'' '''''chown -R <username>:<username> /home/<username>''''' - replacing <username> with your actual username; for example ''chown pandora:pandora /home/pandora'' 

You'll probably want to use sudo, which will require you to be in the wheel group, which we are about to create: 
''Debian'' '''''groupadd wheel''''' 
There's also few groups you'd want to be in, so we'll do that now. 
''Debian'' '''''usermod -a -G wheel <username>''''' - you know the drill now... example; ''usermod -a -G wheel pandora'' 
''Debian'' '''''usermod -a -G adm <username>''''' 
''Debian'' '''''usermod -a -G audio <username>''''' 
''Debian'' '''''usermod -a -G video <username>''''' 
''Debian'' '''''usermod -a -G plugdev <username>''''' 
''Debian'' '''''usermod -a -G users <username>''''' 
''Debian'' '''''usermod -a -G netdev <username>''''' 

Technically, you could've done all this in the one line with adduser, but I'd rather keep it all separate so that if we end up with extra groups, we all know how to add them.

You'll also need to do the above for every new user you create for the moment.

There's a bunch of sudoers rules that are hidden as well that we need to steal ( I completely missed these twice - my thanks to sebt3 and DJWillis for pointing me to them! I thought the #includedir line was commented out due to the # ... *facepalm* ) 
''Angstrom'' '''''sudo cp /etc/sudoers.d/* /media/mmcblk0p1/etc/sudoers.d/'''''

Finally, /tmp can sometimes go mad so we shall fix that just now too. 
''Debian'' '''''chmod a+w /tmp'''''

=== Reboot and Troubleshooting ===

==== auto/boot.txt ====
We need either an autoboot.txt or a boot.txt now or we won't be able to boot up Debian. 
There's no difference between either, other than autoboot will cause the Pandora to automatically boot from SD if it finds it, whereas boot requires holding the right shoulder button as usual. 
''Debian'' '''''nano /autoboot.txt''''' - again, you could use boot.txt instead and press the right shoulder button during boot. 
setenv bootargs root=/dev/mmcblk0p1 rw rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0

ext2load mmc 0:1 0x80300000 /boot/uImage
bootm 0x80300000

All that's really left now is to reboot and catch any issues that may crop up!

==== First Boot ====

===== tslib calibration =====
First Boot should bring you up to GDM in all it's splendour. But Wait! The touchscreen! IT IS MADNESS! 
If you've a USB keyboard, you can be one step ahead and do CTRL+ALT+F1 to jump to a terminal, but we're going to assume just the Pandora so we'll carry on and login.

Once LXDE has finished loading up, press FN+ALT+F2 and type "lxterminal" 
'''''sudo su''''' 
'''''export TSLIB_TSDEVICE=/dev/input/event5''''' 
'''''export TSLIB_CONFFILE=/etc/ts.conf''''' 
'''''ts_calibrate'''''

Touchscreen should behave itself now. 

===== Finish up installing any left overs =====
While root ( that's what sudo su does ) we shall finish setting up anything that didn't take during our chroot session in Angstrom ( bluetooth usually ) 
'''''apt-get -f install''''' 
'''''exit''''' - jump back to our user so we don't accidentally mess things up 

==== Cleanup ====
Potential clean-ups that should occur is packaging up the Pandora specific libraries and scripts into .deb files for maintenance purposes if nothing else. We can then either try and get them fed back into Debian, or provide our own Debian repo for Pandora.

The following should probably be stuffed into deb files for easier maintainability: 
* libpnd
* pandora specific scripts
* SGX drivers
* kernel
* modules and firmware

== Maintenance and Upgrades ==
Maintenance on Debian is very easy.. it's just a case of running '''''sudo apt-get update && sudo apt-get upgrade''''' from a console, or using Synaptic ( see below on how to install if your rootfs didn't have it. )

== Common Issues/Fun Things To Do ==
There's a wealth of power at your fingertips with Debian, so place your fun things to do here! 
Also, sometimes there are odd issues, so if you fix something odd, place it here too.

=== Networking ===
Networking should work effectively the same as on Angstrom, but here's a run down of what to do anyway:
* Click the LXDE menu up.
* Click System Tools -> Toggle Wifi
* Click the Network Manager app between the process bar and the clock.
* Click your network - or select "Connect to Hidden Wireless Network" if it's not there and fill out the details.
* Fill out the keyring for your passwords to go into - so you only need to remember the one ;)
* The Network Manager icon should spin and then give you a strength bar as normal once connected.

=== Synaptic ===
The 1.0.1 release did not include Synaptic.. it's back in 1.0.2 and 1.0.3 
To get it back for the 1.0.1 release, it's simply a case of doing: 
'''''sudo apt-get update''''' - if you haven't done so for a while ( as in, days, not hours ) 
'''''sudo apt-get install synaptic''''' 
Then wait for a while as it downloads and installs.

You'll find Synaptic under System Tools once it's done.

=== My PNDs don't work, why?! ===
Generally, it'll be because of library differences.. I'm still trying to figure out the best way to deal with this, but you've got the Debian armel repository at your disposal, so you should be fine for a while!

1.0.2 has some library compatibility with Pandora Angstrom but it's not complete. The PNDs of Wesnoth and BattleJewels will work for example, whereas SuperTux and GravityForce do not.

Library compatibility was achieved by pulling packages manually from older revisions, symlinking some libraries and pulling stuff from experimental.. it was trial and error so, is a tad iffy.

1.0.3 and 1.0.4 do not have library compatibility as it caused extra issues in 1.0.2, you'll need to either wait for 1.1 or pull in the needed libraries yourself.

=== Wifi and Session Management is broken?! ===
Pre-1.0.3 there was an issue with this.. it should now be fixed in 1.0.3 so if you don't want to update, perform the following: 
'''''sudo rm -f /etc/udev/rules.d/70-persistent-net.rules''''' 
'''''sudo chmod +x /usr/lib/dbus-1.0/dbus-daemon-launch-helper''''' 
and reboot.. everything should now work properly.

=== My PNDs don't appear immediately? ===
This is an odd one.. by rights they should.. and I also don't quite understand why pndnotifyd kicks in when you open a terminal, but it does.

Therefore, if you haven't done so already, open up a terminal and then close it.. pndnotifyd then starts up and takes care of all the PND stuff for you.

This should be fixed in 1.0.4

=== I get no notifications in 1.0.3 ===
This is actually because notification-daemon hasn't been installed.

=== Packages to add in 1.1! ===
Feel free to add packages here that I should include in the next release (1.1)
* wireless-tools
* x11-xserver-utils ( I keep forgetting this.. it's for xmodmap )
* xinput - for evdev's configuration
* console-tools - for chvt
* xterm - for failsafe console
* bash-completion - tis handy to have
* aptitude - somehow I forgot this.

= Emdebian Grip =
Most of the above can be taken for Grip, with the following changes...

Why Grip? It's much smaller and targeted for embedded devices... I originally was going to use Grip actually, but it was a bit buggered at the time, though it seems to be working now. 
Additionally, Emdebian comes in Crush and Baked flavours... Grip is compatible with Desktop Debian, so we'll use that.. Crush is smaller again, and generally requires a cross-compiler to setup packages, and Baked is effectively what we do with Angstrom.

Emdebian could also in theory be shrunk enough to actually fit on NAND... which is something I'll be looking into - if only to document another alternative process to the Angstrom OE bitbake bonanza.

== Multistrap ==
Grip's debootstrap is slightly different... it uses multistrap instead.

This allows us to use Grip's repository as the base, and Desktop Debian's repositories for anything else we might need ( omap3 drivers, for instance. ) This is also particularly useful for us when I get around to doing Pandora specifics compiled for Debian, as then we just add that repository as well.

Anyway, we need Debian running for this - be it on your Desktop ( or Ubuntu ) or on your Pandora ( recommended, as this guide assumes this is what you're doing. ) 
Install Multistrap - '''''sudo apt-get install multistrap'''''

You'll also need to mount an SD card somewhere manually.. I've mounted mine to /tmp/emdebian: '''''sudo umount /dev/mmcblk1p1 && mount /dev/mmcblk1p1 /tmp/emdebian'''''

=== Config File ===
'''''nano multistrap'''''
[General]
arch=armel
directory=/tmp/emdebian
cleanup=true
noauth=false
unpack=true
aptsources=Grip Debian
debootstrap=Grip Debian

[Debian]
packages=
source=ftp://ftp.uk.debian.org/debian
keyring=debian-archive-keyring
suite=squeeze

[Grip]
packages=
keyring=emdebian-archive-keyring
source=http://www.emdebian.org/grip
suite=squeeze

'''''sudo multistrap -f multistrap'''''

Change /tmp/multistrap to where ever you want the debootstrap to occur. 
'''Gotcha''''' I had issues with it complaining about unauthenticated packages, just add '''--no-auth''' to your command line and it'll continue happily.''

This shouldn't take too long ( was about half an hour on my Pandora ) and gives you a very sparse minimal rootfs of 192Mb.

The following multistrap config will give you what's in the 1.0.4 Grip rootfs
[General]
arch=armel
directory=/tmp/emdebian
cleanup=true
noauth=false
unpack=true
aptsources=Grip Debian
debootstrap=Grip Debian

[Debian]
packages=xserver-xorg-video-omap3 libxcb-dri2-0 libnotify-bin xinput
source=ftp://ftp.uk.debian.org/debian
keyring=debian-archive-keyring
suite=squeeze

[Grip]
packages=lxde busybox network-manager-gnome xfce4-power-manager apmd gdm less sudo nano wireless-tools iceweasel synaptic gnome-mplayer x11-xserver-utils notification-daemon gnome-keyring
keyring=emdebian-archive-keyring
source=http://www.emdebian.org/grip
suite=squeeze

You could also add packages into the Grip and Debian configuration parts, and it will automatically pull them down and install them for you, be careful with what you pull in though, as not everything has been repackaged for Grip, so it will pull down the "full fat" variants from Debian instead.

You might get errors of unconfigured packages, just chroot in and run '''''apt-get -f install''''' to finish up.. if there are warnings about proc, ignore them till you reboot into the rootfs and re-run '''''sudo apt-get -f install'''''.

== Chroot and Setup ==
Now we can just chroot in and setup as we see fit. 
'''''sudo chroot /tmp/emdebian''''' - again, you may have mounted your media elsewhere. 
'''''sudo apt-get update'''''

You can now just follow the Debian guide as above, with the added bonus of most packages will come from Grip and be pre-stripped of extra fluff. 
I would recommend to get as much stuff as possible downloaded in the initial multistrap however, as it will automatically clean stuff up for you.

= Debian On NAND =
First of all, 
'''''WARNING: DO NOT ATTEMPT THIS.''''' 
'''''NO, SERIOUSLY, DON'T! THIS IS UTTERLY HACKY AND IT IS ON YOUR OWN HEAD IF YOU MESS UP.''''' 

== Get a Debian Rootfs ==
Your NAND has about 475Mb for the rootfs to play with ( there are other partitions, remember! ), therefore Desktop Debian is a bit too large for our purposes - even 1.0.3's complete massacre still ended up too big by far; so we need to look at Emdebian, of which there are three flavours - grip, crush and baked. 
We'll be using Grip, so follow the guide above for at least getting a working system on SD before going anywhere near your NAND.

We can use compression to get your rootfs down by 40-50%, but I'd still be vary wary of a large rootfs!

If you're lazy, grab my pre-made Grip rootfs, which includes LXDE by default.

== Preparing the Rootfs ==
Boot into your rootfs for this, so we can ensure we're as up to date as we can be, then clean the apt cache, and then any crap we installed which we don't need any more, such as things which were installed as dependencies and the parent's been removed. 
'''''sudo apt-get update''''' 
'''''sudo apt-get upgrade''''' 
'''''sudo apt-get clean''''' 
'''''sudo apt-get autoclean''''' 

Additionally, you could wipe out the documentation ( if any ) and manually pull out unwanted packages. However, if you're pulling stuff out, you shouldn't have installed it in the first place! Go back to the start and do it again as punishment!

This post on the Ubuntu forums is particularly helpful: http://ubuntuforums.org/showthread.php?t=140920

Depending on your needs, you may also want to wipe out your home folder and reinstate it from /etc/skel 
You'll also want to wipe out tmp - '''''sudo rm -rf /tmp/*'''''

Now shut down and either place your SD card in your PC. You can do this on Pandora, but you will need a lot of space.

Copy your rootfs somewhere.. I suggest /tmp/pandora-debian 
'''''mkdir /tmp/pandora-debian''''' 
'''''sudo cp -p -r /media/my/sd/card/* /tmp/pandora-debian''''' - this will preserve Permissions and copy everything Recursively.

We need to edit the fstab so that it can boot properly, if you haven't done so already. 
'''''sudo nano /tmp/pandora-debian/etc/fstab'''''
# OpenPandora fstab.

rootfs / auto defaults,noatime 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
tmpfs /var/volatile tmpfs defaults 0 0
tmpfs /dev/shm tmpfs mode=0777 0 0
tmpfs /media/ram tmpfs defaults 0 0

This should look familiar, as it's effectively your stock fstab minus the boot partition ( we have a kernel in our rootfs, if you've followed the above guides... )

We should also get rid of the autoboot.txt or boot.txt; '''''sudo rm /tmp/pandora-debian/autoboot.txt'''''

== Creating the Image ==
You need mtd-utils in your Debian distro of choice. '''''sudo apt-get install mtd-utils'''''

Now, mkfs.ubifs can compress using either LZO ( by default ) or zlib and will get your rootfs about 40-50% smaller depending on what you choose. It's also possible to use a combination of both, which is what we will do later.. Of course, if your rootfs is full of pre-compressed stuff already, it's not really going to shrink a great deal. 
For a full run down on mkfs.ubifs and co, see here: http://www.linux-mtd.infradead.org/doc/ubifs.html

Download the flash kit: http://openpandora.org/firmware/pandora-flash-kit.zip and extract it to /tmp/flash. I suggest reading the README as well.

Now run these fun commands... what we're doing is we're making a ubifs image first, then making an md5 checksum. 
We're also favoring LZO compression meaning we're mixing zlib and LZO to get the best compression we can. 
'''''sudo mkfs.ubifs -r /tmp/pandora-debian -o rootfs.img -m 2048 -e 129024 -c 4042 -x favor_lzo -X 20''''' 
'''''md5sum rootfs.img > rootfs.md5'''''

'''STOP! If your rootfs.img is getting close to 480Mb, you might not want to try and flash it.. it may be fine, but I would recommend 450Mb as an absolute maximum.'''

== Flashing the Image ==
I shall repeat: 
'''''WARNING: DO NOT ATTEMPT THIS.''''' 
'''''NO, SERIOUSLY, DON'T! THIS IS UTTERLY HACKY AND IT IS ON YOUR OWN HEAD IF YOU MESS UP.''''' 

Stick the following on to a FAT32 formatted SD card: 
* '''boot.scr''' - from the flash kit.
* '''rootfs.img''' - the image you've just created.
* '''rootfs.md5''' - the checksum to the image.

Place it in slot 1 of your Pandora ( the left slot, ) reboot while holding the right trigger, select boot from SD, cross your fingers and pray to the Pandora Gods.

Once it's done.. reboot and see what mess you've made, assuming you get it to boot! 
If you haven't got it to boot, on your FAT32 flasher card, add an autoboot.txt with the following:
setenv bootargs ubi.mtd=4 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw vram=6272K omapfb.vram=0:3000K
ubi part boot && ubifsmount boot && ubifsload ${loadaddr} uImage && bootm ${loadaddr};

As this will let you see what's gone wrong... I had to do this a few times, as I buggered it up myself...

Congratulations, you now have Debian on NAND rather than Angstrom. 
Also, these instructions could easily be adapted to allow you to use any other distro that boots on Pandora.

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Storage card]]
[[Category:Booting]]

Hardware hacking

2012-05-05T13:28:00Z

Notaz: /* UART */

{{introNote|About custom hardware extensions, see also [[Kernel interface]]}}
==Official Hackers Manual==
There is a LOT of great information in this:
[http://www.openpandora.org/downloads/PANDORA_Hackers_manual_v101.pdf Pandora Hackers Manual v1.01 by MWeston]

==Pinouts==
Here's a list of pinouts for the various connectors and boards.

Here's a pic of the board, some of the pinouts can be seen on it. [http://pandorapress.net/files/2010/02/rev5.jpg]

==Ext Connector==
[[Image:Cable_connector pinout.png|thumb|TV cable connector]]
''What does it have?''
* UART2
* UART3
* TV out
* Stereo line out
* Stereo line in
* The UART lines can also be used as GPIO (six of them) and PWM lines (four of them).

''Where can we get the connectors from?''

* The connector appears to be a Tyco Electronics connector, part number 1717169-2
* The manufacturer does *not* stock these for engineering samples, and very few vendors carry them
* Community member [http://boards.openpandora.org/index.php?/user/157-wizardstan/ WizardStan] has ordered a bunch and is selling them at $2 a piece plus shipping from Canada, [http://boards.openpandora.org/index.php?/topic/2675-ext-connectors/ see here (thread)] or [http://pandorapress.net/2011/05/18/ext-connectors-have-arrived/ here (article)]

===How Do I Make a TV-Out Cable?===
* There are some useful tips in the [http://boards.openpandora.org/index.php?/topic/2675-ext-connectors/ EXT Connectors] thread.
* A guide explaining one way of creating the video cables can be found [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,23,465 here]
* MarkoeZ Has written a blog post about it [http://markoez.pirategames.co.uk/index.php/blog/pandora-ext-tv-out-explained/ here]

==Battery==
[[Image:Battery.jpg|thumb]]
* 3.7V
* Lithium polymer single cell battery
* 4000 mAH, 4 AH
* battery cover here: [http://www.openpandora.org/images/Battery2.jpg]
* reading out battery information: [[data provided by Battery and Power driver]]

==Internal connections==

===LCD===
* TD043MTEA1 [http://beyondinfinite.com/lcd/Library/Toppoly/TD043MTEA1.pdf datasheet]
* LTPS (8-bit parallel input for R, G and B, with separate horizontal and vertical sync)
* 3.3V?

===UART===
* UART2 and 3 are available via the EXT connector, and via internal solder pads on the latest revision
** UART2 appears to support hardware flow control with RTS/CTS lines
** On the 2.6.27 Kernel UART3 is /dev/ttyS0
** On 2.6.37 or later, UART2 is accessible through /dev/ttyO1, UART3 is on /dev/ttyO2

===GPIO===
* 6 are available on the EXT connector
* 7 are internal, 2 of which can be used as extra shoulder buttons
* 1 located on the LCD cable

===JTAG===
* Yes, 1.8V 10-pin (board label JTAG)

===I2C===
* One at 1.8V from the OMAP (board label I2C3-1V8)
* One at 2.8V (board label I2C3-2V8)

=== USB ===
* No internal USB ports

===Keypad backlight===
* ?

===Extra LEDs===
LED7 and LED8 can be added. You need to add FETs (Q17 and Q18) and resistors (R165, R166, R167 and R168)
See the official "Pandora Hacker Guide" from Michael Weston for more details and component values.

==Breakout Board==
[[Image:Breakoutboard.jpg|thumb|alt=Developer's breakout board|Developer's breakout board]]
This is the breakout board used by Pandora team members during development. Only a small number were made, and they are not available to the public. However a similar product (or gerber files) may be released in the future. A schematic for this board is available here: http://openpandora.ca/schematic/AV_Board_schematic.pdf

[[Category:Hardware]]
[[Category:Hacking]]

Kernel interface

2012-04-27T23:02:51Z

Notaz: nub modes

{{hint|For apps use higher level libraries/interfaces like SDL, Qt, X or similar for your own good (portability). It may be impossible to retain this layout on some major hardware revision, let's say Pandora 3000, and your program will break. Also this requires some level of Linux programming knowledge.}}

In case you need to write low level code (you can't/don't want to use high level libs like [[SDL]]), you can use [[kernel]] interface. This is the recommended way to access [[hardware]] (as opposed to [[GP2X]] style of accessing chip registers by mmap'ing /dev/mem), because in case hardware changes are needed in future, they could be handled by kernel and all programs would still work. It also should allow several programs to work at the same time and should be more stable.

==Input==
[[Buttons]], [[keypad]], [[touchscreen]] and [[nubs]] are all exposed through Linux event interface (EVDEV). All devices are represented by '''/dev/input/eventX''' files, which can be opened, read and queried (using ioctl calls). The reads can be synchronous (the read will only return when user does something, like presses the button), or asynchronous (the system will report what changed since the last time you asked).

{{warning
|Don't hardcode device filenames in your program!
}}

For example, currently /dev/input/event2 represents game buttons, but in future it may become touchscreen. Scan input device names instead, example:
<source lang="c">
for (i = 0; 1; i++)
{
sprintf(name, "/dev/input/event%i", i);
fd = open(name, O_RDONLY);
if (fd < 0) break; /* no more devices */
ioctl(fd, EVIOCGNAME(sizeof(name)), name);
if (strcmp(name, "gpio-keys") == 0)
return fd; /* found the buttons! */
close(fd); /* we don't need this device */
}
</source>

List of device names and events they send:
{|class="wikitable"
|-
!name
!description
!event.type
!event.code
!event.value
|-
|keypad
|keypad
|EV_KEY
|KEY_0...KEY_Z, KEY_BACKSPACE, KEY_LEFTSHIFT, KEY_SPACE, KEY_ENTER, KEY_COMMA, KEY_DOT, KEY_FN
|0 - released 1 - pressed 2 - autorepeat event
|-
|gpio-keys
|game buttons
|EV_KEY
|KEY_UP, KEY_DOWN, KEY_LEFT, KEY_RIGHT, KEY_MENU (Pandora button), KEY_LEFTALT (Start), KEY_LEFTCTRL (Select), KEY_END (Y/North), KEY_HOME (A/East), KEY_PAGEDOWN (X/South), KEY_END (B/West), KEY_RIGHTSHIFT (Shoulder L), KEY_RIGHTCTRL (Shoulder R), KEY_KPPLUS (Shoulder L2), KEY_KPMINUS (Shoulder R2), KEY_COFFEE (Hold)
|0 - released 1 - pressed
|-
|gpio-keys
|lid state
|EV_SW
|SW_LID
|0 - closing 1 - opening
|-
|touchscreen
|touchscreen
|EV_ABS
|ABS_X, ABS_Y, ABS_PRESSURE
|varies, use calibration data
|-
|nub0
|left nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up) 0 +256 (Right/Down)
|-
|nub1
|right nub
|EV_ABS
|ABS_X, ABS_Y
| -256 (Left/Up)) 0 +256 (Right/Down)
|}

Sample code: 
[http://beagleboard.googlecode.com/files/evtest.c evtest.c]
[http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-misc.git;a=blob;f=op_test_inputs.c;hb=HEAD op_test_inputs.c]

===Nubs===
Nubs have 3 modes that can be switched during runtime: absolute, mouse, mbuttons; this can be done by writing one of those 3 strings to /proc/pandora/nubX/mode . On mode change /dev/input/event* files belonging to nubs are recreated and must be reopened.

Warning: it is not guaranteed that input files will finish recreating after a write to /proc/pandora/nubX/mode finishes, it is application's responsibility to wait until those files are available.

===Touchscreen===
Event interface returns uncalibrated values directly from driver, so you need to use tslib or manage calibration yourself (using data from /etc/pointercal).

===X11===
When using the direct kernel api for input, it is also important to stop X processing the events as well. To do this you can create an X window to eat the events. There is also a utility that comes with the Pandora to do this:
<source lang="c">
op_runfbapp ./yourapp
</source>

==Sound==
Pandora uses [[ALSA]], but it has [[OSS]] emulation enabled too, so [[GP2X]] code should work.

==Video==
===Architecture===
Framebuffer device (/dev/fbX) is supported. There are 3 framebuffers available ('''/dev/fb0''', /dev/fb1 and /dev/fb2), which represent 3 graphics/video layers on [[OMAP3]] by default (but can be reconfigured). Only /dev/fb0 is enabled by default.

[[OMAP3]] display subsystem is controlled by a driver known as [[DSS2]], which has various controls available on /sys/devices/platform/omapdss/ (but they are not meant to be changed by programs, so they are root writable only). The driver exposes 3 layers (called overlays) and 2 displays. Overlays 1 and 2 can perform hardware scaling on the fly using 5-tap poly-phase filter, overlay0 can not. Displays 0 and 1 represent LCD and TV respectively. By default the 3 framebuffers (/dev/fbX) are redirected to 3 overlays, which all output to the LCD. This configuration is not meant to be changed by programs, only firmware should manage these.

===Basic usage===
====framebuffer interface====
Framebuffers can be accessed Linux fbdev interface:
<source lang="c">
fbdev = open("/dev/fb0", O_RDONLY);
buffer = mmap(0, 800*480*2, PROT_WRITE, MAP_SHARED, fbdev, 0);
</source>
(this is basic example, no error checks)

the returned pointer can be used to draw on the screen.

Be sure to #include <linux/fb.h> to get access to the FB device ioctl interface, and <sys/ioctl.h> for access to ioctl itself.

====double buffering====
This can be achieved using FBIOPAN_DISPLAY ioctl system call. For this you need to mmap framebuffer of double size
<source lang="c">
buffer1 = mmap(0, 800*480*2 * 2, PROT_WRITE, MAP_SHARED, fbdev, 0);
buffer2 = (char *)mem + 800*480*2;
</source>

Then to display buffer2 you would call:
<source lang="c">
struct fb_var_screeninfo fbvar;
ioctl(fbdev, FBIOGET_VSCREENINFO, &fbvar);
fbvar.yoffset = 480;
ioctl(fbdev, FBIOPAN_DISPLAY, &fbvar);
</source>
going back to buffer1 would be repeating above with fbvar.yoffset = 0. Tripple or quad buffering can be implemented using the same technique.

====vertical sync====
Linux has standard FBIO_WAITFORVSYNC for this:
<source lang="c">
int arg = 0;
ioctl(fbdev, FBIO_WAITFORVSYNC, &arg);
</source>
be sure to pass argument value 0 or it will not work.

Currently FBIO_WAITFORVSYNC is not defined in <linux/fb.h>, although this is in the process of modification. For now, define in the following manner:

<source lang="c">
#ifndef FBIO_WAITFORVSYNC
#define FBIO_WAITFORVSYNC _IOW('F', 0x20, __u32)
#endif
</source>

====hardware scaling====
Overlay1 (/dev/fb1) can be used to achieve hardware scaling. Technically overlay2 (fb2) can be used for this too, but it is planned to be used by the system for TV-out functionality, so don't use it. The overlay is configured using series of standard and OMAP specific ioctl calls, but the system ships with some tools to achieve this from scripts too. This way the framebuffer can be set up for some arbitrary size (say 320x240) and can output to LCD as 800x480 with hardware scaling.
Here is an example script:
<source lang="bash">
ofbset -fb /dev/fb1 -pos 0 0 -size 800 480 -mem 307200 -en 1
fbset -fb /dev/fb1 -g 320 240 320 480 16

./your_app_here

ofbset -fb /dev/fb1 -pos 0 0 -size 0 0 -mem 0 -en 0
</source>

What it does:
* allocates OMAP DSS layer, asks video output to be 800x480 at position 0,0 (could set it to 640x480 at 80,0 instead to get centered 2x scaling of 320x240). 307200 bytes of video memory are allocated for 2 320x240 16bpp screens (for doublebuffering).
* sets video mode to 320x240@16bpp, virtual resolution 320x480 for doublebuffering.
* runs your app
* cleans the video layer on exit

Now the program can act as if it works with 320x240 16bpp screen.

====LCD refresh rate====
The OS has a dedicated script which can change the LCD refresh rate. It must be ran with sudo:
<source lang="c">
sudo -n /usr/pandora/scripts/op_lcdrate.sh 50
</source>
From code, system() function can be used for this.

'''Note''': this doesn't mean your program has to run as root to use this (it never should!), just run the script as shown above.

===Hardware scaling filter control===
The hardware scaler in pandora uses poly-phase 5-tap 8-phase filter. It is described in 15.4.2.3.4 and 15.6.1.3 sections of TRM. There are 40 coefficients programmable for both horizontal and vertical resampling (vertical resampling might also use 3 taps/24 coefficients, it depends on available pixel clock).
====using predefined filters====
Just run 'sudo /usr/pandora/scripts/op_videofir.sh <name>', where name currently can be:
* default - the default filter from OMAP manual
* none - nearest neighbor
====using custom filters====
run 'sudo /usr/pandora/scripts/op_videofir.sh <basename>', where basename* files contains coefficient table. The script will look for <basename>_h, <basename>_v3 and <basename>_v5 files for 5-tap horizontal, 3-tap vertical and 5-tap vertical configurations respectively. Pass absolute or relative path for basename with './', like './something'. The coefficients should be in a form of table like described in TRM, for example:
<source lang="c">
----
0 0 128 0 0
-1 13 124 -8 0
-2 30 112 -11 -1
-5 51 95 -11 -2
0 -9 73 73 -9
-2 -11 95 51 -5
-1 -11 112 30 -2
0 -8 124 13 -1
</source>
For 3-tap table, first and last columns should contain zeros.

==LEDs and Display backlight==
The LEDs can be controlled via '''/sys/class/leds/''', and then a file [http://www.gp32x.com/board/index.php?s=&showtopic=45309&view=findpost&p=673593]:
* pandora::sd1
* pandora::sd2
* pandora::charger
* pandora::power
* pandora::bluetooth
* pandora::wifi
* pandora::keypad_bl
Backlight can be controlled via '''/sys/class/backlight/'''.

==Misc==
Some things can be controlled through files in /proc/pandora/:
* '''/proc/pandora/cpu_mhz_max''' - if [http://www.kernel.org/pub/linux/utils/kernel/cpufreq/cpufreq.html cpufreq] is enabled, sets maximum allowed cpu clock, if not, just sets CPU clock to value supplied (echo 600 > /proc/pandora/cpu_mhz_max). Might also just use cpufreq parameters themselves.
more to come..

[[Category:Development]]
[[Category:Kernel]]
[[Category:Hardware]]

Emulator List

2012-04-18T16:14:09Z

Notaz: fix wrong version

''These lists were last updated on 2011-10-08 to include the latest files from [http://apps.open-pandora.org/cgi-bin/viewarea.pl?Emulators Pandora Apps], the [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5 File Archive], the [http://repo.openpandora.org/?page=all&s=new Repo], and the [[Emulator list#Forums|community forums]]. For other software lists on the wiki, see [[Software projects]] and [[Games]].''

If different versions of an [[emulator]] were released, the listed "release date" is from the most recent one.

Please click on the little squares to sort by different categories.

To read a usage guide for several emulators, download [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,404 this guide].

==Released emulators==

Entry colors only denote compatibility and speed; interface and features are not taken into account.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Quality
!Description
|- style="background: #81BEF7"
|Perfect
|Emulators with a '''blue''' background, for all intents and purposes, work perfectly. Virtually every game runs at full speed, and ones that don't come close. No overclocking required. Practically no compatibility issues, with the possible exception of extremely obscure hardware tricks or addons.
|- style="background: #90FF90"
|Fantastic
|Emulators with a '''green''' background work very well. A lot of games run great at or close to 500Mhz, though some issues do exist. Little overclocking is required. Compatibility issues are minimum.
|- style="background: #F3F781"
|Decent
|Emulators with a '''yellow''' background have issues. Some games are playable, and a few do run full speed, but overclocking is typically needed. Compatibility issues may be considerable. This could also represent emulators with great compatibility, but low speed (or vice versa).
|- style="background: #F7BE81"
|Bad
|Emulators with an '''orange''' background do not run well. Few games are playable. Overclocking is mandatory. There may be lots of compatibility issues as well.
|- style="background: #F78181"
|Poor
|Emulators with a '''red''' background are worthless. No games are playable at 500Mhz, and you have to overclock very high to see a difference. Full speed is out of the question. Compatibility is likely nonexistent. This is test release territory.
|-
|N/A
|Emulators with a '''white''' background do not have enough information about them. Please try them out and add to this page!
|}


''If you have tried an emulator which has an uncoloured background, please add the appropriate background colour based on the legend to reflect the status of the emulator. You may add a statement in the notes if you feel that it's necessary.''

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Emulated System
! Project Name
! Release Date (YYYY-MM-DD)
! Download
! Authored or Ported By
! C1
! CS2
! Notes
|- style="background: #90FF90"
|Various{{HideableNotes| Atari Lynx, Bandai Wonderswan, GBA, GB/C, Sega Game Gear, Sega Master System, PC Engine/CD, NES, Virtual Boy, Neo Geo Pocket Colour}}
|Mednafen 0.9.17.r3
|2011-07-13
|[http://repo.openpandora.org/?page=detail&app=package.mednafen-pandora.r3 Repo]
|pder
|
|zip, [http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://www.gp32x.com/board/index.php?/topic/59533-mednafen-0-9-17-1-wip/page__gopid__950099&#entry950099 Discussion] GBA and VB don't run fullspeed.
|- style="background: #90FF90"
|Acorn RISC-PC
|[[pandrpcemu]] ('''beta''')
|2011-05-28
|[http://www.pokenet.co.uk/misc/files.pandora/pandrpcemu.pnd Download] [http://repo.openpandora.org/?page=detail&app=pandrpcemu Repo]
|hideki
|
|None
|[http://boards.openpandora.org/index.php?/topic/3762-pandrpcemu-beta-acorn-risc-pc/ Discussion] Also available natively (32-bit RO5) under [[Software projects#Unreleased software ("Projects Under Development")|Software projects]]
|- style="background: #90FF90"
|Amiga 500
|[[UAE4ALL]] 1.1.1.19 & 1.1.1.19a
|2011-05-15
|[http://repo.openpandora.org/?page=detail&app=uae4all Main version]
[http://repo.openpandora.org/?page=detail&app=uae4all_nubs Alternate version]
|Pickle, john4p, Notaz, tuki_cat, et al.
|[http://spreadsheets.google.com/pub?key=0AuBR5X_s_5_idG92ZVQ5cEs4ZEhYTm5sSjFIcl83U2c&hl=en&gid=0 GD]
|gzip
|"Alternate version" has working nubs but unstable video sync. [http://www.gp32x.com/board/index.php?/topic/54915-uae4all-additions/page__view__findpost__p__949095 Discussion] [http://www.gp32x.com/board/index.php?/topic/54915-uae4all-additions/page__view__findpost__p__945563 Readme (tutorial)]. {{HideableNotes|Since v1.1.1.19, conf files not compatible with prior versions.}}
|- style="background: #F3F781"
|Amiga 1200
|[[P-UAE]]
|2010-06-06
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/puae.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,86 Archive]
|Gnostic
|
|
|
|- style="background: #F3F781"
|Amiga
|[[pandeuae]] ('''beta''')
|2011-05-09
|[http://www.hidnet.org.uk/pandeuae.pnd Download]
|hideki
|
|
|[http://boards.openpandora.org/index.php?/topic/3350-euae-port/ Discussion]
|- style="background: #81BEF7"
|Amstrad CPC
|[[Pandora-CAP32]]
|2010-06-27
|[http://zx81.zx81.free.fr/public/pandora/cap32/pandora-cap32-v1.1.0-bin.zip Download] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,115 Archive]
|zx-81
|
|gzip
|[http://www.gp32x.com/board/index.php?/topic/54801-pandora-cap32-v1-1-0/ Discussion]
|- style="background: #90FF90"
|Apple II
|[[LinApple]] 1.3.5.0
|2011-09-13
|[http://repo.openpandora.org/?page=detail&app=linapple-jerryblade-042011 Repo]
|JerryBlade, CFWhitman
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59229-apple-emulator-for-pandora/page__view__findpost__p__957512 GP32X] [http://boards.openpandora.org/index.php?/topic/2490-apple-ii-emulator/ OP]
|- style="background: #90FF90"
|Arcade (laserdisc)
|[[Daphne]] v1.0.0.3
|2011-08-14
|[http://repo.openpandora.org/?page=detail&app=daphne-daphne-25097 Repo]
|mcobit
|
|[http://winff.org/html_new/ Bitrate]
|[http://boards.openpandora.org/index.php?/topic/4852-daphne-wip/ Discussion] {{HideableNotes|Use [http://winff.org/html_new/ WinFF] to re-encode your video files to a lower bitrate if necessary, as doing so will improve speed and shrink the file. Faster SD cards also improve speed greatly.}}
|- style="background: #F3F781"
|Arcade
|[[MAME]] v0.106
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/mame106.pnd.inf Apps] [http://repo.openpandora.org/?page=detail&app=mame.cosam.106 Repo]
|SteveM
|
|zip
|{{HideableNotes|Runs more games than MAME4ALL, but at a slower speed.}}
|- style="background: #90FF90"
|Arcade
|[[MAME4All]] v2.5b7
|2010-09-07
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,200 Archive] [http://repo.openpandora.org/?page=detail&app=mame4all.cosam.2.5-beta7 Repo]
|SteveM, Franxis
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56188-mame4all-beta/ Discussion]
|- style="background: #xxxxxx"
|Arcade
|SDLMAME v.110
|2010-06-30
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,106 Archive]
|?
|
|zip
|Use MAME4ALL instead, this is slow.
|- style="background: #xxxxxx"
|Atari 520
|PAtari v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.4 Download]
|cpasjuste
|
|
|
|-
|Atari 800
|Atari800
|2011-08-06
|[http://ompldr.org/vOXUxYQ/atari800.pnd.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60165-atari-800-emulator-almost-final/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #xxxxxx"
|Atari 8-Bit
|Pandora-Atari
|2010-08-04
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/atari-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,173 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/55724-pandora-atari-atari-8001305200-emulator-for-pandora-v110/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #90FF90"
|Atari Lynx
|[[Handy]]
|2010-06-18
|[http://repo.openpandora.org/?page=detail&app=handy.cosam.0.5.0.0 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54220-handy/ Discussion] {{HideableNotes|Do not turn on the FPS counter, or else the emulator will slow down dramatically.}}
|- style="background: #xxxxxx"
|Atari ST
|Hatari 1.0.3.2
|2011-08-02
|[http://repo.openpandora.org/?page=detail&app=hatari.skeezix.pkg Repo]
|Skeezix
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58088-hatari-atari-st-emu-140-released/page__view__findpost__p__934671 Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2010-05-07
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/Stella312a.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,53 Archive]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 2600
|Pandora-2600 ([[Stella]])
|2010-07-11
|[http://zx81.zx81.free.fr/public/pandora/2600/pandora-2600-v1.1.0-pnd.zip Download] [http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/2600-1.1.0.inf Apps]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54934-pandora-2600-atari-2600-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2011-08-03
|[http://ompldr.org/vOXF0dQ/stella.pnd Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60123-stella-atari-2600-beta-in-pnd/ Discussion]. {{HideableNotes|PAL games don't run.}}
|-
|Atari VCS 2600
|[[Stella]] 3.4.2.2
|2011-10-06
|[http://repo.openpandora.org/?page=detail&app=stella-svn Repo]
|Lomaxx
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 7800
|Pandora-7800 v1.1.0
|2010-07-11
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,146 Archive] [http://zx81.zx81.free.fr/public/pandora/7800/pandora-7800-v1.1.0-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/55189-pandora-7800-atari-7800-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Colecovision
|[[Colem]]
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem_alpha.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,70 Archive] [http://repo.openpandora.org/?page=detail&app=colem.skeezix Repo]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Colecovision
|[[Pandora Colem]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,129 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/60164-colem-port-of-zx81-slightly-modified/ Discussion for modified version (no PND)]
|- style="background: #90FF90"
|Commodore 64
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceX64.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,46 Archive]
|Pickle
|
|
|{{HideableNotes|Very good emulation, deactivate wrap mode in speed seetings if you suffer sound problems}}
|- style="background: #xxxxxx"
|Commodore (Other)
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceMisc.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,47 Archive]
|Pickle
|
|
|{{HideableNotes|Emulates the CBM2, C128, PET, Plus4, and VIC platforms.}}
|- style="background: #90FF90"
|GPH GP2X/Wiz
|[[Ginge]]
|2010-08-16
|[http://repo.openpandora.org/?page=detail&app=package.ginge.notaz Repo]
|Notaz
|
|None
|{{HideableNotes|Not really an emulator. [http://www.gp32x.com/board/index.php?/topic/55980-ginge/page__view__findpost__p__913442 DO NOT run from root]. To get rid of the default blur filter, use [http://www.gp32x.com/board/index.php?/topic/57179-pandora-emulators-vs-gp2xwiz-emulators/page__view__findpost__p__923471 this solution].}}
|- style="background: #xxxxxx"
|HP-48
|[[Pandora-X48]]
|2010-06-17
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,113,96 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/129-HP-48 Download]
|zx-81
|
|
|Emulates a calculator. [http://www.gp32x.com/board/index.php?/topic/54482-x48/ Discussion]
|- style="background: #xxxxxx"
|Macintosh 68K
|Basilisk II
|2010-12-15
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=512 Download] [http://www.mediafire.com/?ue5eyole855fyul 2]
|dgame
|
|
|[http://www.gp32x.com/board/index.php?/topic/56900-basilisk-ii-pnd-68k-macintosh-emulator/ Discussion]
|- style="background: #xxxxxx"
|Mattel Intellivision
|[[Jzintv]]
|2010-09-02
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/jzintv.inf Apps]
|WizardStan
|
|
|[http://www.gp32x.com/board/index.php?/topic/56426-jzintv/ Discussion]
|- style="background: #xxxxxx"
|MSX
|[[Pandora-MSX]]
|2010-06-26
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/msx-1.1.1.inf Apps]
|zx-81
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/54775-pandora-msx-v1-1-0/ Discussion] {{HideableNotes|Only disk images may be gzippped, and if they are, they cannot be written to.}}
|-
|NEC PC-9801
|[[Xnp2]]
|2011-05-01
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,393 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/xnp2.inf Apps] [http://www.mediafire.com/?57qer2aud0e8p9y Download]
|quews (port)
|
|
|[http://www.youtube.com/watch?v=Bd3a-duBfdU Video]
|- style="background: #xxxxxx"
|NEC PC Engine
|[[Pandora HuGo]]
|2010-06-28
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/hugo-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,117 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54833-hugo-pandora-v1-1-0/ Discussion]
|- style="background: #xxxxxx"
|NEC PC Engine
|Temper (alpha)
|2011-07-25
|[http://exophase.devzero.co.uk/temper.pnd Download]
|Exophase
|
|[http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://boards.openpandora.org/index.php?/topic/4621-temper-split-from-other-thread/ Discussion] Also supports the SuperGrafx.
|- style="background: #81BEF7"
|NES
|[[GPFCE-GP2X]]
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,224 Archive] [http://repo.openpandora.org/?page=detail&app=gpfcegp2x Repo]
|notaz
|
|zip
|{{HideableNotes|The GP2X version of GPFCE, packaged into a PND with Ginge.}}
|- style="background: #81BEF7"
|NES
|[[GPFCE]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,72 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/gpfce.inf Apps]
|Notaz, Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|zip
|{{HideableNotes|Sound works if you set the rate to 44000Hz in the options. Forces a 2xsai like filter.}}
|- style="background: #xxxxxx"
|NES
|[[nesemu]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,71 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/nesemu.inf Apps]
|Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|
|[http://code.google.com/p/nesemu/ Website] Seems to only run at 40fps.
|- style="background: #F3F781"
|NES
|[[Nestopia]]
|2011-08-01
|[http://ompldr.org/vOXB2Mg/nestopia_openpandora_streak.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60112-nestopia-for-openpandora-beta/ Discussion] {{HideableNotes|Emulator focus is accuracy. Very high compatibility at a cost of speed. Not a PND.}}
|- style="background: #F3F781"
|Nintendo 64
|[[Mupen64Plus]] 1.5.r20110615.2
|2011-06-16
|[http://repo.openpandora.org/?page=detail&app=mupen64plus Repo]
|Ari64, Adventus, JayFoxRox, sebt3, et al.
|[http://tinyurl.com/6ccuqmc GD]
|zip, 7z, bzip2
|[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__951543 Discussion] Compatibility list is mostly outdated. {{HideableNotes|To get good auto-frameskip, switch to gles2n64 0.0.5, set frame render rate 2, auto frameskip 1 -[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__946705]}}
|- style="background: #F78181"
|Nintendo DS
|[[Desmume]]
|2011-08-04
|[http://www.2shared.com/file/wxnc3MRT/desmume097.html Download]
[http://www.mediafire.com/?8gvvhqz3e2zkxzj 2]
|notaz
|
|
|[http://boards.openpandora.org/index.php?/topic/4744-nintendo-ds-emulator/page__view__findpost__p__82779 Discussion] Not meant for entertainment; was ported only to shut people up.
|- style="background: #F3F781"
|Nintendo GBA/GBC/GB
|[[VisualBoyAdvance]]
|2010-12-08
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/vba-1.7.2-0.inf Apps] [http://www.mediafire.com/?7qbxlnp0h2isokf Download]
|EvilDragon, SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/57808-visualboyadvance-v1-7-2-1/page__p__929521&#entry929521 Discussion]. Runs GB/C well; GBA is slow
|- style="background: #81BEF7"
|Nintendo GBA
|[[gpSP]]
|2011-09-08
|[http://repo.openpandora.org/?page=detail&app=package.gpsp.notaz Repo]
|Exophase, notaz
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60219-gba-emulator-that-you-can-adjust-the-screen-size/page__view__findpost__p__957136 GP32X] [http://boards.openpandora.org/index.php?/topic/5226-gpsp-for-pandora-from-notaz/ OP]. Zipped ROMs only. Now a native port with fullscreen scaling.
|- style="background: #90FF90"
|Nintendo GBA
|[[gpSP]] (Ginged)
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,199 Archive]
|Exophase, notaz
|
|zip
|[http://gpsp-dev.blogspot.com/ Website]. {{HideableNotes|Runs through [[Ginge]], only zipped ROMs. [http://www.gp32x.com/board/index.php?/topic/58722-im-looking-for-a-gba-emulator-without-blurry-upscaling/ No fullscreen scaling].}}
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnuBoy]] 1.0.5Svn
|2010-11-10
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,207 Archive] [http://repo.openpandora.org/?page=detail&app=sdlgnuboy Repo]
|Pickle, EvilDragon
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/56916-gnuboy-updated/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57436-gnuboy-v1-0-5-svn-released/ 2] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnGB]] ('''beta''')
|2010-10-04
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=482 Download] [http://www.mediafire.com/?7qbxlnp0h2isokf 2]
|dgame (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/56886-gngb-pnd-game-boy-and-game-boy-color-emulator/ Discussion]
|- style="background: #xxxxxx"
|Nintendo Pokémon mini
|[[Pokémini]] 0.4.4
|2011-04-13
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/pokemini.inf Apps] [http://www.mediafire.com/?05g9s8w780mt58g Download]
|Wally
|
|
|[http://boards.openpandora.org/index.php?/topic/2898-pokemini-emulator-pokemon-mini Discussion]
|- style="background: #xxxxxx"
|Oric-1/Atmos
|[[PandOricutron]]
|2010-06-16
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/PandOricutron_108.inf Apps]
|torpor
|
|
|[http://www.gp32x.com/board/index.php?/topic/54260-pandoricutron-1-0-8/ Discussion]
|- style="background: #xxxxxx"
|PDP-11
|[[SIMH PDP-11]]
|2010-05-28
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,83 Archive] [http://repo.openpandora.org/?page=detail&app=msimh.cosam.3.8.0.0 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|Philips Odyssey 2
|[[O2EM]] 1.18-1
|2010-08-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,186 Archive] [http://repo.openpandora.org/?page=detail&app=o2em Repo]
|Hitnrun, Daniel Boris
|
|
|
|-
|SAM Coupé
|[[SimCoupe]]
|2011-08-19
|[http://ompldr.org/vOXlsaw/simcoupe.pnd.zip Download]
|StreaK
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60220-simcoupe-a-sam-coupe-emulator-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4947-simcoupe-a-sam-coupe-emulator-beta/ OP]
|- style="background: #81BEF7"
|Sega Genesis, CD, 32X, Master System
|[[PicoDrive]] 1.80
|2010-09-19
|[http://repo.openpandora.org/?page=detail&app=package.picodrive.notaz Repo]
|Notaz
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56713-picodrive-1-80/ Discussion] ([http://www.gp32x.com/board/index.php?/topic/53899-picodrive-released/ old]). {{HideableNotes|Master System support is preliminary. Not all 32X games run.}}
|- style="background: #xxxxxx"
|Sega Master System & Game Gear
|[[Dega]] v1.16-4
|2010-08-15
|[http://repo.openpandora.org/?page=detail&app=dega.cosam.1.16.0.2 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54914-dega/ Discussion]{{HideableNotes|Press R+number to save, L+number to load, Pandora key to quit}}
|- style="background: #xxxxxx"
|Sega Master System
|PSMS v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.10 Download]
|cpasjuste
|
|
|
|- style="background: #F7BE81"
|Sega Saturn
|Yabause r2660
|2011-08-06
|[http://hotfile.com/dl/126054899/6ca83f7/yabause-r2660.pnd.html Download] [http://www.mediafire.com/?fmbn5ij2t3mucjh 2]
|Ari64
|[https://spreadsheets.google.com/spreadsheet/ccc?key=0Aq4SN3wYVIxgdHB4Z2hHcE9fQ3lTaTVMelEyZVBsVFE GD]
|
|[http://boards.openpandora.org/index.php?/topic/4583-yabause/ Discussion]
|- style="background: #90FF90"
|SNES
|[[SNES9X4P]] 1.39ff - v20111205-2
|2011-12-06
|[http://repo.openpandora.org/?page=detail&app=snes9x4p_ivanovic Repo]
|HideableNotes|Ivanovic, Skeezix, SiENcE (Dingoo)
|
|7z
|Dingoo Snes9x port. [http://www.gp32x.com/board/index.php?/topic/55378-snes9x4d4p-another-new-build-now-with-hi-res-and-new-rom-picker/page__view__findpost__p__958887] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|SNES
|SNES9X v0.2
|2009-04-03
|[http://www.pandorasource.de/download.php?view.7 Download]
|cpasjuste (port)
|
|
|
|- style="background: #xxxxxx"
|SNES
|[[PocketSNES]] ('''beta''') 0.1
|2010-08-08
|[http://www.rangelreale.com/pandora/pocketsnes_hack_0.1.pnd Download]
|Hitnrun (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/55796-pocketsnes-hack/ Discussion]
|- style="background: #81BEF7"
|SNK Neo Geo
|[[GnGeo]] 0.8.3
|2011-04-20
|[http://repo.openpandora.org/?page=detail&app=gngeopnd-pepone Repo]
|Pepone, Manolis
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59207-gngeo-0-8-2/page__view__findpost__p__946739 GP32X] [http://boards.openpandora.org/index.php?/topic/2936-gngeo-083/ OP]
|- style="background: #xxxxxx"
|SNK Neo Geo
|NeoGeo SDL
|2009-04-03
|[http://www.pandorasource.de/download.php?view.13 Download]
|Cpasjuste
|
|
|
|-
|SNK NeoGeo Pocket
|NeoPop
|2010-07-15
|[http://www.pdroms.de/files/1969/ Download]
|Cpasjuste
|
|
|[http://www.gp32x.com/board/index.php?/topic/58848-neopop-ngpc-emulator-released/ Discussion]
|- style="background: #xxxxxx"
|SNK Neo Geo Pocket
|[[Race]]
|2010-06-20
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/race10.inf Apps]
|Hooka
|
|
|[http://www.gp32x.com/board/index.php?/topic/54187-race-a-neo-geo-pocket-color-emulator Discussion]
|- style="background: #F7BE81"
|Sony Playstation
|[[PSX4Pandora]]
|2010-11-16
|[http://www.zodttd.com/downloads/psx4pandora10b5.pnd Download]
|ZodTTD
|[http://spreadsheets.google.com/pub?key=0AkBB6e4g1lGtdFVwODhsQzdlWVdrMTRKdDFXa1laZ2c&hl=en_GB&output=html GD]
|
|[http://www.gp32x.com/board/index.php?/topic/57522-psx4pandora-1-0b5/ Discussion]
|- style="background: #90FF90"
|Sony Playstation
|[[PCSX-ReARMed]] r14
|2012-03-04
|[http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz Repo] [http://notaz.gp2x.de/releases/pcsxr/pcsx_rearmed_r14.pnd Download]
|notaz
|[https://spreadsheets.google.com/ccc?key=0ArSWWAWRjErldHZVZlFxY0tBVnRRNXM5U3ZqWFNuN0E&hl=en#gid=0 GD]
|[http://boards.openpandora.org/index.php?/topic/4046-tutorial-how-to-save-space-on-ps1-games-without-ripping-video-or-music/ pbp]
|[http://boards.openpandora.org/index.php?/topic/6546-pcsx-rearmed-r13-with-a-new-gpu/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57973-pcsx-rearmed/page__view__findpost__p__955679 old thread]
|-
|Thomson TO8D
|[[TO8_PND]]
|2011-11-15
|[http://repo.openpandora.org/?page=detail&app=TO8D_PND Repo]
|SladeCraven
|
|None
|Emulates the Thomson TO8/TO8D computer. [http://boards.openpandora.org/index.php?/topic/6076-thomson-to8-emulator-beta-version-040/page__fromsearch__1 Discussion]
|-
|TI89/TI89 Titanium / TI92/TI92+ / V200PLT
|[[TiEmu]]
|2011-09-10
|[http://repo.openpandora.org/?page=detail&app=tiemu-6232 Repo]
|Kazuki
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TI-99
|Pandora-TI99 ([[TI99Sim]])
|2010-07-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,164 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/147-TI99 Download]
|zx-81
|
|
|
|-
|TI-92
|[[XTiger]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ti92-1.1.0.inf Apps]
|zx-81
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TRS-80
|[[SDLTRS]]
|2011-08-03
|[http://www.mediafire.com/download.php?72etxpjqaosa11b Download]
|Blue Protoman
|
|
|I give no support to this! This is a hackjob port!
|- style="background: #81BEF7"
|Vectrex
|[[Pandora-Vectrex]] v1.1.1
|2011-03-06
|[http://zx81.zx81.free.fr/public/pandora/vectrex/pandora-vectrex-v1.1.1-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58846-pandora-vectrex-vectrex-emulator-for-pandora-v110/page__view__findpost__p__942010 Discussion] Download game overlays [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,355 here].
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox]] v0.74svn
|2010-11-09
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,54 Archive]
|Pickle
|[[DOSBox compatibility list|W]]
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/57424-dosbox/ GP32Xa] [http://www.gp32x.com/board/index.php?/topic/53942-post-your-dosbox-successes-here/ GP32Xb] [http://boards.openpandora.org/index.php?/topic/2346-dosbox-room-for-optimization/ OPa] [http://boards.openpandora.org/index.php?/topic/2063-dosbox/ OPb]. [http://www.dosbox.com/comp_list.php General compatibility list]
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox EX]]
|2011-08-16
|[http://ompldr.org/vOXhhMA/dosbox_ex.pnd.zip Download]
|StreaK
|
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60175-dosbox-ex-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4855-dosbox-ex/ OP]
|- style="background: #F3F781"

|x86 PC
|[[Qemu for Pandora]]
|2012-03-02
|[http://www.openpandora.org/rebirth/qemu.pnd Download]
|IngoReis, mcobit
|
|None
|Discussion: [http://boards.openpandora.org/index.php?/topic/7004-qemu-for-pandora-for-rebirth-competition OP-Boards]
|- style="background: #F3F781"
|x86 Windows 3.1 r2, r1
|[[WinBox]] ('''beta''')
|2010-12-15
|[http://repo.openpandora.org/?page=detail&app=winbox-1 Repo] [http://urjaman.dyndns.info/winbox_r2.pnd Download]
|urjaman
|
|None
|[http://www.gp32x.com/board/index.php?/topic/54985-win-3-1-via-dosbox-at-native-resolution/page__view__findpost__p__887198 Discussion] {{HideableNotes|Modified DOSBox to run Windows 3.1 at Pandora's native resolution}}
|-
|ZX-80 & ZX-81
|sz81
|2011-08-19
|[http://ompldr.org/vOXk0eA/sz81.pnd.zip Download]
|StreaK
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Fuse]]
|2010-06-24
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/fuse-0.9.0.inf Apps] [http://repo.openpandora.org/?page=detail&app=fuse.cosam.0.10.0.2 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Zx Pandy]] v3.2.1.4
|2011-04-12
|[http://repo.openpandora.org/?page=detail&app=zx_pandy.dave18.001 Repo]
|Dave18
|
|
|[http://www.gp32x.com/board/index.php?/topic/58536-zx-pandy-released/ Discussion]
|}

1 "C" is short for compatibility list.
FT = Forum Topic
GD = Google Docs
W = Wiki page

2 "CS" is short for "Compression Support". The entries denote the formats that can be used to save space on the games. A blank entry doesn't mean "none", it means there's not enough info! Please add more if you can!

==Unreleased emulators==
This section includes both emulators that are actively being worked on, as well as ones that are or may be abandoned. The latter are included for historical purposes.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
!Emulated System
!Project Name
!Last Update
!Status
!Author/Port Author
!Notes
|-
|Amstrad PCW
|Joyce / Anne emu
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/page__view__findpost__p__85612 2011-08-18]
|Working build
|StreaK
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/ Discussion] Looking for help for testing from someone familiar with the platform.
|-
|Sega Dreamcast
|NullDC
|[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 2011-03-28]
|On hold
|Zezu / drkIIraziel
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910] drkIIraziel says he will have time to work on it "[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 after April 10]"
|-
|Nintendo SNES
|[[PandaSNES]]
|[http://www.gp32x.com/board/index.php?/topic/43213-any-snes-fans-in-the-house/page__view__findpost__p__631020 2008-07-29]
|Abandoned
|Squidge
|[http://www.gp32x.com/board/index.php?showtopic=43213] Probably discontinued; Squidge has not been heard from for a long time.
|-
|Sony Playstation Portable
|Pandora-PSP
|[http://jannikvogel.de/2011 2011-01]
|Abandoned
|[[User:JayFoxRox|JayFoxRox]]
|[http://www.gp32x.com/board/index.php?showtopic=47270] Probably discontinued; JayFoxRox has since left the community.
|-
|}

==External links==
*[http://sebt3.openpandora.org/pnd/ Releases by sebt3]
*[http://www.hermocom.com/en/downloads/openpandora/ Releases by Hermocom]
*[http://rebirthofxeen.com/files/pandora/ Releases by WizardStan]
*[http://www.stuckiegamez.co.uk/apps/pandora/ Releases by StuckieGamez]

===Forums===
The following community forums are checked when updating this page:
*From GP32X: [http://www.gp32x.com/board/index.php?/forum/63-news-zone-pandora/ News Zone], [http://www.gp32x.com/board/index.php?/forum/71-beta-testing-pandora/ Beta Testing] and [http://www.gp32x.com/board/index.php?/forum/64-developers-corner-pandora/ Developer's Corner]
*From OP: [http://boards.openpandora.org/index.php?/forum/26-software-news/ Software News] and [http://boards.openpandora.org/index.php?/forum/10-beta-testing/ Beta Testing]
*From GP2X.de: [http://forum.gp2x.de/viewforum.php?f=24 News] and [http://forum.gp2x.de/viewforum.php?f=59 Betatest]

[[Category:Emulators]]
[[Category:Software]]
[[Category:List]]

Emulator List

2012-04-18T16:04:40Z

Notaz: update rearmed

''These lists were last updated on 2011-10-08 to include the latest files from [http://apps.open-pandora.org/cgi-bin/viewarea.pl?Emulators Pandora Apps], the [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5 File Archive], the [http://repo.openpandora.org/?page=all&s=new Repo], and the [[Emulator list#Forums|community forums]]. For other software lists on the wiki, see [[Software projects]] and [[Games]].''

If different versions of an [[emulator]] were released, the listed "release date" is from the most recent one.

Please click on the little squares to sort by different categories.

To read a usage guide for several emulators, download [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,404 this guide].

==Released emulators==

Entry colors only denote compatibility and speed; interface and features are not taken into account.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Quality
!Description
|- style="background: #81BEF7"
|Perfect
|Emulators with a '''blue''' background, for all intents and purposes, work perfectly. Virtually every game runs at full speed, and ones that don't come close. No overclocking required. Practically no compatibility issues, with the possible exception of extremely obscure hardware tricks or addons.
|- style="background: #90FF90"
|Fantastic
|Emulators with a '''green''' background work very well. A lot of games run great at or close to 500Mhz, though some issues do exist. Little overclocking is required. Compatibility issues are minimum.
|- style="background: #F3F781"
|Decent
|Emulators with a '''yellow''' background have issues. Some games are playable, and a few do run full speed, but overclocking is typically needed. Compatibility issues may be considerable. This could also represent emulators with great compatibility, but low speed (or vice versa).
|- style="background: #F7BE81"
|Bad
|Emulators with an '''orange''' background do not run well. Few games are playable. Overclocking is mandatory. There may be lots of compatibility issues as well.
|- style="background: #F78181"
|Poor
|Emulators with a '''red''' background are worthless. No games are playable at 500Mhz, and you have to overclock very high to see a difference. Full speed is out of the question. Compatibility is likely nonexistent. This is test release territory.
|-
|N/A
|Emulators with a '''white''' background do not have enough information about them. Please try them out and add to this page!
|}


''If you have tried an emulator which has an uncoloured background, please add the appropriate background colour based on the legend to reflect the status of the emulator. You may add a statement in the notes if you feel that it's necessary.''

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Emulated System
! Project Name
! Release Date (YYYY-MM-DD)
! Download
! Authored or Ported By
! C1
! CS2
! Notes
|- style="background: #90FF90"
|Various{{HideableNotes| Atari Lynx, Bandai Wonderswan, GBA, GB/C, Sega Game Gear, Sega Master System, PC Engine/CD, NES, Virtual Boy, Neo Geo Pocket Colour}}
|Mednafen 0.9.17.r3
|2011-07-13
|[http://repo.openpandora.org/?page=detail&app=package.mednafen-pandora.r3 Repo]
|pder
|
|zip, [http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://www.gp32x.com/board/index.php?/topic/59533-mednafen-0-9-17-1-wip/page__gopid__950099&#entry950099 Discussion] GBA and VB don't run fullspeed.
|- style="background: #90FF90"
|Acorn RISC-PC
|[[pandrpcemu]] ('''beta''')
|2011-05-28
|[http://www.pokenet.co.uk/misc/files.pandora/pandrpcemu.pnd Download] [http://repo.openpandora.org/?page=detail&app=pandrpcemu Repo]
|hideki
|
|None
|[http://boards.openpandora.org/index.php?/topic/3762-pandrpcemu-beta-acorn-risc-pc/ Discussion] Also available natively (32-bit RO5) under [[Software projects#Unreleased software ("Projects Under Development")|Software projects]]
|- style="background: #90FF90"
|Amiga 500
|[[UAE4ALL]] 1.1.1.19 & 1.1.1.19a
|2011-05-15
|[http://repo.openpandora.org/?page=detail&app=uae4all Main version]
[http://repo.openpandora.org/?page=detail&app=uae4all_nubs Alternate version]
|Pickle, john4p, Notaz, tuki_cat, et al.
|[http://spreadsheets.google.com/pub?key=0AuBR5X_s_5_idG92ZVQ5cEs4ZEhYTm5sSjFIcl83U2c&hl=en&gid=0 GD]
|gzip
|"Alternate version" has working nubs but unstable video sync. [http://www.gp32x.com/board/index.php?/topic/54915-uae4all-additions/page__view__findpost__p__949095 Discussion] [http://www.gp32x.com/board/index.php?/topic/54915-uae4all-additions/page__view__findpost__p__945563 Readme (tutorial)]. {{HideableNotes|Since v1.1.1.19, conf files not compatible with prior versions.}}
|- style="background: #F3F781"
|Amiga 1200
|[[P-UAE]]
|2010-06-06
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/puae.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,86 Archive]
|Gnostic
|
|
|
|- style="background: #F3F781"
|Amiga
|[[pandeuae]] ('''beta''')
|2011-05-09
|[http://www.hidnet.org.uk/pandeuae.pnd Download]
|hideki
|
|
|[http://boards.openpandora.org/index.php?/topic/3350-euae-port/ Discussion]
|- style="background: #81BEF7"
|Amstrad CPC
|[[Pandora-CAP32]]
|2010-06-27
|[http://zx81.zx81.free.fr/public/pandora/cap32/pandora-cap32-v1.1.0-bin.zip Download] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,115 Archive]
|zx-81
|
|gzip
|[http://www.gp32x.com/board/index.php?/topic/54801-pandora-cap32-v1-1-0/ Discussion]
|- style="background: #90FF90"
|Apple II
|[[LinApple]] 1.3.5.0
|2011-09-13
|[http://repo.openpandora.org/?page=detail&app=linapple-jerryblade-042011 Repo]
|JerryBlade, CFWhitman
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59229-apple-emulator-for-pandora/page__view__findpost__p__957512 GP32X] [http://boards.openpandora.org/index.php?/topic/2490-apple-ii-emulator/ OP]
|- style="background: #90FF90"
|Arcade (laserdisc)
|[[Daphne]] v1.0.0.3
|2011-08-14
|[http://repo.openpandora.org/?page=detail&app=daphne-daphne-25097 Repo]
|mcobit
|
|[http://winff.org/html_new/ Bitrate]
|[http://boards.openpandora.org/index.php?/topic/4852-daphne-wip/ Discussion] {{HideableNotes|Use [http://winff.org/html_new/ WinFF] to re-encode your video files to a lower bitrate if necessary, as doing so will improve speed and shrink the file. Faster SD cards also improve speed greatly.}}
|- style="background: #F3F781"
|Arcade
|[[MAME]] v0.106
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/mame106.pnd.inf Apps] [http://repo.openpandora.org/?page=detail&app=mame.cosam.106 Repo]
|SteveM
|
|zip
|{{HideableNotes|Runs more games than MAME4ALL, but at a slower speed.}}
|- style="background: #90FF90"
|Arcade
|[[MAME4All]] v2.5b7
|2010-09-07
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,200 Archive] [http://repo.openpandora.org/?page=detail&app=mame4all.cosam.2.5-beta7 Repo]
|SteveM, Franxis
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56188-mame4all-beta/ Discussion]
|- style="background: #xxxxxx"
|Arcade
|SDLMAME v.110
|2010-06-30
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,73,106 Archive]
|?
|
|zip
|Use MAME4ALL instead, this is slow.
|- style="background: #xxxxxx"
|Atari 520
|PAtari v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.4 Download]
|cpasjuste
|
|
|
|-
|Atari 800
|Atari800
|2011-08-06
|[http://ompldr.org/vOXUxYQ/atari800.pnd.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60165-atari-800-emulator-almost-final/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #xxxxxx"
|Atari 8-Bit
|Pandora-Atari
|2010-08-04
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/atari-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,173 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/55724-pandora-atari-atari-8001305200-emulator-for-pandora-v110/ Discussion] {{HideableNotes|Emulates the 800, 800XL, 130XE, and 5200 platforms.}}
|- style="background: #90FF90"
|Atari Lynx
|[[Handy]]
|2010-06-18
|[http://repo.openpandora.org/?page=detail&app=handy.cosam.0.5.0.0 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54220-handy/ Discussion] {{HideableNotes|Do not turn on the FPS counter, or else the emulator will slow down dramatically.}}
|- style="background: #xxxxxx"
|Atari ST
|Hatari 1.0.3.2
|2011-08-02
|[http://repo.openpandora.org/?page=detail&app=hatari.skeezix.pkg Repo]
|Skeezix
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58088-hatari-atari-st-emu-140-released/page__view__findpost__p__934671 Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2010-05-07
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/Stella312a.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,53 Archive]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 2600
|Pandora-2600 ([[Stella]])
|2010-07-11
|[http://zx81.zx81.free.fr/public/pandora/2600/pandora-2600-v1.1.0-pnd.zip Download] [http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/2600-1.1.0.inf Apps]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54934-pandora-2600-atari-2600-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Atari VCS 2600
|[[Stella]]
|2011-08-03
|[http://ompldr.org/vOXF0dQ/stella.pnd Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60123-stella-atari-2600-beta-in-pnd/ Discussion]. {{HideableNotes|PAL games don't run.}}
|-
|Atari VCS 2600
|[[Stella]] 3.4.2.2
|2011-10-06
|[http://repo.openpandora.org/?page=detail&app=stella-svn Repo]
|Lomaxx
|
|
|
|- style="background: #xxxxxx"
|Atari VCS 7800
|Pandora-7800 v1.1.0
|2010-07-11
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,146 Archive] [http://zx81.zx81.free.fr/public/pandora/7800/pandora-7800-v1.1.0-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/55189-pandora-7800-atari-7800-emulator-for-pandora-v110/ Discussion]
|- style="background: #xxxxxx"
|Colecovision
|[[Colem]]
|2010-05-29
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem_alpha.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,70 Archive] [http://repo.openpandora.org/?page=detail&app=colem.skeezix Repo]
|Skeezix
|
|
|
|- style="background: #xxxxxx"
|Colecovision
|[[Pandora Colem]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/colem-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,129 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/60164-colem-port-of-zx81-slightly-modified/ Discussion for modified version (no PND)]
|- style="background: #90FF90"
|Commodore 64
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceX64.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,46 Archive]
|Pickle
|
|
|{{HideableNotes|Very good emulation, deactivate wrap mode in speed seetings if you suffer sound problems}}
|- style="background: #xxxxxx"
|Commodore (Other)
|[[Vice]]
|2010-03-25
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ViceMisc.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,47 Archive]
|Pickle
|
|
|{{HideableNotes|Emulates the CBM2, C128, PET, Plus4, and VIC platforms.}}
|- style="background: #90FF90"
|GPH GP2X/Wiz
|[[Ginge]]
|2010-08-16
|[http://repo.openpandora.org/?page=detail&app=package.ginge.notaz Repo]
|Notaz
|
|None
|{{HideableNotes|Not really an emulator. [http://www.gp32x.com/board/index.php?/topic/55980-ginge/page__view__findpost__p__913442 DO NOT run from root]. To get rid of the default blur filter, use [http://www.gp32x.com/board/index.php?/topic/57179-pandora-emulators-vs-gp2xwiz-emulators/page__view__findpost__p__923471 this solution].}}
|- style="background: #xxxxxx"
|HP-48
|[[Pandora-X48]]
|2010-06-17
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,113,96 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/129-HP-48 Download]
|zx-81
|
|
|Emulates a calculator. [http://www.gp32x.com/board/index.php?/topic/54482-x48/ Discussion]
|- style="background: #xxxxxx"
|Macintosh 68K
|Basilisk II
|2010-12-15
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=512 Download] [http://www.mediafire.com/?ue5eyole855fyul 2]
|dgame
|
|
|[http://www.gp32x.com/board/index.php?/topic/56900-basilisk-ii-pnd-68k-macintosh-emulator/ Discussion]
|- style="background: #xxxxxx"
|Mattel Intellivision
|[[Jzintv]]
|2010-09-02
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/jzintv.inf Apps]
|WizardStan
|
|
|[http://www.gp32x.com/board/index.php?/topic/56426-jzintv/ Discussion]
|- style="background: #xxxxxx"
|MSX
|[[Pandora-MSX]]
|2010-06-26
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/msx-1.1.1.inf Apps]
|zx-81
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/54775-pandora-msx-v1-1-0/ Discussion] {{HideableNotes|Only disk images may be gzippped, and if they are, they cannot be written to.}}
|-
|NEC PC-9801
|[[Xnp2]]
|2011-05-01
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,393 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/xnp2.inf Apps] [http://www.mediafire.com/?57qer2aud0e8p9y Download]
|quews (port)
|
|
|[http://www.youtube.com/watch?v=Bd3a-duBfdU Video]
|- style="background: #xxxxxx"
|NEC PC Engine
|[[Pandora HuGo]]
|2010-06-28
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/hugo-1.1.0.inf Apps] [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,117 Archive]
|zx-81
|
|
|[http://www.gp32x.com/board/index.php?/topic/54833-hugo-pandora-v1-1-0/ Discussion]
|- style="background: #xxxxxx"
|NEC PC Engine
|Temper (alpha)
|2011-07-25
|[http://exophase.devzero.co.uk/temper.pnd Download]
|Exophase
|
|[http://boards.openpandora.org/index.php?/topic/4047-tutorial-how-to-save-space-on-turbo-cdpc-engine-cd-games/ ogg]
|[http://boards.openpandora.org/index.php?/topic/4621-temper-split-from-other-thread/ Discussion] Also supports the SuperGrafx.
|- style="background: #81BEF7"
|NES
|[[GPFCE-GP2X]]
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,224 Archive] [http://repo.openpandora.org/?page=detail&app=gpfcegp2x Repo]
|notaz
|
|zip
|{{HideableNotes|The GP2X version of GPFCE, packaged into a PND with Ginge.}}
|- style="background: #81BEF7"
|NES
|[[GPFCE]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,72 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/gpfce.inf Apps]
|Notaz, Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|zip
|{{HideableNotes|Sound works if you set the rate to 44000Hz in the options. Forces a 2xsai like filter.}}
|- style="background: #xxxxxx"
|NES
|[[nesemu]]
|2010-05-29
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,71 Archive] [http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/nesemu.inf Apps]
|Pickle
|[[Compat:Emulator_Compatibility_-_NES | W]]
|
|[http://code.google.com/p/nesemu/ Website] Seems to only run at 40fps.
|- style="background: #F3F781"
|NES
|[[Nestopia]]
|2011-08-01
|[http://ompldr.org/vOXB2Mg/nestopia_openpandora_streak.zip Download]
|StreaK
|
|
|[http://www.gp32x.com/board/index.php?/topic/60112-nestopia-for-openpandora-beta/ Discussion] {{HideableNotes|Emulator focus is accuracy. Very high compatibility at a cost of speed. Not a PND.}}
|- style="background: #F3F781"
|Nintendo 64
|[[Mupen64Plus]] 1.5.r20110615.2
|2011-06-16
|[http://repo.openpandora.org/?page=detail&app=mupen64plus Repo]
|Ari64, Adventus, JayFoxRox, sebt3, et al.
|[http://tinyurl.com/6ccuqmc GD]
|zip, 7z, bzip2
|[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__951543 Discussion] Compatibility list is mostly outdated. {{HideableNotes|To get good auto-frameskip, switch to gles2n64 0.0.5, set frame render rate 2, auto frameskip 1 -[http://www.gp32x.com/board/index.php?/topic/53683-mupen64plus/page__view__findpost__p__946705]}}
|- style="background: #F78181"
|Nintendo DS
|[[Desmume]]
|2011-08-04
|[http://www.2shared.com/file/wxnc3MRT/desmume097.html Download]
[http://www.mediafire.com/?8gvvhqz3e2zkxzj 2]
|notaz
|
|
|[http://boards.openpandora.org/index.php?/topic/4744-nintendo-ds-emulator/page__view__findpost__p__82779 Discussion] Not meant for entertainment; was ported only to shut people up.
|- style="background: #F3F781"
|Nintendo GBA/GBC/GB
|[[VisualBoyAdvance]]
|2010-12-08
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/vba-1.7.2-0.inf Apps] [http://www.mediafire.com/?7qbxlnp0h2isokf Download]
|EvilDragon, SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/57808-visualboyadvance-v1-7-2-1/page__p__929521&#entry929521 Discussion]. Runs GB/C well; GBA is slow
|- style="background: #81BEF7"
|Nintendo GBA
|[[gpSP]]
|2011-09-08
|[http://repo.openpandora.org/?page=detail&app=package.gpsp.notaz Repo]
|Exophase, notaz
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60219-gba-emulator-that-you-can-adjust-the-screen-size/page__view__findpost__p__957136 GP32X] [http://boards.openpandora.org/index.php?/topic/5226-gpsp-for-pandora-from-notaz/ OP]. Zipped ROMs only. Now a native port with fullscreen scaling.
|- style="background: #90FF90"
|Nintendo GBA
|[[gpSP]] (Ginged)
|2010-10-13
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,199 Archive]
|Exophase, notaz
|
|zip
|[http://gpsp-dev.blogspot.com/ Website]. {{HideableNotes|Runs through [[Ginge]], only zipped ROMs. [http://www.gp32x.com/board/index.php?/topic/58722-im-looking-for-a-gba-emulator-without-blurry-upscaling/ No fullscreen scaling].}}
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnuBoy]] 1.0.5Svn
|2010-11-10
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,207 Archive] [http://repo.openpandora.org/?page=detail&app=sdlgnuboy Repo]
|Pickle, EvilDragon
|
|zip, gzip
|[http://www.gp32x.com/board/index.php?/topic/56916-gnuboy-updated/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57436-gnuboy-v1-0-5-svn-released/ 2] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|Nintendo GB/GBC
|[[GnGB]] ('''beta''')
|2010-10-04
|[http://www.gp32x.com/board/index.php?app=core&module=attach&section=attach&attach_id=482 Download] [http://www.mediafire.com/?7qbxlnp0h2isokf 2]
|dgame (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/56886-gngb-pnd-game-boy-and-game-boy-color-emulator/ Discussion]
|- style="background: #xxxxxx"
|Nintendo Pokémon mini
|[[Pokémini]] 0.4.4
|2011-04-13
|[http://apps.openpandora.org/cgi-bin/viewapp.pl?/Emulator/pokemini.inf Apps] [http://www.mediafire.com/?05g9s8w780mt58g Download]
|Wally
|
|
|[http://boards.openpandora.org/index.php?/topic/2898-pokemini-emulator-pokemon-mini Discussion]
|- style="background: #xxxxxx"
|Oric-1/Atmos
|[[PandOricutron]]
|2010-06-16
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/PandOricutron_108.inf Apps]
|torpor
|
|
|[http://www.gp32x.com/board/index.php?/topic/54260-pandoricutron-1-0-8/ Discussion]
|- style="background: #xxxxxx"
|PDP-11
|[[SIMH PDP-11]]
|2010-05-28
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,83 Archive] [http://repo.openpandora.org/?page=detail&app=msimh.cosam.3.8.0.0 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|Philips Odyssey 2
|[[O2EM]] 1.18-1
|2010-08-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,71,186 Archive] [http://repo.openpandora.org/?page=detail&app=o2em Repo]
|Hitnrun, Daniel Boris
|
|
|
|-
|SAM Coupé
|[[SimCoupe]]
|2011-08-19
|[http://ompldr.org/vOXlsaw/simcoupe.pnd.zip Download]
|StreaK
|
|
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60220-simcoupe-a-sam-coupe-emulator-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4947-simcoupe-a-sam-coupe-emulator-beta/ OP]
|- style="background: #81BEF7"
|Sega Genesis, CD, 32X, Master System
|[[PicoDrive]] 1.80
|2010-09-19
|[http://repo.openpandora.org/?page=detail&app=package.picodrive.notaz Repo]
|Notaz
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/56713-picodrive-1-80/ Discussion] ([http://www.gp32x.com/board/index.php?/topic/53899-picodrive-released/ old]). {{HideableNotes|Master System support is preliminary. Not all 32X games run.}}
|- style="background: #xxxxxx"
|Sega Master System & Game Gear
|[[Dega]] v1.16-4
|2010-08-15
|[http://repo.openpandora.org/?page=detail&app=dega.cosam.1.16.0.2 Repo]
|SteveM
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/54914-dega/ Discussion]{{HideableNotes|Press R+number to save, L+number to load, Pandora key to quit}}
|- style="background: #xxxxxx"
|Sega Master System
|PSMS v0.1
|2009-04-03
|[http://www.pandorasource.de/download.php?view.10 Download]
|cpasjuste
|
|
|
|- style="background: #F7BE81"
|Sega Saturn
|Yabause r2660
|2011-08-06
|[http://hotfile.com/dl/126054899/6ca83f7/yabause-r2660.pnd.html Download] [http://www.mediafire.com/?fmbn5ij2t3mucjh 2]
|Ari64
|[https://spreadsheets.google.com/spreadsheet/ccc?key=0Aq4SN3wYVIxgdHB4Z2hHcE9fQ3lTaTVMelEyZVBsVFE GD]
|
|[http://boards.openpandora.org/index.php?/topic/4583-yabause/ Discussion]
|- style="background: #90FF90"
|SNES
|[[SNES9X4P]] 1.39ff - v20111205-2
|2011-12-06
|[http://repo.openpandora.org/?page=detail&app=snes9x4p_ivanovic Repo]
|HideableNotes|Ivanovic, Skeezix, SiENcE (Dingoo)
|
|7z
|Dingoo Snes9x port. [http://www.gp32x.com/board/index.php?/topic/55378-snes9x4d4p-another-new-build-now-with-hi-res-and-new-rom-picker/page__view__findpost__p__958887] uses [[PickleLauncher]]
|- style="background: #xxxxxx"
|SNES
|SNES9X v0.2
|2009-04-03
|[http://www.pandorasource.de/download.php?view.7 Download]
|cpasjuste (port)
|
|
|
|- style="background: #xxxxxx"
|SNES
|[[PocketSNES]] ('''beta''') 0.1
|2010-08-08
|[http://www.rangelreale.com/pandora/pocketsnes_hack_0.1.pnd Download]
|Hitnrun (port)
|
|
|[http://www.gp32x.com/board/index.php?/topic/55796-pocketsnes-hack/ Discussion]
|- style="background: #81BEF7"
|SNK Neo Geo
|[[GnGeo]] 0.8.3
|2011-04-20
|[http://repo.openpandora.org/?page=detail&app=gngeopnd-pepone Repo]
|Pepone, Manolis
|
|zip
|Discussion: [http://www.gp32x.com/board/index.php?/topic/59207-gngeo-0-8-2/page__view__findpost__p__946739 GP32X] [http://boards.openpandora.org/index.php?/topic/2936-gngeo-083/ OP]
|- style="background: #xxxxxx"
|SNK Neo Geo
|NeoGeo SDL
|2009-04-03
|[http://www.pandorasource.de/download.php?view.13 Download]
|Cpasjuste
|
|
|
|-
|SNK NeoGeo Pocket
|NeoPop
|2010-07-15
|[http://www.pdroms.de/files/1969/ Download]
|Cpasjuste
|
|
|[http://www.gp32x.com/board/index.php?/topic/58848-neopop-ngpc-emulator-released/ Discussion]
|- style="background: #xxxxxx"
|SNK Neo Geo Pocket
|[[Race]]
|2010-06-20
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/race10.inf Apps]
|Hooka
|
|
|[http://www.gp32x.com/board/index.php?/topic/54187-race-a-neo-geo-pocket-color-emulator Discussion]
|- style="background: #F7BE81"
|Sony Playstation
|[[PSX4Pandora]]
|2010-11-16
|[http://www.zodttd.com/downloads/psx4pandora10b5.pnd Download]
|ZodTTD
|[http://spreadsheets.google.com/pub?key=0AkBB6e4g1lGtdFVwODhsQzdlWVdrMTRKdDFXa1laZ2c&hl=en_GB&output=html GD]
|
|[http://www.gp32x.com/board/index.php?/topic/57522-psx4pandora-1-0b5/ Discussion]
|- style="background: #90FF90"
|Sony Playstation
|[[PCSX-ReARMed]] r13
|2012-03-04
|[http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz Repo] [http://notaz.gp2x.de/releases/pcsxr/pcsx_rearmed_r13.pnd Download]
|notaz
|[https://spreadsheets.google.com/ccc?key=0ArSWWAWRjErldHZVZlFxY0tBVnRRNXM5U3ZqWFNuN0E&hl=en#gid=0 GD]
|[http://boards.openpandora.org/index.php?/topic/4046-tutorial-how-to-save-space-on-ps1-games-without-ripping-video-or-music/ pbp]
|[http://boards.openpandora.org/index.php?/topic/6546-pcsx-rearmed-r13-with-a-new-gpu/ Discussion] [http://www.gp32x.com/board/index.php?/topic/57973-pcsx-rearmed/page__view__findpost__p__955679 old thread]
|-
|Thomson TO8D
|[[TO8_PND]]
|2011-11-15
|[http://repo.openpandora.org/?page=detail&app=TO8D_PND Repo]
|SladeCraven
|
|None
|Emulates the Thomson TO8/TO8D computer. [http://boards.openpandora.org/index.php?/topic/6076-thomson-to8-emulator-beta-version-040/page__fromsearch__1 Discussion]
|-
|TI89/TI89 Titanium / TI92/TI92+ / V200PLT
|[[TiEmu]]
|2011-09-10
|[http://repo.openpandora.org/?page=detail&app=tiemu-6232 Repo]
|Kazuki
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TI-99
|Pandora-TI99 ([[TI99Sim]])
|2010-07-21
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,164 Archive] [http://zx81.zx81.free.fr/serendipity/index.php?/categories/147-TI99 Download]
|zx-81
|
|
|
|-
|TI-92
|[[XTiger]]
|2010-06-30
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/ti92-1.1.0.inf Apps]
|zx-81
|
|
|Emulates a calculator.
|- style="background: #xxxxxx"
|TRS-80
|[[SDLTRS]]
|2011-08-03
|[http://www.mediafire.com/download.php?72etxpjqaosa11b Download]
|Blue Protoman
|
|
|I give no support to this! This is a hackjob port!
|- style="background: #81BEF7"
|Vectrex
|[[Pandora-Vectrex]] v1.1.1
|2011-03-06
|[http://zx81.zx81.free.fr/public/pandora/vectrex/pandora-vectrex-v1.1.1-pnd.zip Download]
|zx-81
|
|zip
|[http://www.gp32x.com/board/index.php?/topic/58846-pandora-vectrex-vectrex-emulator-for-pandora-v110/page__view__findpost__p__942010 Discussion] Download game overlays [http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,5,355 here].
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox]] v0.74svn
|2010-11-09
|[http://dl.openhandhelds.org/cgi-bin/pandora.cgi?0,0,0,0,72,54 Archive]
|Pickle
|[[DOSBox compatibility list|W]]
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/57424-dosbox/ GP32Xa] [http://www.gp32x.com/board/index.php?/topic/53942-post-your-dosbox-successes-here/ GP32Xb] [http://boards.openpandora.org/index.php?/topic/2346-dosbox-room-for-optimization/ OPa] [http://boards.openpandora.org/index.php?/topic/2063-dosbox/ OPb]. [http://www.dosbox.com/comp_list.php General compatibility list]
|- style="background: #F3F781"
|x86 DOS
|[[DOSBox EX]]
|2011-08-16
|[http://ompldr.org/vOXhhMA/dosbox_ex.pnd.zip Download]
|StreaK
|
|None
|Discussion: [http://www.gp32x.com/board/index.php?/topic/60175-dosbox-ex-beta/ GP32X] [http://boards.openpandora.org/index.php?/topic/4855-dosbox-ex/ OP]
|- style="background: #F3F781"

|x86 PC
|[[Qemu for Pandora]]
|2012-03-02
|[http://www.openpandora.org/rebirth/qemu.pnd Download]
|IngoReis, mcobit
|
|None
|Discussion: [http://boards.openpandora.org/index.php?/topic/7004-qemu-for-pandora-for-rebirth-competition OP-Boards]
|- style="background: #F3F781"
|x86 Windows 3.1 r2, r1
|[[WinBox]] ('''beta''')
|2010-12-15
|[http://repo.openpandora.org/?page=detail&app=winbox-1 Repo] [http://urjaman.dyndns.info/winbox_r2.pnd Download]
|urjaman
|
|None
|[http://www.gp32x.com/board/index.php?/topic/54985-win-3-1-via-dosbox-at-native-resolution/page__view__findpost__p__887198 Discussion] {{HideableNotes|Modified DOSBox to run Windows 3.1 at Pandora's native resolution}}
|-
|ZX-80 & ZX-81
|sz81
|2011-08-19
|[http://ompldr.org/vOXk0eA/sz81.pnd.zip Download]
|StreaK
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Fuse]]
|2010-06-24
|[http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/fuse-0.9.0.inf Apps] [http://repo.openpandora.org/?page=detail&app=fuse.cosam.0.10.0.2 Repo]
|SteveM
|
|
|
|- style="background: #xxxxxx"
|ZX Spectrum
|[[Zx Pandy]] v3.2.1.4
|2011-04-12
|[http://repo.openpandora.org/?page=detail&app=zx_pandy.dave18.001 Repo]
|Dave18
|
|
|[http://www.gp32x.com/board/index.php?/topic/58536-zx-pandy-released/ Discussion]
|}

1 "C" is short for compatibility list.
FT = Forum Topic
GD = Google Docs
W = Wiki page

2 "CS" is short for "Compression Support". The entries denote the formats that can be used to save space on the games. A blank entry doesn't mean "none", it means there's not enough info! Please add more if you can!

==Unreleased emulators==
This section includes both emulators that are actively being worked on, as well as ones that are or may be abandoned. The latter are included for historical purposes.

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
!Emulated System
!Project Name
!Last Update
!Status
!Author/Port Author
!Notes
|-
|Amstrad PCW
|Joyce / Anne emu
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/page__view__findpost__p__85612 2011-08-18]
|Working build
|StreaK
|[http://boards.openpandora.org/index.php?/topic/4939-any-amstrad-pcw-lovers-in-da-house/ Discussion] Looking for help for testing from someone familiar with the platform.
|-
|Sega Dreamcast
|NullDC
|[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 2011-03-28]
|On hold
|Zezu / drkIIraziel
|[http://www.gp32x.com/board/index.php?s=&showtopic=47065&view=findpost&p=709910] drkIIraziel says he will have time to work on it "[http://www.gp32x.com/board/index.php?/topic/57821-dreamcast/page__view__findpost__p__944843 after April 10]"
|-
|Nintendo SNES
|[[PandaSNES]]
|[http://www.gp32x.com/board/index.php?/topic/43213-any-snes-fans-in-the-house/page__view__findpost__p__631020 2008-07-29]
|Abandoned
|Squidge
|[http://www.gp32x.com/board/index.php?showtopic=43213] Probably discontinued; Squidge has not been heard from for a long time.
|-
|Sony Playstation Portable
|Pandora-PSP
|[http://jannikvogel.de/2011 2011-01]
|Abandoned
|[[User:JayFoxRox|JayFoxRox]]
|[http://www.gp32x.com/board/index.php?showtopic=47270] Probably discontinued; JayFoxRox has since left the community.
|-
|}

==External links==
*[http://sebt3.openpandora.org/pnd/ Releases by sebt3]
*[http://www.hermocom.com/en/downloads/openpandora/ Releases by Hermocom]
*[http://rebirthofxeen.com/files/pandora/ Releases by WizardStan]
*[http://www.stuckiegamez.co.uk/apps/pandora/ Releases by StuckieGamez]

===Forums===
The following community forums are checked when updating this page:
*From GP32X: [http://www.gp32x.com/board/index.php?/forum/63-news-zone-pandora/ News Zone], [http://www.gp32x.com/board/index.php?/forum/71-beta-testing-pandora/ Beta Testing] and [http://www.gp32x.com/board/index.php?/forum/64-developers-corner-pandora/ Developer's Corner]
*From OP: [http://boards.openpandora.org/index.php?/forum/26-software-news/ Software News] and [http://boards.openpandora.org/index.php?/forum/10-beta-testing/ Beta Testing]
*From GP2X.de: [http://forum.gp2x.de/viewforum.php?f=24 News] and [http://forum.gp2x.de/viewforum.php?f=59 Betatest]

[[Category:Emulators]]
[[Category:Software]]
[[Category:List]]

Configuring ext signals

2011-07-20T21:18:13Z

Notaz: new page about software side of ext port

=Pin functions (mux)=
Currently this needs recompiling u-boot, but some easier control is planned.

By default UART2 pins are set up as GPIOs, and UART3 as an UART.

=Power supply=
Currently requires patching bootloaders (xload and u-boot).

This is connected to VAUX3 supply on PMIC, with these programmable voltages (200mA max):
1.5V, 1.8V, 2.5V, 2.8V and 3.0V, with 2.8V as default.

'''warning''': at the time of this writing, both bootloaders (xload and u-boot) set this to 2.8V, so don't rely on this providing other voltages during reboot until you patch both bootloaders.

=GPIOs=
Can be controlled using GPIO sysfs class device, as described in beagleboard tutorials [http://bbfordummies.blogspot.com/2009/07/1.html here].

=UART3=
By default, kernel messages are directed there and a terminal with a shell is attached. The port runs at 115200 8N1 baud rate.
==Disabling kernel messages==
To disable kernel mesages, you need to edit kernel boot arguments. Probably easiest way to do it is to create autoboot.txt and place on root directory of a card in slot1 with this content:
<source lang="bash">
setenv bootargs ubi.mtd=4 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw rootflags=bulk_read
</source>
Alternatives are using u-boot environment (configure through USB or UART3 serial before system boots up) or patching and reflashing u-boot itself.
==Disabling attached terminal==
For this you need to edit /etc/inittab on pandora rootfs and comment out this line:
<source lang="bash">
#S:2345:respawn:/sbin/getty 115200 ttyS0
</source>