Pandora Wiki - User contributions [en]

Ångström

2014-11-12T01:12:34Z

RygD: /* To NAND - internal storage */ removed unneeded capital

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== '''Installation''' prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the operating system is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== '''Fresh''' - full installation ==

=== To '''SD-card''' - external storage ===

==== With '''GUI-tool''' ====

Prerequisites: You only need the downloaded Super Zaxxon tarball, the sd_installer.pnd and a suitable SD card.
If you have an existing installation of Super Zaxxon you can use the '''GUI-driven tool sd_installer.pnd by David Boucher'''.
http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10
to install to an SD card.

==== Done '''Manually''' ====

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the operating system .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
#'''[http://openpandora.org/firmware/fullflash/SuperZaxxon162RC.zip Download the operating system image, Super Zaxxon 1.62RC (18-Oct-2014)]''' [http://boards.openpandora.org/topic/17176-superzaxxon-v162rc-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To '''[[NAND]]''' - internal storage ===

This is where where Super Zaxxon boots from out of the box.

# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

== '''Upgrade''' - distribution upgrade ==
Only upgrade the parts that need upgrading.
Versions after Super Zaxxon 1.52 come with an online operating system update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

== '''Online''' - install from a system in use to a drive that isnt ==

The UBIFS-Version can be used to flash the whole firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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.

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the Pandora.
* Things missing in the default operating system on the Pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

*http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/
*http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/
*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/
*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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 hotfixes, doing so will break the system.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-11-12T01:11:40Z

RygD: /* With GUI-tool */ fixed spelling and caps

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== '''Installation''' prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the operating system is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== '''Fresh''' - full installation ==

=== To '''SD-card''' - external storage ===

==== With '''GUI-tool''' ====

Prerequisites: You only need the downloaded Super Zaxxon tarball, the sd_installer.pnd and a suitable SD card.
If you have an existing installation of Super Zaxxon you can use the '''GUI-driven tool sd_installer.pnd by David Boucher'''.
http://repo.openpandora.org/?page=detail&app=sd-install-2011-03-10
to install to an SD card.

==== Done '''Manually''' ====

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the operating system .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
#'''[http://openpandora.org/firmware/fullflash/SuperZaxxon162RC.zip Download the operating system image, Super Zaxxon 1.62RC (18-Oct-2014)]''' [http://boards.openpandora.org/topic/17176-superzaxxon-v162rc-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To '''[[NAND]]''' - internal storage ===

This is where Where Super Zaxxon boots from out of the box.

# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

== '''Upgrade''' - distribution upgrade ==
Only upgrade the parts that need upgrading.
Versions after Super Zaxxon 1.52 come with an online operating system update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

== '''Online''' - install from a system in use to a drive that isnt ==

The UBIFS-Version can be used to flash the whole firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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.

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the Pandora.
* Things missing in the default operating system on the Pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

*http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/
*http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/
*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/
*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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 hotfixes, doing so will break the system.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T20:38:22Z

RygD: /* Older versions of Ångstrom */ Removed a bullet (ouch!)

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
#'''[http://openpandora.org/firmware/fullflash/SuperZaxxon162RC.zip Download firmware image of Super Zaxxon 1.62RC (18-Oct-2014)]''' [http://boards.openpandora.org/topic/17176-superzaxxon-v162rc-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the Pandora.
* Things missing in the default operating system on the Pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

*http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/
*http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/
*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/
*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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 hotfixes, doing so will break the system.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T20:36:00Z

RygD: /* To SD card (external) */ Fixed numbering that was previously interrupted due to links

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
#'''[http://openpandora.org/firmware/fullflash/SuperZaxxon162RC.zip Download firmware image of Super Zaxxon 1.62RC (18-Oct-2014)]''' [http://boards.openpandora.org/topic/17176-superzaxxon-v162rc-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the Pandora.
* Things missing in the default operating system on the Pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

*In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

*http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/
*http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/
*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/
*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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 hotfixes, doing so will break the system.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T20:30:07Z

