Pandora Wiki - User contributions [en]

GLESGAE

2012-07-01T05:21:25Z

Wtachi: Undo revision 10583 by Apple (talk)

= 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.<br />
These will be written when I have time.. the uncreated ones below being an indicator of what's to come.<br />
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.<br />
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.<br />
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.<br />
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.<br />
This involved writing a custom renderer for GLES1 and then onto GLES2.<br />
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?<br />
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.<br />
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.<br />
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.<br />
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.<br />
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.<br />
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.<br />
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;<br />
* 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.<br />
Same for if you have a preferred development environment already.. if it works for you, there's no point changing it.<br />
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.<br />
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.<br />

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.<br />
Stick it in your left slot.<br />
Open up a terminal.<br />
You'll need to manually unmount it before going near it with cfdisk to repartition.<br />
'''''sudo umount /dev/mmcblk0p1''''' -- and possibly p2, p3, p# depending on how many partitions it has. Generally, it'll only have the one.<br />
'''''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.<br />
Press up and down to move the selector if need be to remove the rest of them if you've more than one.<br />
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. )<br />
Press Left to highlight '''[ Write ]''' and press return. Type "yes" and hit return to confirm the changes, then '''[ Quit ]'''<br />
You could have added swap if you wanted.. it's up to you really.<br />

Now we have to format it.<br />
'''''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...<br />
'''''cd /media/mmcblk0p1'''''<br />
'''''sudo su''''' -- we'll need to be root for this, as we'll have no permission by default to touch this card.<br />
'''''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!<br />
'''''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.<br />
'''''rm pandora-rootfs.tar.bz2'''''

We want the system to autoboot this when the card is inserted, so let's create autoboot.txt<br />
'''''nano autoboot.txt'''''<br />
Fill it with the following:<br />
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.<br />
Open up a terminal<br />
'''''sudo opkg update'''''<br />
'''''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.<br />
'''''mkdir Projects'''''<br />
'''''cd Projects'''''<br />
'''''nano main.cpp'''''<br />
#include <cstdio>

int main(void)
{
printf("Hello World!\n");

return 0;
}

'''''g++ -o main main.cpp'''''<br />
'''''./main''''' <br />

''' 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.<br />
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]]

Combining OpenGL ES 1.1 and SDL to create a window on the Pandora

2012-07-01T05:20:54Z

Wtachi: Undo revision 10645 by Apple (talk)

There are two options for combining GLES and SDL:

= 1: Grab the modified version of SDL =

There is a special [[SDL]] source code for pandora with [[OpenGL ES]] capability
available here : http://github.com/Cpasjuste

The screen initialisation is now easy as this : SDL_SetVideoMode(800, 480, 16, SDL_OPENGLES)

An [[SDL]]/[[GLES]] exemple is also available on the git repository.

= 2: Use EGL Directly (with SDL 1.2) =

Sometimes its not best to use the modified version of SDl (when working on cross platform games). Instead you can use [[EGL]] to create the GLES graphics context for you.
The following functions do just that.

Steps:
# Make sure you call InitOpenGL() straight after creating the window (SDL_SetVideoMode()).
# When using EGL you should not pass in the SDL_OPENGL flag to SDL_SetVideoMode(). SDL_HWSurface and SDL_SWSurface should do.
# You will notice '#ifdef GLES1' around much of the EGL code. Simply define GLES1 in your preprocessor (-DGLES1 on the command line of gcc if i recall correctly?) to use GLES. Without the define SDL will be set up for standard OpenGL (I left it in as its useful for cross platform dev).
# Once you have finished with the window and just before terminating it call TerminateOpenGL() to clean up.

NOTE - If you call SDL_SetVideoMode more than once you will probably need to terminate and reset the context (TerminateOpenGL(); SDL_SetVideoMode(); InitOpenGL();)

// OpenGLInit.c
<source lang="c">

#ifdef GLES1
#include <EGL/egl.h>
#include <GLES/gl.h>
#include <SDL/SDL_syswm.h>
#else
#include <GL/gl.h>
#include <SDL/SDL.h>
#endif

#include "OpenGLInit.h"

#ifdef GLES1
EGLDisplay g_eglDisplay = 0;
EGLConfig g_eglConfig = 0;
EGLContext g_eglContext = 0;
EGLSurface g_eglSurface = 0;
Display *g_x11Display = NULL;
#endif

// consts
#define COLOURDEPTH_RED_SIZE 5
#define COLOURDEPTH_GREEN_SIZE 6
#define COLOURDEPTH_BLUE_SIZE 5
#define COLOURDEPTH_DEPTH_SIZE 16

#ifdef GLES1
static const EGLint g_configAttribs[] ={
EGL_RED_SIZE, COLOURDEPTH_RED_SIZE,
EGL_GREEN_SIZE, COLOURDEPTH_GREEN_SIZE,
EGL_BLUE_SIZE, COLOURDEPTH_BLUE_SIZE,
EGL_DEPTH_SIZE, COLOURDEPTH_DEPTH_SIZE,
EGL_SURFACE_TYPE, EGL_WINDOW_BIT,
EGL_RENDERABLE_TYPE, EGL_OPENGL_ES_BIT,
EGL_BIND_TO_TEXTURE_RGBA, EGL_TRUE,
EGL_NONE
};
#endif

/*===========================================================
Initialise opengl settings. Call straight after SDL_SetVideoMode()
===========================================================*/

