View source for Devirginator/it
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Templates used on this page:
Return to Devirginator/it.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Templates used on this page:
Return to Devirginator/it.
Il devirginator un è un programma utilizzato in combinazione con dfu-util, OpenOCD e Debug Board per reporogrammare alle impostazioni di fabbrica il telefono from scratch.
Il codice sorgente di devirginator è disponibile qui http://svn.openmoko.org/trunk/src/host/devirginator/
Per iniziare,
% cp config.example config
e fai le modifiche necessarie. In particulare, devi configurare SNAPSHOT. Quindi
% make
Questo richiede Netpbm e transfig. Infine assicurati che openocd sia attivo, accendi il dispositivo, diventa root, ed esegui
# ./devirginate
Il dispositivo deve essere connesso con:
Inoltre, se una serial console è connessa al dispositivo, la progressione dell'installazione può essere monitorata.
Sono bnecessari i seguenti programmi:
Per fara il build di dfu-util, esegui:
cd $OMDIR/openmoko/trunk/src/host/dfu-util ./autogen.sh ./configure make
OpenOCD SVN revision 130 con libftdi 0.8 funziona. Altre combinazioni possono anche funzionarec. E' richiesto il seguente patch:
http://svn.openmoko.org/developers/werner/openocd-wait-patiently.patch
Per el istruzioni per il build, vedi http://svn.openmoko.org/developers/werner/notes/openocd
Se stai usando la build di OpenOCD fatta dalla OpenMoko distribution (SVN revision 1180 o successiva), il patch è già applicato.
Oltre a tutto ciò, "devirginate" necessita di telnet.
"setup.sh" può essere eseguito da un'altra macchian che ha in share la stessa gerarchia del file system. Necessita di Netpbm, transfig, wget, e Perl.
Innazitutto devirginator necessita di essere configurato. Questo include
Per il momento il setup deve essere fatto nella directory contente tutti i files riferiti a devirginator. I files generati durante il setup sono posizionati nella directory tmp/. I files in tmp/ sono inoltre usati durante l'uso di devirginator.
Per iniziare, copia config.example su "config" e applica le modifiche necessarie. Quasi tutte le configurazioni necessarie sono di defaults, ma una cosa che potresti voler fare è configurare SNAPSHOT con il date code dello the snapshot che desideri.
Poi esegui ./setup.sh o semplicemente make .
setup.sh ora scaricherà ogni file perduto ed eseguirà le varie conversioni. Se apapre qualche errore durante questo processo, ad esempio a causa della mancanza di strumenti o di un errore di configurazione, setup.sh si fermerà con un errore. Potrai quindi correggere l'errore e riprovare. I files già scaricati in tmp/ verranno saltati quando riprovi (setup.sh lo farà lo stessose i files avranno subito dei cambiamenti).
setup.sh inoltre controlla se gli esguibili sono disponibili durante l'uso di devirgination e segnalerà se manca qualcosa. In generale, si può eseguire setup.sh su una macchina diversa che "devirginate", in questo caso questi avvisi saranno ignorati.
The following files contain scripts and other "static" configuration information that is used in the devirgination process. In general, it is only necessary to edit these files when changing functionality of the setup process.
Each of these files is converted in some way by setup.sh. Below, we indicate the name of the respective resulting file after the arrow.
Commands to execute by OpenOCD in phase 0. To perform variable expansion, each line of this file is processed by the shell with eval "echo $line". Due to this, shell meta-characters should be avoided.
If changing any addresses in openocd.in, you also need to update u-boot.in.
Commands to execute in u-boot during stage 0. This file is converted to an image understood by u-boot, and then executed from memory with u-boot's "autoscr" command.
Environment settings for the regular u-boot environment. Note that the changes in this file are made on top of the interim environment produced in stage 0. In particular, the "mtdparts" variable is retained from that stage.
Long lines can be split in environment.in by simply indenting the continuation. Note that the newline and the indentation are replaced with one space. E.g.,
foo=some thing
would yield foo=some thing
The stage 0 splash screen, a smiling face on a green background.
This is a copy of the OpenMoko logo, which then gets converted to a gzip-ed raw framebuffer image.
The first few messages should look like this:
Open On-Chip Debugger > script /home/moko/om/trunk/src/host/devirginator/tmp/script.ocd reset halt wait_halt waiting for target halted... Target 0 halted target halted in ARM state due to debug request, current mode: Supervisor cpsr: 0x400000d3 pc: 0x00000000 [...]
The "pc: 0x00000000" is important. If the number is different, e.g., something like "pc: 0xffffffed", the device is probably not turned on. In this case, you can try to restart, or, if openocd is stuck,
The setup process is divided into three stages (plus a special zero stage, see below). Each stage leaves the device in a stable state. An installation run can include all or only some stages. Each stage requires successful completion of all previous ones.
Note that you most likely require privileges for some of the USB operations "devirginate" performs. Therefore, do all this as "root".
To perform all stages, run
# ./devirginate
from the trunk/src/host/devirginator/ directory.
To run only individual stages, specify the stage numbers, each prefixed by "-", e.g.,
# ./devirginate -1
If the NAND bad block table is invalid, it can be erased at the beginning of stage 1. We call this "stage 0".
In general, this is not a desirable option, because if the last NAND blocks are defective, this information will be lost, and unreliable operation may result. By default, stage 0 is not performed.
Immediately after starting, the screen lights up, showing random junk. This is an indication that the setup process has started. Note that the screen content may change ("decay") during all this. This is normal.
After 10-30 seconds, the screen will go dark. This indicates that we now a have u-boot running on the device.
About 60-90 seconds later, the screen will light up again and show a smiling face on a green background. This indicates that the first stage has completed. The smiling face will appear each time you activate the device.
The device now contains:
What is still missing:
To begin phase 2, activate the device. The stage 1 smiley will show.
Phase 2 can take several minutes. Progress of the download procedure is indicated by hash signs (#) printed on the terminal where "devirginate" runs.
At the end of phase 2, the device resets, displays a partial OpenMoko splash screen, then resets again, displays the correct splash screen and finally boots Linux.
TBD.