User:Talpa

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(My notes)
m (matchbox development)
 
(10 intermediate revisions by one user not shown)
Line 1: Line 1:
 
=== My notes ===
 
=== My notes ===
 +
 +
==== Debian Notes ====
 +
All hail Debian...
 +
 +
* git repository for device configuration [http://git.debian.org/?p=pkg-fso/openmoko-files.git;a=summary http://git.debian.org/?p=pkg-fso/openmoko-files.git;a=summary]
 +
* [http://wiki.debian.org/Teams/DebianFSO FreeSmartphone.Org packaging team page]
  
 
==== Private index of useful pages ====
 
==== Private index of useful pages ====
# [[http://wiki.openmoko.org/wiki/Application_Development_Crash_Course Application_Development_Crash_Course]]
+
# [[Application_Development_Crash_Course Application_Development_Crash_Course]]
# [[http://wiki.openmoko.org/wiki/MokoMakefile MokoMakefile]]
+
# [[MokoMakefile]]
 +
# [[Picocom]]
 +
# [[User:Klaszlo#Checking_GSM_firmware_version]]
 +
 
 +
==== matchbox development ====
 +
apt-get install xserver-xephyr
 +
 
 +
  Xephyr :1 -screen 480x640x16
 +
 
 +
trayer --top --height 64 --heighttype pixels
 +
matchbox-window-manager &
  
 
==== Interesting paths ====
 
==== Interesting paths ====
 
# moko/openembedded contains the bb files for 2007.2
 
# moko/openembedded contains the bb files for 2007.2
 
# moko/openmoko/trunk/src/target/OM-2007.2/ contains the src files for the OpenMoko 2007.2 apps
 
# moko/openmoko/trunk/src/target/OM-2007.2/ contains the src files for the OpenMoko 2007.2 apps
 +
 +
==== OpenEmbedded/bitbake ====
 +
# [[http://www.openembedded.org/user-manual&dpage=usage_tasks bitbake task list]]
  
 
==== Backing up data stored on the factory Neo ====
 
==== Backing up data stored on the factory Neo ====
 
Things that needs to be backed up.
 
Things that needs to be backed up.
  
# GPS software ('''no need''' to back it up see: [[http://lists.openmoko.org/pipermail/community/2007-July/008466.html  GPS driver (gllin) licensing question]])
 
 
# Factory-programmed NAND bad block information?
 
# Factory-programmed NAND bad block information?
  
Line 32: Line 50:
 
Can the method described in [[NAND_bad_blocks#BBT_creation | BBT Creation]] does it (sort of) recreate the Factory-programmed NAND bad block information<br>
 
Can the method described in [[NAND_bad_blocks#BBT_creation | BBT Creation]] does it (sort of) recreate the Factory-programmed NAND bad block information<br>
 
'''NOTE: this method probably requires a JTAG cable'''
 
'''NOTE: this method probably requires a JTAG cable'''
 +
 +
==== U-boot ====
 +
 +
setenv bodt_menu_timeout 3600
 +
 +
./neocon -t 30 /dev/ttyACM0
 +
 +
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot glamo_mci.sd_max_clk=10000000 glamo_mci.sd_drive=2

Latest revision as of 00:04, 1 August 2010

Contents

[edit] My notes

[edit] Debian Notes

All hail Debian...

[edit] Private index of useful pages

  1. Application_Development_Crash_Course Application_Development_Crash_Course
  2. MokoMakefile
  3. Picocom
  4. User:Klaszlo#Checking_GSM_firmware_version

[edit] matchbox development

apt-get install xserver-xephyr

 Xephyr :1 -screen 480x640x16
trayer --top --height 64 --heighttype pixels
matchbox-window-manager &

[edit] Interesting paths

  1. moko/openembedded contains the bb files for 2007.2
  2. moko/openmoko/trunk/src/target/OM-2007.2/ contains the src files for the OpenMoko 2007.2 apps

[edit] OpenEmbedded/bitbake

  1. [bitbake task list]

[edit] Backing up data stored on the factory Neo

Things that needs to be backed up.

  1. Factory-programmed NAND bad block information?


Initial Backup Describes the backup of the 4 partitions, but does this include the factory bad block table? I think NOT

NAND_bad_blocks contains some information on the bad block information stored in the flash

[edit] Bad block notes

According to NAND_basics each flash page (512 bytes) has 16 bytes of out-of-band (OOB) data. The OOB contains different information but among other things it can mark a page? as bad.

According to Bad Block Table (BBT) there is also a Bad Block Table that contains additional information.
Is this the same as the factory-programmed NAND bad block information discussed in Neo1973_Hardware?

[edit] Recreating the Factory-programmed NAND bad block information

Can the method described in BBT Creation does it (sort of) recreate the Factory-programmed NAND bad block information
NOTE: this method probably requires a JTAG cable

[edit] U-boot

setenv bodt_menu_timeout 3600
./neocon -t 30 /dev/ttyACM0
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot glamo_mci.sd_max_clk=10000000 glamo_mci.sd_drive=2
Personal tools

My notes

Private index of useful pages

  1. [Application_Development_Crash_Course]
  2. [MokoMakefile]

Interesting paths

  1. moko/openembedded contains the bb files for 2007.2
  2. moko/openmoko/trunk/src/target/OM-2007.2/ contains the src files for the OpenMoko 2007.2 apps

Backing up data stored on the factory Neo

Things that needs to be backed up.

  1. GPS software (no need to back it up see: [GPS driver (gllin) licensing question])
  2. Factory-programmed NAND bad block information?


Initial Backup Describes the backup of the 4 partitions, but does this include the factory bad block table? I think NOT

NAND_bad_blocks contains some information on the bad block information stored in the flash

Bad block notes

According to NAND_basics each flash page (512 bytes) has 16 bytes of out-of-band (OOB) data. The OOB contains different information but among other things it can mark a page? as bad.

According to Bad Block Table (BBT) there is also a Bad Block Table that contains additional information.
Is this the same as the factory-programmed NAND bad block information discussed in Neo1973_Hardware?

Recreating the Factory-programmed NAND bad block information

Can the method described in BBT Creation does it (sort of) recreate the Factory-programmed NAND bad block information
NOTE: this method probably requires a JTAG cable