RygD: added SZ 1.62 and cleaned up a few things

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
#'''[http://openpandora.org/firmware/fullflash/SuperZaxxon162RC.zip Download firmware image of Super Zaxxon 1.62RC (18-Oct-2014)]'''
[http://boards.openpandora.org/topic/17176-superzaxxon-v162rc-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the Pandora.
* Things missing in the default operating system on the Pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

*In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

*http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/
*http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/
*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/
*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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 hotfixes, doing so will break the system.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T19:54:00Z

RygD: /* Stuff that belongs there */ changed p to P on Pandora

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
'''[http://openpandora.org/firmware/pandora-rootfs.tar.bz2 Download firmware image of Super Zaxxon 1.61 (30-Apr-2014)]'''
[http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the Pandora.
* Things missing in the default operating system on the Pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

*In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

http://openpandora.org/firmware/fullflash/SuperZaxxon160.zip (20-dec-2013)] [http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/ forum thread]

*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/

'''[http://openpandora.org/firmware/fullflash/SuperZaxxon155.zip Download firmware image of SuperZaxxon 1.55 (2013-07)]'''

*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T19:40:36Z

RygD: /* Configuring newer kernels */

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
'''[http://openpandora.org/firmware/pandora-rootfs.tar.bz2 Download firmware image of Super Zaxxon 1.61 (30-Apr-2014)]'''
[http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

=== Stuff that belongs there ===

* Bugs that happen with the default operating system on the pandora.
* Things missing in the default operating system on the pandora.
* Bugs and issues with the codec pack.

=== What does not belong in the official tracker ===

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

=== Issue attributes explained ===

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

*In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

http://openpandora.org/firmware/fullflash/SuperZaxxon160.zip (20-dec-2013)] [http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/ forum thread]

*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/

'''[http://openpandora.org/firmware/fullflash/SuperZaxxon155.zip Download firmware image of SuperZaxxon 1.55 (2013-07)]'''

*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T19:39:00Z

RygD: /* not merged */ changed n to N

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
'''[http://openpandora.org/firmware/pandora-rootfs.tar.bz2 Download firmware image of Super Zaxxon 1.61 (30-Apr-2014)]'''
[http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

== Stuff that belongs there ==

* Bugs that happen with the default operating system on the pandora.
* Things missing in the default operating system on the pandora.
* Bugs and issues with the codec pack.

== What does not belong in the official tracker ==

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

== Issue attributes explained ==

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

*In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

http://openpandora.org/firmware/fullflash/SuperZaxxon160.zip (20-dec-2013)] [http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/ forum thread]

*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/

'''[http://openpandora.org/firmware/fullflash/SuperZaxxon155.zip Download firmware image of SuperZaxxon 1.55 (2013-07)]'''

*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Ångström

2014-10-23T19:38:00Z

RygD: Added a couple caps.

'''Super Zaxxon''' is currently the official operating system for the pandora based on [http://www.angstrom-distribution.org/ Ångström] Linux|Gnu. Super Zaxxon is a version upgrade system with frequent system-wide small releases. Compatibility is ensured as a basis of Super Zaxxon. Packages, often relying on their own environment are self retained within the .pnd format and available on [http://repo.openpandora.org/ a pnd repo] separate from the self hosted system packages. An evolutionary non-compatible similarly customized Ångström build called .next is in development.

== SUPER ZAXXON ==

== Installation prerequisites (Offline) ==

You need a Pandora, and alternatively an SD card, the latter is preferred because running from SD card is the ''recommended install method''.

=== General Notes ===

* Remember that your Pandora will turn on as soon as a charger is connected. It's also not possible to completely power down a Pandora that's connected to an external power supply.
* Even while charging, a Pandora can be rebooted, either by software (for example, during the installation process below), or with the reboot hotkey: Hold the Pandora button on the keyboard, and flick the power switch to the right.
* Do not connect an external power supply while the battery is removed.

* '''When the firmware is (re-)installed, all personal files and settings stored on internal flash are DELETED (your PND applications and all data on your SD cards will not be touched).
** Your Pandora will revert to it's default settings and show the first boot wizard on bootup.'''

== Full fresh installation ==

=== To SD card (external) ===

# SD card formatted with the FAT32 filesystem (default on Windows). Extract the contents of the firmware .zip file to the root (top level) directory of that card.
# Make sure your Pandora is turned off (remove the battery in case it crashes or doesn't turn off by using normal means).
'''[http://openpandora.org/firmware/pandora-rootfs.tar.bz2 Download firmware image of Super Zaxxon 1.61 (30-Apr-2014)]'''
[http://boards.openpandora.org/topic/16218-superzaxxon-v161-released/ forum thread]
# Insert the SD card into your Pandora's first slot (the one on the left, which is closer to headphone jack).
# Press and hold the right shoulder button ('R'), then turn the power on (if you removed the battery, insert it while holding 'R').
# A text menu should appear on screen. Switch to "boot from SD1" using the d-pad, and select this entry with either the 'B' or 'X' controller button.
# Wait for the flash process to finish. Connect a charger to be sure the battery doesn't run out while flashing. Press enter when asked to do so. Might take up to 15 minutes, be sure to wait for it to finish.
# If you use an external power supply, the device will reboot. Othwerwise, it should turn off - in this case press power (without holding 'R') to turn it back on.
# It should then start it's first boot process which might take up to 15 minutes. Be sure to wait for it to finish, otherwise firmware corruption might happen. The installation process will show some warnings, which can be safely ignored.
# When everything is set up, you will be guided through the first boot wizard.

=== To [[NAND]] (internal) ===
# Download [http://openpandora.org/firmware/pandora-flash-kit.zip flashkit], unzip, and put on a FAT32 formatted SD-card.
# Download the [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img image] and [http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img.md5 checksum] for image.
# Rename them rootfs.img for the image and rootfs.md5 for the checksum, and put on a SD-card.
# Insert SD-card into slot closest to headphone jack on pandora, and hold right trigger button "R" while turning on the device.
# Select Boot from SD 1:1 and follow instructions.

Where Super Zaxxon boots from out of the box.

The UBIFS-Version can be used to flash the firmware to the Pandora.

Please only use it if you really need to. Reflashing CAN solve some problems, but it's not the magical tool that can fix everything. You should always try to find another solution. Before reflashing, try the upgrade path below You can get help at the [http://boards.openpandora.org/index.php?/forum/8-support/ Support Section at the boards].

http://openpandora.org/firmware/images/Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20140430-omap3-pandora.ubifs.img

== Partial distribution upgrade ==

Versions after Super Zaxxon 1.52 come with an online firmware update utility: Just select ''System'' -> ''Upgrade Pandora OS'' from the Pandora menu to download the latest system packages (needs working internet connection).

=== To SD-card ===

==== GUI-driven SD installer tool ====

Instead of installing the firmware manually on the SD card, 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.

=== To [[NAND]] (internal) ===

You can extract the tar.bz2-version of the pandora-image onto an SD Card (EXT2) and directly boot off it.Be sure to include a kernel in /boot (unless you want to use the one on the NAND) and use a boot.txt / autoboot.txt to pass parameters to u-boot.This way, you can boot off your SD Card and meddle around with the OS without risking breaking NAND state.

== Installation perquisites (Online) ==

It is also possible to do an install while the system is running.
Grab the ubifs image and install that from nand to SD-card or vice versa. This is an advanced option.

The sourcecode for the programs included in the images can be found in the sources-directory, including licenses for each single one of them. The kernel and u-boot sourcecode as well as some other Pandora specific sourcecode can be found on http://git.openpandora.org/
Advanced users can get raw firmware images and rootfs (for SD Card bootup) as well as older versions [http://www.openpandora.org/firmware/ here].

== .next (version in development) ==

Also called Yars' Revenge W.I.P

== Compile build from source code ==

''openembedded.git''

This the the OpenEmbedded repository containing recipes for all kinds of stuff.

{| class="wikitable"
|-
! Head
! Content
|-
| op.openembedded.next
| .next with Pandora specific changes
|-
| org.openembedded.dev
| .dev without any changes
|-
| op.openembedded.dev
| .dev with Pandora specific changes
|-
| op_unstable
| Something unstable I'm guessing
|}

''openpandora.oe.git''

This is a Pandora specific OpenEmbedded overlay containing recipes only used on the Pandora.

{| class="wikitable"
|-
! Head
! Content
|-
| master
|-
| overlay.next
|-
| overlay.stable
|}

''pandora-oe-environment.git''

This contains scripts to set up bitbake, and the above OpenEmbedded repositories.

''Environment setup''

<source lang="bash">
git clone git://git.openpandora.org/pandora-oe-environment.git pandora-firmware
cd pandora-firmware
source ./op-env-oe.sh
./initial-setup.sh
</source>

''Building Yars' Revenge W.I.P.'' (Also called .next). Query aTc or DJWillis until you get a response.

The following instructions will allow you to build the current .next image.

Remember that your building the tip of the experimental tree and not everything even remotely works. Best for people who want to hack and help get it into shape. Do not expect anything remotely good enough to run on your Pandora for real

It is suggested that you use Debian or a Debian chroot.

In addition to the base Debian install you will need:

autoconf
automake
build-essential
coreutils
diffstat
diffstat texi2html gawk chrpath
docbook-utils
fdisk
gawk
gcc
git
git-core
gnome-doc-utils
groff
help2man
libc6-dev-i386
libsdl1.2-dev
liburi-perl
make
mercurial
python-pysqlite2
qemu-arm-static
scrollkeeper
subversion
texi2html
texinfo
unzip
util-linux
x11-xserver-utils

<source lang="bash">
cd <INSTALLDIR>
git clone git://github.com/openpandora/openpandora-oe-environment.git
cd openpandora-oe-environment
./openpandora-setup.sh config
</source>

This will install a number of git repositories containing the build tools and recipes:

* bitbake
* openembedded-core
* meta-openembedded
* meta-angstrom
* meta-texasinstruments
* meta-openpandora

* The basic hardware layer that works with OpenEmbedded and can be used in most OpenEmbedded distributions (Angstrom, Yocto, SHR etc.). That hardware layer also needs meta-texasinstruments (the scripts will bring that in, the Angstrom ones or ours).
meta-openpandora-vendor
* The vendor (i.e. openpandora) specific stuff, scripts, tweaks, image files, task files (i.e. what to install and order) and some recipes for things like libpnd.

From time to time you will want to update and fetch the changes to the base and openpandora recipes. e.g. those report on #openpandora by CIA-57

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment
./openpandora-setup.sh update
</source>

There are a number of recipes for build images in openpandora-oe-environment/metadata/meta-openpandora-vendor/recipes-core/images :

* pandora-core-image no desktop or X11
* pandora-xfce-image XFCE desktop environment
* systemd-pndwip-image

<source lang="bash">
. ~/.oe/environment-openpandora
cd <INSTALLDIR>/openpandora-oe-environment/build
bitbake systemd-core-image
</source>

This will download required sources and package dependancies, depending on the state of updatesm, build packages and produc an image.

The preferred method for sending patches for meta-openpandora and meta-openpandora-vendor is to create a fork in github apply you changes and send pull requests to OpenPandora Firmware mailing list: firmware-dev@openpandora.org ([http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev subscribe])

= Kernel status =

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 =
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!

= 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]].

==Pandora Firmware Governance==

The Pandora device is an open ecology --

The official [[firmware]] is open source and open to patches from the public; to maintain high quality firmware releases a process needs to exist -- audit trails need to be kept to ensure licensing is clear, testing has to be ensured to keep quality high, and our standard practice for submission made clear so it is easy and swift to submit your work.

Help us sort it out :) This process itself is open source -- as the ecosystem expands our model will change with it; if you are seeing problems, then contact one of the maintainers, mailing list, or the community at large and
All of which are part of the [[Team]]

The firmware is all of the software that is supplied with a device, so does include the applications which are provided as standard. It is all open source (meaning that OpenPandora provides the source code, often as a requirement of the [http://www.gnu.org/licenses/gpl.html GNU GPL]). A small quantity of the firmware is provided as binary files, which OpenPandora may not be at liberty to disclose the full details of. An example of closed source firmware is for the analogue nubs, which are shipped with small micro-controllers pre-programmed by the nub manufacturer. Only some of the hardware designs and occasional binary blobs like the [[WiFi]] driver are currently not open source; the rest of the firmware stack is open source (predominantly GPL with some LGPL).

== Replacing the Firmware (Un-bricking) ==

Rather than patch the firmware, the firmware may be replaced wholesale with a freshly downloaded firmware. This ought to be regarded as a last resort in the case of problems, there is almost certainly a simpler way to fix most problems.

The process for reinstalling the firmware is as follows: [http://www.gp32x.com/board/index.php?/topic/53637-first-boot-its-asking-for-a-login-and-password/page__view__findpost__p__858053]
, otherwise firmware corruption might happen again.

In case of emergency, there is an older version
[http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (Version: 2010-05-01-Zaxxon)

== Debugging broken firmware ==

[http://pandorawiki.org/Boot_setup#Rescue_console_boot] will help you in case booting normally breaks. That way you can provide debugging info to source what went wrong instead of just re-installing.

== Reporting bugs ==

Please do make sure that you are using the latest official firmware and hotfix. You can find it in the [http://www.open-pandora.org/index.php?option=com_content&view=article&id=178&Itemid=32&lang=en official support section of the website]. Reports made against older versions might be invalid since the issues were already fixed.

If the bug does still exist in the latest released version, please follow these steps when reporting it in the [http://bugs.openpandora.org official bug tracker]. You will need to register an account in the tracker. Once you are logged into the account, just click on ''Add new task'' to see a form where you can provide the information required to assign and solve the bugs. Below is an explanation of what you should enter where.

== Stuff that belongs there ==

* Bugs that happen with the default operating system on the pandora.
* Things missing in the default operating system on the pandora.
* Bugs and issues with the codec pack.

== What does not belong in the official tracker ==

* Bugs with other .pnd files like eg [[emulators]], [[games]] or other applications that are not part of the main OS.
* Features missing in other progs.

== Issue attributes explained ==

Here is the list of things you should keep in mind and mention in your bug report or feature request to make sure that it can be solved. Please do also make sure to react on comments that are left in the report, since the people that feel responsible for solving the issues might need more information that only you can provide.

;Summary: This should be a really short summary of the issue at hand, as clean as possible. Something like eg ''ABC does not work'' is not good, better write ''ABC crashes when sounds are played''.

;Drop Down Boxes: This area on the left side is used to provide some general information that makes it easier for devs to assign the reports to the correct people for fixing things. They are often useful in fixing the report in the end, too.

;Task Type: Just select it from the drop down box. If you want to report a bug, make it ''Bug Report'', if it is a missing feature, select ''Feature Request''. You should only select ''To Do (Reminder)'' if you are one of the devs to leave a note for yourself.

;Category Core: Everything that belongs to the basic systems like the kernel and the drivers. The real core that lies beneath.

;Category Application: Meant for all the programs on top of the basis core. This eg. includes problems in minimenu, Pandora specific XFCE, pidgin, ... Basically you should ask yourself if your issue might be kernel/driver related, if it is not, select this one.

;Status: Can only be changed by bug tracker admins (aka "official pandora devs").

;Operating System: Select the "series" of the operating system on the pandora here. The first firmware series is called Zaxxon.

;Severity: How important do you estimate this bug/issue? It should only be marked ''critical'' if it is a real security breach or something breaking *everything*. Often the default ''low'' is fine, since the values can be adjusted later on by bug tracker admins.

;Priority: Can only be changed by bug tracker admins (aka "official pandora devs").

;Reported Version: Please select which version state your pandora has in the release that you selected under ''Operating System''. Basically list the latest hotfix that you installed.

;Due in Version: Can only be changed by bug tracker admins (aka "official pandora devs").

;Details: A neat, large field with lots of space for all the details that you can provide. Yes, in general a case of "the more, the better" applies here. Here is a list of things that you should mention in the report:

;Problem: Detailed description of the *exact* problem you see. Please do include some log output, if you have it available.

;Reproducibility: How often does the issue occur? Is it reproducible? If it is, please provide detailed steps to do so.

;Actual Results: What happened after you performed the steps you listed under "Reproducibility"?

;Expected Results: What should have happened?

;Additional Information: Please do list any additional information, like for example the *exact* version of your OS (or the application). This is especially important if you were not able to select the exact version in the '''Reported Version''' drop down field. If you have any log output or patches, please do attach those as files to the report. If the file size would be too big, just compress them.

== Syntax in the Flyspray issue tracker ==

=== Internal reference to other issues ===

To refer to another issue use the syntax FS#N where N is the issue number you want to refer to, i.e. FS#123.
The parser then automatically renders this as a link to the other issue (HTML href attribute), and shows the issue's title in the mouseover info (HTML title attribute).

== Submission Workflow ==

The general workflow for submitting a patch is something like this:

# Clone the appropriate section of the GIT repository - GIT is http://git.openpandora.org/cgi-bin/gitweb.cgi
# Apply changes and have fun
# Document and pass test cases
# Contact the maintainer of the subdomain the patch falls within - by mailing list above, or perhaps by PM in the forums, or email; for example, post first to the mailing list. In a pinch for libpnd submissions talk to skeezix, or notaz regarding kernel changes. But talk to the mailing list first, to keep discussion logged and centralized; if a backup neds to step up, the post history will already be there, right?
# If the maintainer is unavailable, contact the backups as listed above; they will know how to contact the champion, or can make the submission call themselves.
# If the maintainer and backups are not available, contact EvilDragon as release maintainer

== Submission Standards ==

Submission are welcome! Historically the firmware has been built by a very small team, but that [[team]] size limits the number of changes that can be managed and developed simultaneously. If you've the skills and motivation to help, feel free to join the fray!

Patches have a few requirements; failing these requirements will cause your patch to be overlooked!

* '''Clearly documented''' -- what is this patch for?
* '''Clearly tested''' -- a list of test cases and test results -- the onus is on the submitter to test and prove testing; the committers have limited time and many people talking to them
* '''Proper format''' -- unix line ending, not dos line endings :)

== 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.

== Updating Super Zaxxon ==

=== Updating graphics drivers ===

[http://pandoralive.info/?p=2303 guided tour de blog by eki]

== Community Codec Package - for Pandora OS, Release 2010-05 ==

Installation of non-free codecs is highly discouraged. Consider instead free counterparts like opus, ogg vorbis and Flac for audio. webM, ogg theora for video or equivalent.

Due to licensing issues, licensed codecs like MP3 or MPEG-Video can not be distributed freely. They are optionally available in the Codec Package.
The package will install Gnome-MPlayer as well as a lot of audio / video-plugins and enables NTFS-support.
To install it, simply download the .PND-Package and place it into either the /pandora/menu or /pandora/desktop - Folder on your SD-Card.
Simply start it and follow the on-screen instructions. You can remove the .PND-Package from the card once it has been installed.

; Legal Notice:
Patent and copyright laws operate differently depending on which country you are in. Please obtain legal advice if you are unsure whether a particular patent or restriction applies to a media format you wish to use in your country.

'''[http://openpandora.org/downloads/CodecPack.pnd Click here to download Community Codec Pack]'''

The Codec Package enables NTFS-Support and installs [http://pastebin.com/TyzWBi0X|these packages]

== Older versions of Ångstrom ==

*In case you need them, you can download older firmware relases [http://openpandora.org/firmware/fullflash/ here].

http://openpandora.org/firmware/fullflash/SuperZaxxon160.zip (20-dec-2013)] [http://boards.openpandora.org/topic/15198-superzaxxon-v160-released/ forum thread]

*http://boards.openpandora.org/topic/13854-superzaxxon-v155-released/

'''[http://openpandora.org/firmware/fullflash/SuperZaxxon155.zip Download firmware image of SuperZaxxon 1.55 (2013-07)]'''

*http://boards.openpandora.org/index.php/topic/12490-superzaxxon-v54-final-has-been-released/
*http://boards.openpandora.org/index.php/topic/10374-superzaxxon-v152-released/ 

SuperZaxxon1.50 can be upgraded to 1.52 without reinstallation by downloading and running the [http://repo.openpandora.org/?page=detail&app=szupdater1.openpandora.org Pandora SuperZaxxon updater PND].

=== Zaxxon (Old version) ===

The original Zaxxon firmware has been updated with a number of Hotfixes. Since then, a newer firmware called Super Zaxxon 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.

In general it's possible to apply hotfixes to any lower firmware versions without installing all previous hotfixes.

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.

: [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 version
* [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 OS
* You can download the very first release of the Pandora's Zaxxon OS from [http://notaz.gp2x.de/releases/pandora/pandora-firmware-2010-05-01-Zaxxon.zip here] (2010-05-01)

[[Category:Documentation]]
[[Category:Operating system]]
[[Category:Software]]

Power modes

2014-10-23T05:18:50Z

RygD: /* Is it be able to run from the AC Adaptor alone? */ changed "be able" to "possible"

[[File:Lead_Photo_For_Power_modes0-2920264867079787.jpg|thumbnail|Powerbutton]]

=Power Supply=
==Can it charge from USB?==
Yes, through the mini-AB OTG port. However, whilst the Pandora is in use the charge rate may be so low as to make it impractical for normal purposes. [http://www.gp32x.com/board/index.php?s=&showtopic=45902&view=findpost&p=683572]

==What kind of battery does it have?==

The Pandora has a 4000mAh Lithium Polymer battery.

Batteries are user-replaceable and spares are sold by Pandora retailers.

==How long does the battery last?==
* The actual battery runtime varies based on the the software being run, peripherals in use, and consequently the [[Power modes|power mode]] in which the Pandora operates.
** For instance, using Wifi constantly, or having it constantly polling will reduce the life by a couple hours, compared to disabling the wifi altogether.
* Starting with the OS [http://boards.openpandora.org/index.php?/topic/7558-superzaxxon-beta-2-released/ SuperZaxxon, Beta 2, using kernel 3.2.1], the Pandora has:
** a total standby of averagely 180 hours,
** an active runtime of 10 to 30 hours (screen on & WiFi on, PND app(s) which utilize more/less CPU)
** up to 75 hours (idle system, screen & WiFi off).
** Source: [http://boards.openpandora.org/index.php?/topic/7196-32-kernel-issue-tracking-thread/page__st__200#entry138048 Study by user porg]

==What about the power cable?==
The Pandora ships with a switching power supply with a standard cord socket which should function with 110V and 240V AC power. These are either localised, or shipped with an appropriate adaptor.

A PSP power supply will work fine with the Pandora [http://forum.openpandora.org/viewtopic.php?f=17&t=41&st=0&sk=t&sd=a].

==Is it possible to run from the AC Adaptor alone?==
Originally, it was thought not, due to the design of the OMAP chipset appearing to require a battery to be connected. [http://www.gp32x.com/board/index.php?s=&showtopic=41548&view=findpost&p=600811] However, it has now been confirmed that the Pandora DOES now work without a battery installed, although some features (like backlight) may have to be turned off via software to enable this[http://www.gp32x.com/board/index.php?/topic/51654-notaz-and-his-pandora/page__view__findpost__p__806714]. The hardware tweak or tweaks have been performed as part of Pandora development, and are not something that the end user will have to worry about/perform[http://www.gp32x.com/board/index.php?/topic/51654-notaz-and-his-pandora/page__view__findpost__p__806734][http://www.gp32x.com/board/index.php?/topic/51654-notaz-and-his-pandora/page__view__findpost__p__806808].

Information from Mweston [http://www.gp32x.com/board/index.php?/topic/53635-so-are-the-batteries-tested-at-all/page__view__findpost__p__858065]
When no battery is found on AC adapter insertion, the unit goes into constant voltage mode which provides a constant 4.0V on the battery net. It doesn't like it if you put a battery in at this point because the TI chip doesn't appear to be designed to jump back to normal mode without a power cycle. It could do weird things like dump ridiculous amounts of current into the battery without software control. I liked the idea of letting customers power without a battery so we left this feature in but be aware of this restriction:

IF YOU POWERED THE SYSTEM WITHOUT A BATTERY, SHUT IT OFF BEFORE STICKING THE BATTERY BACK IN. (not an angry sentence, just making it clear.) :)

When the battery is inserted first, the system will power up using the normal mode. When the AC adapter is plugged in after this, it will power the system and charge the battery up to the limits set in software. Currently, Notaz and I have chosen 1A on the AC adapter and 600mA from the USB input. It can be changed by sending commands to the chip to alter these set numbers but that is a software lesson better learned from someone else. With the LCD off (lid closed perhaps) idling on the desktop, something like 750mA will go to the battery for a 6 hour charge time or so. With the system doing stuff and demanding more power, less current will go to the battery and it will charge slower. 1A was also chosen to consider thermal dissipation because the regulator of the TI chip is linear and wastes energy dropping the voltage from the 5V down to just above the cell voltage. You may notice the system feels warmer when the battery is more discharged than when it is full which is normal.

I haven't had much luck hot swapping batteries while the system is live but I think it worked for ED once. For me, as soon as I pull the battery, the system resets. The power management chip seems to rely on the status of the thermistor in the battery and it if disappears, it can trigger events. Maybe there are software work arounds but I don't know.

==Does the Pandora have 'sleep' or 'hibernate' modes?==
Pandora supports suspend-to-RAM (sleep) but not suspend-to-disk (hibernate)[http://boards.openpandora.org/topic/16732-hibernation-on-the-pandora]. Entering these [[Power modes|power saving modes]] will be controlled by software and can be configured to happen when you press the power switch, close the lid, or only on demand.

[[Image:Battery.jpg|thumb|The Pandora's battery]]

==Power Modes==

Without switching the device entirely off, it may be placed into low power mode or regular power mode; simply pressing the power button will toggle modes. Note that as of [[hotfix3]], opening the lid in low power mode has no effect.

===Normal Mode===
This is the normal operating mode, [[display]] on, [[WiFi]] and [[Bluetooth]] on if requested. CPU speed can be selected by the user, and has a small impact on battery life. Screen brightness will also have a significant effect on battery life. The CPU should automatically self-regulate to the current task, and 10-20 hours battery life is possible depending on usage. This is mostly independent of the set CPU speed for any given task. At any time, the battery gauge will show the remaining battery life ''if the usage remains the same as over the past some seconds''.
See [http://boards.openpandora.org/index.php?/topic/10738-pandora-power-consumption-breakdown/] for a detailed breakdown of power consumption.

===Lid Closed===
The only change with the lid closed is to turn off the LCD backlight and the display itself. This improves battery life, allowing music playback and streaming to continue. As of Hotfix2, the screen remains on if the device is powered up with the lid closed. It is also possible to set xfce to blank the screen after a period of inactivity, which helps with battery.

===Low Power===
Low power mode is toggled by a short press of the power switch to the right. The screen is off, the [[radios]] are disabled, the CPU max speed is set to 14 MHz. The device is still silently on, allowing for alarms to go off or it to be turned on again instantly. The power LED will be dimmed, and may appear to be off if you are outside in the sunshine.

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 days or longer.

Since the Pandora has to be powered whilst it is charging, low power mode is best for fastest charging, and will even allow a full charge to be achieved from USB. It is also the best way to use the Pandora as a USB charger for other devices.

Opening the screen whilst in low power mode has no effect (screen stays off, clocks stay low), and you will need to use the power switch to resume.

At the moment, there is no clear advantage in slowing the clocks (other than being an effective pause button when playing MP3). The only saving is through disabling the radios. This is likely to be improved in due course since there are features in the omap processor for power saving which are being added to the linux kernel.

===Power Off===
Select Logout then Shutdown from the window manager to power off. If a charger is connected, the device will re-boot immediately. It is possible to get into a state where you believe it is powered off, but in fact it is using power at the normal screen off rate - so after 12 hours, 50% of your battery is gone. The Power green LED ought to be a tell-tale. It is possible that some bugs exist in this area, but nothing has been clearly identified[http://www.gp32x.com/board/index.php?/topic/54652-solved-pandora-lost-charge-overnight/]

A common problem seems to be that if you switch off ''before'' unplugging, your Pandora will re-boot even though it is now left unplugged. This problem is compounded by the low battery shutdown script being called repeatedly (and actually preventing shutdown).

To do a '''hard-reset''' of the Pandora (in case of software crashes), press and hold the Pandora key and flick the power button to the right.

To do a '''hard-shutdown''' of the Pandora, press and hold the Pandora key ''with right shoulder button held'' and flick the power button to the right, and then select shutdown from the menu.[http://www.gp32x.com/board/index.php?/topic/59233-hf5-not-shutting-down-or-rebooting/page__view__findpost__p__946375]

==Events==
The events which control power can be customised [http://www.gp32x.com/board/index.php?/topic/54544-forcing-shutdown-at-10-battery-life/page__view__findpost__p__878418]. Lid switch, Power Switch, battery threshold and Window Manager shutdown commands. Note that the battery manager in xfce will also take action when the battery is low, by default forcing a shutdown at 5% (so you may observe a full boot process, the window manager appears, then immediately shuts down)

==Charging==
[[image:Power_uk.png|thumb|alt=UK charger and adapter|UK charger and adapter]]
It is possible to charge from the mains charger (use the supplied one or a ''GENUINE'' PSP adaptor only) or USB cable. While a charger is connected, remaining battery level is displayed, but the time displays 00:00. If charging from USB, it is possible that the battery will still discharge slowly, since the Pandora takes more current (in normal mode) than the USB can supply. Mains charge is configured to draw 1000mA, USB charge is more like 600mA.

It is not possible to charge the Pandora without turning it on - connecting the mains charger or the USB cable will turn it on automatically. The normal charging circuits rely on the CPU for configuration. In practice, this has minimal impact on usage, except that after charging,
you might wish to unplug the charger and explicitly turn off if you don't intend to use the Pandora soon. 

Full discharge charging: The pandora will shutdown in case of low battery power. However there is a protection circuit in the battery itself which will cut off the power output of the battery. The battery and the pandora seems to be dead in this condition, but it's not. If you plug in the power

you'll see nothing happen - but the battery will be recharged very slowly until the battery is above it's cutoff level. This could take up to 30 minutes. Then the pandora will startup and the normal CPU controlled faster charging will continue.
[http://boards.openpandora.org/index.php?/topic/8426-battery-completely-dead/#entry150209]


If your Pandora's battery is at less than 1% (actually configurable in XFCE), then you may have problems in using USB to charge the Pandora. Currently, USB is not recognised by the XFCE battery monitor so it will shutdown with no warning. As a workaround, you can put your Pandora into low power mode as soon as the flashing mouse icon (XFCE startup) appears. This should significantly delay loading the battery monitor widget, and even if the charge hasn't passed 1% by the time it checks, on the next try you should be there.

==Operating Point==
The ''OPP'' is a TI term which reflects the fact that low clock speeds can be achieved with lower supply voltage than the higher clock speeds. Increasing OPP will reduce the lifetime of the device significantly (from 10 years to 5 years of continuous use.) OPP3 is the default as shipped by OpenPandora.

Since at least SuperZaxxon 1.52, the system has shipped with a utility to modify the maximum OPP. It is part of the CPU-Settings app (found in your Settings menu). Select the option 'Set the max OPP level', select 'Change Setting' and read the following warning. Agreeing to it will allow you to set the maximum OPP in the range 3-5.

As of Hotfix4, it is possible to set a maximum OPP in the range 1-5 (for example, to 5):
<source lang="bash">echo 5 | sudo tee -a /proc/pandora/cpu_opp_max</source>

This will then increase OPP to suit the requested CPU max, as pre-determined by a table built in to the kernel. These thresholds use OPP1 for below 125 MHz, and OPP5 for above 720 MHz . It is possible to set the limiter and maybe run at 500 MHz in OPP2 (depending on your specific chip). See [http://boards.openpandora.org/index.php?/topic/22-using-hotfix4-how-high-can-you-clock/ this forum thread] for actual results.

{{warning
|Using anything above OPP3 WILL shorten the lifetime of your Pandora, although it should still outlive the 1 year warranty. Using anything above OPP5 and 1Ghz will void your warranty (see [[Overclocking#Warranty_information|here]])
}}

==Times==
* This data originates from different studies performed under different OS versions and use cases.
* Please add the source and a short note about the conditions you used, and if necessary more detailed ones to the Talk page. You can use [http://repo.openpandora.org/?page=detail&app=sysinfo.wb Pandora System Info] to monitor power consumption.
{| class="wikitable"
!Mode
!Time
!Details, Source
|-
! Active applications/games
| 8-18 hours
| SZ 1.52
|-
! Low load, low backlight brightness
| 20-25 hours
| SZ 1.52
|-
! Drain the battery as fast as possible
| 4 hours
| SZ 1.52, backlight at max brightness, constant wifi activity (big download), CPU stress test running at OPP5 and overclocking above 900 MHz, copying huge files from one SD card to the other, USB host and bluetooth activated (but nothing connected)
|-
! MP3 play, screen off
| 43 hours
| MP3 playback in [http://repo.openpandora.org/?page=detail&app=audacious Audacious] in [http://boards.openpandora.org/index.php?/topic/7196-32-kernel-issue-tracking-thread/page__st__200#entry138048 OS SuperZaxxon, Beta 2, Kernel 3.2.1]
|
|-
! Low Power Mode
|30-75 hours
| [http://boards.openpandora.org/index.php?/topic/7196-32-kernel-issue-tracking-thread/page__st__200#entry138048 OS SuperZaxxon, Beta 2, Kernel 3.2.1]
|-
! Power off
|5% charge loss per week
| although there are reports of much faster drain?[http://boards.openpandora.org/index.php?/topic/24-battery-drain/]
|-
! Standby Mode (no longer applicable?)
| 160-200 hours
| [http://boards.openpandora.org/index.php?/topic/7196-32-kernel-issue-tracking-thread/page__st__200#entry138048 OS SuperZaxxon, Beta 2, Kernel 3.2.1]
|-
! Mains charge, lid closed
| 4 hours
| SuperZaxxon 1.52
|-
! USB Charge, operating
| 20 hours
| inactive, screen+wifi on, may charge or discharge depending on load
|-
! USB Charge, low power
|20 hours
|estimate
|}

==Battery Calibration==
* Fully charge to 100%, turn off the Pandora and leave it for 5 hours.
* A full charge is when, while charging,"cat /sys/class/power_supply/bq27500-0/voltage_now" reads around 4200000 and "cat /sys/class/power_supply/bq27500-0/current_now" reads around 800000. If the meter reads 100%, make sure to check these two files to ensure it's actually FULL. Realistically a charge current below 100000 is close enough.
* Then fully discharge (make sure that "cat /sys/class/power_supply/bq27500-0/voltage_now" returns about 300000), turn it off again for 5 hours.
* That's the process for recalibrating the fuel gauge.

==Battery Care==
* You can charge your battery to full charge, the charging circuits will then reduce the current to avoid overheating
* If you won't use the battery for more than a week, it is best to leave it at about 40% charged (as opposed to full)
* Don't worry about running it down too low, there are protection circuits to avoid a '''damagingly low discharge'''.
**Avoid leaving the battery completely discharged though. When the power runs out, the system will be unable to shutdown cleanly, and might corrupt your files or the system.
* No harm will come if you only partially recharge it. If you've only got 10 free minutes to charge before leaving, go ahead. You'll put an hour of usage back into the battery, and you can always charge it more later.
* For best accuracy, the battery meter relies on watching the battery discharge over most of it's range (down to say 10%).
**This will only affect the 'time to run' indication
* If you're not going to be using your battery for a very long time, the extremely best thing you can do for it is to discharge to 40%, seal it in an airtight bag, and put it in the fridge. Even years later, you pull it out, and it will be almost as good as when you put it in.

== My Pandora does not start, even with the mains adapter plugged in ==

When a battery is inserted, the power goes into the battery, charges it and the battery powers the Pandora.
When no battery is inserted, the power goes through the charging circuit directly into the Pandora.

What this means is, if the battery is really empty, the Pandora won't power on when connected to AC until the battery reaches a certain voltage level. Let it charge the battery (it could take 10 or more minutes before it starts to charge) or remove the battery and plug in the mains adaptor, it then should start.

{{warning|If you powered the system without a battery, shut it off before sticking the battery back in!}}

== Controlling LEDs and backlight ==
[[LEDs_and_backlight]]

== Data provided by battery and power driver ==
Information from the battery and power supply in the pandora when it is booted. It lists readout data that is provided so that you for example can write your own applet showing current power status or include some power information in your application.

Power information is available via sysfs. This is the dmesg information about the battery:
bq27x00-battery 3-0055: support ver. 1.1.0 enabled

==Fuel Gauge/ Battery Monitoring==
''/sys/class/power_supply/bq27500-0'' reports how long the battery will run for.

Here is a list of the provided information and how to interpret the values:

{|class="wikitable"
!node
!meaning
!interpretation
|-
|capacity
|remaining capacity in %
|100=full, 0=empty
|-
|current_now
|discharging/loading rate
|µA; negative: discharging; positive: loading
|-
|present
|is a battery inserted?
|1=yes; 0=no
|-
|status
|Discharging/Charging
|
|-
|temp
|monitoring IC temperature
|decidegree celsius, value of 250 = 25.0°C
|-
|time_to_empty_avg
|battery time left based on drain on some average; not used in XFCE applet
|seconds; only relevant/existing when discharging!
|-
|time_to_empty_now
|time left based on current drain; used in the XFCE applet
|seconds; only relevant/existing when discharging!
|-
|time_to_full_now
|time left for charging with the current usage; not used in XFCE applet
|seconds; only relevant/existing when charging!
|-
|type
|should always read "Battery" since it is a battery...
|
|-
|uevent
|empty
|
|-
|voltage_now
|current voltage left
|µV
|-
|}

==Power Management IC==
''/sys/class/power_supply/twl4030_bci_battery/'' Manages charging, from the mains charger or from USB.
* ''online''
** 0 = No charger
** 2 = Mains charger
** 3 = USB charge

The mains charger takes precedence if USB and mains charger are plugged in. Pandora seems not to take power from both inputs for charging.
Charging by USB only works with a powered system. If the system is off or the battery is empty, it is not possible to boot the system only by USB power (only tested on one Pandora, please recheck).

Please do keep in mind that all time values are plain estimates and can be "jumpy" depending on current system load, display brightness, WiFi/Bluetooth activity and things like the phase of the moon.

== Charging ==
/sys/class/power_supply/twl4030_*/*. Enable/disable charging through those files. The charger chip has trouble operating in automatic mode (overcharges the battery), so pndevmapperd uses enable/disable to prevent that.
=== config ===
/etc/pandora/conf/eventmap

[[Category:Power supply]]
[[Category:Drivers]]