int InitOpenGL()
{
#ifdef GLES1
// use EGL to initialise GLES
g_x11Display = XOpenDisplay(NULL);

if (!g_x11Display)
{
fprintf(stderr, "ERROR: unable to get display!n");
return 0;
}

g_eglDisplay = eglGetDisplay((EGLNativeDisplayType)g_x11Display);
if (g_eglDisplay == EGL_NO_DISPLAY)
{
printf("Unable to initialise EGL display.");
return 0;
}

// Initialise egl
if (!eglInitialize(g_eglDisplay, NULL, NULL))
{
printf("Unable to initialise EGL display.");
return 0;
}

// Find a matching config
EGLint numConfigsOut = 0;
if (eglChooseConfig(g_eglDisplay, g_configAttribs, &g_eglConfig, 1, &numConfigsOut) != EGL_TRUE || numConfigsOut == 0)
{
fprintf(stderr, "Unable to find appropriate EGL config.");
return 0;
}

// Get the SDL window handle
SDL_SysWMinfo sysInfo; //Will hold our Window information
SDL_VERSION(&sysInfo.version); //Set SDL version
if(SDL_GetWMInfo(&sysInfo) <= 0)
{
printf("Unable to get window handle");
return 0;
}

g_eglSurface = eglCreateWindowSurface(g_eglDisplay, g_eglConfig, (EGLNativeWindowType)sysInfo.info.x11.window, 0);
if ( g_eglSurface == EGL_NO_SURFACE)
{
printf("Unable to create EGL surface!");
return 0;
}

// Bind GLES and create the context
eglBindAPI(EGL_OPENGL_ES_API);
EGLint contextParams[] = {EGL_CONTEXT_CLIENT_VERSION, 1, EGL_NONE}; // Use GLES version 1.x
g_eglContext = eglCreateContext(g_eglDisplay, g_eglConfig, NULL, NULL);
if (g_eglContext == EGL_NO_CONTEXT)
{
printf("Unable to create GLES context!");
return 0;
}

if (eglMakeCurrent(g_eglDisplay, g_eglSurface, g_eglSurface, g_eglContext) == EGL_FALSE)
{
printf("Unable to make GLES context current");
return 0;
}

#else

SDL_GL_SetAttribute(SDL_GL_RED_SIZE, COLOURDEPTH_RED_SIZE);
SDL_GL_SetAttribute(SDL_GL_GREEN_SIZE, COLOURDEPTH_GREEN_SIZE);
SDL_GL_SetAttribute(SDL_GL_BLUE_SIZE, COLOURDEPTH_BLUE_SIZE);
SDL_GL_SetAttribute(SDL_GL_DEPTH_SIZE, COLOURDEPTH_DEPTH_SIZE);

#endif

return 1;
}

/*======================================================
* Kill off any opengl specific details
====================================================*/
void TerminateOpenGL()
{
#ifdef GLES1
eglMakeCurrent(g_eglDisplay, NULL, NULL, EGL_NO_CONTEXT);
eglDestroySurface(g_eglDisplay, g_eglSurface);
eglDestroyContext(g_eglDisplay, g_eglContext);
g_eglSurface = 0;
g_eglContext = 0;
g_eglConfig = 0;
eglTerminate(g_eglDisplay);
g_eglDisplay = 0;
XCloseDisplay(g_x11Display);
g_x11Display = NULL;
#endif
}

int SwapBuffers()
{
#ifdef GLES1
eglSwapBuffers(g_eglDisplay, g_eglSurface);
#else
SDL_GL_SwapBuffers();
#endif
}
</source>

[[Category:Development]]
[[Category:Tutorials]]
[[Category:OpenGL ES]]

SD compatibility list

2012-05-24T01:01:40Z

Wtachi: Add Samsung 32GB MicroSDHC (MB-MSBGA)

