http://openmoko.org/api.php?action=feedcontributions&user=Muthusuba&feedformat=atomOpenmoko - User contributions [en]2024-03-28T18:37:27ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/Android_debug_bridgeAndroid debug bridge2010-02-19T11:59:43Z<p>Muthusuba: </p>
<hr />
<div>{{Languages|Android debug bridge}}<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
[[Image:android.png]]<br />
<br />
= ADB : Android debug bridge =<br />
To assist in debugging and to gain shell access to the phone with Android, you can use<br />
[http://people.openmoko.org/sean_mcneil/adb adb]<br />
<br />
== Enabling Debug mode ==<br />
Due to security issues with ADB, the shell has been disabled by default in AoF. You can enable ADB again by navigating to Settings -> Application -> Development -> USB Debugging. <br />
See [http://code.google.com/p/android-on-freerunner/wiki/AndroidDebugBridge AndroidDebugBridge] for updated information<br />
<br />
== Connecting ==<br />
<br />
You should be able to connect to the phone as long as you start it up with the USB connected to your host. I don't think it will work if you plug it in after starting. Of course, you need to setup [[USB_Networking]] (<tt>ifconfig usb0</tt> ...) on your host before connecting.<br />
<br />
Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.<br />
<br />
If Adb cannot find any device:<br />
Make sure you can ping the device. Make sure the date and timesettings are valid. Kill the background running adb-server by "adb kill-server" and start your first adb instance (which starts the background process) with "ADBHOST=192.168.0.202 ./adb devices". After that, you can run adb without ADBHOST-Variable.<br />
<br />
<br />
Some helpful commands are:<br />
<br />
./adb logcat - like a tail -f of the android log<br />
./adb logcat -b radio - same as above for the radio logs<br />
./adb shell - bring up a command shell to the phone<br />
./adb kill-server - kill the background server on the host<br />
./adb install app.apk - install app.apk on the phone<br />
<br />
== Fixing startup problems ==<br />
Startup problems (Beta2): adb shell to the device and delete /data/data/com.android.providers.settings/databases/settings.db<br />
<br />
= See also =<br />
* [[Android|Main Android page on this wiki]]<br />
* [[Debug Board]]<br />
<br />
[[Category:Android]]</div>Muthusubahttp://openmoko.org/wiki/Flashing_the_Neo_FreeRunnerFlashing the Neo FreeRunner2009-07-29T14:35:53Z<p>Muthusuba: </p>
<hr />
<div>{{Languages|Flashing_the_Neo_FreeRunner}}<br />
Openmoko regularly releases updated versions of the Openmoko root filesystem, the [[kernel]], and the [[Bootloader]] (either [[Uboot]] or [[Qi]]) as binary images. These may be programmed into the [[NAND_Flash|Flash memory (NAND)]] of Neo FreeRunner. For that, you can use the USB cable and another computer which will run an Openmoko-provided tool to flash the Neo FreeRunner "through" USB.<br />
<br />
== 3 software components and 2 kinds of storage ==<br />
<br />
Inside the FreeRunner 3 software components are working:<br />
* '''bootloader''': a small program that runs first and starts everything else when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from [[NOR_Flash|NOR]] or NAND is booted).<br />
* '''kernel''': the central component in the Linux operating system.<br />
* '''root filesystem''': contains all the files that make up the commands and applications that you can run.<br />
All software components in the FreeRunner are bundled together into binary images. <br />
<br />
The FreeRunner has two kinds of internal program storage: NOR flash and NAND flash. On a desktop computer when you want to replace the operating system (OS), you would boot it from a CD-ROM drive, then copy OS files from the CD to the internal hard drive. The FreeRunner does not have a CD-ROM drive and files must typically be re-written/flashed directly into internal storage (NAND flash). Alternatively, it is possible to boot from a microSD where all the files have been loaded onto.<br />
<br />
NOR flash is small and stores only a special boot program used when you need to re-write the contents of the NAND flash. Usually it is not necessary to re-write the NOR flash. Instructions to do so is here: [[Flashing NOR]].<br />
<br />
NAND flash acts more like a hard drive. It is divided into 3 partitions for the bootloader, kernel, and root filesystem. Being on different partitions, each component can be flashed separately. For example if you are trying to install a modified kernel, you only have to follow the steps to flash the kernel image.<br />
<br />
'''Before you start: Erasing the root filesystem or flashing the bootloader are radical measures. Take the time to ponder the necessity. Sometimes problems can be fixed by only updating the kernel.'''<br />
<br />
== Alternative : running from microSD card ==<br />
<br />
You may install this distribution on the microSD card, in order to [[Booting from SD | boot from microSD card]]. That allows you to keep another distribution installed in NAND (for instance to test 2008.08 while still having 2007.2 for default boot).<br />
<br />
== Software you need ==<br />
<br />
=== #1 Tools for flashing: DFU-util and NeoTool ===<br />
<br />
''Command-line''. DFU-util, the tool to flash the FreeRunner has to be installed on you laptop or desktop machine. It is available for Linux, MacOS X, and Windows (see links below). DFU-util allows you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking. For more details, see the separate [[dfu-util]] page.<br />
<br />
''GUI''. Instead of the command-line-based DFU-util, you can use NeoTool, a graphical tool for flashing the FreeRunner: see the [[NeoTool]] page.<br />
<br />
'''Linux:''' http://downloads.openmoko.org/distro/releases/Om2008.9/dfu-util<br />
<br />
Make sure it is executable by setting the permissions with this command: chmod a+x dfu-util<br />
<br />
'''Linux 64-bit:''' You need 64-bit version of dfu-util, which usually can be found in your distribution repository.<br />
If your destribution does not provide 64-bit dfu-util, or it consistently fails with a "-62" error, you have two ways to go:<br />
# Seek for 32-bit machine and do flashing form it.<br />
# Use 32-bit chroot (on amd64 debian). Worked for me --[[User:Bubak|Bubak]] 16:54, 4 September 2008 (UTC).<br />
# Just try the 32-bit dfu-util. Worked fine on my x86_64 Fedora 10 --[[User:Pcfe|pcfe]] 2009-01-16.<br />
#* I can confirm this (Gentoo multilib x86_64) --[[User:Unlotto|Unlotto]] 14:15, 4 February 2009 (UTC)<br />
#* I can confirm this (OpenSuSE 11.0 x86_64) --[[User:muthusuba|muthusuba]] 29 July 2009<br />
<br />
'''MacOS X:''' [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]<br />
<br />
'''Windows:''' http://projects.openmoko.org/frs/?group_id=166&release_id=162<br />
<br />
See additional driver installation instructions for Windows at [[Dfu-util-windows]]<br />
<br />
'''Virtual machines''' While there has been some limited success reported using dfu-util from within a Virtual Machine (such as VMware), in general it is not possible to use dfu-util in this fashion. You must use dfu-util on an operating system that has direct access to the physical USB device hardware.<br />
<br />
=== #2 Image files to flash into FreeRunner memory ===<br />
<br />
There are separate image files for all 3 software components and depending on what you want to install, you pick the respective image file. In most cases you will need to install a Kernel (uImage) and a Root Filesystem (rootfs). In rare cases, when there is a bug you need fixed, you will also install a new bootloader.<br />
<br />
Please read [[Distributions]] for choosing the distribution which fits your needs, and then see [[Download]] for downloading.<br />
<br />
== Boot the FreeRunner from NOR Flash ==<br />
<br />
[[Image:menu15.jpg|thumb|Booting from NOR Flash]]<br />
<br />
# Read the other sections of this page first, because you will have 30 seconds to enter the flashing commands, come back here when ready.<br />
# Make sure your FreeRunner is off.<br />
# Do not connect the USB cable from the PC to your Neo FreeRunner yet (disconnect it).<br />
# Boot your Neo FreeRunner into the NOR uBoot menu for flashing.<br />
## Press and hold AUX button<br />
## Press the Power button until the boot menu comes up<br />
## This menu is labelled '''*** BOOT MENU (NOR) ***'''<br />
## See also [[Booting the Neo FreeRunner]]<br />
# Stay in NOR uBoot menu, do not select or enter any item in menu. Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with dfu-util.<br />
# The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something.<br />
# Connect your Neo to the GNU/Linux or Windows host via a USB cable.<br />
# Now you can enter the dfu-util commands on your PC as described below.<br />
# If the Neo FreeRunner turns off before you press start flashing ('''screen goes black'''), go back to step 2. If you start flashing in time, the phone will not turn off meanwhile.<br />
<br />
<!-- The following, upto dfu-util -l is taken from the thread "Re: FreeRunner (GTK2007.2) has suddenly become unbootable" on the Support list. --><br />
<br />
Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (on Windows, you need a DFU class driver, or you can use the LibUSB-Win32 driver described on the [[Dfu-util-windows]] page). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.<br />
<br />
After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:<br />
<br />
<pre>dfu-util -l</pre><br />
<br />
If you get error messages from the dfu-util command then try again. Often it works on the second try.<br />
<br />
dfu-util uses the DeviceFirmwareUpgrade protocol, and may list more than one device. If so, try unplugging the other device (e.g. a USB mouse) or using the -d switch to tell dfu-util which device it should talk to, as described at the relevant bug report [http://docs.openmoko.org/trac/ticket/2039].<br />
<br />
Also, please remember to execute the dfu-util command with sufficient privileges (ie. root) -- you will need complete control over the usb bus.<br />
<br />
== Do a backup ==<br />
<br />
If you have a working image that you're happy with but want to try something different, you should probably do a [[Backup]].<br />
<br />
== Using dfu-util ==<br />
<br />
dfu-util can be used to read flash memory, write memory, and get information from the device.<br />
<br />
This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :<br />
<br />
dfu-util -a ''<altsetting>'' -R -D ''<file_name>''<br />
<br />
where:<br><br />
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number<br><br />
-R : Issue USB Reset signalling once we're finished<br><br />
-D ''file_name'' : Write firmware from ''file_name'' into device<br />
<br />
On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.<br />
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"<br />
<br />
On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.<br />
<br />
More detailed manual for dfu-util is available here : [[Dfu-util]]<br />
<br />
GUI frontend for dfu-util (and more): [[NeoTool]]<br />
<br />
== Flashing the Kernel ==<br />
<br />
Note: The phone needs to be in the U-boot bootup menu for this to work.<br />
Get there by holding down the aux button while powering up the device.<br />
<br />
The command format is <br />
<br />
dfu-util -a kernel -R -D ''/path/to/uImage''<br />
<br />
When flashing succeeds the following will be shown:<br />
<br />
status(0) = No error condition is present<br />
Done!<br />
<br />
Flashing may fail with an error -110. This indicates that the kernel is too big for the default kernel partition. uboot can be used to change the size of the default partitions on the device. It may also mean that you are trying to put the wrong thing in the kernel space.<br />
<br />
== Flashing the Root Filesystem ==<br />
<br />
The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz, bz2, .zip, tar, tar.gz or .tgz extension) you have to uncompress it first.<br />
<br />
The command format is<br />
<br />
<pre><br />
dfu-util -a rootfs -R -D rootfs_filename.jffs2<br />
</pre><br />
| U-Boot<br />
where ''rootfs_filename.jffs2'' is the name of the file containing the root file system.<br />
<br />
The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.<br />
<br />
When flashing succeeds the following will be shown:<br />
<br />
<pre><br />
status(0) = No error condition is present<br />
Done!<br />
</pre><br />
<br />
== Flashing the boot loader to the NAND==<br />
<br />
{{Note|In most cases you don't need to flash your bootloader. Flash it only if you want to update for a specific feature or due to a specific problem.}}<br />
<br />
The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.<br />
<br />
The command format is <br />
<br />
dfu-util -a u-boot -R -D ''uboot.bin''<br />
<br />
where ''uboot.bin'' is the name of the boot loader binary image file.<br />
<br />
''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|boot from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.<br />
<br />
=== Optional: Verifying boot-loader version ===<br />
<br />
<!-- The following should probably be moved to [[Bootloader_versions]], IMHO --><br />
<br />
<!-- Taken from posts by Mikael Berthe <mikael.berthe@lilotux.net> and Torfinn Ingolfsen <tingox@gmail.com> to Support list, subject: Re: Upgrading u-boot needed ? --><br />
(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:<br />
root@om-gta02:~# grep Bootloader /dev/mtdblock1<br />
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb<br />
<br />
You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:<br />
root@om-gta02:~# grep Bootloader /dev/mtdblock0<br />
Neo1973 Bootloader U-Boot 1.3.2-moko12<br />
<br />
<!-- ENDS ... subject: Re: Upgrading u-boot needed ? --><br />
<br />
== Reboot the FreeRunner from NAND ==<br />
<br />
You should now be able to boot into the new images.<br />
<br />
Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')<br />
<br />
The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).<br />
<br />
== A command line script to simplify dfu-util ==<br />
<br />
DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]<br />
<br />
== Alternative: using nandwrite ==<br />
<br />
This approach involves writing the '''rootfs''' into nand directly on the phone from a system already running on it, not necessarily via usb from a computer.<br />
<br />
If you have a system running from a different partition that you intend to flash (for example sd card), you can use nandwrite to do the work, which is much faster (it takes about 30s to write a 59MB jffs2 image).<br />
<br />
Make sure you have nandwrite installed (on gentoo, it's in sys-fs/mtd-utils package)<br />
<br />
Also make sure that the host system has received correct partition list, for example for my stock Neo Freerunner partition list:<br />
<br />
<pre><br />
#cat /proc/mtd<br />
dev: size erasesize name<br />
mtd0: 00200000 00010000 "physmap-flash.0"<br />
mtd1: 00040000 00020000 "u-boot"<br />
mtd2: 00040000 00020000 "u-boot_env"<br />
mtd3: 00800000 00020000 "kernel"<br />
mtd4: 000a0000 00020000 "splash"<br />
mtd5: 00040000 00020000 "factory"<br />
mtd6: 0f6a0000 00020000 "rootfs"<br />
</pre><br />
<br />
In this case, we're looking for 'rootfs' which according to above is mtd6. If you have it somewhere else, substitute mtd6 with whatever you have in the remainder of this section.<br />
<br />
You can test your nand for bad blocks by issuing '''nandtest /dev/mtd6''' '''(this is a data destructive test !)'''<br />
<br />
First, put your .jffs2 file somewhere the phone system can read it<br />
<br />
Second, write the desired image into the nand this way:<br />
<pre><br />
flash_eraseall /dev/mtd6<br />
nandwrite -p /dev/mtd6 /path/to/image.jffs2<br />
</pre><br />
<br />
* The -m flag can be used to tell nandwrite to mark blocks it detects bad as bad, so if nandwrite is bugged, your entire partition will be marked as bad. See http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks if this happened to you.<br />
<br />
You're all done !<br />
<br />
== Troubleshooting ==<br />
<br />
Okay, so you just reflashed. The splash screen pops up, but uBoot fail to load the kernel, and return to boot menu. WTF?<br />
<br />
* It is likely that the wrong bits went to the wrong place. Try reflashing just the kernel, double checking that you select the uImage.bin kernel file, not the u-boot.bin bootloader file.<br />
* Try redownloading and reflashing the kernel, checking file integrity with the MD5 hash sums.<br />
<br />
==See also==<br />
*[http://www.denx.de/wiki/U-Boot/WebHome U-Boot home page]<br />
<br />
[[Category:Flashing Openmoko| ]]</div>Muthusuba