ReferencePlatforms/Imaging/Nokia N810: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
=N810 Imaging=
==Step 1: Reset Hardware==
We use N810s to do on-device testing of our maemo4 builds of our mobile browser.  In order to deal with maintaining 80 of these devices we have developed an imaging solution.  Our initial attempt was to create a custom firmware image but file corruption became an issue.  We eventually figured out how to boot these devices from MiniSD cards.  We have special tools for creating and maintaining the filesystems on these cards.
'''NOTE: You should be in the RF Shielded room with the door *CLOSED* to ensure machines connect to correct network'''


Our process has the following logical blocks:
For each session:
*Firmware installation and configuration (RE)
*Ensure USB A end of Nokia MicroUSB cable is in computer
*Moving filesystem to SD card (RE)
*Remove batteries and backplates from all devices to be imaged
*Creating image on imaging computer (RE)
<pre>
*Resetting hardware (IT)
cd ~/n810-imaging
*Imaging cards (IT)
sudo ./moz-prep.sh
*Powering on devices (IT)
#Follow onscreen prompts
#once all devices are prepped press CTRL+C to quit moz-prep.sh
</pre>


All RE actions are documented at [[ReferencePlatforms/Test/Maemo]]. If the imaging machine needs to be set up again, the instructions for this action are located at [[ReferencePlatforms/mobile-imaging-linux]]
==Step 2: Image multiple cards==
<pre>
#Detach all MicroSD card readers from computer
#Insert MicroSD cards to be imaged into MicroSD card readers
#Plug in MicroSD card readers with MicroSD cards into computer
#then run
cd ~/n810-imaging
sudo ./bulk-image.sh
#This will take approx 5-7 minutes per card; computer will beep when all cards are imaged.
# JHFORD will paste sample output here
#Remove all MicroSD card readers
#Remove MicroSD cards from MicroSD card readers
#Final output will tell you how many cards were successful,
#this for your information and is not critical to the imaging process
</pre>


The remainder of this document is to give instruction on the IT imaging actions
==Step 3: Verify card and power on device==
<pre>
#Run and follow on screen instructions
cd ~/n810-imaging
sudo ./bulk-verify.sh
</pre>


=Resetting hardware=
==Step 4: Boot device==
The purpose of this step is to zero out the root mtd device as well as reflashing the linux kernel and bootloader. We want to make sure that any possible corruption in these critical subsystems is repaired
*This step assumes that the MicroSD card has been inserted into the correct device
*Press the power button on the top of the device '''then''' plug the charger into the device (NOTE: order is important).
*Verify the device comes turns on successfully with the blue geometry-themed desktop.
*Verify that the grey Wifi logo in top right of screen turns to solid white
** may take 5 minutes


