Confirmed users
3,816
edits
Auto-tools/Projects/Pandaboard Setup: Difference between revisions
Auto-tools/Projects/Pandaboard Setup (view source)
Revision as of 21:55, 23 February 2012
, 23 February 2012no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
Bringing up a panda board is a bit different than a Tegra machine. With the pandas we will be building our own Android OS and we will be only doing that once in a while (when a new version is released). This page contains the information on how to build that image and flash a first image to a panda as well as how to re-use that image to flash additional pandas (w/o going through the build process). | Bringing up a panda board is a bit different than a Tegra machine. With the pandas we will be building our own Android OS and we will be only doing that once in a while (when a new version is released). This page contains the information on how to build that image and flash a first image to a panda as well as how to re-use that image to flash additional pandas (w/o going through the build process). | ||
= Building the Android OS for the Pandaboard = | == Building the Android OS for the Pandaboard == | ||
<ol> | <ol> | ||
<li>Initialize your [http://source.android.com/source/initializing.html build environment].</li> | <li>Initialize your [http://source.android.com/source/initializing.html build environment].</li> | ||
| Line 18: | Line 18: | ||
It takes about 30-40 minutes to build on a reasonably fast machine (i7, 8Gb RAM). Currently this will produce a build of androidOS that will change its MAC address on each boot if configured with DHCP. This may be something we change by either applying a kernel patch, or by ensuring pandas always use static IPs. So the above instructions may be modified to accommodate that patch once we figure that out. | It takes about 30-40 minutes to build on a reasonably fast machine (i7, 8Gb RAM). Currently this will produce a build of androidOS that will change its MAC address on each boot if configured with DHCP. This may be something we change by either applying a kernel patch, or by ensuring pandas always use static IPs. So the above instructions may be modified to accommodate that patch once we figure that out. | ||
= Making an OS Image For Distribution = | == Making an OS Image For Distribution == | ||
Once you have a built, working androidOS on your pandaboard you will want to re-distribute it. Follow these steps (and note they may change in the future). | Once you have a built, working androidOS on your pandaboard you will want to re-distribute it. Follow these steps (and note they may change in the future). | ||
| Line 33: | Line 33: | ||
</ol> | </ol> | ||
= Flashing More SDCards = | == Flashing More SDCards == | ||
Once you have a "golden master" image you can use it to stamp out sdcards easily. | Once you have a "golden master" image you can use it to stamp out sdcards easily. | ||
<ol> | <ol> | ||
| Line 43: | Line 43: | ||
</ul> | </ul> | ||
</ol> | </ol> | ||
== Flashing Cards Remotely Without Removing From Panda == | |||
It should be possible to use the fastboot mechanism on the device to flash a replacement OS onto the board remotely. However, we haven't yet had time to work out those steps yet. We will update this section when we do. | |||
== Changing Panda Board Resolution == | |||
We may need to modify bootloader arguments to the kernel to change the pandaboard resolution. TBD: Update these steps | |||
== Changing Panda Board to Not Reset MAC address on every boot == | |||
TBD: Figure this out. | |||
Workaround: use static IPs for the time being. | |||