ReferencePlatforms/Imaging/Nokia N810: Difference between revisions

no edit summary
No edit summary
No edit summary
 
Line 42: Line 42:
** may take 5 minutes
** may take 5 minutes


=Troubleshooting Tips=
==Troubleshooting Tips==
IGNORE BELOW HERE UNLESS YOU ARE *REALLY* CURIOUS
IGNORE BELOW HERE UNLESS YOU ARE *REALLY* CURIOUS


=N810 Imaging=
===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.
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=
===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
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==
===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.
Confirmed users
1,377

edits