This is a compatibility list for SD, SDHC and SDXC cards. The cards listed in '''green''' work with any file system. The cards listed in '''yellow''' work well only with one file system (this still means they can be used on the Pandora). The cards listed in '''red''' do not work well with any file system. Although it is not covered on this list, the Pandora can also read NTFS-formatted SD cards if the [http://www.open-pandora.org/downloads/CodecPack.pnd Community Codec Pack] is installed.

Note: always measure read speed by opening a terminal window and typing this command:
* the first inserted SD Card: '''dd if=/dev/mmcblk0 of=/dev/null bs=4MiB count=100'''
* the second inserted SD Card: '''dd if=/dev/mmcblk1 of=/dev/null bs=4MiB count=100'''

Note: The first inserted SD Card will always be /dev/mmcblk0, regardless if you put it into the second or first SD Card slot, whereas the second will be /dev/mmcblk1

If you can afford '''''destroying''''' all your data, you can test write speed. But be careful, you will need to create a new partition table, afterwards! You can use [http://www.gp32x.com/board/index.php?/topic/56915-gparted/ Gparted] to make new partition table.
* the first inserted SD Card: # '''dd if=/dev/zero of=/dev/mmcblk0 bs=4MiB count=100'''
* the second inserted SD Card: # '''dd if=/dev/zero of=/dev/mmcblk1 bs=4MiB count=100'''

By default, the first partition starts at block 8192 (4096KB) for 32GB cards, and block 32768 (16384KB) for 64GB cards. 64GB cards may need to be [[formatting SD cards|reformatted]] before use.

{|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"
! Card size in GB
! Card class
! Full name
! URL
! fat32 is working?
! ext2/3/4 are working?
! read speed MB/sec
! write speed MB/sec
! actual capacity (1024byte blocks)
! Notes
|-
| 32
| 10
| Centon 32GB Class 10 SDHC
| [http://www.microcenter.com/single_product_results.phtml?product_id=0335228]
| yes
| ?
| 17.3
| 23.9
| ?
| ok {{HideableNotes|so far, first few hours of use}}
|- style="background: #90Ff90"
| 1
| n/a
| Kingston 1GB (blue)
| [http://www.newegg.com/Product/Product.aspx?Item=N82E16820160032]
| yes
| yes
| 12.5
| ?
| 1006080
| ok
|-
| 8
| 4
| Kingston 8GB Class 4 (black)
|
| not long-term tested yet
| not long-term tested yet
| 17.1
| 4.8
| ?
| From Craig's shop, so must be ok ;)
|- style="background: #FF9090"
| 16
| 4
| Kingston 16 GB Class 4 SDHC
| [http://www.amazon.com/Kingston-Class-Memory-SD4-16GB/dp/B0013AV9TW]
| no
| no
| 15
| 9.5
| 15663104
| {{HideableNotes|Bad controller chip, fails in the same manner as the 32GB card.}}
|- style="background: #FF9090"
| 32
| 4
| Kingston 32 GB Class 4 SDHC
| [http://www.amazon.com/Kingston-Class-Memory-SD4-32GB/dp/B001C9P5TO]
| no
| no
| 16
| 9.5
| 31539200
| {{HideableNotes|Defective flash controller randomly loses writes regardless of filesystem. When attempting to write, blocks sometimes get erased but not written.}}
|- style="background: #F3F781"
| 32
| 10
| Kingston 32GB (red) Class 10
| [http://www.newegg.com/Product/Product.aspx?Item=N82E16820139146]
| yes
| no
| 15.2
| ?
| ?
| {{HideableNotes|doesn't have badblocks, seems that "Flash Translation Layer" is not suitable for ext filesystems}}
|- style="background: #90FF90"
| 32
| 4
| Lexar Multi-Use 32GB
| [http://www.amazon.com/Lexar-Flash-memory-card-Class/dp/B0040J1ET8]
| yes
| yes
| 16.1
| 14.4
| 31267840
| {{HideableNotes|Much faster than would be expected for a class 4 card. Usual warning about high-speed cards being susceptible to power supply glitches applies.}}
|- style="background: #F3F781"
| 32
| 10
| Lexar Premium Series 32GB 100x
| [http://www.amazon.com/Lexar-Secure-Digital-Premium-Memory/dp/B003PJ657K/ref=sr_1_11?s=electronics&ie=UTF8&qid=1321986834&sr=1-11]
| yes
| no
| 16.7
| 12.0
| ?
| Worst ext2 support ever. Copying fine, a LOT of I/O errors at first boot. Literally unusable. Fat32 seems perfectly supported.
|- style="background: #90FF90"
| 64
| 10
| Lexar Professional 64GB 133x
| [http://www.amazon.com/Lexar-Professional-Flash-memory-Memory/dp/B004QWRZWY]
| yes
| yes
| 19.6
| 15.1
| 62536704
| {{HideableNotes|R/W speed in the pandora is limited to 16.1/11.3 MB/sec. High power consumption, may fail under load.}}[http://boards.openpandora.org/index.php?/topic/2556-32gb-sdhc-card-problems/page__st__40]
|- style="background: #90FF90"
| 128
| 10
| Lexar Professional 128GB 133x SDXC
| [http://www.bhphotovideo.com/c/product/756124-REG/Lexar_LSD128CRBNA133_128GB_Professional_SDXC_Card.html]
| yes
| yes
| 17.2
| 11.8
| 122.97GiB
| {{HideableNotes|Speeds listed are IN a Pandora.}}[http://boards.openpandora.org/index.php?/topic/7682-128gb-lexar-sdxc-card-benchmarks/]
|- style="background: #90FF90"
| 16
| 6
| Maxflash 16GB Class 6 SDHC
| [http://www.max-flash.eu/en/products/SDHC%20Card.html]
| ?
| yes
| 14.4
| ?
| 16186368
| Works fine
|- style="background: #90FF90"
| 32
| 10
| Patriot LX 32GB SDHC Class 10 (PSF32GSDHC10)
| [http://www.bestdirect.ca/products/227442/Patriot/PSF32GSDHC10/] [http://www.amazon.ca/gp/product/B002TABU5I/]
| yes
| no/yes
| 18.1
| 12.6
| ?
| {{HideableNotes|Formatting EXT2 and then running fsck right after finds errors. Seems to work well with fat32 /// Entry 2 from another user: Works great with ext2. No errors or issues.}}
|- style="background: #90Ff90"
| 4
| 10
| Pretec 4GB, Class 10, 233x (white/green)
| [http://pamatove-karty.heureka.sk/pretec-sdhc-4gb-class-10/]
| yes
| yes (mostly)
| 14.0
| ?
| 3883008
| {{HideableNotes|I had very few fsck problems, and after several tries running fsck, they eventually got corrected. It looks very similar to that broken 32GB pretec. Except that this one almost works good.}}
|- style="background: #F3F781"
| 32
| 10
| Pretec 32GB Class 10, 233x (white/green)
| [http://www.prva.sk/detail/pretec-sdhc-32gb-class-10/kk296d49525.aspx]
| yes
| no
| 14.1
| 12.4
| ?
| {{HideableNotes|doesn't have badblocks, seems that "Flash Translation Layer" is not suitable for ext filesystems}}
|- style="background: #F3F781"
| 32
| 10
| PNY 32GB (P-SDHC32G10)
| [http://www.amazon.com/PNY-SDHC-Flash-Memory-P-SDH32G10-EFS2/dp/B004LQYV5E]
| yes
| ?
| 17.1
| ?
| ?
| {{HideableNotes|Works fine. EXT untested.}}
|- style="background: #90FF90"
| 32
| 10
| Samsung 32GB MicroSDHC Class 10 (MB-MSBGA)
| [http://www.samsung.com/us/computer/memory-storage/MB-MSBGA/US]
| yes
| yes
| 18.1
| 11.7
| 30657536
| Works. {{HideableNotes|Claimed to be resistant to magnets, shocks, and seawater—as if you’d be able to find it in the ocean!}}
|- style="background: #90FF90"
| 8
| 10
| SanDisk SDHC 8GB Extreme 30MB/s Edition
| [http://www.amazon.de/SanDisk-SDHC-Extreme-Speicherkarte-30MB/dp/B001G87S1Y/ref=sr_1_2?ie=UTF8&qid=1304020731&sr=8-2]
| yes
| yes
| 16.6
| ?
| ?
| Works nice. {{HideableNotes|Installed Angstrom on it and copied some stuff onto it. Angstrom runs as fast as from NAND. Best thing was, where I ordered it it said class 6, but it is actually 10. :-D Still have to test its speed and actual size. Didn't test Fat a lot, but it seemed to work.}}
|- style="background: #90FF90"
| 8
| 10 - UHS 1
| SanDisk Extreme HD Video SDHC UHS-I 8GB 30MB/s 200X
| [http://www.amazon.com/SanDisk-Extreme-Video-Memory-SDSDRX3-8192-A21/dp/B000XZCIX4/ref=sr_1_2?s=electronics&ie=UTF8&qid=1322082251&sr=1-2]
| yes
| yes
| 16.6
| 15
| ?
| Works.
|- style="background: #90FF90"
| 16
| 10 - UHS 1
| SanDisk Extreme HD Video SDHC UHS-I 16GB 30MB/s 200X
| [http://www.amazon.com/SanDisk-Extreme-Video-Memory-SDSDRX3-016G-A21/dp/B003D5MY5I/ref=sr_1_2?s=electronics&ie=UTF8&qid=1322074343&sr=1-2]
| yes
| yes
| 16.5
| 14.5
| ?
| Works.
|- style="background: #90FF90"
| 32
| 10 - UHS 1
| SanDisk Extreme SDHC UHS-I 32GB 45MB/s 300X
| [http://www.amazon.com/SanDisk-EXTREME-SDSDRX3-032G-A21-Newest-Version/dp/B0077SCBGE/ref=sr_1_13?s=electronics&ie=UTF8&qid=1330369724&sr=1-13]
| yes
| yes
| 17.0
| 13.0
| ?
| Works.
|- style="background: #90FF90"
| 8
| UHS 1
| SanDisk Extreme Pro SDHC UHS-I 8GB 45MB/s 300X
| [http://www.amazon.com/SanDisk-Carte-M%C3%A9moire-Extreme-UHS-I/dp/B004JJU6I4]
| yes
| yes
| 15.8
| 12.5
| ?
| Works.
|- style="background: #90FF90"
| 32
| 4
| SanDisk Ultra 32 GB Class 4 SDHC
| [http://www.sandisk.com/products/imaging/sandisk-ultra-sdhc]
| yes
| yes
| 16.4
| 7.1
| 31166976
| OK.
|- style="background: #90FF90"
| 64
| 4
| Sandisk 64GB SDXC Class 4
| [http://www.amazon.com/SanDisk-Secure-Digital-Capacity-Memory/dp/B003FVG3PC/]
| yes
| yes
| 16.1
| 4.5
| 62367744
| Works fine
|-
| 32
| 6
| TOPRAM 32GB CLASS 6 SDHC HIGH SPEED (TRSD32GSDHCR3)
| [http://www.buy.com/prod/topram-32gb-class-6-sdhc-high-speed-flash-memory-card-usb-2-0-sdhc/q/loc/101/210247368.html]
| ?
| ?
| ?
| ?
| ?
| Reported working [http://www.gp32x.com/board/index.php?/topic/55506-recommended-sd-cards-for-pandora/page__view__findpost__p__897478 here].
|- style="background: #F3F781"
| 8
| 10
| Transcend 8GB SDHC Class 10
| [http://www.amazon.com/Transcend-Carte-m%C3%A9moire-SDHC-Class/dp/B002WE6D44]
| yes
| yes
| 13.3
| 10.1
| ?
| Have serious doubts about this card. May fail when transferring a lot of data. Seems it doesn't handle.
|- style="background: #FF9090"
| 32
| 10
| Transcend 32GB SDHC Class 10
| [http://www.amazon.co.uk/Transcend-Flash-memory-card-Class/dp/B003P3MCXW/ref=sr_1_1?ie=UTF8qid=1301320598sr=8-1]
| no
----
<div style="background: #F3F781">yes{{HideableNotes| working for me}}</div>
| no
----
<div style="background: #F3F781">yes{{HideableNotes| working fo me}}</div>
| 16.0
| ?
| ?
| Has serious issues [http://boards.openpandora.org/index.php?/topic/1592-sd-card-instability/]
----
<div style="background: #F3F781">Bad partitioning ?{{HideableNotes| working fo me}}</div>
|- style="background: #FF9090"
| 64
| 10
| Transcend SDXC Card 64GB ULTIMATE CLASS 10 (PN:TS64GSDXC10)
| [http://www.transcendusa.com/Products/ModDetail.asp?ModNo=286&LangNo=0&Func1No=1&Func2No=13]
| yes (needs more testing)

----
<div style="background: #F3F781">yes{{HideableNotes|but look at the notes, not good}}</div>
| no
----
<div style="background: #F3F781">?{{HideableNotes|Might work but didn't really test it long enough}}</div>
| 16.1
----
<div style="background: #F3F781"><=16</div>
| 16.1
----
<div style="background: #F3F781"><=16</div>
| ?
| {{HideableNotes|After some time the system gives read/write errors. Works fine on a pc with linux with ext2/ext3.}}
----
<div style="background: #F3F781">Serious issues. {{HideableNotes|My Linux computer can't read it, but that is probably the computer. First formatted it to ext2 while leaving 16MiB free at the beginning because it was like that when I got it. Had 16MB/s r/w. Then started to have problems after writing about 64GB to it, couldn't mount it, reformatted it, no change, reformatted it as Fat32, still no change, reformatted again as fat32, no problems so far but write speed is 0.5MB/s and read speed 14.76MB/s. I let F3 run over it, the speed was measured using it too. --A few weeks later-- It has got variable w/r speed, it drops after a few seconds of writing data to it. Sometimes it gives other errors, stops working until I reboot, etc. It's useable, but I wouldn't buy it again.}}</div>
|- style="background: #FF9090"
| 32
| 6
| Verbatim Class 6 Premium HD Video 32GB SDHC
| [http://www.amazon.co.uk/Verbatim-44032-32GB-Video-Class/dp/B0035MSOX0/ref=sr_1_2?ie=UTF8&s=electronics&qid=1304517332&sr=8-2]
| no
| no
| ?
| ?
| ?
| Behaviour similar to Kingston 32GB Class 4 -[http://www.gp32x.com/board/index.php?/topic/59113-pnd-run-sh/page__view__findpost__p__948196]
|- style="background: #90FF90"
| 32
| 4
| Zap Glider 32GB Class 4
| [http://www.teknikmagasinet.se/db.pl?tf=product.html&artnr=181043]
| ?
| yes
| 16.6
| 4.6
| ?
| Works fine
|}

[[Category:Hardware]]
[[Category:List]]
[[Category:Storage card]]

Compile on the Pandora

2012-05-23T00:14:53Z

Wtachi: /* The opkg way */ libgcc-dev is apparently the same as libgcc-s-dev, but better

== Lazy but working way ==

This is how I, T4b, set up my develepment environment. Of course it is on an SD card, the NAND is way to small. I recommend an 8GB card.
=== Installing the OS to an SD ===
This part was almost only copied from there: http://www.pandorabits.org/index.php?page=sd-installer
#Copy the PND to an SD card in the usual manner. You can get it from [http://www.pandorabits.org/index.php?page=sd-installer-downloads PandoraBits' download page].
#Copy a firmware image to the same card. You can get one from [http://openpandora.org/firmware/ here], the file "pandora-rootfs.tar.bz2" should always be the latest image, older ones are under the "images" directory. I suggest using the newest one, I did it with the (at the moment of writing this) newest one, with HotFix5.
#Ensure that you have both SD cards in Pandora. It doesn't matter which one is in which slot.
#Run the PND. You will probably be asked for your password at this point. This is needed because the installer needs to run as root in order to partition and format the SD card.
#Follow the prompts that appear. You will be asked for the firmware image file, then asked to select the card that you want to use, then asked to choose how much space to allocate to the VFAT (Windows, see below) and swap partitions.
#Once you have gone through all the prompts, the firmware image will be installed to the SD card. This will take upwards of ten minutes. The larger the card, the longer it takes, so be patient.
#Once complete, you will be able to boot your Pandora from the SD card by powering it on with the card in the left slot. Please note that the first boot will take longer than usual, at least ten minutes. Cards of 16 GB or more seem to take a lot longer.
=== Getting the actual development environment ===
No you'll find out why I called it a "lazy" way.
#Download the newest archive from [http://forum.gp2x.de/viewtopic.php?f=24&t=11865 this] thread in the German gp2x.de forum. Use google translator if necessary (at the time of writing this the newest one was [http://kimu.usenet-verwaltung.de/devel-pandora-native-20110411.tar.bz2 this] [direct download])
#Copy it on an SD which you insert into your Pandora
#<source lang="bash">cd /</source>
#<source lang="bash">sudo tar -xjf path/to/archive.tar.bz2</source>
#Reboot
Done!

== The opkg way ==
torpor described how to [http://www.gp32x.com/board/index.php?/topic/53964-cross-compiling-is-bollocks-toolchains-are-bollocks-use-your-pandora-to-build-apps/ build apps directly on the Pandora].

{{warning
|Please note that as of March 2011, you will break your install if you follow those instructions directly! The angstrom "unstable" distribution is well named.
}}

You can try the following:

1. I found that the www.angstrom-distribution.org repo was very slow, so changed the config files in /etc/opkg/ to use us.feeds.angstrom-distribution.org instead.

2. Enable sshd, and ssh in from another machine. This helps keep control when things break. To get root:

<source lang="bash">sudo bash</source>

3. Set up a [http://pandorawiki.org/Extend_Utils#Creating_a_Root_or_Home_Overlay_PreMount root overlay] on your SD card. This gives you a way to try again when things break, and there are other benefits. I added /home/ to the overlay also, by editing the "premount" script. To explain the extend terminology a bit, a "root overlay" is a loop mounted filesystem (on an SD) which goes over the top of (most of) your normal root filesystem. You can still read the files underneath it, but any writes / deletes are recorded only in the overlay filesystem. Your real root on the NAND is not modified at all. The "premount" shell script is used to mount your overlay, have a look in it to see how it works. You can sort of unmount them using umount -l (lazy umount), but I'm not sure if this is safe. The reliable way to unmount it is to reboot the Pandora!

4. Mount the overlay. Check this worked, with "mount" or "df".

5. Get new fresh package lists:

<source lang="bash">opkg update</source>

6. ncurses packaging seems to be broken, and ncurses is important! So, I suggest to do this first (in the overlay), or be prepared for things to start breaking when it gets removed later. If it does get removed, make sure to install it again!

<source lang="bash">opkg install libncurses5</source>

7. Install dev packages:

<source lang="bash">opkg install gcc gcc-symlinks make-dev binutils-dev cpp cpp-symlinks libgcc-dev
opkg install g++ g++-symlinks libstdc++-dev</source>

8. Try to compile "hello world".

9. I had trouble with libsdl-image-1.2-dev and libpng / libpng-dev. libpng-dev from the repo conflicts with 'libpng' on the Pandora. That latter package is misnamed I guess, it should be called 'libpng-dev', only contains libpng-config and libpng12-config (dev tools, not essential) but task-pandora-core depends on it. The real libs are in libpng12-0 / libpng3. So I did this:
<source lang="bash">
opkg remove libpng --force-depends
opkg install libpng-dev
</source>

10. Install extra dev libs:
<source lang="bash">
opkg install libgles-omap3-dev
opkg install libsdl-1.2-dev libsdl-gfx-dev libsdl-image-1.2-dev libsdl-mixer-1.2-dev libsdl-net-1.2-dev libsdl-ttf-2.0-dev
</source>

Hopefully this will go smoothly if you've fixed the png conflict in step 9.

11. Install optional extra stuff, if you want them:
<source lang="bash">
opkg install vim vim-syntax
opkg install libgles-omap3-demos
opkg install screen git rsync
</source>

The above was from memory, I didn't re-test all of it because it took too long even the first time! If you find other problems or quirks, please correct it.

After all this, I was able to build torpor's suggested dev demo app, [http://w1xer.at/pandora/ WakeBreaker].

== Using the C Development Tools PND ==

For compiling C/C++ programs that use SDL, GTK+, QT or Allegro, a PND is now available: [http://repo.openpandora.org/?page=detail&app=cdevtools.freamon.40n8e repo]. Running this PND gives your Pandora access to gcc and g++ without changing the root filesystem.

[[Category:Development]]
[[Category:Tutorials]]

Compile on the Pandora

2012-05-22T22:42:23Z

Wtachi: /* Torpor's way */ change section name and note libgcc-s-dev

== Lazy but working way ==

This is how I, T4b, set up my develepment environment. Of course it is on an SD card, the NAND is way to small. I recommend an 8GB card.
=== Installing the OS to an SD ===
This part was almost only copied from there: http://www.pandorabits.org/index.php?page=sd-installer
#Copy the PND to an SD card in the usual manner. You can get it from [http://www.pandorabits.org/index.php?page=sd-installer-downloads PandoraBits' download page].
#Copy a firmware image to the same card. You can get one from [http://openpandora.org/firmware/ here], the file "pandora-rootfs.tar.bz2" should always be the latest image, older ones are under the "images" directory. I suggest using the newest one, I did it with the (at the moment of writing this) newest one, with HotFix5.
#Ensure that you have both SD cards in Pandora. It doesn't matter which one is in which slot.
#Run the PND. You will probably be asked for your password at this point. This is needed because the installer needs to run as root in order to partition and format the SD card.
#Follow the prompts that appear. You will be asked for the firmware image file, then asked to select the card that you want to use, then asked to choose how much space to allocate to the VFAT (Windows, see below) and swap partitions.
#Once you have gone through all the prompts, the firmware image will be installed to the SD card. This will take upwards of ten minutes. The larger the card, the longer it takes, so be patient.
#Once complete, you will be able to boot your Pandora from the SD card by powering it on with the card in the left slot. Please note that the first boot will take longer than usual, at least ten minutes. Cards of 16 GB or more seem to take a lot longer.
=== Getting the actual development environment ===
No you'll find out why I called it a "lazy" way.
#Download the newest archive from [http://forum.gp2x.de/viewtopic.php?f=24&t=11865 this] thread in the German gp2x.de forum. Use google translator if necessary (at the time of writing this the newest one was [http://kimu.usenet-verwaltung.de/devel-pandora-native-20110411.tar.bz2 this] [direct download])
#Copy it on an SD which you insert into your Pandora
#<source lang="bash">cd /</source>
#<source lang="bash">sudo tar -xjf path/to/archive.tar.bz2</source>
#Reboot
Done!

== The opkg way ==
torpor described how to [http://www.gp32x.com/board/index.php?/topic/53964-cross-compiling-is-bollocks-toolchains-are-bollocks-use-your-pandora-to-build-apps/ build apps directly on the Pandora].

{{warning
|Please note that as of March 2011, you will break your install if you follow those instructions directly! The angstrom "unstable" distribution is well named.
}}

You can try the following:

1. I found that the www.angstrom-distribution.org repo was very slow, so changed the config files in /etc/opkg/ to use us.feeds.angstrom-distribution.org instead.

2. Enable sshd, and ssh in from another machine. This helps keep control when things break. To get root:

<source lang="bash">sudo bash</source>

3. Set up a [http://pandorawiki.org/Extend_Utils#Creating_a_Root_or_Home_Overlay_PreMount root overlay] on your SD card. This gives you a way to try again when things break, and there are other benefits. I added /home/ to the overlay also, by editing the "premount" script. To explain the extend terminology a bit, a "root overlay" is a loop mounted filesystem (on an SD) which goes over the top of (most of) your normal root filesystem. You can still read the files underneath it, but any writes / deletes are recorded only in the overlay filesystem. Your real root on the NAND is not modified at all. The "premount" shell script is used to mount your overlay, have a look in it to see how it works. You can sort of unmount them using umount -l (lazy umount), but I'm not sure if this is safe. The reliable way to unmount it is to reboot the Pandora!

4. Mount the overlay. Check this worked, with "mount" or "df".

5. Get new fresh package lists:

<source lang="bash">opkg update</source>

6. ncurses packaging seems to be broken, and ncurses is important! So, I suggest to do this first (in the overlay), or be prepared for things to start breaking when it gets removed later. If it does get removed, make sure to install it again!

<source lang="bash">opkg install libncurses5</source>

7. Install dev packages:

<source lang="bash">opkg install gcc gcc-symlinks make-dev binutils-dev cpp cpp-symlinks g++ g++-symlinks libstdc++-dev libgcc-s-dev</source>

8. Try to compile "hello world".

9. I had trouble with libsdl-image-1.2-dev and libpng / libpng-dev. libpng-dev from the repo conflicts with 'libpng' on the Pandora. That latter package is misnamed I guess, it should be called 'libpng-dev', only contains libpng-config and libpng12-config (dev tools, not essential) but task-pandora-core depends on it. The real libs are in libpng12-0 / libpng3. So I did this:
<source lang="bash">
opkg remove libpng --force-depends
opkg install libpng-dev
</source>

10. Install extra dev libs:
<source lang="bash">
opkg install libgles-omap3-dev
opkg install libsdl-1.2-dev libsdl-gfx-dev libsdl-image-1.2-dev libsdl-mixer-1.2-dev libsdl-net-1.2-dev libsdl-ttf-2.0-dev
</source>

Hopefully this will go smoothly if you've fixed the png conflict in step 9.

11. Install optional extra stuff, if you want them:
<source lang="bash">
opkg install vim vim-syntax
opkg install libgles-omap3-demos
opkg install screen git rsync
</source>

The above was from memory, I didn't re-test all of it because it took too long even the first time! If you find other problems or quirks, please correct it.

After all this, I was able to build torpor's suggested dev demo app, [http://w1xer.at/pandora/ WakeBreaker].

== Using the C Development Tools PND ==

For compiling C/C++ programs that use SDL, GTK+, QT or Allegro, a PND is now available: [http://repo.openpandora.org/?page=detail&app=cdevtools.freamon.40n8e repo]. Running this PND gives your Pandora access to gcc and g++ without changing the root filesystem.

[[Category:Development]]
[[Category:Tutorials]]

SD compatibility list

2012-05-22T19:56:13Z

Wtachi: add some better links and move notes around so it looks better without JS

This is a compatibility list for SD, SDHC and SDXC cards. The cards listed in '''green''' work with any file system. The cards listed in '''yellow''' work well only with one file system (this still means they can be used on the Pandora). The cards listed in '''red''' do not work well with any file system. Although it is not covered on this list, the Pandora can also read NTFS-formatted SD cards if the [http://www.open-pandora.org/downloads/CodecPack.pnd Community Codec Pack] is installed.

Note: always measure read speed by opening a terminal window and typing this command:
* the first inserted SD Card: '''dd if=/dev/mmcblk0 of=/dev/null bs=4MiB count=100'''
* the second inserted SD Card: '''dd if=/dev/mmcblk1 of=/dev/null bs=4MiB count=100'''

Note: The first inserted SD Card will always be /dev/mmcblk0, regardless if you put it into the second or first SD Card slot, whereas the second will be /dev/mmcblk1

If you can afford '''''destroying''''' all your data, you can test write speed. But be careful, you will need to create a new partition table, afterwards! You can use [http://www.gp32x.com/board/index.php?/topic/56915-gparted/ Gparted] to make new partition table.
* the first inserted SD Card: # '''dd if=/dev/zero of=/dev/mmcblk0 bs=4MiB count=100'''
* the second inserted SD Card: # '''dd if=/dev/zero of=/dev/mmcblk1 bs=4MiB count=100'''

By default, the first partition starts at block 8192 (4096KB) for 32GB cards, and block 32768 (16384KB) for 64GB cards. 64GB cards may need to be [[formatting SD cards|reformatted]] before use.

{|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"
! Card size in GB
! Card class
! Full name
! URL
! fat32 is working?
! ext2/3/4 are working?
! read speed MB/sec
! write speed MB/sec
! actual capacity (1024byte blocks)
! Notes
|-
| 32
| 10
| Centon 32GB Class 10 SDHC
| [http://www.microcenter.com/single_product_results.phtml?product_id=0335228]
| yes
| ?
| 17.3
| 23.9
| ?
| ok {{HideableNotes|so far, first few hours of use}}
|- style="background: #90Ff90"
| 1
| n/a
| Kingston 1GB (blue)
| [http://www.newegg.com/Product/Product.aspx?Item=N82E16820160032]
| yes
| yes
| 12.5
| ?
| 1006080
| ok
|-
| 8
| 4
| Kingston 8GB Class 4 (black)
|
| not long-term tested yet
| not long-term tested yet
| 17.1
| 4.8
| ?
| From Craig's shop, so must be ok ;)
|- style="background: #FF9090"
| 16
| 4
| Kingston 16 GB Class 4 SDHC
| [http://www.amazon.com/Kingston-Class-Memory-SD4-16GB/dp/B0013AV9TW]
| no
| no
| 15
| 9.5
| 15663104
| {{HideableNotes|Bad controller chip, fails in the same manner as the 32GB card.}}
|- style="background: #FF9090"
| 32
| 4
| Kingston 32 GB Class 4 SDHC
| [http://www.amazon.com/Kingston-Class-Memory-SD4-32GB/dp/B001C9P5TO]
| no
| no
| 16
| 9.5
| 31539200
| {{HideableNotes|Defective flash controller randomly loses writes regardless of filesystem. When attempting to write, blocks sometimes get erased but not written.}}
|- style="background: #F3F781"
| 32
| 10
| Kingston 32GB (red) Class 10
| [http://www.newegg.com/Product/Product.aspx?Item=N82E16820139146]
| yes
| no
| 15.2
| ?
| ?
| {{HideableNotes|doesn't have badblocks, seems that "Flash Translation Layer" is not suitable for ext filesystems}}
|- style="background: #90FF90"
| 32
| 4
| Lexar Multi-Use 32GB
| [http://www.amazon.com/Lexar-Flash-memory-card-Class/dp/B0040J1ET8]
| yes
| yes
| 16.1
| 14.4
| 31267840
| {{HideableNotes|Much faster than would be expected for a class 4 card. Usual warning about high-speed cards being susceptible to power supply glitches applies.}}
|- style="background: #F3F781"
| 32
| 10
| Lexar Premium Series 32GB 100x
| [http://www.amazon.com/Lexar-Secure-Digital-Premium-Memory/dp/B003PJ657K/ref=sr_1_11?s=electronics&ie=UTF8&qid=1321986834&sr=1-11]
| yes
| no
| 16.7
| 12.0
| ?
| Worst ext2 support ever. Copying fine, a LOT of I/O errors at first boot. Literally unusable. Fat32 seems perfectly supported.
|- style="background: #90FF90"
| 64
| 10
| Lexar Professional 64GB 133x
| [http://www.amazon.com/Lexar-Professional-Flash-memory-Memory/dp/B004QWRZWY]
| yes
| yes
| 19.6
| 15.1
| 62536704
| {{HideableNotes|R/W speed in the pandora is limited to 16.1/11.3 MB/sec. High power consumption, may fail under load.}}[http://boards.openpandora.org/index.php?/topic/2556-32gb-sdhc-card-problems/page__st__40]
|- style="background: #90FF90"
| 128
| 10
| Lexar Professional 128GB 133x SDXC
| [http://www.bhphotovideo.com/c/product/756124-REG/Lexar_LSD128CRBNA133_128GB_Professional_SDXC_Card.html]
| yes
| yes
| 17.2
| 11.8
| 122.97GiB
| {{HideableNotes|Speeds listed are IN a Pandora.}}[http://boards.openpandora.org/index.php?/topic/7682-128gb-lexar-sdxc-card-benchmarks/]
|- style="background: #90FF90"
| 16
| 6
| Maxflash 16GB Class 6 SDHC
| [http://www.max-flash.eu/en/products/SDHC%20Card.html]
| ?
| yes
| 14.4
| ?
| 16186368
| Works fine
|- style="background: #90FF90"
| 32
| 10
| Patriot LX 32GB SDHC Class 10 (PSF32GSDHC10)
| [http://www.bestdirect.ca/products/227442/Patriot/PSF32GSDHC10/] [http://www.amazon.ca/gp/product/B002TABU5I/]
| yes
| no/yes
| 18.1
| 12.6
| ?
| {{HideableNotes|Formatting EXT2 and then running fsck right after finds errors. Seems to work well with fat32 /// Entry 2 from another user: Works great with ext2. No errors or issues.}}
|- style="background: #90Ff90"
| 4
| 10
| Pretec 4GB, Class 10, 233x (white/green)
| [http://pamatove-karty.heureka.sk/pretec-sdhc-4gb-class-10/]
| yes
| yes (mostly)
| 14.0
| ?
| 3883008
| {{HideableNotes|I had very few fsck problems, and after several tries running fsck, they eventually got corrected. It looks very similar to that broken 32GB pretec. Except that this one almost works good.}}
|- style="background: #F3F781"
| 32
| 10
| Pretec 32GB Class 10, 233x (white/green)
| [http://www.prva.sk/detail/pretec-sdhc-32gb-class-10/kk296d49525.aspx]
| yes
| no
| 14.1
| 12.4
| ?
| {{HideableNotes|doesn't have badblocks, seems that "Flash Translation Layer" is not suitable for ext filesystems}}
|- style="background: #F3F781"
| 32
| 10
| PNY 32GB (P-SDHC32G10)
| [http://www.amazon.com/PNY-SDHC-Flash-Memory-P-SDH32G10-EFS2/dp/B004LQYV5E]
| yes
| ?
| 17.1
| ?
| ?
| {{HideableNotes|Works fine. EXT untested.}}
|- style="background: #90FF90"
| 8
| 10
| SanDisk SDHC 8GB Extreme 30MB/s Edition
| [http://www.amazon.de/SanDisk-SDHC-Extreme-Speicherkarte-30MB/dp/B001G87S1Y/ref=sr_1_2?ie=UTF8&qid=1304020731&sr=8-2]
| yes
| yes
| 16.6
| ?
| ?
| Works nice. {{HideableNotes|Installed Angstrom on it and copied some stuff onto it. Angstrom runs as fast as from NAND. Best thing was, where I ordered it it said class 6, but it is actually 10. :-D Still have to test its speed and actual size. Didn't test Fat a lot, but it seemed to work.}}
|- style="background: #90FF90"
| 8
| 10 - UHS 1
| SanDisk Extreme HD Video SDHC UHS-I 8GB 30MB/s 200X
| [http://www.amazon.com/SanDisk-Extreme-Video-Memory-SDSDRX3-8192-A21/dp/B000XZCIX4/ref=sr_1_2?s=electronics&ie=UTF8&qid=1322082251&sr=1-2]
| yes
| yes
| 16.6
| 15
| ?
| Works.
|- style="background: #90FF90"
| 16
| 10 - UHS 1
| SanDisk Extreme HD Video SDHC UHS-I 16GB 30MB/s 200X
| [http://www.amazon.com/SanDisk-Extreme-Video-Memory-SDSDRX3-016G-A21/dp/B003D5MY5I/ref=sr_1_2?s=electronics&ie=UTF8&qid=1322074343&sr=1-2]
| yes
| yes
| 16.5
| 14.5
| ?
| Works.
|- style="background: #90FF90"
| 32
| 10 - UHS 1
| SanDisk Extreme SDHC UHS-I 32GB 45MB/s 300X
| [http://www.amazon.com/SanDisk-EXTREME-SDSDRX3-032G-A21-Newest-Version/dp/B0077SCBGE/ref=sr_1_13?s=electronics&ie=UTF8&qid=1330369724&sr=1-13]
| yes
| yes
| 17.0
| 13.0
| ?
| Works.
|- style="background: #90FF90"
| 8
| UHS 1
| SanDisk Extreme Pro SDHC UHS-I 8GB 45MB/s 300X
| [http://www.amazon.com/SanDisk-Carte-M%C3%A9moire-Extreme-UHS-I/dp/B004JJU6I4]
| yes
| yes
| 15.8
| 12.5
| ?
| Works.
|- style="background: #90FF90"
| 32
| 4
| SanDisk Ultra 32 GB Class 4 SDHC
| [http://www.sandisk.com/products/imaging/sandisk-ultra-sdhc]
| yes
| yes
| 16.4
| 7.1
| 31166976
| OK.
|- style="background: #90FF90"
| 64
| 4
| Sandisk 64GB SDXC Class 4
| [http://www.amazon.com/SanDisk-Secure-Digital-Capacity-Memory/dp/B003FVG3PC/]
| yes
| yes
| 16.1
| 4.5
| 62367744
| Works fine
|-
| 32
| 6
| TOPRAM 32GB CLASS 6 SDHC HIGH SPEED (TRSD32GSDHCR3)
| [http://www.buy.com/prod/topram-32gb-class-6-sdhc-high-speed-flash-memory-card-usb-2-0-sdhc/q/loc/101/210247368.html]
| ?
| ?
| ?
| ?
| ?
| Reported working [http://www.gp32x.com/board/index.php?/topic/55506-recommended-sd-cards-for-pandora/page__view__findpost__p__897478 here].
|- style="background: #F3F781"
| 8
| 10
| Transcend 8GB SDHC Class 10
| [http://www.amazon.com/Transcend-Carte-m%C3%A9moire-SDHC-Class/dp/B002WE6D44]
| yes
| yes
| 13.3
| 10.1
| ?
| Have serious doubts about this card. May fail when transferring a lot of data. Seems it doesn't handle.
|- style="background: #FF9090"
| 32
| 10
| Transcend 32GB SDHC Class 10
| [http://www.amazon.co.uk/Transcend-Flash-memory-card-Class/dp/B003P3MCXW/ref=sr_1_1?ie=UTF8qid=1301320598sr=8-1]
| no
----
<div style="background: #F3F781">yes{{HideableNotes| working for me}}</div>
| no
----
<div style="background: #F3F781">yes{{HideableNotes| working fo me}}</div>
| 16.0
| ?
| ?
| Has serious issues [http://boards.openpandora.org/index.php?/topic/1592-sd-card-instability/]
----
<div style="background: #F3F781">Bad partitioning ?{{HideableNotes| working fo me}}</div>
|- style="background: #FF9090"
| 64
| 10
| Transcend SDXC Card 64GB ULTIMATE CLASS 10 (PN:TS64GSDXC10)
| [http://www.transcendusa.com/Products/ModDetail.asp?ModNo=286&LangNo=0&Func1No=1&Func2No=13]
| yes (needs more testing)

----
<div style="background: #F3F781">yes{{HideableNotes|but look at the notes, not good}}</div>
| no
----
<div style="background: #F3F781">?{{HideableNotes|Might work but didn't really test it long enough}}</div>
| 16.1
----
<div style="background: #F3F781"><=16</div>
| 16.1
----
<div style="background: #F3F781"><=16</div>
| ?
| {{HideableNotes|After some time the system gives read/write errors. Works fine on a pc with linux with ext2/ext3.}}
----
<div style="background: #F3F781">Serious issues. {{HideableNotes|My Linux computer can't read it, but that is probably the computer. First formatted it to ext2 while leaving 16MiB free at the beginning because it was like that when I got it. Had 16MB/s r/w. Then started to have problems after writing about 64GB to it, couldn't mount it, reformatted it, no change, reformatted it as Fat32, still no change, reformatted again as fat32, no problems so far but write speed is 0.5MB/s and read speed 14.76MB/s. I let F3 run over it, the speed was measured using it too. --A few weeks later-- It has got variable w/r speed, it drops after a few seconds of writing data to it. Sometimes it gives other errors, stops working until I reboot, etc. It's useable, but I wouldn't buy it again.}}</div>
|- style="background: #FF9090"
| 32
| 6
| Verbatim Class 6 Premium HD Video 32GB SDHC
| [http://www.amazon.co.uk/Verbatim-44032-32GB-Video-Class/dp/B0035MSOX0/ref=sr_1_2?ie=UTF8&s=electronics&qid=1304517332&sr=8-2]
| no
| no
| ?
| ?
| ?
| Behaviour similar to Kingston 32GB Class 4 -[http://www.gp32x.com/board/index.php?/topic/59113-pnd-run-sh/page__view__findpost__p__948196]
|- style="background: #90FF90"
| 32
| 4
| Zap Glider 32GB Class 4
| [http://www.teknikmagasinet.se/db.pl?tf=product.html&artnr=181043]
| ?
| yes
| 16.6
| 4.6
| ?
| Works fine
|}

[[Category:Hardware]]
[[Category:List]]
[[Category:Storage card]]