==Instructions==
==Troubleshooting Tips==
We have a program [http://hg.mozilla.org/build/tools/file/tip/buildfarm/mobile/n810-imaging/moz-prep.sh moz-prep.sh] that automates this process.  To launch this program, run:
IGNORE BELOW HERE UNLESS YOU ARE *REALLY* CURIOUS
$ cd ~/n810-imaging
$ sudo ./moz-prep.sh
There will be lots of extraneous output that is useful in debugging.  There should be a line saying
Suitable USB device not found, waiting
as the last line of output.  This is a sign that you are ready to plug in the next N810 to prep.


You will follow the same process for the entirety of the program executionThe suggested process is:
===N810 Imaging===
*remove the battery and backplate for all devices to be imaged
We use N810s to do on-device testing of our maemo4 builds of our mobile browserIn order to deal with maintaining 80 of these devices we have developed an imaging solution.  Our initial attempt was to create a custom firmware image but file corruption became an issue.  We eventually figured out how to boot these devices from MiniSD cards. We have special tools for creating and maintaining the filesystems on these cards.
*launch moz-prep.sh as outlined above
 
*plug microusb cable into computer if not all ready there
===Resetting hardware===
*for each device to image:
The purpose of this step is to zero out the root mtd device as well as reflashing the linux kernel and bootloader. We want to make sure that any possible corruption in these critical subsystems is repaired
**plug microusb cable into device
**replace battery and backplate
**plug in charger
***if the power doesn't turn on automatically, press power button
***There should be a blue USB logo in the top right of the screen, a progress bar on the bottom of the screen and a large 'NOKIA' logo in the center of the screen
**Wait until you see something like:
  UNPLUG DEVICE
Bus 008 Device 003: ID 0421:0105 Nokia Mobile Phones Nokia Firmware Upgrade Mode
**Unplug usb cable
**Once you see 'Suitable USB device not found, waiting' again, you should plug in the next device
*once all devices are prepped press CTRL+C to quit moz-prep.sh


==Potential issues==
===Potential issues===
If you see
If you see
  ERROR! Lost USB Connection while flashing RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin.  Dead battery?
  ERROR! Lost USB Connection while flashing RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin.  Dead battery?
this is a sign that moz-prep encountered an error.  This is a sign that for some reason, the nokia flashing program lost connection to the device.  This is often caused by trying to flash with a dead battery.  We mitigate this by flashing with the charger connected.  This has also been caused by issues with the linux kernel on the imaging host.  If you encounter this error on multiple devices using different batteries reboot the imaging machine.  If you still have issues, someone has broken the imaging machine.
this is a sign that moz-prep encountered an error.  This is a sign that for some reason, the nokia flashing program lost connection to the device.  This is often caused by trying to flash with a dead battery.  We mitigate this by flashing with the charger connected.  This has also been caused by issues with the linux kernel on the imaging host.  If you encounter this error on multiple devices using different batteries reboot the imaging machine.  If you still have issues, someone has broken the imaging machine.

Latest revision as of 21:39, 20 May 2010

Step 1: Reset Hardware

NOTE: You should be in the RF Shielded room with the door *CLOSED* to ensure machines connect to correct network

For each session:

  • Ensure USB A end of Nokia MicroUSB cable is in computer
  • Remove batteries and backplates from all devices to be imaged
cd ~/n810-imaging
sudo ./moz-prep.sh 
#Follow onscreen prompts
#once all devices are prepped press CTRL+C to quit moz-prep.sh

Step 2: Image multiple cards

#Detach all MicroSD card readers from computer 
#Insert MicroSD cards to be imaged into MicroSD card readers
#Plug in MicroSD card readers with MicroSD cards into computer
#then run
cd ~/n810-imaging
sudo ./bulk-image.sh
#This will take approx 5-7 minutes per card; computer will beep when all cards are imaged.
# JHFORD will paste sample output here
#Remove all MicroSD card readers
#Remove MicroSD cards from MicroSD card readers
#Final output will tell you how many cards were successful, 
#this for your information and is not critical to the imaging process

Step 3: Verify card and power on device

#Run and follow on screen instructions
cd ~/n810-imaging
sudo ./bulk-verify.sh

Step 4: Boot device

  • This step assumes that the MicroSD card has been inserted into the correct device
  • Press the power button on the top of the device then plug the charger into the device (NOTE: order is important).
  • Verify the device comes turns on successfully with the blue geometry-themed desktop.
  • Verify that the grey Wifi logo in top right of screen turns to solid white
    • may take 5 minutes

Troubleshooting Tips

IGNORE BELOW HERE UNLESS YOU ARE *REALLY* CURIOUS

N810 Imaging

We use N810s to do on-device testing of our maemo4 builds of our mobile browser. In order to deal with maintaining 80 of these devices we have developed an imaging solution. Our initial attempt was to create a custom firmware image but file corruption became an issue. We eventually figured out how to boot these devices from MiniSD cards. We have special tools for creating and maintaining the filesystems on these cards.

Resetting hardware

The purpose of this step is to zero out the root mtd device as well as reflashing the linux kernel and bootloader. We want to make sure that any possible corruption in these critical subsystems is repaired

Potential issues

If you see

ERROR! Lost USB Connection while flashing RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin.  Dead battery?

this is a sign that moz-prep encountered an error. This is a sign that for some reason, the nokia flashing program lost connection to the device. This is often caused by trying to flash with a dead battery. We mitigate this by flashing with the charger connected. This has also been caused by issues with the linux kernel on the imaging host. If you encounter this error on multiple devices using different batteries reboot the imaging machine. If you still have issues, someone has broken the imaging machine.