MozillaWiki

ReferencePlatforms/Test/Tegra250-Android: Difference between revisions

Page Discussion

ReferencePlatforms/Test/Tegra250-Android (view source)

Revision as of 20:20, 7 October 2011

55 bytes added ,  7 October 2011
→‎Install SUT
 
(28 intermediate revisions by 2 users not shown)
Line 10: Line 10:


If you don't already have a properly formatted SD card, you need to format one.
If you don't already have a properly formatted SD card, you need to format one.
It may also be best practice to re-format the SD card when reimaging a tegra.


* Insert an SD4/8GB SD card into the SD card reader on the right side of the netbook.
* Insert an SD4/8GB SD card into the SD card reader on the right side of the netbook.
Line 16: Line 18:
** if it's mounted, "Unmount Volume"
** if it's mounted, "Unmount Volume"
** Format Volume (FAT).
** Format Volume (FAT).
* When that finishes, physically remove the SD card from the netbook and insert it in the tegra.
'''Do not "safely remove" the drive'''; this will eject the virtual SD drive and you'll have to reboot to get it back.


== Prepare the Tegra ==
== Prepare the Tegra ==
Line 23: Line 29:
** VGA cable to monitor
** VGA cable to monitor
* Make sure the ACOK switch is set in the NORM position.
* Make sure the ACOK switch is set in the NORM position.
[[File:Tegra250_batt.jpg]]
[[File:Tegra250_battnorm.jpg]]


* Insert the formatted SD card.
* Do not connect power yet; the board will power on automatically if the ACOK switch is set correctly.
* Do not connect power yet; the board will power on automatically if the ACOK switch is set correctly.


* The Tegra should look like this:
* The Tegra should look like this:


TODO picture
[[File:Tegra250_plugged_in.jpg]]


== Put the Tegra into flashing mode ==
== Put the Tegra into flashing mode ==


If the Tegra's power buttons are on the side facing you, the power button is on the left.
If the Tegra's power buttons are on the side facing you, the power button is on the left, the reset button is on the right, and the firmware reset button is in the middle.


You need to do the following steps within a few seconds of booting. This will happen immediately if the ACOK switch is set to NORM. If you need to reset, hit the reset button:
You need to do the following steps within a few seconds of booting. The tegra will boot automatically when power is applied if the ACOK switch is set to NORM.


[[File:Tegra250_flashing3.jpg]]
Insert power.


Immediately after booting, push and hold the firmware reset button (middle) for 2 seconds:
Immediately after booting, push and hold the firmware reset button (middle) for 2 seconds:
Line 53: Line 58:


Then let go.  The screen should be dark.
Then let go.  The screen should be dark.
If you need to restart, hit the reset button (far right) and try again.
(Reset button to start over: [[File:Tegra250_flashing1.jpg]] )


== Flash the Tegra with Android 2.2 (Froyo) ==
== Flash the Tegra with Android 2.2 (Froyo) ==


On the netbook, you should still have your android_image bash prompt up.
On the netbook, open up terminal and run the follow commands;
 
cd ~/android-tegra/tegra_froyo_20101105
./nvflash_lcd.sh


If you get "USB device not foundPress enter to continue:" you need to put the Tegra in flashing mode.
# cd ~/android-tegra/tegra_froyo_20110207
# ./nvflash_crt.sh


Otherwise you should see a lot of creating partition/formatting partition/sending file messages with "done!" and "successfully".
If you get "USB device not foundPress enter to continue:" you need to put the Tegra in flashing mode (see above).


If you see no errors and you get "Press enter to continue:", your Tegra should already be booting into Android 2.2.
Otherwise you should see a lot of creating partition/formatting partition/sending file messages with "done!" and "successfully".  The monitor should also show activity.


Press enter and wait for the Tegra to boot.
If you see no errors, your Tegra should already be booting into Android 2.2.


== Install SUT ==
== Install SUT ==
Line 73: Line 80:
In your android_install bash prompt:
In your android_install bash prompt:


  ./initialize.sh SERVER_IP
  ./initialize_tegra.sh TEGRA_NAME


SERVER_IPs to use:
This waits for the tegra to boot, then sleeps 60 before proceeding, so you can do this at any point after the imaging finishes.


{| border="1px" class="sortable" style="border: 1px solid black"
(Currently initialize_tegra.sh knows about tegra-001 through tegra-094. If the tegra is outside of those bounds, there may need to be changes made to initialize_tegra.sh.)
|-
! Server name
! Server use
! Tegra list
! SERVER_IP
|-
| bm-foopy
| staging
| tegra-001 - tegra-010
| 10.250.48.9
|-
| foopy01
| production 01
| tegra-011 - tegra-030
| 10.250.48.151
|-
| foopy02
| production 02
| tegra-031 - tegra-050
| 10.250.48.152
|-
| foopy03
| production 03
| tegra-051 - tegra-070
| 10.250.48.153
|-
| foopy04
| production 04
| tegra-071 - tegra-090
| 10.250.48.154
|}


There's nothing harmful about trying this multiple times if needed. (The installs will fail out on subsequent attempts if they were successful previously and run without a -r option.)
There's nothing harmful about trying this multiple times if needed.


The 'am' command launched a preference window on your Tegra!  With your Tegra keyboard or mouse:
The 'am' command launched a preference window on your Tegra!  With your Tegra keyboard or mouse:
* Development -> Unknown Sources
** In keystrokes (even works when headless):
*** return


* Development -> Stay Awake
* Development -> Stay Awake
** In keystrokes (even works when headless):
*** down arrow x4
*** return
*** down arrow
*** return
*** esc esc


Click "Stay Awake" '''once'''.  This is a toggle, where the toggle setting is off the screen.  If you click twice, you just turned it off again.
* Now unplug the tegra, starting with the power.


Headless, without a mouse, you can:
* Move the tegra to its designated location, and plug in network and power.


** down arrow x4
* Go on to the next tegra.
** return
** down arrow
** return
** esc esc


* Hit 'esc' on your Tegra USB keyboard twice.
== Add buildbot slave + clientproxy on bm-foopy ==
 
* If you clicked "Stay Awake" properly, your Tegra shouldn't shut off immediately.
 
* Once you've verified it doesn't shut off immediately (give it a few minutes, ideally), you can reset it via button or <tt>adb reboot</tt> .


== Add buildbot slave + clientproxy on bm-foopy ==
(Only needed when first adding a new tegra.  For RelEng; not IT's responsibility.)


We're going to overload bm-foopy soon, so we'll need a bunch of 'em.  The following should be true, though:
We're going to overload bm-foopy soon, so we'll need a bunch of 'em.  The following should be true, though:
Line 146: Line 124:
Make sure the buildbot.tac looks good.  '''Don't start the slave manually!'''
Make sure the buildbot.tac looks good.  '''Don't start the slave manually!'''


Edit <tt>/builds/tegras.txt</tt> to add the new tegra:
TODO insert new clientproxy info


tegra-015 IP.ADD.RE.SS
= Windows 7 Imaging steps =


clientproxy.py should automatically detect the new Tegra and start the buildslave, assuming it's up and running SUT.
'''Note: Aki is no longer going to update the below information; it may go stale.'''


 
The latest&greatest MoCo RelEng imaging documentation is on Fedora 14.
= Windows 7 Imaging steps =


== Prepare the netbook ==
== Prepare the netbook ==
Digipengi
3

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/284373...356288"